RE: [Ips] ips WG Last Call: iSCSI Implementer's Guide

I have not yet read this draft, which a WG Chair is required
to do before sending the publication request to Lars, so
let's do a quick respin, especially as a normative reference
to RFC 3721 is going to cause "reference to RFC at lower
publication status" concerns/issues.

Thanks,
--David 

> -----Original Message-----
> From: Lars Eggert [mailto:lars.eggert@nokia.com] 
> Sent: Monday, February 12, 2007 3:06 PM
> To: ext Mallikarjun C.
> Cc: ips@ietf.org
> Subject: Re: [Ips] ips WG Last Call: iSCSI Implementer's Guide
> 
> On 2007-2-12, at 11:45, ext Mallikarjun C. wrote:
> > You are right about the reference to 3721.  Sorry about that.  The  
> > Introduction should have said:
> > "The text in this document, however, updates
> >     and supersedes the text in [RFC3720] whenever
> >     there is such a question."
> >
> > Consequently, the normative reference in section 12.1 to [RFC3721]  
> > should move down to the informative references in section 12.2.
> 
> OK
> 
> > On the "Updates" boilerplate..... I was not aware of such a  
> > section.  I ran the draft through the i-d nit tool and it didn't  
> > complain, so I assumed it should be alright.
> 
> The idnits tool can't check this (yet). See http://www.ietf.org/ID- 
> Checklist.html Section 3.
> 
> Also note that the IESG likes to see "Intended status:" 
> fields in IDs  
> these days, because it lets idnits check for DOWNREFs. I'd consider  
> adding one.
> 
> > On the best way to address these tweaks - wait for the IESG review  
> > and then consider the RFC Editor publication process to address  
> > them?  Or would you suggest another revision now?
> 
> Up to the chair and editor to decide. If it's all the same to you, I  
> have a slight preference for a quick respin.
> 
> Lars
> 
> 
> 

_______________________________________________
Ips mailing list
Ips@ietf.org
https://www1.ietf.org/mailman/listinfo/ips