ANCP Protocol draftietfancpprotocol08

1
ANCP Protocol draft-ietf-ancp-protocol-08
2
Changes from -06 to -07

• Replaced the "Multicast Status" message with
  "General Response message, based on Tom Taylor's
  proposal
• http//www.ietf.org/mail-archive/web/ancp/current/
  msg00955.html
• Removed completely the description of the
  multicast use case in section 4.4, already
  included in ancp mcast draft
• Released unused values 0x01 - 0x04 for Tech Type
• Allocated Tech Type 0x01 for PON technology
• Allocated the range (0x1000 - 0x01020) for
  Target Type TLV. Target TVL 0x1000 for a single
  Access- Port
• Allocated TLV 0x106 for Status info
• Updated the IANA section accordingly

3
Versioning

• Added an editor's note for sub-version change
  from 1 to 2 upon publication. Standard ANCP
  version will be 3.2
• In section 2 added some sentences to explain the
  historic aspects of GSMP/ANCP v3.1
  implementations, which are based on early
  versions of the ANCP protocol draft
• In section 5.2 added the explanation of
  version/sub-version negotiation process, based on
  existing GSMP version negotiation mechanism
  described in sections 11.1 and 11.2 of RFC3292
• Added a non-normative Appendix that will contain
  a clarification of what version of the ANCP
  protocol draft specification constitutes version
  3.1

4
Changes from -07 to -08

• Re-inserted the two possible options to select
  the Partition ID
• AN and NAS MAY agree on the partition ID using
  one of the following possible options
• 1 - The partition ID could be configured on the
  AN and learnt by NAS in the adjacency message
  
• 2 - The partition ID could be statically
  configured on the NAS as part of configuring the
  neighbor information.
• Updated Thomas Haags contact information

5
Next steps

• Ready for Last Call?