[66371] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Upcoming change to SOA values in .com and .net zones

daemon@ATHENA.MIT.EDU (Stephen J. Wilcox)
Thu Jan 8 12:23:30 2004

Date: Thu, 8 Jan 2004 17:22:49 +0000 (GMT)
From: "Stephen J. Wilcox" <steve@telecomplete.co.uk>
To: Joe Abley <jabley@isc.org>
Cc: Owen DeLong <owen@delong.com>, <nanog@merit.edu>
In-Reply-To: <3A8C9F7C-41FB-11D8-AB12-00039312C852@isc.org>
Errors-To: owner-nanog-outgoing@merit.edu


> YYYYMMDDnnn exceeds 32 bits for contemporary values of YYYY, so that's 
> not a viable alternative. YYMMDDnnn would work, but has Y2K-ignorant 
> connotations (not that that's particular relevant, post Y2K). Using a 

Hmm bearing in mind how the calculation is done YYMMDDnnnn (or nnn) wouldnt be a
problem..  going from 9912319999 to 0001010000 is considered to be an increase
isnt it? [actually it wraps at 2^31 =~ 4e10]

Steve


home help back first fref pref prev next nref lref last post