[OpenAFS] Retirement of grand.central.org AFSDB records

Tue, 5 Mar 2019 21:56:18 +0000

--_000_75b68aaed7b74a819ba134546632a84acmuedu_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

TL;DR: AFSDB records for grand.central.org and openafs.org will go away at =
the end of March.

Over the next several months, we'll be making a number of changes and impro=
vements to the infrastructure behind grand.central.org and openafs.org. Muc=
h of this work will be mostly or completely transparent, but from time to t=
ime, we'll be announcing changes visible to the community in some way. This=
 message discusses one such change.

The use of DNS SRV records to identify and locate AFS database servers was =
originally defined in RFC5864, published in April, 2010. This has been supp=
orted in OpenAFS since version 1.6.0, released in 2011. So, we feel fairly =
confident that the majority of clients include this functionality. The use =
of AFSDB records for this purpose, originally defined in RFC1183, has now b=
een deprecated for many years. As with many older, obsolete, and uncommon R=
RTYPEs, a number of DNS implementations no longer support publishing AFSDB =
RRs.

In order to support eventual migration of DNS for central.org and openafs.o=
rg off of CMU infrastructure, we intend to remove the AFSDB records for the=
 grand.central.org cell and for openafs.org (which is really the same cell)=
. This change will be made on or around the end of March, 2019. Existing SR=
V records will remain, and no changes are currently planned to the names or=
 IP addresses of the database servers for this cell.

-- Jeff

--_000_75b68aaed7b74a819ba134546632a84acmuedu_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<style type=3D"text/css" style=3D"display:none;"><!-- P {margin-top:0;margi=
n-bottom:0;} --></style>
</head>
<body dir=3D"ltr">
<div id=3D"divtagdefaultwrapper" style=3D"font-size:12pt;color:#000000;font=
-family:Calibri,Helvetica,sans-serif;" dir=3D"ltr">
<p>TL;DR: AFSDB records for grand.central.org and openafs.org will go away =
at the end of March.</p>
<p><br>
</p>
<p>Over the next several months, we'll be making a number of changes and im=
provements to the infrastructure behind grand.central.org and openafs.org. =
Much of this work will be mostly or completely transparent, but from time t=
o time, we'll be announcing changes
 visible to the community in some way. This message discusses one such chan=
ge.</p>
<p><br>
</p>
<p>The use of DNS SRV records to identify and locate AFS database servers w=
as originally defined in RFC5864, published in April, 2010. This has been s=
upported in OpenAFS since version 1.6.0, released in 2011. So, we feel fair=
ly confident that the majority of
 clients include this functionality. The use of AFSDB records for this purp=
ose, originally defined in RFC1183, has now been deprecated for many years.=
 As with many older, obsolete, and uncommon RRTYPEs, a number of DNS implem=
entations no longer support publishing
 AFSDB RRs.</p>
<p><br>
</p>
<p>In order to support eventual migration of DNS for central.org and openaf=
s.org off of CMU infrastructure, we intend to remove the AFSDB records for =
the grand.central.org cell and for openafs.org (which is really the same ce=
ll). This change will be made on
 or around the end of March, 2019. Existing SRV records will remain, and no=
 changes are currently planned to the names or IP addresses of the database=
 servers for this cell.</p>
<p><br>
</p>
<p>-- Jeff</p>
<p></p>
</div>
</body>
</html>

--_000_75b68aaed7b74a819ba134546632a84acmuedu_--