================================================================= ANCP WG, Monday, November 7th, 2010, 13:00-15:00, Beijing 15 mins WG Status and Update - Chairs 10 mins - ANCP protocol draft update - draft-ietf-ancp-protocol-12.txt - Tom Taylor 15 mins - ANCP in wireless access - Richard 30 mins - ANCP Scenarios and Use Case for PON - Hongyu Li ================================================================= Chairs: Matthew Bocci @ Wojceich Dec Scribes: Hongyu Li ================================================================= 1. WG Status and Update ¨C Chairs Regarding protocol draft revision 12, editor's view is it's not finished yet, because of many open issues. 2. ANCP protocol draft update - draft-ietf-ancp-protocol-12.txt - Tom Taylor See slides. Missing semantics and normative text, particularly for the topology discovery capability -What MUST/SHOULD/MAY be implemented? -What MUST/SHOULD/MAY appear in messages? Proposal: MUST implement messages as described in message format sections woj: this is key for protocol design, OK to take everything MUST MUST implement all of the TLVs? woj: maybe not all TLVs should be MUST tom: necessary for completeness and avoid malformed messages woj: suggest to have an error code for the case some parameters should appear but actually not manuel: suggest to put all TLVs as MUST for interoperability. AGREED: should say clearly: NAS is ready for all TLVs, but some may appear or not. Port Up Message Contents woj: not all combinations appear, if there is a must, if something is missing, there would be an error reported. tom: Access-Loop-Circuit-ID is a must, others are conditional, meaning if configured, must present. From a NAS' view, they are may, but for AN, they are must. AGREED: Distinguish the view of NAS and AN behaviors and capabilities of the parameters. matthew: many modifications, propose a second LC. Normative Language For "Generally Useful" Constructs no comments from the group Tech Type In port management message AGREED: Send to the email list for discussion. New Topic - Handling of Code Values matthew: what do we do when receiving a result/code woj: this may come from multicast draft, help with request and response expectation. tom provides some example codes and possible actions. chair: send to the list for further discussion. 3. ANCP in wireless access -- Tom Taylor See slides. use case is from China. wifi/wimax/2G/3G networks reuse NAS. propose to use ANCP for these networks. Tom: there is a problem statement draft Q: relation to CAPWAP? A: it's between wireless AN and WTP, while ANCP is between NAS and AN. chair: send to the list for discussion on problem statement. there are quite a lot of areas may use ANCP, prefer to see the problem statement first and decide what to do. Ralph: need to have both ANCP and CAPWAP chairs in the same room to discuss where should this go. nabil: for wifi roaming or for any wireless listed? roaming between different operators? matthew: don't create a tool already available. shall not conflict with 3GPP and the scope should be defined very carefully. 4. ANCP Scenarios and Use Case for PON -- Hongyu Li See slides. Presented scenarios were discussed in BBF and agreed by many operators. The multicast use case in current draft works for both pon and DSL. Authors believe some scenarios not covered in current ancp-pon draft and propose either have a new draft of pon or merge these scenarios in current draft. Nabil: I think many scenarios are already covered in the draft. Francois: there are some gaps between multicast use case in ancp-pon and the one for DSL. manuel: scenarios in the slides are very important and need to be covered in ancp-pon draft. chairs: as described in the charter, we already have a working group draft about ancp on pon, we should keep it. Suggest to create a draft on what's missing, which can be merged into current ancp-pon draft. Need to look at if there are something in the multicast section of ancp-pon that not covered by DSL related drafts, if there are, these contents could be reworked and add to DSL drafts. Current ancp-pon draft is only a framework, there will be another draft for protocol extensions.