headers
Mike Eisler | 7 Jan 2008 18:58
Picon
Favicon

Re: NFSv4.1 I-D working group last call planning

Spencer is out this week.

As an editor, I formally request a WG last call for:

  http://www3.tools.ietf.org/html/draft-ietf-nfsv4-minorversion1-18.txt

http://www3.tools.ietf.org/html/draft-ietf-nfsv4-minorversion1-dot-x-02.txt

The proposed period of time for the Last Call is now through March 7.

Regarding, 

> [...]  The first half
> of the review will be completed around Feb 1st and the second
> half just before the next IETF meeting (roughly March 7th).
> 
> Specifics are forthcoming but the contents of the first half of
> the review will entail the portions of the I-D that are more
> expository in nature or that cover functionality that exists
> in NFSv4.0.  The second half will focus on the Sessions and pNFS
> functionality given that we have a bakeathon scheduled the
> week of Feb 18th.

I've no problem with taking comments on sessions and pNFS before Feb
18,
especially given that these are the key features of NFSv4.1.

_______________________________________________
nfsv4 mailing list
nfsv4 <at> ietf.org
(Continue reading)

Permalink | Reply | 20 comments |
headers
J. Bruce Fields | 7 Jan 2008 19:14

Re: NFSv4.1 I-D working group last call planning

On Mon, Jan 07, 2008 at 09:58:30AM -0800, Mike Eisler wrote:
> Spencer is out this week.
> 
> As an editor, I formally request a WG last call for:
> 
>   http://www3.tools.ietf.org/html/draft-ietf-nfsv4-minorversion1-18.txt
>      
> http://www3.tools.ietf.org/html/draft-ietf-nfsv4-minorversion1-dot-x-02.txt
> 
> The proposed period of time for the Last Call is now through March 7.
> 
> Regarding, 
> 
> > [...]  The first half
> > of the review will be completed around Feb 1st and the second
> > half just before the next IETF meeting (roughly March 7th).
> > 
> > Specifics are forthcoming but the contents of the first half of
> > the review will entail the portions of the I-D that are more
> > expository in nature or that cover functionality that exists
> > in NFSv4.0.  The second half will focus on the Sessions and pNFS
> > functionality given that we have a bakeathon scheduled the
> > week of Feb 18th.
> 
> I've no problem with taking comments on sessions and pNFS before Feb
> 18,
> especially given that these are the key features of NFSv4.1.

Basic questions: what does "Last Call" mean?
(Continue reading)

Permalink | Reply | 19 comments |
headers
Spencer Shepler | 7 Jan 2008 19:39
Picon

NFSv4.1 and XDR I-D last call start (ends on March 7th)


In short, NFSv4 working group last call for NFSv4.1 and XDR I-Ds
is underway and will be completed on March 7th.

----

As I noted in my original note on Dec 13th
http://www1.ietf.org/mail-archive/web/nfsv4/current/msg05209.html

We are using Draft 18 as the "Last Call" draft.  Therefore,
the following drafts are now in working group last call:

"NFS Version 4 Minor Version 1"
http://www.ietf.org/internet-drafts/draft-ietf-nfsv4- 
minorversion1-18.txt

-and-

"NFSv4 Minor Version 1 XDR Description"
http://www.ietf.org/internet-drafts/draft-ietf-nfsv4-minorversion1- 
dot-x-02.txt

IETF "tools" version of these are available at:
http://www3.tools.ietf.org/html/draft-ietf-nfsv4-minorversion1-18
http://www3.tools.ietf.org/html/draft-ietf-nfsv4-minorversion1-dot-x-02

The documents are being reviewed in the entirety and for any and
all comments: from nits, readability, protocol issues, etc.

Comments should be sent to the working group such that everyone
(Continue reading)

Permalink | Reply | 0 comments |
headers
Mike Eisler | 7 Jan 2008 19:43
Picon
Favicon

Re: NFSv4.1 I-D working group last call planning


