RE: DNSEXT WGLC: RFC2536bis and RFC2539bis
"Scott Rose" <scottr@nist.gov> Wed, 25 January 2006 12:24 UTC
From: Scott Rose <scottr@nist.gov>
Subject: RE: DNSEXT WGLC: RFC2536bis and RFC2539bis
Date: Wed, 25 Jan 2006 07:24:49 -0500
Lines: 104
References: <6.2.5.6.2.20060124143010.0372a2c8@ogud.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-From: owner-namedroppers@ops.ietf.org Wed Jan 25 16:05:10 2006
Return-path: <owner-namedroppers@ops.ietf.org>
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on psg.com
X-Spam-Level:
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00 autolearn=ham version=3.1.0
To: namedroppers@ops.ietf.org
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
In-Reply-To: <6.2.5.6.2.20060124143010.0372a2c8@ogud.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
Importance: Normal
X-NIST-MailScanner: Found to be clean
X-NIST-MailScanner-From: scottr@nist.gov
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
X-Message-ID:
Message-ID: <20140418072127.2560.45629.ARCHIVE@ietfa.amsl.com>
I read the two drafts, and I think they should be progressed. I found 2 minor typos in the RFC2536bis: 1. In section 3 last paragraph, SIG is used instead of RRSIG 2. In section 5, last paragraph, "[random]" is used as the endnote, I assume it is supposed to be RFC4086 in the references. Scott **************************************** Scott Rose Adv. Network Tech. Div., NIST +1 301-975-8439 https://www-x.antd.nist.gov/dnssec/ **************************************** > -----Original Message----- > From: owner-namedroppers@ops.ietf.org > [mailto:owner-namedroppers@ops.ietf.org]On Behalf Of Ólafur Guðmundsson > /DNSEXT co-chair > Sent: Tuesday, January 24, 2006 2:40 PM > To: Ólafur Guðmundsson /DNSEXT co-chair; namedroppers@ops.ietf.org > Subject: Re: DNSEXT WGLC: RFC2536bis and RFC2539bis > > > Come on can someone please review these simple documents. > > In the last 40 days 2 people have spoken up. > Summary of changes from the RFC's is provided in > http://ops.ietf.org/lists/namedroppers/namedroppers.2005/msg01888.html > > Unless 3 more people say they have read the documents and > agree with them being forwarded. > > An alternative approach is to obsolete DSA RFC2536 and > move DHK 2539 off standards track. > > Please be nice to your chairs and either > read the documents > or tell chairs you support the alternate plans. > > Olafur > > At 19:06 13/12/2005, Ólafur Guðmundsson /DNSEXT wrote: > >In light of the new WG requirement that every document the working > >group advances there must be a set of WG members on record that they > >have reviewed the documents before the WG chairs can advance the > document. > > > >This is a call for 5 members of the WG to read and review each of > >these documents. > > > > thanks > > Olafur > > > >At 23:48 17/10/2005, Ólafur Guðmundsson /DNSEXT wrote: > > > >>This message starts a 2 week Working Group Last call ending on > >>November 1, for the two following documents: > >>http://www.ietf.org/internet-drafts/draft-ietf-dnsext-rfc2536bis -dsa-06.txt >>http://www.ietf.org/internet-drafts/draft-ietf-dnsext-rfc2539bis-dhk-06.tx t >> >>These two documents replace older RFC's to reflect the fact DSA and >>Diffie-Hellman keying information is encoded the same way in KEY and >>DNSKEY RR's (and other DNS RR types). >>The documents contain few minor textual changes from the RFC's they are >>replacing, including references to the DNSSEC-bis documents. >> >>These documents are on standards track and will be recycled at >>proposed standard, to be at the same level as DNSSEC-bis. >> >>The default action is to advance these documents, if you find any >>issues with the documents please raise them now. >> >> Olafur & Olaf >> >>-- >>to unsubscribe send a message to namedroppers-request@ops.ietf.org with >>the word 'unsubscribe' in a single line as the message text body. >>archive: <http://ops.ietf.org/lists/namedroppers/> > > >-- >to unsubscribe send a message to namedroppers-request@ops.ietf.org with >the word 'unsubscribe' in a single line as the message text body. >archive: <http://ops.ietf.org/lists/namedroppers/> > -- to unsubscribe send a message to namedroppers-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: <http://ops.ietf.org/lists/namedroppers/> -- to unsubscribe send a message to namedroppers-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: <http://ops.ietf.org/lists/namedroppers/>
- DNSEXT WGLC: RFC2536bis and RFC2539bis Ólafur Guðmundsson /DNSEXT co-chair
- Re: DNSEXT WGLC: RFC2536bis and RFC2539bis Samuel Weiler
- RE: DNSEXT WGLC: RFC2536bis and RFC2539bis Eastlake III Donald-LDE008
- Re: DNSEXT WGLC: RFC2536bis and RFC2539bis Ólafur Guðmundsson /DNSEXT co-chair
- Re: DNSEXT WGLC: RFC2536bis and RFC2539bis Mark Andrews
- Re: DNSEXT WGLC: RFC2536bis and RFC2539bis Mark Andrews
- RE: DNSEXT WGLC: RFC2536bis and RFC2539bis Eastlake III Donald-LDE008
- Re: DNSEXT WGLC: RFC2536bis and RFC2539bis Ólafur Guðmundsson /DNSEXT co-chair
- RE: DNSEXT WGLC: RFC2536bis and RFC2539bis Scott Rose
- RE: DNSEXT WGLC: RFC2536bis and RFC2539bis Eastlake III Donald-LDE008
- Re: DNSEXT WGLC: RFC2536bis and RFC2539bis Andrew Sullivan