Re: LC: draft-ietf-forces-protocol-10.txt>>comments

Fenggen,

Please open issues on the tracker and CC avri; sometimes when people
are busy they only read emails if addressed directly to them.

cheers,
jamal


On Wed, 2007-13-06 at 02:35 +0800, Wang,Weiming wrote:
>   Hi current version editors,
>  
>  I think Fenggen has raised very important issues. Quite several TLV descriptions 
> in Table 1 in current version 10 is inconsistent with the followed message descriptions 
> in version 9 and version 10 itself. And descriptions of OPER-TLV in teardown, redirect, 
> and heartbeat messages sections are not correct.They are not OPER-TLVs and there is no 
> LFBselect TLV at the top-level of message body.  
>  
>  thanks,
> Weiming
>  
> 
> > ----- Original Message ----- 
> > From: "Jia Fenggen" <[email protected]>
> > To: <[email protected]>
> > Sent: Tuesday, June 12, 2007 7:29 PM
> > Subject: Re: LC: draft-ietf-forces-protocol-10.txt>>comments
> > 
> > 
> > > Here are some comments on the draft-ietf-forces-protocol-10.txt.
> > > 1 Page43,table1,on association teardown message: Does Association Teardown 
> > > message need LFB selectTLV, I can't find any clue in Section 7.5.3?
> > > 2 Page43,table1,on Heartbeat message:Section 7.10 says clearly that 
> > > heartbeat message doesn't need LFB SelectTLV,so the top level TLV for this 
> > > should be none?
> > > 3 Page43,table1,on packet redirect message:Section 7.9 says it doesn't need 
> > > LFBSelectTLV,it only needs REDIRECT TLV,what is the right one?
> > > 4 Page43,table1,on Config message:what is the meaning of ()+,does anywhere 
> > > explain this?
> > > 5 Page46,table2,on GET-RESPONSE TLV:   (RESULT-TLV)* (what is the meaning 
> > > of ()* ?)
> > > 6 Page46,table2 and page50 table 3:here is conflict on Redirect TLV, table 
> > > 2 treats Redirect TLV as a kind of Oper TLV while table 3 not,which is 
> > > right?
> > > 7 suggestion:we should add a tree structure for Packet redirect 
> > > message,also for association setup response message,Association Teardown 
> > > Message,config 
> > > response message and query response message to clarify the format of the 
> > > specified messages.
> > > Yours,Fenggen
> > > >From: Patrick Droz <[email protected]>
> > > >Reply-To: Patrick Droz <[email protected]>
> > > >To: [email protected]
> > > >Subject: LC: draft-ietf-forces-protocol-10.txt
> > > >Date: Tue, 5 Jun 2007 15:02:54 +0200
> > > >
> > > >As you have seen we have version 10 out. I would like to initiate
> > > >LC for the protocol draft starting today June 6th. The LC duration
> > > >is 2 weeks and will end on June 20th. Please raise your final 
> > > >comments
> > > >and issues.
> > > >
> > > >Patrick
> > > >
> > > >
> > > >[email protected] wrote:
> > > >>A New Internet-Draft is available from the on-line Internet-Drafts 
> > > >>directories.
> > > >>This draft is a work item of the Forwarding and Control Element 
> > > >>Separation Working Group of the IETF.
> > > >>
> > > >> Title : ForCES Protocol Specification
> > > >> Author(s) : A. Doria, et al.
> > > >> Filename : draft-ietf-forces-protocol-10.txt
> > > >> Pages : 122
> > > >> Date : 2007-6-4
> > > >>
> > > >>This document specifies the Forwarding and Control Element 
> > > >>Separation
> > > >>    (ForCES) protocol.  ForCES protocol is used for communications
> > > >>    between Control Elements(CEs) and Forwarding Elements (FEs) in 
> > > >>a
> > > >>    ForCES Network Element (ForCES NE).  This specification is 
> > > >>intended
> > > >>    to meet the ForCES protocol requirements defined in RFC3654.  
> > > >>Besides
> > > >>    the ForCES protocol messages, the specification also defines 
> > > >>the
> > > >>    framework, the mechanisms, and the Transport Mapping Layer 
> > > >>(TML)
> > > >>    requirements for ForCES protocol.
> > > >>
> > > >>A URL for this Internet-Draft is:
> > > >>http://www.ietf.org/internet-drafts/draft-ietf-forces-protocol-10.txt
> > > >>
> > > >>To remove yourself from the I-D Announcement list, send a message 
> > > >>to [email protected] with the word unsubscribe in the 
> > > >>body of the message. You can also visit 
> > > >>https://www1.ietf.org/mailman/listinfo/I-D-announce to change your 
> > > >>subscription settings.
> > > >>
> > > >>Internet-Drafts are also available by anonymous FTP. Login with the 
> > > >>username "anonymous" and a password of your e-mail address. After 
> > > >>logging in, type "cd internet-drafts" and then "get 
> > > >>draft-ietf-forces-protocol-10.txt".
> > > >>
> > > >>A list of Internet-Drafts directories can be found in
> > > >>http://www.ietf.org/shadow.html or 
> > > >>ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> > > >>
> > > >>Internet-Drafts can also be obtained by e-mail.
> > > >>
> > > >>Send a message to:
> > > >> [email protected].
> > > >>In the body type:
> > > >> "FILE /internet-drafts/draft-ietf-forces-protocol-10.txt".
> > > >>
> > > >>NOTE: The mail server at ietf.org can return the document in
> > > >> MIME-encoded form by using the "mpack" utility.  To use this
> > > >> feature, insert the command "ENCODING mime" before the "FILE"
> > > >> command.  To decode the response(s), you will need "munpack" or
> > > >> a MIME-compliant mail reader.  Different MIME-compliant mail 
> > > >>readers
> > > >> exhibit different behavior, especially when dealing with
> > > >> "multipart" MIME messages (i.e. documents which have been split
> > > >> up into multiple messages), so check your local documentation on
> > > >> how to manipulate these messages.
> > > >>
> > > >>Below is the data which will enable a MIME compliant mail reader
> > > >>implementation to automatically retrieve the ASCII version of the
> > > >>Internet-Draft.
> > > >>
> > > >>
> > > >>------------------------------------------------------------------------
> > > >>
> > > >>_______________________________________________
> > > >>I-D-Announce mailing list
> > > >>[email protected]
> > > >>https://www1.ietf.org/mailman/listinfo/i-d-announce
> > > >
> > > >--
> > > >   Dr. Patrick Droz                  | [email protected]
> > > >   IBM Zurich Research Laboratory    | 
> > > >http://www.zurich.ibm.com/~dro
> > > >   Saumerstrasse 4                   | Tel. +41-44-724-85-25
> > > >   CH-8803 Rueschlikon/Switzerland   | Fax. +41-44-724-85-78
> > > 
> > > 
> > > ><< smime.p7s >>
> > > 
> > > _________________________________________________________________
> > > 与联机的朋友进行交流，请使用 MSN Messenger:  http://messenger.msn.com/cn