--- "J. Bruce Fields" <bfields <at> fieldses.org> wrote:

> Basic questions: what does "Last Call" mean?

The last chance for this working group to make comments
on the two NFSv4.1 documents before the documents are
handed to the Area Advisor for review and ultimately
a decision to publish the documents as RFCs. 

> What specifically do you want from people at this point?  (Any
> particular kinds of comments?)

Nits, errors, this won't work, this could be clearer
etc. Essentially if you are happy with the two documents 
being issued as RFCs as is, then say nothing. Otherwise, speak up.

(Remember: RFCs are forever.)

Jason Glasgow, for example, has already spoken.

_______________________________________________
nfsv4 mailing list
nfsv4 <at> ietf.org
https://www1.ietf.org/mailman/listinfo/nfsv4
Permalink | Reply | 18 comments |
headers
J. Bruce Fields | 7 Jan 2008 19:52

Re: NFSv4.1 I-D working group last call planning

On Mon, Jan 07, 2008 at 10:43:05AM -0800, Mike Eisler wrote:
> 
> --- "J. Bruce Fields" <bfields <at> fieldses.org> wrote:
> 
> > Basic questions: what does "Last Call" mean?
> 
> The last chance for this working group to make comments
> on the two NFSv4.1 documents before the documents are
> handed to the Area Advisor for review and ultimately
> a decision to publish the documents as RFCs. 

How are corrections going to be handled?  Will some kind of drafts still
be issued during this period?

> Nits, errors, this won't work, this could be clearer
> etc. Essentially if you are happy with the two documents 
> being issued as RFCs as is, then say nothing. Otherwise, speak up.
> 
> (Remember: RFCs are forever.)

What was the story with 3010 and 3530?  I assume that was the result of
discovering a serious protocol problem after issuing the first rfc, and
not something that's expected?

--b.

_______________________________________________
nfsv4 mailing list
nfsv4 <at> ietf.org
https://www1.ietf.org/mailman/listinfo/nfsv4
(Continue reading)

Permalink | Reply | 2 comments |
headers
Dean Hildebrand | 7 Jan 2008 19:56
Picon

Re: NFSv4.1 I-D working group last call planning


Mike Eisler wrote:
> --- "J. Bruce Fields" <bfields <at> fieldses.org> wrote:
>
>   
>> Basic questions: what does "Last Call" mean?
>>     
>
> The last chance for this working group to make comments
> on the two NFSv4.1 documents before the documents are
> handed to the Area Advisor for review and ultimately
> a decision to publish the documents as RFCs. 
>
>   
>> What specifically do you want from people at this point?  (Any
>> particular kinds of comments?)
>>     
>
> Nits, errors, this won't work, this could be clearer
> etc. Essentially if you are happy with the two documents 
> being issued as RFCs as is, then say nothing. Otherwise, speak up.
>
> (Remember: RFCs are forever.)
>
>   
How does issues found after march 7th due to development issues fit into 
this?  On the Linux side, I'm not sure draft-18 will be fully 
implemented by March 7th.

Also, I remember someone mentioning something about requiring 2
(Continue reading)

Permalink | Reply | 13 comments |
headers
Noveck, Dave | 7 Jan 2008 20:00
Picon

RE: NFSv4.1 I-D working group last call planning

> What was the story with 3010 and 3530?  I assume that was the result
of
> discovering a serious protocol problem after issuing the first rfc, 

Yes.

> and
> not something that's expected?

We hope not.  One of the reasons for the formal review sessions was to
make that as unlikely as we can.  Another way of preventing that sort of
things is careful review during the last-call period.

-----Original Message-----
From: J. Bruce Fields [mailto:bfields <at> fieldses.org] 
Sent: Monday, January 07, 2008 1:53 PM
To: Mike Eisler
Cc: Spencer Shepler; Pawlowski, Brian; nfsv4 <at> ietf.org
Subject: Re: [nfsv4] NFSv4.1 I-D working group last call planning

