Subject: [Pana] FW: [[email-masked]: [IANA #82695] RE: Last Call: draft-ietf-pana-pana-15.txt]

From: "Alper Yegin" <[email-masked]>
Date: Fri, 8 Jun 2007 12:28:34 +0300

IANA feedback on PANA base specification...

> IESG:
> 
> The IANA has reviewed the following Internet-Draft
> which is in Last Call: draft-ietf-pana-pana-15.txt,
> and has the following comments/questions with regards
> to the publication of this document:
> 
> IANA HAS QUESTIONS.
> 
> Upon approval of this document, the IANA will take
> the following Actions:
> 
> 
> Action 1 (section 10.1):
> 
> Upon approval of this document, the IANA will make
> the following assignments in the "PORT NUMBERS"
> registry located at
> 
> http://www.iana.org/assignments/port-numbers
> 
> sub-registry "WELL KNOWN PORT NUMBERS"
> 
> Keyword Decimal Description References
> ------- ------- ----------- ----------
> pana [tbd]/udp PANA	 [RFC-pana-pana-15]
> 
> 
> Action 2 (General PANA Registry):
> 
> [ NOTE: The document never explicitly requests a
> registry be created ]
> 
> Upon approval of this document, the IANA will
> create the following registry "PANA Protocol
> Numbers" located at
> 
> http://www.iana.org/assignments/TBD
> 
> This registry contains the following sub-registries..
> 
> 
> Action 3 (section 10.2.1):
> 
> [ NOTE: section 10.2 is confusing. it says "two
> fields" and then lists "the Version, Message Type,
> and Flags fields". Unless my math is wrong, that
> would be three. ]
> 
> Upon approval of this document, the IANA will
> in the following registry "PANA Protocol Numbers"
> located at
> 
> http://www.iana.org/assignments/TBD
> 
> create a new sub-registry "Message Types (version 1)"
> 
> Assignment policy: IETF Consensus
> 
> Initial contents of this sub-registry will be:
> 
> Message Number Description Reference
> (16-bits)
> -------------- ------------- ---------
> 1 Client-Initiation [RFC-pana-pana-15]
> 2 Auth Request/Answer [RFC-pana-pana-15]
> 3 Termination Request/Answer [RFC-pana-pana-15]
> 4 Notification Request/Answer [RFC-pana-pana-15]
> 5-65519 Reserved to IANA [RFC-pana-pana-15]
> 65520-65535 Reserved for Experimental [RFC-pana-pana-15]
> Messages [RFC-pana-pana-15]
> 
> [ NOTE: While this section refers back to sections
> 7.1-7.7, it's unclear what the actual definition of
> this registry should be. This document needs to get
> its IANA considerations fixed to be more clear. Perhaps
> pointing back to section 7? Also, there are multiple
> messages defined for each Message Number code.]
> 
> Action 4 (section 10.2.3):
> 
> Upon approval of this document, the IANA will in
> the following registry "PANA Protocol Numbers"
> located at
> 
> http://www.iana.org/assignments/TBD
> 
> create a new sub-registry "Message Flags (version 1)"
> 
> Assignment policy: Standards Action
> 
> Initial contents of this sub-registry will be:
> 
> Flag Bit Code Description Reference
> -------- ---- --------------------- ---------
> 0 R Request [RFC-pana-pana-15]
> 1 S Start [RFC-pana-pana-15]
> 2 C Complete [RFC-pana-pana-15]
> 3 A re-Authentication [RFC-pana-pana-15]
> 4 P Ping [RFC-pana-pana-15]
> 5-15 Reserved to IANA [RFC-pana-pana-15]
> 
> 
> [ NOTE: this registry did not point back to a
> previous section where these flags are defined.
> A back-pointer to section 6.1 should be added ]
> 
> 
> Action 5 (section 10.3.1):
> 
> Upon approval of this document, the IANA will
> in the following registry "PANA Protocol Numbers"
> located at
> 
> http://www.iana.org/assignments/TBD
> 
> create a new sub-registry "AVP Codes"
> 
> Assignment policy: Designated Expert with
> Specification or Standards Action
> 
> NOTE: IESG must designate an expert.
> 
> Initial contents of this sub-registry will be:
> 
> Code Bit Description Reference
> -------- --------------------- ---------
> 0 Reserved [RFC-pana-pana-15]
> 1 Algorithm [RFC-pana-pana-15]
> 2 AUTH [RFC-pana-pana-15]
> 3 EAP-Payload [RFC-pana-pana-15]
> 4 Key-Id [RFC-pana-pana-15]
> 5 Nonce [RFC-pana-pana-15]
> 6 Result-Code [RFC-pana-pana-15]
> 7 Session-Lifetime [RFC-pana-pana-15]
> 8 Termination-Cause [RFC-pana-pana-15]
> 9 ??? [RFC-pana-pana-15]
> 10 ??? [RFC-pana-pana-15]
> 11-15 Reserved to IANA [RFC-pana-pana-15]
> 
> [ NOTE: Section 10.3.1 specifies codes 1-10,
> but refers back to  sections 8.1-8.8 which only
> define codes 1-8 ]
> 
> 
> Action 6 (section 10.3.2):
> 
> Upon approval of this document, the IANA will
> in the following registry "PANA Protocol Numbers"
> located at
> 
> http://www.iana.org/assignments/TBD
> 
> create a new sub-registry "AVP Flags"
> 
> Assignment policy: Standards Action
> 
> Initial contents of this sub-registry will be:
> 
> Flag Bit Code Description Reference
> -------- ---- --------------------- ---------
> 0 V Vendor [RFC-pana-pana-15]
> 1 M Mandatory [RFC-pana-pana-15]
> 2-15 Reserved to IANA [RFC-pana-pana-15]
> 
> 
> Action 7 (section 10.4.1):
> 
> Upon approval of this document, the IANA will
> in the following registry "PANA Protocol Numbers"
> located at
> 
> http://www.iana.org/assignments/TBD
> 
> create a new sub-registry "Result-Code AVP
> Values (AVP Code 6)"
> 
> Allocation policy: IETF Consensus
> 
> Initial contents of this sub-registry will be:
> 
> Value Description Reference
> 32-bit
> ----- ------------------ ---------
> 0 PANA_SUCCESS [RFC-pana-pana-15]
> 1 PANA_AUTHENTICATION_REJECTED [RFC-pana-pana-15]
> 2 PANA_AUTHORIZATION_REJECTED [RFC-pana-pana-15]
> 3 to Reserved to IANA [RFC-pana-pana-15]
> 2^32
> 
> 
> Action 8 (section 10.4.2):
> 
> Upon approval of this document, the IANA will
> in the following registry "PANA Protocol Numbers"
> located at
> 
> http://www.iana.org/assignments/TBD
> 
> create a new sub-registry "Termination-Cause AVP
> Values (AVP Code 8)"
> 
> Allocation policy: IETF Consensus
> 
> Initial contents of this sub-registry will be:
> 
> Value Description Reference
> (32-bit)
> ----- ------------------ ---------
> 1 LOGOUT [RFC-pana-pana-15]
> 2-3 Reserved to IANA [RFC-pana-pana-15]
> 4 ADMINISTRATIVE [RFC-pana-pana-15]
> 5-7 Reserved to IANA [RFC-pana-pana-15]
> 8 SESSION_TIMEOUT [RFC-pana-pana-15]
> 9 to Reserved to IANA [RFC-pana-pana-15]
> 2^32
> 
> 
> Action 9 (section 10.4):
> 
> [ Question: The document requests First-come,
> First-serve entries into 'registries' for Values
> for the other AVP Codes. Should these registries
> get created now or on-demand? ]
> 
> 
> We understand the above to be the only IANA
> Actions for this document.
> 
> 
> Thank you.
> 
> Yoshiko Chong
> (on behalf of IANA)
> 
> 
> 
> 
> > ------ Forwarded Message
> > From: The IESG <[email-masked]>
> > Reply-To: <[email-masked]>
> > Date: Thu, 24 May 2007 17:15:08 -0400
> > To: IETF-Announce <[email-masked]>
> > Cc: <[email-masked]>
> > Subject: [Iana-rfcs] Last Call: draft-ietf-pana-framework (Protocol
> for
> > Carrying Authentication for Network Access (PANA) Framework) to
> > Informational RFC
> >
> > The IESG has received a request from the Protocol for carrying
> > Authentication for Network Access WG (pana) to consider the
> following
> > documents:
> >
> > - 'Protocol for Carrying Authentication for Network Access (PANA) '
> >    <draft-ietf-pana-pana-15.txt> as a Proposed Standard
> > - 'Protocol for Carrying Authentication for Network Access (PANA)
> >    Framework '
> >    <draft-ietf-pana-framework-08.txt> as an Informational RFC
> >
> > This is a second IETF Last Call for these documents. During the
> previous
> > Last Call, a number of objections were raised on these documents. It
> > has been exactly one year since these objections were raised, and
> > the PANA WG has been busy working to address the community's
> > concerns. The protocol and resulting documentation has been
> > simplified in the process. A high-level summary of changes may be
> > found here:
> >
> > http://panasec.org/docs/listof-changes.txt
> >
> > The IESG plans to make a decision in the next few weeks on these
> > documents, and solicits final comments on this action.  Please send
> > substantive comments to the [email-masked] mailing lists by 2007-06-
> 07.
> > Exceptionally, comments may be sent to [email-masked] instead. In
> either
> > case, please retain the beginning of the Subject line to allow
> automated
> > sorting.
> >
> > The files can be obtained via
> >
> > http://www.ietf.org/internet-drafts/draft-ietf-pana-framework-08.txt
> > http://www.ietf.org/internet-drafts/draft-ietf-pana-pana-15.txt
> >
> > IESG discussion can be tracked via
> >
>
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=1177
> > 6&rfc_flag=0
> >
> >
> > _______________________________________________
> > IETF-Announce mailing list
> > [email-masked]
> > https://www1.ietf.org/mailman/listinfo/ietf-announce
> >
> > _______________________________________________
> > Iana-rfcs mailing list
> > [email-masked]
> > https://rs.icann.org/mailman/listinfo/iana-rfcs
> >
> > ------ End of Forwarded Message
> >
> >
> 
> 

----- End forwarded message -----

_______________________________________________
Pana mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/pana