{
  "id": "https://ryan.freumh.org/2024-05-20.html",
  "title": "20 May 2024",
  "link": "https://ryan.freumh.org/2024-05-20.html",
  "updated": "2024-05-20T00:00:00",
  "published": "2024-05-20T00:00:00",
  "summary": "<div>\n        <span>  Previous: <a href=\"2024-05-13.html\">13 May 2024</a>  </span>\n        <span>  Next: <a href=\"2024-05-27.html\">27 May 2024</a>  </span>\n    </div>\n    \n    \n\n        <ul>\n<li>Mon: Met with Anil\n<ul>\n<li>We skimmed the Carbon-aware name resolution paper. Anil said it was\na narrow contribution, we’re making too many points in one paper, and\nthat it needs to be framed in a research style with a hypothesis and\nexperimentation attempting to disprove the hypothesis.</li>\n<li>He liked the mailserver redundancy example (powering up the backup\nwhen the primary goes down), which he likened to self-scaling\napplications managing the power state of machines.</li>\n<li>He said that the carbon-aware load balancing (Patrick’s section)\nseems more general than specific to emissions.</li>\n<li>Anil also said carbon isn’t the best terminology. I agree – we were\nfollowing HotCarbon’s wording.</li>\n<li>We talked about doing a simulation to disprove the hypothesis.</li>\n<li>And how there’s a pareto front of latency/availability vs power\nefficiency.</li>\n<li>As a next step Anil requested a table of protocols and their\nproperties regarding local and global operation, their data model, key\nmanagement, etc, for consideration of how they can be made carbon-aware\n(and spatially aware?).</li>\n</ul></li>\n<li>Tue: Preparing for supervising concepts of PL and supervising\nconcepts of PL.</li>\n<li>Wed: Tarides Opam Nix system dependancy management.</li>\n<li>Thur: Created table of protocols for consideration in carbon-aware\nname resolution and spatial networking.</li>\n<li>Fri: Met with Anil and Patick, and ended up talking about Nix a lot.\nI said I’d send over my configuration as a starting place for Anil to\nre-try NixOS.</li>\n</ul>\n<p><span>I read <a href=\"https://datatracker.ietf.org/doc/rfc2352/\">RFC2352</a> which\ndescibes a scheme for creating domain names based on legal names,\nnamespaced by country. This is similar to the geocivic heirarchy\ndescribed in the spatial name system paper.</span></p>",
  "content": "<div>\n        <span>  Previous: <a href=\"2024-05-13.html\">13 May 2024</a>  </span>\n        <span>  Next: <a href=\"2024-05-27.html\">27 May 2024</a>  </span>\n    </div>\n    \n    \n\n        <ul>\n<li>Mon: Met with Anil\n<ul>\n<li>We skimmed the Carbon-aware name resolution paper. Anil said it was\na narrow contribution, we’re making too many points in one paper, and\nthat it needs to be framed in a research style with a hypothesis and\nexperimentation attempting to disprove the hypothesis.</li>\n<li>He liked the mailserver redundancy example (powering up the backup\nwhen the primary goes down), which he likened to self-scaling\napplications managing the power state of machines.</li>\n<li>He said that the carbon-aware load balancing (Patrick’s section)\nseems more general than specific to emissions.</li>\n<li>Anil also said carbon isn’t the best terminology. I agree – we were\nfollowing HotCarbon’s wording.</li>\n<li>We talked about doing a simulation to disprove the hypothesis.</li>\n<li>And how there’s a pareto front of latency/availability vs power\nefficiency.</li>\n<li>As a next step Anil requested a table of protocols and their\nproperties regarding local and global operation, their data model, key\nmanagement, etc, for consideration of how they can be made carbon-aware\n(and spatially aware?).</li>\n</ul></li>\n<li>Tue: Preparing for supervising concepts of PL and supervising\nconcepts of PL.</li>\n<li>Wed: Tarides Opam Nix system dependancy management.</li>\n<li>Thur: Created table of protocols for consideration in carbon-aware\nname resolution and spatial networking.</li>\n<li>Fri: Met with Anil and Patick, and ended up talking about Nix a lot.\nI said I’d send over my configuration as a starting place for Anil to\nre-try NixOS.</li>\n</ul>\n<p><span>I read <a href=\"https://datatracker.ietf.org/doc/rfc2352/\">RFC2352</a> which\ndescibes a scheme for creating domain names based on legal names,\nnamespaced by country. This is similar to the geocivic heirarchy\ndescribed in the spatial name system paper.</span></p>",
  "content_type": "html",
  "categories": [],
  "source": "https://ryan.freumh.org/atom.xml"
}