On Mon, Jan 07, 2008 at 10:43:05AM -0800, Mike Eisler wrote:
> 
> --- "J. Bruce Fields" <bfields <at> fieldses.org> wrote:
> 
> > Basic questions: what does "Last Call" mean?
> 
> The last chance for this working group to make comments
> on the two NFSv4.1 documents before the documents are
> handed to the Area Advisor for review and ultimately
> a decision to publish the documents as RFCs.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Glasgow_Jason | 7 Jan 2008 20:08

RE: NFSv4.1 I-D working group last call planning

Dean,

See ftp://ftp.isi.edu/in-notes/rfc2026.txt 

Section 4 defines the maturity levels.  It would appear that the "2 
inter-operating implementations" requirement refers to moving from a
"Proposed Standard" to a "Draft Standard".

-Jason

-----Original Message-----
From: Dean Hildebrand [mailto:seattleplus <at> gmail.com] 
Sent: Monday, January 07, 2008 1:57 PM
To: email2mre-ietf <at> yahoo.com
Cc: J. Bruce Fields; Spencer Shepler; Brian Pawlowski; nfsv4 <at> ietf.org
Subject: Re: [nfsv4] NFSv4.1 I-D working group last call planning

Mike Eisler wrote:
> --- "J. Bruce Fields" <bfields <at> fieldses.org> wrote:
>
>   
>> Basic questions: what does "Last Call" mean?
>>     
>
> The last chance for this working group to make comments
> on the two NFSv4.1 documents before the documents are
> handed to the Area Advisor for review and ultimately
> a decision to publish the documents as RFCs. 
>
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Spencer Shepler | 7 Jan 2008 20:18
Picon

Re: NFSv4.1 I-D working group last call planning


On Jan 7, 2008, at 12:56 PM, Dean Hildebrand wrote:
>>
> How does issues found after march 7th due to development issues fit  
> into this?  On the Linux side, I'm not sure draft-18 will be fully  
> implemented by March 7th.
>
> Also, I remember someone mentioning something about requiring 2  
> inter-operating implementations before a rfc could be finalized.   
> Is this urban legend or is it referring to something else?

You will find an overview of the IETF standards process here:
http://www.ietf.org/IESG/content/ions/ion-procdocs.html

In response to the "what happens after March 7th"...

What we have started now is the working group last call.
This is the work that the working group goes through to ensure
the quality and content of the I-D before it is submitted
to the IESG for overall IETF review (which may include things
like expert review, an IETF last call and will include review
by IANA and the the IETF editors, etc.).

So this is an iterative process.

Comments received at March 7th may be feed back into the
working group because we  are in another WG last call or
it may be directed at the IESG because the I-Ds are in
last call processing there.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Mike Eisler | 7 Jan 2008 20:30
Picon
Favicon

Re: NFSv4.1 I-D working group last call planning


--- "J. Bruce Fields" <bfields <at> fieldses.org> wrote:

> On Mon, Jan 07, 2008 at 10:43:05AM -0800, Mike Eisler wrote:
> > 
> > --- "J. Bruce Fields" <bfields <at> fieldses.org> wrote:
> > 
> > > Basic questions: what does "Last Call" mean?
> > 
> > The last chance for this working group to make comments
> > on the two NFSv4.1 documents before the documents are
> > handed to the Area Adviser for review and ultimately
> > a decision to publish the documents as RFCs. 
> 
> How are corrections going to be handled?  Will some kind of drafts
> still
> be issued during this period?

Corrections will be checked into the cvs respository, and will
appear in the documents before they become RFCs.
Depending on the number/scope of corrections, new drafts might be
issued between now and the end of WG last call, or just one pair of
drafts will be issued before handing to Area Adviser. I'm hoping for
the best, planning for the worst [no extended holidays for me from now
through the end of April], expecting as with most things in life for
the outcome to fall somewhere between.

_______________________________________________
nfsv4 mailing list
nfsv4 <at> ietf.org
(Continue reading)

Permalink | Reply | 0 comments |

Gmane