From nobody Mon Feb 24 08:04:49 2014 Return-Path: X-Original-To: ancp@ietfa.amsl.com Delivered-To: ancp@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A65A41A00F4; Mon, 24 Feb 2014 08:04:43 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.81 X-Spam-Level: X-Spam-Status: No, score=0.81 tagged_above=-999 required=5 tests=[BAYES_50=0.8, T_TVD_MIME_NO_HEADERS=0.01] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eSOSnRGR8_ZU; Mon, 24 Feb 2014 08:04:41 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A3451A01AD; Mon, 24 Feb 2014 08:04:41 -0800 (PST) MIME-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 5.0.1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20140224160441.19766.7871.idtracker@ietfa.amsl.com> Date: Mon, 24 Feb 2014 08:04:41 -0800 Archived-At: http://mailarchive.ietf.org/arch/msg/ancp/yMZkicnuDxUgLXEvWyM2iceXafI Cc: ancp@ietf.org Subject: [ANCP] I-D ACTION:draft-ietf-ancp-mc-extensions-15.txt X-BeenThere: ancp@ietf.org X-Mailman-Version: 2.1.15 List-Id: Access Node Control Protocol working group mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Feb 2014 16:04:43 -0000 --NextPart A new Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Access Node Control Protocol Working Group of the IETF. Title : Multicast Control Extensions for ANCP Author(s) : F. Le Faucheur, et al Filename : draft-ietf-ancp-mc-extensions Pages : 97 Date : 2014-02-24 This document specifies the extensions to the Access Node Control Protocol required for support of the multicast use cases defined in the Access Node Control Protocol framework document and one additional use case described in this document. These use cases are organized into the following ANCP capabilities: o NAS-initiated multicast replication; o conditional access and admission control with white and black lists; o conditional access and admission control with grey lists; o bandwidth delegation; o committed bandwidth reporting. These capabilities may be combined according to the rules given in this specification. This document updates RFC 6320 by assigning capability type 3 to a capability specified in this document and by changing the starting point for IANA allocation of result codes determined by IETF Consensus from 0x100 to 0x64. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-ancp-mc-extensions-15.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Message/External-body; name="draft-ietf-ancp-mc-extensions"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2014-02-24080441.I-D@ietf.org> --NextPart-- From nobody Tue Feb 25 00:55:39 2014 Return-Path: X-Original-To: ancp@ietfa.amsl.com Delivered-To: ancp@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 498B21A0388 for ; Tue, 25 Feb 2014 00:55:38 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.7 X-Spam-Level: X-Spam-Status: No, score=0.7 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NsSUWIVTrBgD for ; Tue, 25 Feb 2014 00:55:36 -0800 (PST) Received: from mail-ie0-x234.google.com (mail-ie0-x234.google.com [IPv6:2607:f8b0:4001:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id 35CF51A041E for ; Tue, 25 Feb 2014 00:55:35 -0800 (PST) Received: by mail-ie0-f180.google.com with SMTP id ar20so62309iec.11 for ; Tue, 25 Feb 2014 00:55:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=EymKuJzJOHwieRyti/7Sp2v7puGRwyINLt0cwYaZuGM=; b=rwQ6giLTK9q/rXAuxIc6k/Sngf1MfAL48WtJgHX3zlMqJyoyDrfEfMDKEHGkn3SYXS bK88ttQy3JiLOWdMA8tlZchJRUpoeGWpWzlYEj0gUJ4J5UqBvl4HHSuYe5L+iaosg9Bd /sjjIu3vIqx7xLjkJbaW5EEmam2KeVT5SV4gl4Uwb5An40kbLa0jD9uUZFuXZIBCGF+8 VmWK9d97xWRB9xMerLSKIkngrxoPTA6v2yJHHiEKX0ONXclJ5Tu5QSJHUYHsO1i8gn7G zP8SdLr1hb4+JHEBGWTOcFNjd3hMBEsjbht/GQpJBZsauh6Voq7l6hjk9B9rhcS+QjoK JWjA== X-Received: by 10.42.246.131 with SMTP id ly3mr18440396icb.8.1393318534397; Tue, 25 Feb 2014 00:55:34 -0800 (PST) Received: from [192.168.0.101] (dsl-173-206-150-99.tor.primus.ca. [173.206.150.99]) by mx.google.com with ESMTPSA id rj10sm35580199igc.8.2014.02.25.00.55.33 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 25 Feb 2014 00:55:33 -0800 (PST) Message-ID: <530C5A86.6080505@gmail.com> Date: Tue, 25 Feb 2014 03:55:34 -0500 From: Tom Taylor User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: "ancp@ietf.org" Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Archived-At: http://mailarchive.ietf.org/arch/msg/ancp/YfucvfQ4EaG3g9ClptQbBbXWqKs Subject: [ANCP] Updates to draft-ietf-ancp-mc-extensions X-BeenThere: ancp@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Access Node Control Protocol working group mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Feb 2014 08:55:38 -0000 draft-ietf-ancp-mc-extensions-15.txt reflects changes that came from IESG comments and a discuss from Brian Haberman. The comments in turn resulted from a very thorough review by Dacheng Zhang for the Security Area directorate and a review by Mehmet Ersue for the Ops Directorate. Christer Holmberg also reviewed the document for GenArt, but no action items came out of that. The substantive changes were as follows: -- allowed specification of multiple SSM flows to be added or deleted by the same Command in the Multicast Replication Control message. See full description in item 8) below. -- changed a SHOULD NOT to a MUST NOT for unsupported list types in the multicast flow profile. See item 4) below. -- changed the effect of changes to the Report-Buffering-Time TLV to avoid the possible need for two timers. See item 5) below. Tom Taylor Here is a summary of the complete set of changes, with a list of the affected sections. 1) Editorial: brought terminology into line with RFC 5851. Specifically, the terms "conditional access" and "admission control" are now used throughout the document in place of "policy-based admission control" and "resource-based admission control". Affects numerous sections beginning with the Abstract. See Section 2 Terminology for a formal statement. 2) Editorial: recognized that the two conditional access capabilities also include admission control by renaming them. Affects several sections beginning with the Abstract. 3) Editorial: in Section 1, second paragraph after the bulleted list of capabilities, described the multicast-related sub-sections of RFC 5851 more accurately. 4) Editorial: added new sub-section 1.1 A Note On Scope to bring out architectural assumptions made in RFC 5851 and their impact. 5) Editorial/architectural: added a paragraph at the end of introductory Section 3 to say that in the use cases following, the Home Gateway could operate either in bridged or in routed mode, but the latter might be required to allow hosts behind the Home Gateway to get access to non-IPTV multicast services. The figures following were modified accordingly. 6) Substantive: in Section 4.1.1, changed the prohibition of a list type not supported by the negotiated set of capabilities from a SHOULD NOT to a MUST NOT. 7) Substantive: in Section 4.1.2, made a slight change to the effect of receiving a new value of the Report-Buffering-Time TLV. The original statement suggested that two timers might be needed rather than one. OLD The buffering time specified in an instance of the Report-Buffering- Time TLV applies only to Committed Bandwidth Report messages initiated after the new buffering time is received at the AN, not to any message already in the process of accumulation. NEW The buffering time specified in an instance of the Report-Buffering- Time TLV will not be applied until the current accumulation process of Committed Bandwidth Report messages finishes. 8) Substantive: in SSM, IGMPv3 and MLDv2 allow the Join to specify multiple sources for a specific group. To support this, the Multicast-Flow TLV has been significantly restructured by using the previously reserved field to give the number of source addresses and allowing multiple source addresses at the end of the TLV. See Section 5.12. Receiver behaviour for the Multicast Replication Control message (Section 4.3.2) now talks about the Command TLV adding one or flows rather than a flow, and error processing in the same section now deals with the case of an error in the middle of processing a list of SSM flows. A pending update to Section 5.12 to close out the Discuss will indicate that the Multicast-Flow TLV supports INCLUDE mode only, with reference to RFC 5790 for guidance on converting EXCLUDE mode to INCLUDE mode. 9) Non-normative: added new Section 7 Miscellaneous Considerations section discussing two topics. The first is an appropriate value for the Report-Buffering-Time TLV for the Committed Bandwidth Reporting capability and its potential impact. I would be happy for comments on this one, since the current text makes some rather extreme assumptions. The second topic is a warning to implementors that they have to be careful about control plane overloading, since otherwise a single channel-surfing subscriber might generate enough messaging traffic to bring down the AN or cause significant congestion. 10) Security recommendation: added a paragraph to Security Considerations recommending that operators protect the path between the NAS and AAA, in accordance with RFC 6733 if using Diameter, or applying RFC 6614 for RADIUS. 11) Editorial: extended the acknowledgements, added a number of references. From nobody Tue Feb 25 10:48:57 2014 Return-Path: X-Original-To: ancp@ietfa.amsl.com Delivered-To: ancp@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B7961A074B; Tue, 25 Feb 2014 10:48:47 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.89 X-Spam-Level: X-Spam-Status: No, score=-1.89 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_TVD_MIME_NO_HEADERS=0.01] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oMsuZpKUSzgW; Tue, 25 Feb 2014 10:48:43 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E9A81A072F; Tue, 25 Feb 2014 10:48:43 -0800 (PST) MIME-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" From: Internet-Drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 5.0.2 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20140225184843.6901.31624.idtracker@ietfa.amsl.com> Date: Tue, 25 Feb 2014 10:48:43 -0800 Archived-At: http://mailarchive.ietf.org/arch/msg/ancp/B6RiYiXy9dA0-Cy2DRICnL0w8xE Cc: ancp@ietf.org Subject: [ANCP] I-D ACTION:draft-ietf-ancp-mc-extensions-16.txt X-BeenThere: ancp@ietf.org X-Mailman-Version: 2.1.15 List-Id: Access Node Control Protocol working group mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Feb 2014 18:48:48 -0000 --NextPart A new Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Access Node Control Protocol Working Group of the IETF. Title : Multicast Control Extensions for ANCP Author(s) : F. Le Faucheur, et al Filename : draft-ietf-ancp-mc-extensions Pages : 97 Date : 2014-02-25 This document specifies the extensions to the Access Node Control Protocol required for support of the multicast use cases defined in the Access Node Control Protocol framework document and one additional use case described in this document. These use cases are organized into the following ANCP capabilities: o NAS-initiated multicast replication; o conditional access and admission control with white and black lists; o conditional access and admission control with grey lists; o bandwidth delegation; o committed bandwidth reporting. These capabilities may be combined according to the rules given in this specification. This document updates RFC 6320 by assigning capability type 3 to a capability specified in this document and by changing the starting point for IANA allocation of result codes determined by IETF Consensus from 0x100 to 0x64. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-ancp-mc-extensions-16.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Message/External-body; name="draft-ietf-ancp-mc-extensions"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2014-02-25104843.I-D@ietf.org> --NextPart-- From nobody Tue Feb 25 15:50:48 2014 Return-Path: X-Original-To: ancp@ietfa.amsl.com Delivered-To: ancp@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B97171A0326; Tue, 25 Feb 2014 15:50:41 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fXEJM6Jdpgh1; Tue, 25 Feb 2014 15:50:39 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FC5F1A07DE; Tue, 25 Feb 2014 15:50:31 -0800 (PST) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: The IESG To: IETF-Announce X-Test-IDTracker: no X-IETF-IDTracker: 5.0.2 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20140225235031.5071.94758.idtracker@ietfa.amsl.com> Date: Tue, 25 Feb 2014 15:50:31 -0800 Archived-At: http://mailarchive.ietf.org/arch/msg/ancp/fiZSm4twI80J2ax062MRg0CSEnE Cc: ancp mailing list , ancp chair , RFC Editor Subject: [ANCP] Protocol Action: 'Multicast Control Extensions for ANCP' to Proposed Standard (draft-ietf-ancp-mc-extensions-16.txt) X-BeenThere: ancp@ietf.org X-Mailman-Version: 2.1.15 List-Id: Access Node Control Protocol working group mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Feb 2014 23:50:41 -0000 The IESG has approved the following document: - 'Multicast Control Extensions for ANCP' (draft-ietf-ancp-mc-extensions-16.txt) as Proposed Standard This document is the product of the Access Node Control Protocol Working Group. The IESG contact persons are Ted Lemon and Brian Haberman. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-ancp-mc-extensions/ Technical Summary: This document specifies the extensions to the Access Node Control Protocol required for support of the multicast use cases defined in the Access Node Control Protocol framework document and one additional use case described in this document. These use cases are organized into the following ANCP capabilities: o NAS-initiated multicast replication; o conditional access with white and black lists; o conditional access with grey lists; o bandwidth delegation; o committed bandwidth reporting. These capabilities may be combined according to the rules given in this specification. Working Group Summary: The document specifies a solution to a set of multicast use cases for ANCP. These use cases are largely specified in RFC5851. That framework draft also contains use cases for the base ANCP protocol, which is specified in RFC6320. The multicast solution was split from the other use case solutions that were eventually published in RFC6320 because, at the time, it was felt that the multicast solution needed further development and review. Document Quality: There are no concerns with document quality. It is believed that there is at least one implementation of the protocol extensions described in the draft, and it has had significant review and refinement over a number of years. There are no formal review criteria. Personnel: Matthew Bocci is the document shepherd. Ted Lemon is the responsible Area Director.