
From root@core3.amsl.com  Sun Feb  7 06:45:02 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: ancp@ietf.org
Delivered-To: ancp@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 68CF83A6D86; Sun,  7 Feb 2010 06:45:01 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100207144502.68CF83A6D86@core3.amsl.com>
Date: Sun,  7 Feb 2010 06:45:02 -0800 (PST)
Cc: ancp@ietf.org
Subject: [ANCP] I-D Action:draft-ietf-ancp-framework-13.txt
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list <ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>, <mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>, <mailto:ancp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Feb 2010 14:45:02 -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           : Framework and Requirements for an Access Node Control Mechanism in Broadband Multi-Service Networks
	Author(s)       : S. Ooghe, et al.
	Filename        : draft-ietf-ancp-framework-13.txt
	Pages           : 53
	Date            : 2010-02-07

The purpose of this document is to define a framework for an Access
Node Control Mechanism between a Network Access Server (NAS) and an
Access Node (e.g. a Digital Subscriber Line Access Multiplexer
(DSLAM)) in a multi-service reference architecture in order to
perform QoS-related, service-related and Subscriber-related
operations.  The Access Node Control Mechanism will ensure that the
transmission of the information does not need to go through distinct
element managers but rather using a direct device-device
communication.  This allows for performing access link related
operations within those network elements, while avoiding impact on
the existing Operational Support Systems (OSSes).

This document first identifies a number of use cases for which the
Access Node Control Mechanism may be appropriate.  It then presents
the requirements for the Access Node Control Protocol (ANCP) that
must be taken into account during protocol design.  Finally, it
describes requirements for the network elements that need to support
ANCP and the described use cases.  These requirements should be seen
as guidelines rather than as absolute requirements.  RFC 2119
therefore does not apply to the nodal requirements.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ancp-framework-13.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-framework-13.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2010-02-07064237.I-D@ietf.org>


--NextPart--

From Sven.Ooghe@alcatel-lucent.com  Sun Feb  7 06:39:33 2010
Return-Path: <Sven.Ooghe@alcatel-lucent.com>
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8D0CC3A7208 for <ancp@core3.amsl.com>; Sun,  7 Feb 2010 06:39:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.76
X-Spam-Level: 
X-Spam-Status: No, score=-0.76 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, HELO_EQ_FR=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Js0Bc2T2Q3Is for <ancp@core3.amsl.com>; Sun,  7 Feb 2010 06:39:32 -0800 (PST)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [64.208.49.57]) by core3.amsl.com (Postfix) with ESMTP id 358AE3A7207 for <ancp@ietf.org>; Sun,  7 Feb 2010 06:39:32 -0800 (PST)
Received: from FRVELSBHS06.ad2.ad.alcatel.com (frvelsbhs06.dc-m.alcatel-lucent.com [155.132.6.78]) by smail2.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id o17EeO9L017966;  Sun, 7 Feb 2010 15:40:25 +0100
Received: from FRVELSMBS22.ad2.ad.alcatel.com ([155.132.6.53]) by FRVELSBHS06.ad2.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.3959); Sun, 7 Feb 2010 15:40:24 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Sun, 7 Feb 2010 15:40:24 +0100
Message-ID: <7168964CAC5C144685272595141B6DBA039E7511@FRVELSMBS22.ad2.ad.alcatel.com>
In-Reply-To: <20091227074411.62680@gmx.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ANCP] My review notes for draft-ietf-ancp-framework-12.txt
Thread-Index: AcqGyGjV4sJzT+Z3T9SpK+eX47viAgRbNeOQ
References: <20091227074411.62680@gmx.net>
From: "OOGHE Sven" <Sven.Ooghe@alcatel-lucent.com>
To: "Hannes Tschofenig" <Hannes.Tschofenig@gmx.net>, "Tina TSOU" <tena@huawei.com>
X-OriginalArrivalTime: 07 Feb 2010 14:40:24.0437 (UTC) FILETIME=[7B882A50:01CAA803]
X-Scanned-By: MIMEDefang 2.64 on 155.132.188.80
X-Mailman-Approved-At: Mon, 08 Feb 2010 02:08:34 -0800
Cc: ancp@ietf.org
Subject: Re: [ANCP] My review notes for draft-ietf-ancp-framework-12.txt
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list <ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>, <mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>, <mailto:ancp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Feb 2010 14:39:33 -0000

Hi Hannes and Tina,

Thanks for reviewing, sorry for the delayed response. My proposed
changes are indicated below. I will update the draft accordingly. The
document is now in the RFC-Editor's queue, so I will directly inform the
RFC-Editor Team to make the corresponding changes.

Regards
Sven

-----Original Message-----
From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of
Hannes Tschofenig
Sent: zondag 27 december 2009 8:44
To: ancp@ietf.org
Subject: [ANCP] My review notes for draft-ietf-ancp-framework-12.txt

Hi all,=20

I just went through
http://www.ietf.org/id/draft-ietf-ancp-framework-12.txt.=20

It is a nice and interesting document but I noticed a few minor areas
for improvement.=20

0. Terminology

If you cite some ITU-T documents then put the cited text in quotes. If
you modify their definition then say so.=20

<Sven> Ok, I will make the changes.

1. Definition of "Multicast flow"

Here is what you have in the draft=20

"
   o  Multicast Flow: multicast Any Source Multicast (ASM) group or
      multicast Source Specific Multicast (SSM) (S,G) channel.  An
      application channel (such as a TV channel) is mapped onto a
      Multicast Flow.
"

This does not sound complete nor understandable.=20
Looking at RFC 4045 http://tools.ietf.org/html/rfc4045 I can find the
following definition:

"
   Multicast flow

      Designates datagrams sent to a group from a set of sources for
      which multicast reception is desired.
"

Maybe this is more appropriate?=20

<Sven> Agreed, I will update the second definition but adding a few
words on ASM (*,G) and SSM (S,G) multicast.

3. "General Architecture Aspects" Section=20

The "Access Node Control Mechanism" term is described as=20
"	 =20
   o  Access Node Control Mechanism: a method for multiple network
      scenarios with an extensible communication scheme that conveys
      status and control information between one or more ANs and one or
      more NASs without using intermediate element managers.
"

There are two concepts that readers are typically familiar with, namely
a protocol and an architecture.=20
The main product of the working group is the protocol. The architecture
already exists elsewhere, namely largely in the Broadband Forum (former
DSL Forum) and there is potential (maybe) applicability elsewhere (e.g.,
IEEE 802.16).=20

Now, Section 2.1 describes something that others would typically call
"architecture". Section 2.2 is a mixture of a) description of Figure 1,
and=20
b) the text provides an instantiation of the architectural figure shown
in Section 2.1.=20

Section 2.3. has the fancy title of "Access Node Control Mechanism
Transport Methods". What this section only does is to discuss how QoS
treatment of control traffic can be accomplished when used over Ethernet
and ATM networks. I don't think that this is crucial for the description
of the architecture but your view might be different. Maybe there is a
chance to provide a better introduction to this section and a different
title for the section. Something like "Preferential Treatment for
Signaling Traffic" or "Separating Signaling and Control Traffic".

Section 2.4 is also not very fortunate with regard to the section
heading. "Operations and Management" is a rather broad term and you
address only a very specific aspect in this section, namely the
challenge of having more than one management entities and the potential
conflicts that may arise.=20

Overall, I believe that there is something wrong with the structure of
Section 2. The introduction of Section 2 talks about two aspects that
are described but then there are 5 sub-sections, with an unclear
relationship among either other. Some "glue" is missing here.=20

<Sven>
I will update the beginning of section 2:
"This section introduces the basic concept of the Access Node Control
Mechanism and describes the reference architecture where it is being
applied. Based on the reference architecture, the section then describes
how Access Node Control messages are to be prioritized over other data
traffic, and the interaction between ANCP and the network management
system. Finally, the addressing schemes are described that allow
identifying an Access Port in Access Node Control messages."

. I will update the title of section 2.3 to " Prioritizing Access Node
Control traffic" and add following description:
"When sending Access Node Control messages across the aggregation
network, care is needed that messages won&apos;t get lost. The
connectivity between the Access Node and the NAS may differ depending on
the actual layer 2 technology used (ATM or Ethernet). This section
briefly outlines how network connectivity can be established."

. I will update the title of section 2.4 to "Interaction with management
systems"

4. Figures have a title. =20

Figure 1 is missing a title.=20

<Sven> I will add the title.

5. Abbreviations

When you introduce abbreviations please expand them (otherwise you will
be asked again by the RFC Editor later).=20

<Sven> I will cross-check and update.

6. "Access Node" and other terms.=20

Section 1.2 defines the term "Access Node" and Section 2.2.3 defines it
again.=20
The same is true for "Network Access Server" defined in Section 1.2 and
again defined in Section 2.2.6. =20

<Sven> I will remove the definitions in section 2.2.3 and 2.2.6.=20

7. Justify your statements

When you talk about other mechanisms being error prone and complex then
you need to provide a discussion why they are error prone or more
complex than the mechanism being proposed here to gain credibility.=20

Example:

"
   OSS systems are rarely able to enforce in a reliable and scalable
   manner the consistency of such data, notably across organizational
   boundaries.=20
   The Access Topology Discovery function allows the NAS to
   perform these advanced functions without having to depend on an
   error-prone & possibly complex integration with an OSS system.
"

<Sven> I will reword as follows:
"OSS systems are typically not designed to enforce the consistency of
such data in a reliable and scalable manner across organizational
boundaries. The Access Topology Discovery function is indended to allow
the NAS to perform these functions without having to rely on an
integration with an OSS system."

8. Section 3.2 - OPEX

I have a question regarding the OPEX statement in the following
paragraph:

"
   Access Loop rates are typically configured in a static way.  When a
   Subscriber wants to change its Access Loop rate, the network operator
   needs to reconfigure the Access Port configuration, possibly implying
   a business-to-business transaction between an Internet Service
   Provider (ISP) and an Access Provider.  From an Operating
   Expenditures (OPEX) perspective this is a costly operation.

   Using the Access Node Control Mechanism to change the Access Loop
   rate from the NAS avoids those cross-organization business-to-
   business interactions and allows to centralize Subscriber-related
   service data in e.g. a Policy Server.
" =20

I guess I understand that there are still two organizations involved but
you essentially claim that by using some protocol mechanisms the OPEX
cost would be reduced compared to a potential human interaction as it is
done today.=20
Is my understanding correct?=20

<Sven> Yes, that's correct.

9. Section 5 "Policy Server Interaction" is useless. Maybe better to
delete this section?

<Sven> Given that it is already captured elsewhere in the document, I
see no need to keep section 5. If no-one objects I will remove it.
 =20
10. Editorial issues=20

Let some native English speaker read through the text to make sure that
the language, punctuation, etc. problems get fixed.=20

<Sven> During Last Call the draft was reviewed by several native English
speakers - if there are other edits to be done please let me know.

Thanks
Sven


Ciao
Hannes
_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp

From tom111.taylor@bell.net  Tue Feb  9 11:22:07 2010
Return-Path: <tom111.taylor@bell.net>
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8C60F28C217 for <ancp@core3.amsl.com>; Tue,  9 Feb 2010 11:22:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.019
X-Spam-Level: 
X-Spam-Status: No, score=-0.019 tagged_above=-999 required=5 tests=[AWL=-1.256, BAYES_40=-0.185, MSGID_FROM_MTA_HEADER=0.803, RCVD_IN_SORBS_WEB=0.619]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xEf6VHBkmglv for <ancp@core3.amsl.com>; Tue,  9 Feb 2010 11:22:06 -0800 (PST)
Received: from blu0-omc2-s2.blu0.hotmail.com (blu0-omc2-s2.blu0.hotmail.com [65.55.111.77]) by core3.amsl.com (Postfix) with ESMTP id AE55028C0D0 for <ancp@ietf.org>; Tue,  9 Feb 2010 11:22:06 -0800 (PST)
Received: from BLU0-SMTP92 ([65.55.111.72]) by blu0-omc2-s2.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 9 Feb 2010 11:23:13 -0800
X-Originating-IP: [76.64.156.247]
X-Originating-Email: [tom111.taylor@bell.net]
Message-ID: <BLU0-SMTP92FF0CECA8B014B251846BD8500@phx.gbl>
Received: from [192.168.2.11] ([76.64.156.247]) by BLU0-SMTP92.blu0.hotmail.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Tue, 9 Feb 2010 11:23:13 -0800
Date: Tue, 09 Feb 2010 14:23:10 -0500
From: Tom Taylor <tom111.taylor@bell.net>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: ancp@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 09 Feb 2010 19:23:13.0491 (UTC) FILETIME=[52B3D230:01CAA9BD]
Subject: [ANCP] Small ANCP issues -- definition of sub-TLV
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list <ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>, <mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>, <mailto:ancp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Feb 2010 19:22:07 -0000

I'm doing a revision of the multicast extensions draft and have a couple of 
trivial issues, the sort of thing that is important to an editor.

Can we provide a consistent definition of a sub-TLV? My problem is that 
currently the text in the base document says that the Status-Info TLV, for 
instance, can contain sub-TLVs. However, these sub-TLVs are actually TLVs which 
happen to be encapsulated in the Status-Info. On the other hand, both the base 
protocol draft and the multicast extensions draft have IANA registries for 
sub-TLV numbers.

I make the following proposal:

a) A sub-TLV is defined as a tag-length-value field that is always a subordinate 
part of a specific TLV type. That is, sub-TLVs are not reusable between TLVs. I 
doubt this introduces much if any specification redundancy. This definition 
should be given as part of the terminology section of the base protocol document.

b) If we want the set of sub-TLVs for a given TLV type to be extensible, we 
define an IANA registry for "Sub-TLVs of TLV Type xxxxx".

c) It is also possible for TLVs to be encapsulated in other TLVs. We would use 
the term "encapsulated TLV" instead of "sub-TLV" for this case.



From tom111.taylor@bell.net  Tue Feb  9 11:28:11 2010
Return-Path: <tom111.taylor@bell.net>
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BBDB23A75CB for <ancp@core3.amsl.com>; Tue,  9 Feb 2010 11:28:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.327
X-Spam-Level: 
X-Spam-Status: No, score=-1.327 tagged_above=-999 required=5 tests=[AWL=0.469,  BAYES_00=-2.599, MSGID_FROM_MTA_HEADER=0.803]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jIEOquvgsOWc for <ancp@core3.amsl.com>; Tue,  9 Feb 2010 11:28:11 -0800 (PST)
Received: from blu0-omc2-s22.blu0.hotmail.com (blu0-omc2-s22.blu0.hotmail.com [65.55.111.97]) by core3.amsl.com (Postfix) with ESMTP id DDE413A75B3 for <ancp@ietf.org>; Tue,  9 Feb 2010 11:28:10 -0800 (PST)
Received: from BLU0-SMTP88 ([65.55.111.73]) by blu0-omc2-s22.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 9 Feb 2010 11:29:17 -0800
X-Originating-IP: [76.64.156.247]
X-Originating-Email: [tom111.taylor@bell.net]
Message-ID: <BLU0-SMTP883E13C3EEC9F708E8C6FBD8500@phx.gbl>
Received: from [192.168.2.11] ([76.64.156.247]) by BLU0-SMTP88.blu0.hotmail.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Tue, 9 Feb 2010 11:29:16 -0800
Date: Tue, 09 Feb 2010 14:29:13 -0500
From: Tom Taylor <tom111.taylor@bell.net>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: ancp@ietf.org
References: <4B71B61E.6000301@bell.net>
In-Reply-To: <4B71B61E.6000301@bell.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 09 Feb 2010 19:29:17.0133 (UTC) FILETIME=[2B732FD0:01CAA9BE]
Subject: Re: [ANCP] Small ANCP issues -- definition of sub-TLV
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list <ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>, <mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>, <mailto:ancp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Feb 2010 19:28:11 -0000

I forgot to say as part of my proposal for sub-TLVs that the type number for a 
sub-TLV is scoped to the specific TLV rather than the set of TLVs. That is, the 
set of sub-TLV type numbers for any given TLV always runs from 0x01 up.

Another name for "sub-TLV" might be "variable-length field".

Tom Taylor wrote:
> I'm doing a revision of the multicast extensions draft and have a couple 
> of trivial issues, the sort of thing that is important to an editor.
> 
> Can we provide a consistent definition of a sub-TLV? My problem is that 
> currently the text in the base document says that the Status-Info TLV, 
> for instance, can contain sub-TLVs. However, these sub-TLVs are actually 
> TLVs which happen to be encapsulated in the Status-Info. On the other 
> hand, both the base protocol draft and the multicast extensions draft 
> have IANA registries for sub-TLV numbers.
> 
> I make the following proposal:
> 
> a) A sub-TLV is defined as a tag-length-value field that is always a 
> subordinate part of a specific TLV type. That is, sub-TLVs are not 
> reusable between TLVs. I doubt this introduces much if any specification 
> redundancy. This definition should be given as part of the terminology 
> section of the base protocol document.
> 
> b) If we want the set of sub-TLVs for a given TLV type to be extensible, 
> we define an IANA registry for "Sub-TLVs of TLV Type xxxxx".
> 
> c) It is also possible for TLVs to be encapsulated in other TLVs. We 
> would use the term "encapsulated TLV" instead of "sub-TLV" for this case.
> 
> 
> 

From tom111.taylor@bell.net  Wed Feb 10 13:28:46 2010
Return-Path: <tom111.taylor@bell.net>
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9FA9428C237 for <ancp@core3.amsl.com>; Wed, 10 Feb 2010 13:28:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.094
X-Spam-Level: 
X-Spam-Status: No, score=-0.094 tagged_above=-999 required=5 tests=[AWL=-0.898, BAYES_50=0.001, MSGID_FROM_MTA_HEADER=0.803]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iUryFAKmzInI for <ancp@core3.amsl.com>; Wed, 10 Feb 2010 13:28:46 -0800 (PST)
Received: from blu0-omc2-s25.blu0.hotmail.com (blu0-omc2-s25.blu0.hotmail.com [65.55.111.100]) by core3.amsl.com (Postfix) with ESMTP id AC4D528C211 for <ancp@ietf.org>; Wed, 10 Feb 2010 13:28:45 -0800 (PST)
Received: from BLU0-SMTP15 ([65.55.111.71]) by blu0-omc2-s25.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 10 Feb 2010 13:27:51 -0800
X-Originating-IP: [76.64.156.247]
X-Originating-Email: [tom111.taylor@bell.net]
Message-ID: <BLU0-SMTP15BD9762DB59D409C2B5B7D84F0@phx.gbl>
Received: from [192.168.2.11] ([76.64.156.247]) by BLU0-SMTP15.blu0.hotmail.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Wed, 10 Feb 2010 13:27:51 -0800
Date: Wed, 10 Feb 2010 16:27:49 -0500
From: Tom Taylor <tom111.taylor@bell.net>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: ancp@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 10 Feb 2010 21:27:51.0136 (UTC) FILETIME=[E623A600:01CAAA97]
Subject: [ANCP] Multicast extension codepoints
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list <ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>, <mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>, <mailto:ancp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Feb 2010 21:28:46 -0000

Can I tidy up the various codepoint assignments in the multicast extensions 
document, or have people started to implement it already?

One issue I've noticed is that the GSMPv3 registries we are updating use decimal 
codepoint assignments, while we've used hexadecimal in both the base protocol 
document and the multicast extensions document. We'll have to try to sort that out.

Tom Taylor
co-editor

From tom111.taylor@bell.net  Wed Feb 10 13:44:52 2010
Return-Path: <tom111.taylor@bell.net>
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0C0A33A7497 for <ancp@core3.amsl.com>; Wed, 10 Feb 2010 13:44:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.019
X-Spam-Level: 
X-Spam-Status: No, score=0.019 tagged_above=-999 required=5 tests=[AWL=-0.785,  BAYES_50=0.001, MSGID_FROM_MTA_HEADER=0.803]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dDBmFe479uWM for <ancp@core3.amsl.com>; Wed, 10 Feb 2010 13:44:49 -0800 (PST)
Received: from blu0-omc2-s37.blu0.hotmail.com (blu0-omc2-s37.blu0.hotmail.com [65.55.111.112]) by core3.amsl.com (Postfix) with ESMTP id F41813A6840 for <ancp@ietf.org>; Wed, 10 Feb 2010 13:44:48 -0800 (PST)
Received: from BLU0-SMTP99 ([65.55.111.73]) by blu0-omc2-s37.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 10 Feb 2010 13:46:00 -0800
X-Originating-IP: [76.64.156.247]
X-Originating-Email: [tom111.taylor@bell.net]
Message-ID: <BLU0-SMTP99403FACE684B095329E67D84F0@phx.gbl>
Received: from [192.168.2.11] ([76.64.156.247]) by BLU0-SMTP99.blu0.hotmail.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Wed, 10 Feb 2010 13:46:00 -0800
Date: Wed, 10 Feb 2010 16:45:59 -0500
From: Tom Taylor <tom111.taylor@bell.net>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: ancp@ietf.org
References: <4B71B61E.6000301@bell.net> <BLU0-SMTP883E13C3EEC9F708E8C6FBD8500@phx.gbl>
In-Reply-To: <BLU0-SMTP883E13C3EEC9F708E8C6FBD8500@phx.gbl>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 10 Feb 2010 21:46:00.0652 (UTC) FILETIME=[6F8A98C0:01CAAA9A]
Subject: Re: [ANCP] Small ANCP issues -- definition of sub-TLV
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list <ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>, <mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>, <mailto:ancp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Feb 2010 21:44:52 -0000

I've decided this is a bad idea. The basic problem is how the receiver 
distinguishes between encapsulated TLVs and sub-TLVs within the same TLV. My 
conclusion is that "sub-TLVs" should all share the same type code space, which 
means changes in presentation in the base document (I think the actual type 
codes can stay the same) and changes in both type code values and presentation 
in the multicast extensions document.

The definition of a sub-TLV is a TLV that happens to be encapsulated in another 
TLV. It may or may not occur on its own in a different context.

Tom Taylor
Multicast extensions co-editor

Tom Taylor wrote:
> I forgot to say as part of my proposal for sub-TLVs that the type number 
> for a sub-TLV is scoped to the specific TLV rather than the set of TLVs. 
> That is, the set of sub-TLV type numbers for any given TLV always runs 
> from 0x01 up.
> 
...

From wdec@cisco.com  Thu Feb 11 01:59:51 2010
Return-Path: <wdec@cisco.com>
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EE2D93A7825 for <ancp@core3.amsl.com>; Thu, 11 Feb 2010 01:59:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id etMrC4e7iWwX for <ancp@core3.amsl.com>; Thu, 11 Feb 2010 01:59:49 -0800 (PST)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id 3B7A73A781A for <ancp@ietf.org>; Thu, 11 Feb 2010 01:59:49 -0800 (PST)
Authentication-Results: rtp-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEADZkc0utJV2a/2dsb2JhbACaenSlFJdihFYE
X-IronPort-AV: E=Sophos;i="4.49,450,1262563200"; d="scan'208";a="85330179"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rtp-iport-1.cisco.com with ESMTP; 11 Feb 2010 10:01:02 +0000
Received: from xbh-ams-101.cisco.com (xbh-ams-101.cisco.com [144.254.74.71]) by rcdn-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id o1BA0m4K026919;  Thu, 11 Feb 2010 10:01:02 GMT
Received: from xmb-ams-111.cisco.com ([144.254.74.86]) by xbh-ams-101.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 11 Feb 2010 11:00:58 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 11 Feb 2010 11:00:58 +0100
Message-ID: <A16B9A4922C4A544A94565E870362B500138557F@XMB-AMS-111.cisco.com>
In-Reply-To: <BLU0-SMTP15BD9762DB59D409C2B5B7D84F0@phx.gbl>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ANCP] Multicast extension codepoints
Thread-Index: AcqqmEatioqJeJkQTU2Ke1MtSfOb7wAY2ijw
References: <BLU0-SMTP15BD9762DB59D409C2B5B7D84F0@phx.gbl>
From: "Wojciech Dec (wdec)" <wdec@cisco.com>
To: "Tom Taylor" <tom111.taylor@bell.net>, <ancp@ietf.org>
X-OriginalArrivalTime: 11 Feb 2010 10:00:58.0575 (UTC) FILETIME=[1BF3A5F0:01CAAB01]
Subject: Re: [ANCP] Multicast extension codepoints
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list <ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>, <mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>, <mailto:ancp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Feb 2010 09:59:51 -0000

Hi Tom,

Do you mean the message type code-points?

Regards,
Woj.

> -----Original Message-----
> From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On=20
> Behalf Of Tom Taylor
> Sent: 10 February 2010 22:28
> To: ancp@ietf.org
> Subject: [ANCP] Multicast extension codepoints
>=20
> Can I tidy up the various codepoint assignments in the=20
> multicast extensions document, or have people started to=20
> implement it already?
>=20
> One issue I've noticed is that the GSMPv3 registries we are=20
> updating use decimal codepoint assignments, while we've used=20
> hexadecimal in both the base protocol document and the=20
> multicast extensions document. We'll have to try to sort that out.
>=20
> Tom Taylor
> co-editor
> _______________________________________________
> ANCP mailing list
> ANCP@ietf.org
> https://www.ietf.org/mailman/listinfo/ancp
>=20

From wdec@cisco.com  Thu Feb 11 01:59:51 2010
Return-Path: <wdec@cisco.com>
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BF9F63A7825 for <ancp@core3.amsl.com>; Thu, 11 Feb 2010 01:59:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xID8uhJvQjAY for <ancp@core3.amsl.com>; Thu, 11 Feb 2010 01:59:51 -0800 (PST)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id DC71A3A7824 for <ancp@ietf.org>; Thu, 11 Feb 2010 01:59:50 -0800 (PST)
Authentication-Results: sj-iport-6.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAKVkc0utJV2d/2dsb2JhbACaenSlCpdihFYE
X-IronPort-AV: E=Sophos;i="4.49,450,1262563200"; d="scan'208";a="481596657"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by sj-iport-6.cisco.com with ESMTP; 11 Feb 2010 10:01:02 +0000
Received: from xbh-ams-101.cisco.com (xbh-ams-101.cisco.com [144.254.74.71]) by rcdn-core-6.cisco.com (8.14.3/8.14.3) with ESMTP id o1BA0T4F010238;  Thu, 11 Feb 2010 10:01:02 GMT
Received: from xmb-ams-111.cisco.com ([144.254.74.86]) by xbh-ams-101.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 11 Feb 2010 11:00:58 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 11 Feb 2010 11:00:58 +0100
Message-ID: <A16B9A4922C4A544A94565E870362B5001385580@XMB-AMS-111.cisco.com>
In-Reply-To: <BLU0-SMTP99403FACE684B095329E67D84F0@phx.gbl>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ANCP] Small ANCP issues -- definition of sub-TLV
Thread-Index: AcqqmnVSa1fHBjEDRyiAucZ0bvHZZQAYdfeQ
References: <4B71B61E.6000301@bell.net><BLU0-SMTP883E13C3EEC9F708E8C6FBD8500@phx.gbl> <BLU0-SMTP99403FACE684B095329E67D84F0@phx.gbl>
From: "Wojciech Dec (wdec)" <wdec@cisco.com>
To: "Tom Taylor" <tom111.taylor@bell.net>, <ancp@ietf.org>
X-OriginalArrivalTime: 11 Feb 2010 10:00:58.0763 (UTC) FILETIME=[1C1055B0:01CAAB01]
Subject: Re: [ANCP] Small ANCP issues -- definition of sub-TLV
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list <ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>, <mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>, <mailto:ancp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Feb 2010 09:59:51 -0000

=20

> -----Original Message-----
> From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On=20
> Behalf Of Tom Taylor
> Sent: 10 February 2010 22:46
> To: ancp@ietf.org
> Subject: Re: [ANCP] Small ANCP issues -- definition of sub-TLV
>=20
> I've decided this is a bad idea. The basic problem is how the=20
> receiver distinguishes between encapsulated TLVs and sub-TLVs=20
> within the same TLV. My conclusion is that "sub-TLVs" should=20
> all share the same type code space, which means changes in=20
> presentation in the base document (I think the actual type=20
> codes can stay the same) and changes in both type code values=20
> and presentation in the multicast extensions document.
>=20
> The definition of a sub-TLV is a TLV that happens to be=20
> encapsulated in another TLV. It may or may not occur on its=20
> own in a different context.

I believe that this is inline with the intent to try to get "re-usable"
information elements (to avoid calling them TLVs or sub-TLVs). What
changes in the base document you think will be required?

Regards,
Woj.

>=20
> Tom Taylor
> Multicast extensions co-editor
>=20
> Tom Taylor wrote:
> > I forgot to say as part of my proposal for sub-TLVs that the type=20
> > number for a sub-TLV is scoped to the specific TLV rather=20
> than the set of TLVs.
> > That is, the set of sub-TLV type numbers for any given TLV=20
> always runs=20
> > from 0x01 up.
> >=20
> ...
> _______________________________________________
> ANCP mailing list
> ANCP@ietf.org
> https://www.ietf.org/mailman/listinfo/ancp
>=20

From tom111.taylor@bell.net  Thu Feb 11 06:08:54 2010
Return-Path: <tom111.taylor@bell.net>
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9024828C1C6 for <ancp@core3.amsl.com>; Thu, 11 Feb 2010 06:08:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.194
X-Spam-Level: 
X-Spam-Status: No, score=-1.194 tagged_above=-999 required=5 tests=[AWL=0.602,  BAYES_00=-2.599, MSGID_FROM_MTA_HEADER=0.803]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1Xa7f70J0CP7 for <ancp@core3.amsl.com>; Thu, 11 Feb 2010 06:08:53 -0800 (PST)
Received: from blu0-omc2-s32.blu0.hotmail.com (blu0-omc2-s32.blu0.hotmail.com [65.55.111.107]) by core3.amsl.com (Postfix) with ESMTP id 99ECC28C104 for <ancp@ietf.org>; Thu, 11 Feb 2010 06:08:53 -0800 (PST)
Received: from BLU0-SMTP98 ([65.55.111.73]) by blu0-omc2-s32.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 11 Feb 2010 06:10:08 -0800
X-Originating-IP: [76.64.156.247]
X-Originating-Email: [tom111.taylor@bell.net]
Message-ID: <BLU0-SMTP987CC4C7A51BACFD64A89ED84E0@phx.gbl>
Received: from [192.168.2.11] ([76.64.156.247]) by BLU0-SMTP98.blu0.hotmail.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Thu, 11 Feb 2010 06:10:07 -0800
Date: Thu, 11 Feb 2010 09:10:05 -0500
From: Tom Taylor <tom111.taylor@bell.net>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: "Wojciech Dec (wdec)" <wdec@cisco.com>
References: <4B71B61E.6000301@bell.net><BLU0-SMTP883E13C3EEC9F708E8C6FBD8500@phx.gbl> <BLU0-SMTP99403FACE684B095329E67D84F0@phx.gbl> <A16B9A4922C4A544A94565E870362B5001385580@XMB-AMS-111.cisco.com>
In-Reply-To: <A16B9A4922C4A544A94565E870362B5001385580@XMB-AMS-111.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 11 Feb 2010 14:10:08.0067 (UTC) FILETIME=[EA8B1930:01CAAB23]
Cc: ancp@ietf.org
Subject: Re: [ANCP] Small ANCP issues -- definition of sub-TLV
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list <ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>, <mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>, <mailto:ancp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Feb 2010 14:08:54 -0000

The last entry in the current IANA section is a sub-TLV type registry. That 
should be absorbed into the TLV registry.

Wojciech Dec (wdec) wrote:
>  
> 
>> -----Original Message-----
>> From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On 
>> Behalf Of Tom Taylor
>> Sent: 10 February 2010 22:46
>> To: ancp@ietf.org
>> Subject: Re: [ANCP] Small ANCP issues -- definition of sub-TLV
>>
>> I've decided this is a bad idea. The basic problem is how the 
>> receiver distinguishes between encapsulated TLVs and sub-TLVs 
>> within the same TLV. My conclusion is that "sub-TLVs" should 
>> all share the same type code space, which means changes in 
>> presentation in the base document (I think the actual type 
>> codes can stay the same) and changes in both type code values 
>> and presentation in the multicast extensions document.
>>
>> The definition of a sub-TLV is a TLV that happens to be 
>> encapsulated in another TLV. It may or may not occur on its 
>> own in a different context.
> 
> I believe that this is inline with the intent to try to get "re-usable"
> information elements (to avoid calling them TLVs or sub-TLVs). What
> changes in the base document you think will be required?
> 
> Regards,
> Woj.
> 
>> Tom Taylor
>> Multicast extensions co-editor
>>
>> Tom Taylor wrote:
>>> I forgot to say as part of my proposal for sub-TLVs that the type 
>>> number for a sub-TLV is scoped to the specific TLV rather 
>> than the set of TLVs.
>>> That is, the set of sub-TLV type numbers for any given TLV 
>> always runs 
>>> from 0x01 up.
>>>
>> ...
>> _______________________________________________
>> ANCP mailing list
>> ANCP@ietf.org
>> https://www.ietf.org/mailman/listinfo/ancp
>>
> 
> 

From wdec@cisco.com  Thu Feb 11 06:49:49 2010
Return-Path: <wdec@cisco.com>
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 62E193A76FF for <ancp@core3.amsl.com>; Thu, 11 Feb 2010 06:49:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OloIEoWFORtx for <ancp@core3.amsl.com>; Thu, 11 Feb 2010 06:49:45 -0800 (PST)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id 3C4AA3A76FE for <ancp@ietf.org>; Thu, 11 Feb 2010 06:49:45 -0800 (PST)
Authentication-Results: rtp-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEACOoc0utJV2b/2dsb2JhbACaenSmZpddhFYE
X-IronPort-AV: E=Sophos;i="4.49,453,1262563200"; d="scan'208";a="85392748"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rtp-iport-1.cisco.com with ESMTP; 11 Feb 2010 14:50:59 +0000
Received: from xbh-ams-101.cisco.com (xbh-ams-101.cisco.com [144.254.74.71]) by rcdn-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id o1BEolQb029955;  Thu, 11 Feb 2010 14:50:58 GMT
Received: from xmb-ams-111.cisco.com ([144.254.74.86]) by xbh-ams-101.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 11 Feb 2010 15:50:48 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 11 Feb 2010 15:50:41 +0100
Message-ID: <A16B9A4922C4A544A94565E870362B50013857C4@XMB-AMS-111.cisco.com>
In-Reply-To: <BLU0-SMTP987CC4C7A51BACFD64A89ED84E0@phx.gbl>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ANCP] Small ANCP issues -- definition of sub-TLV
Thread-Index: AcqrI/G8gWMMgQUsRS+T16yGBsm/dgABZO5Q
References: <4B71B61E.6000301@bell.net><BLU0-SMTP883E13C3EEC9F708E8C6FBD8500@phx.gbl> <BLU0-SMTP99403FACE684B095329E67D84F0@phx.gbl> <A16B9A4922C4A544A94565E870362B5001385580@XMB-AMS-111.cisco.com> <BLU0-SMTP987CC4C7A51BACFD64A89ED84E0@phx.gbl>
From: "Wojciech Dec (wdec)" <wdec@cisco.com>
To: "Tom Taylor" <tom111.taylor@bell.net>
X-OriginalArrivalTime: 11 Feb 2010 14:50:48.0888 (UTC) FILETIME=[9962D380:01CAAB29]
Cc: ancp@ietf.org
Subject: Re: [ANCP] Small ANCP issues -- definition of sub-TLV
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list <ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>, <mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>, <mailto:ancp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Feb 2010 14:49:49 -0000

=20

> -----Original Message-----
> From: Tom Taylor [mailto:tom111.taylor@bell.net]=20
> Sent: 11 February 2010 15:10
> To: Wojciech Dec (wdec)
> Cc: ancp@ietf.org
> Subject: Re: [ANCP] Small ANCP issues -- definition of sub-TLV
>=20
> The last entry in the current IANA section is a sub-TLV type=20
> registry. That should be absorbed into the TLV registry.

I see no problem with that. Others?

-Woj.

>=20
> Wojciech Dec (wdec) wrote:
> > =20
> >=20
> >> -----Original Message-----
> >> From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org]=20
> On Behalf=20
> >> Of Tom Taylor
> >> Sent: 10 February 2010 22:46
> >> To: ancp@ietf.org
> >> Subject: Re: [ANCP] Small ANCP issues -- definition of sub-TLV
> >>
> >> I've decided this is a bad idea. The basic problem is how the=20
> >> receiver distinguishes between encapsulated TLVs and=20
> sub-TLVs within=20
> >> the same TLV. My conclusion is that "sub-TLVs" should all=20
> share the=20
> >> same type code space, which means changes in presentation=20
> in the base=20
> >> document (I think the actual type codes can stay the same) and=20
> >> changes in both type code values and presentation in the multicast=20
> >> extensions document.
> >>
> >> The definition of a sub-TLV is a TLV that happens to be=20
> encapsulated=20
> >> in another TLV. It may or may not occur on its own in a different=20
> >> context.
> >=20
> > I believe that this is inline with the intent to try to get=20
> "re-usable"
> > information elements (to avoid calling them TLVs or sub-TLVs). What=20
> > changes in the base document you think will be required?
> >=20
> > Regards,
> > Woj.
> >=20
> >> Tom Taylor
> >> Multicast extensions co-editor
> >>
> >> Tom Taylor wrote:
> >>> I forgot to say as part of my proposal for sub-TLVs that the type=20
> >>> number for a sub-TLV is scoped to the specific TLV rather
> >> than the set of TLVs.
> >>> That is, the set of sub-TLV type numbers for any given TLV
> >> always runs
> >>> from 0x01 up.
> >>>
> >> ...
> >> _______________________________________________
> >> ANCP mailing list
> >> ANCP@ietf.org
> >> https://www.ietf.org/mailman/listinfo/ancp
> >>
> >=20
> >=20
>=20

From tom111.taylor@bell.net  Thu Feb 11 06:56:43 2010
Return-Path: <tom111.taylor@bell.net>
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 600C63A76EB for <ancp@core3.amsl.com>; Thu, 11 Feb 2010 06:56:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.254
X-Spam-Level: 
X-Spam-Status: No, score=-1.254 tagged_above=-999 required=5 tests=[AWL=0.542,  BAYES_00=-2.599, MSGID_FROM_MTA_HEADER=0.803]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Jr-FgPe6SMdN for <ancp@core3.amsl.com>; Thu, 11 Feb 2010 06:56:42 -0800 (PST)
Received: from blu0-omc2-s6.blu0.hotmail.com (blu0-omc2-s6.blu0.hotmail.com [65.55.111.81]) by core3.amsl.com (Postfix) with ESMTP id 788403A755A for <ancp@ietf.org>; Thu, 11 Feb 2010 06:56:42 -0800 (PST)
Received: from BLU0-SMTP48 ([65.55.111.73]) by blu0-omc2-s6.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 11 Feb 2010 06:57:57 -0800
X-Originating-IP: [76.64.156.247]
X-Originating-Email: [tom111.taylor@bell.net]
Message-ID: <BLU0-SMTP488D0FED680078DC5EE690D84E0@phx.gbl>
Received: from [192.168.2.11] ([76.64.156.247]) by BLU0-SMTP48.blu0.hotmail.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Thu, 11 Feb 2010 06:57:56 -0800
Date: Thu, 11 Feb 2010 09:57:55 -0500
From: Tom Taylor <tom111.taylor@bell.net>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: "Wojciech Dec (wdec)" <wdec@cisco.com>
References: <BLU0-SMTP15BD9762DB59D409C2B5B7D84F0@phx.gbl> <A16B9A4922C4A544A94565E870362B500138557F@XMB-AMS-111.cisco.com>
In-Reply-To: <A16B9A4922C4A544A94565E870362B500138557F@XMB-AMS-111.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 11 Feb 2010 14:57:56.0933 (UTC) FILETIME=[98854F50:01CAAB2A]
Cc: ancp@ietf.org
Subject: Re: [ANCP] Multicast extension codepoints
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list <ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>, <mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>, <mailto:ancp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Feb 2010 14:56:43 -0000

Here's a tabulation of everything we have now and what I propose.

Message Types
-------------

Message                             Current         Proposed

Multicast Replication Control         0x90            100
Multicast Admission Control           0x92            101
Bandwidth Reallocation Request        0x94            102
Bandwidth Transfer                    0x95            103
Delegated Bandwidth Query             0x96            104
Multicast Flow Query                  0x97            105

Command Directives
------------------

Directive                           Current (no change proposed)

Add                                              0x01
Delete                                           0x02
Delete all                                       0x03
Admission Control Reject                         0x04
Conditional Access Reject                        0x05
Admission Control and Conditional Access Reject  0x06

Failure Codes
-------------

Error Condition                     Current         Proposed

Command error                         0x100           100
Bad flow address                      0x101           101
Multicast flow does not exist         0x102           102
Invalid preferred bandwidth amount    0x103           103
Inconsistent views of delegated       0x104           104
  bandwidth amount
Bandwidth request conflict            0x105           105

TLVs
----
I'm assuming we continue with hexadecimal for this one.

TLV                                 Current         Proposed

Multicast-Service-Profile              0x13          0x20
Multicast-Service-Profile-Name         0x01          delete
  (sub-TLV)
List-Action (sub-TLV)                  0x02          0x21
Command-Number                        (none)         0x22
Bandwidth-Allocation                   0x15          0x23
White-List-CAC                        (none)         0x24
MRepCtl-CAC                           (none)         0x25
Bandwidth-Request                      0x16          0x26
Multicast-Service-Profile-Name (TLV)   0x18          0x27
Request-Source-IP (sub-TLV)            0x92          0x28
Request-Source-MAC (sub-TLV)           0x93          0x29
Multicast-Flow                         0x19          0x2A

Capabilities
------------

Capability                          Current (no change proposed)

NAS-initiated replication              0x05
Conditional access with                0x06
  white and black lists
Conditional access with grey lists     0x07
Bandwidth delegation                   0x08


Wojciech Dec (wdec) wrote:
> Hi Tom,
> 
> Do you mean the message type code-points?
> 
> Regards,
> Woj.
> 
>> -----Original Message-----
>> From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On 
>> Behalf Of Tom Taylor
>> Sent: 10 February 2010 22:28
>> To: ancp@ietf.org
>> Subject: [ANCP] Multicast extension codepoints
>>
>> Can I tidy up the various codepoint assignments in the 
>> multicast extensions document, or have people started to 
>> implement it already?
>>
>> One issue I've noticed is that the GSMPv3 registries we are 
>> updating use decimal codepoint assignments, while we've used 
>> hexadecimal in both the base protocol document and the 
>> multicast extensions document. We'll have to try to sort that out.
>>
>> Tom Taylor
>> co-editor
>> _______________________________________________
>> ANCP mailing list
>> ANCP@ietf.org
>> https://www.ietf.org/mailman/listinfo/ancp
>>
> 
> 

From tom111.taylor@bell.net  Thu Feb 11 11:45:23 2010
Return-Path: <tom111.taylor@bell.net>
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1926D28C1FA for <ancp@core3.amsl.com>; Thu, 11 Feb 2010 11:45:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.004
X-Spam-Level: 
X-Spam-Status: No, score=-0.004 tagged_above=-999 required=5 tests=[AWL=-0.808, BAYES_50=0.001, MSGID_FROM_MTA_HEADER=0.803]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sC+FMAJKnxz5 for <ancp@core3.amsl.com>; Thu, 11 Feb 2010 11:45:22 -0800 (PST)
Received: from blu0-omc2-s15.blu0.hotmail.com (blu0-omc2-s15.blu0.hotmail.com [65.55.111.90]) by core3.amsl.com (Postfix) with ESMTP id D471628C169 for <ancp@ietf.org>; Thu, 11 Feb 2010 11:45:21 -0800 (PST)
Received: from BLU0-SMTP21 ([65.55.111.73]) by blu0-omc2-s15.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 11 Feb 2010 11:46:37 -0800
X-Originating-IP: [76.64.156.247]
X-Originating-Email: [tom111.taylor@bell.net]
Message-ID: <BLU0-SMTP2127CB5C28F2B4BFAE4674D84E0@phx.gbl>
Received: from [192.168.2.11] ([76.64.156.247]) by BLU0-SMTP21.blu0.hotmail.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Thu, 11 Feb 2010 11:46:36 -0800
Date: Thu, 11 Feb 2010 14:46:34 -0500
From: Tom Taylor <tom111.taylor@bell.net>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: ancp@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 11 Feb 2010 19:46:36.0863 (UTC) FILETIME=[EC00E4F0:01CAAB52]
Subject: [ANCP] Need for application-level fragmentation in ANCP
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list <ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>, <mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>, <mailto:ancp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Feb 2010 19:45:23 -0000

The Multicast Flow Query response in the mulitcast extensions document could be 
very large. It seems to me it might sometimes be desirable to break the response 
up into multiple packets to allow other traffic onto the control channel in 
between. GSMPv3 already has facilities for fragmentation, including the I flag 
and Sub-Message Number fields in the header and a registered Result field value 
of "More" (0x5).

The rest of the stuff is documented in the base protocol document (even though 
it "SHOULD NOT" be used), but could the base protocol document also record the 
"More" value for the Result field?

Tom Taylor

From tom111.taylor@bell.net  Thu Feb 11 13:49:48 2010
Return-Path: <tom111.taylor@bell.net>
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E00CE3A75B5 for <ancp@core3.amsl.com>; Thu, 11 Feb 2010 13:49:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.064
X-Spam-Level: 
X-Spam-Status: No, score=0.064 tagged_above=-999 required=5 tests=[AWL=-0.740,  BAYES_50=0.001, MSGID_FROM_MTA_HEADER=0.803]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bV6JBAoI5Op1 for <ancp@core3.amsl.com>; Thu, 11 Feb 2010 13:49:48 -0800 (PST)
Received: from blu0-omc2-s27.blu0.hotmail.com (blu0-omc2-s27.blu0.hotmail.com [65.55.111.102]) by core3.amsl.com (Postfix) with ESMTP id E54503A744C for <ancp@ietf.org>; Thu, 11 Feb 2010 13:49:47 -0800 (PST)
Received: from BLU0-SMTP15 ([65.55.111.71]) by blu0-omc2-s27.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 11 Feb 2010 13:51:03 -0800
X-Originating-IP: [76.64.156.247]
X-Originating-Email: [tom111.taylor@bell.net]
Message-ID: <BLU0-SMTP1593E62D89D76ED5914163D84E0@phx.gbl>
Received: from [192.168.2.11] ([76.64.156.247]) by BLU0-SMTP15.blu0.hotmail.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Thu, 11 Feb 2010 13:51:03 -0800
Date: Thu, 11 Feb 2010 16:51:01 -0500
From: Tom Taylor <tom111.taylor@bell.net>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: ancp@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 11 Feb 2010 21:51:03.0435 (UTC) FILETIME=[4E6D5DB0:01CAAB64]
Subject: [ANCP] New failure code value
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list <ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>, <mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>, <mailto:ancp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Feb 2010 21:49:49 -0000

We need a new failure code value that is not currently in the base protocol 
document. Proposal:

85  Invalid value in TLV

Tom Taylor

From tom111.taylor@bell.net  Sun Feb 14 18:38:55 2010
Return-Path: <tom111.taylor@bell.net>
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 468263A79F7 for <ancp@core3.amsl.com>; Sun, 14 Feb 2010 18:38:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.179
X-Spam-Level: 
X-Spam-Status: No, score=-1.179 tagged_above=-999 required=5 tests=[AWL=0.617,  BAYES_00=-2.599, MSGID_FROM_MTA_HEADER=0.803]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 60D9qL0oMYBh for <ancp@core3.amsl.com>; Sun, 14 Feb 2010 18:38:54 -0800 (PST)
Received: from blu0-omc2-s14.blu0.hotmail.com (blu0-omc2-s14.blu0.hotmail.com [65.55.111.89]) by core3.amsl.com (Postfix) with ESMTP id A85B73A79F0 for <ancp@ietf.org>; Sun, 14 Feb 2010 18:38:53 -0800 (PST)
Received: from BLU0-SMTP49 ([65.55.111.71]) by blu0-omc2-s14.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959);  Sun, 14 Feb 2010 18:40:22 -0800
X-Originating-IP: [76.64.156.247]
X-Originating-Email: [tom111.taylor@bell.net]
Message-ID: <BLU0-SMTP4907C8594A54F9F7D7117DD84A0@phx.gbl>
Received: from [192.168.2.11] ([76.64.156.247]) by BLU0-SMTP49.blu0.hotmail.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Sun, 14 Feb 2010 18:40:22 -0800
Date: Sun, 14 Feb 2010 21:40:19 -0500
From: Tom Taylor <tom111.taylor@bell.net>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Francois Le Faucheur <flefauch@cisco.com>
References: <BLU0-SMTP57A5B6EB2D730B6B34E3E3D8B90@phx.gbl> <AD74C748-8ED3-488F-8D14-5D7B4483C3DB@cisco.com>
In-Reply-To: <AD74C748-8ED3-488F-8D14-5D7B4483C3DB@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 15 Feb 2010 02:40:22.0164 (UTC) FILETIME=[38467540:01CAADE8]
Cc: ancp@ietf.org
Subject: Re: [ANCP] [Fwd:  I-D ACTION:draft-ietf-ancp-mc-extensions-01.txt]
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list <ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>, <mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>, <mailto:ancp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Feb 2010 02:38:55 -0000

I'm working on getting the multicast extensions document into shape for review 
leading up to WGLC, and responding to these comments as a part of the process. 
See responses below marked [PTT].

Francois Le Faucheur wrote:
> Tom and all,
> 
>> Francois had a hand in getting the main ideas into shape, but due to 
>> circumstances on my side he didn't have a chance to read and approve 
>> the final version of the draft.
> 
> I reviewed the final text of section 6. In general, it is in line with 
> the discussions & conclusions Tom and I had.
> 
> Below are a the most important comments that I'd like to make sure we 
> agree on:
> 
> * 6.2.1. The case where CAC is done on NAS is clearly implied but not 
> explicit. I think we want to be explicit about it. So I propose:
> REPLACE:
> "The NAS MAY enable admission control at the AN for Nas-initiated 
> replication.  To do this, it MUST include the MRepCtl-CAC TLV in a 
> Provisioning message sent to the AN.  It MUST also include a 
> Bandwidth-Allocation TLV in a Port Management message for each access line.
> "
> BY:
> "The NAS MAY perform admission control of the NAS-initiated replication. 
> Alternatively, the NAS MAY enable admission control at the AN for 
> NAS-initiated replication.  To do this, it MUST include the MRepCtl-CAC 
> TLV in a Provisioning message sent to the AN and it MUST include a 
> Bandwidth-Allocation TLV in a Port Management message for each access line.
> "
[PTT] Done.
> 
> * 6.2.3.1. The case where CAC is done on NAS is clearly implied but not 
> explicit. I think we want to be explicit about it. So I propose:
> REPLACE:
> "The NAS can enable admission control at the AN for Grey-listed flows. 
> To do this, it MUST include the MRepCtl-CAC TLV in a Provisioning 
> message sent to the AN.  It MUST also provide a Bandwidth-Allocation TLV 
> in a Port Management message for each access line.
> "
> BY:
> "The NAS MAY perform admission control for grey-listed flows. 
> Alternatively, the NAS MAY enable admission control at the AN for 
> Grey-listed flows. To do this, it MUST include the MRepCtl-CAC TLV in a 
> Provisioning message sent to the AN and MUST also provide a 
> Bandwidth-Allocation TLV in a Port Management message for each access line.
> "
> 
[PTT] Done.
> 
> * Result Codes
> On Tom's proposal, -01 reverted to using Result values AckAll & NAck 
> instead of Ignore (as was done in previous versions) with a few commands 
> where AckAll & NAck seem ed to match teh desired response behavior. I 
> don't feel strongly about that, but want to point out this is a 
> departure from what was agreed before and I am requesting WG opinions on 
> that.
> 
[PTT] I've assumed this is acceptable to the WG.
> 
> * Response to Multicast Replication Control:
> This comment assumes that the WG agrees that Results AckAll & NAck is 
> the right approach for some commands like Multicast Replication Control.
> Tom and I agreed that the NAS decides whether to use AckAll or NAck.
> This has been reflected correctly in 4.3.1:
> "In that case, the NAS MUST set the Result field to AckAll (0x2) or Nack 
> (0x1) according to its requirements."
> But it has not yet been reflected in the multiple relevant subsections 
> under section 6.
> For example, section 6.2.3.2 says:
> " It MUST then send a Multicast Admission Control message to the NAS 
> indicating the deletion."
> While this should depend on Result Code.
> Also, section 6.3.2 says:
> "If the flow was Grey-listed, the AN MUST then send a Multicast 
> Admission Control message to the NAS indicating the deletion.  Thus the 
> AN needs to retain the fact that
>    the flow was Grey-listed for the life of the flow."
> Again, I think responding would depend on the Result field. And I think 
> the AN need not retain the fact that the flow was Grey-Listed.
> 
[PTT] I suspect you're a little confused on the timing. The response or 
non-response is to the Multicast Replication Control message that causes the 
flow to be enabled in the first place. The existing text respects that at the 
time of flow creation. These follow-up Multicast Admission Control messages 
occur perhaps hours later, when the subscriber leaves the flow. The messages 
have the vital task of allowing the NAS to keep its records of active flows up 
to date.
> 
> * section 6.3.3:
> it says:
> "If either or both conditional access capabilities are combined with the 
> delegated bandwidth capability, the AN always does admission
>    control. "
> I think this text is not correct and needs to be updated to reflect the 
> White-List-CAC TLV and the MRepCtl-CAC TLV
> 
[PTT] Fixed, I think. New text is:

  The provisioning and bandwidth management procedures of Section 6.2.4 apply in 
addition to the procedures in Section 6.2.2, Section 6.2.3, or Section 6.3.1 as 
applicable. Admission control follows the rules for conditional access rather 
than the rules in Section 6.2.4.2.
> 
> There is also a bunch of editos I will share off-line with co-authors 
> for next rev.
> 
> Francois
> 
> 

From tom111.taylor@bell.net  Sun Feb 14 18:41:29 2010
Return-Path: <tom111.taylor@bell.net>
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 538793A7A2F for <ancp@core3.amsl.com>; Sun, 14 Feb 2010 18:41:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.077
X-Spam-Level: 
X-Spam-Status: No, score=0.077 tagged_above=-999 required=5 tests=[AWL=-0.727,  BAYES_50=0.001, MSGID_FROM_MTA_HEADER=0.803]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WoOMTrRzYPbW for <ancp@core3.amsl.com>; Sun, 14 Feb 2010 18:41:28 -0800 (PST)
Received: from blu0-omc2-s1.blu0.hotmail.com (blu0-omc2-s1.blu0.hotmail.com [65.55.111.76]) by core3.amsl.com (Postfix) with ESMTP id 37F593A79F0 for <ancp@ietf.org>; Sun, 14 Feb 2010 18:41:28 -0800 (PST)
Received: from BLU0-SMTP71 ([65.55.111.73]) by blu0-omc2-s1.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959);  Sun, 14 Feb 2010 18:42:56 -0800
X-Originating-IP: [76.64.156.247]
X-Originating-Email: [tom111.taylor@bell.net]
Message-ID: <BLU0-SMTP71672D6D54A38CD0A468AFD84A0@phx.gbl>
Received: from [192.168.2.11] ([76.64.156.247]) by BLU0-SMTP71.blu0.hotmail.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Sun, 14 Feb 2010 18:42:56 -0800
Date: Sun, 14 Feb 2010 21:42:53 -0500
From: Tom Taylor <tom111.taylor@bell.net>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Francois Le Faucheur <flefauch@cisco.com>
References: <BLU0-SMTP57A5B6EB2D730B6B34E3E3D8B90@phx.gbl> <AD74C748-8ED3-488F-8D14-5D7B4483C3DB@cisco.com> <3DA866A8-8894-4C88-8AAA-BF9812AC3ECD@cisco.com>
In-Reply-To: <3DA866A8-8894-4C88-8AAA-BF9812AC3ECD@cisco.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-OriginalArrivalTime: 15 Feb 2010 02:42:56.0435 (UTC) FILETIME=[943A5830:01CAADE8]
Cc: ancp@ietf.org
Subject: Re: [ANCP] [Fwd:  I-D ACTION:draft-ietf-ancp-mc-extensions-01.txt]
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list <ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>, <mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>, <mailto:ancp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Feb 2010 02:41:29 -0000

That is stated in the last paragraph of section 6.2.4.1. I think that's the 
right place for it.

Francois Le Faucheur wrote:
> One additional comment:
> 
> In section 6.2.4.2 (Delegated Bandwidth), I think we need to add a 
> statement along the lines of "The NAS MAY at any time change the 
> allocated bandwidth using …"
> 
> 
> Francois
> 
>...

From tom111.taylor@bell.net  Sun Feb 14 19:04:03 2010
Return-Path: <tom111.taylor@bell.net>
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C406F3A73B2 for <ancp@core3.amsl.com>; Sun, 14 Feb 2010 19:04:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.125
X-Spam-Level: 
X-Spam-Status: No, score=0.125 tagged_above=-999 required=5 tests=[AWL=-0.679,  BAYES_50=0.001, MSGID_FROM_MTA_HEADER=0.803]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U2Oa7Vm6HdLT for <ancp@core3.amsl.com>; Sun, 14 Feb 2010 19:04:03 -0800 (PST)
Received: from blu0-omc2-s3.blu0.hotmail.com (blu0-omc2-s3.blu0.hotmail.com [65.55.111.78]) by core3.amsl.com (Postfix) with ESMTP id 0F88A3A677D for <ancp@ietf.org>; Sun, 14 Feb 2010 19:04:02 -0800 (PST)
Received: from BLU0-SMTP37 ([65.55.111.72]) by blu0-omc2-s3.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959);  Sun, 14 Feb 2010 19:05:31 -0800
X-Originating-IP: [76.64.156.247]
X-Originating-Email: [tom111.taylor@bell.net]
Message-ID: <BLU0-SMTP37057F1BCEB463A8A039F4D84A0@phx.gbl>
Received: from [192.168.2.11] ([76.64.156.247]) by BLU0-SMTP37.blu0.hotmail.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Sun, 14 Feb 2010 19:05:31 -0800
Date: Sun, 14 Feb 2010 22:05:28 -0500
From: Tom Taylor <tom111.taylor@bell.net>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: ancp@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 15 Feb 2010 03:05:31.0607 (UTC) FILETIME=[BBF92E70:01CAADEB]
Subject: [ANCP] Unsupported registry in ANCP base protocol document
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list <ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>, <mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>, <mailto:ancp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Feb 2010 03:04:03 -0000

The ANCP Command Code registry in the base protocol document is in the awkward 
position of reserving a value for a field that is not defined in that document. 
May I suggest that we provide the necessary support by carving the Command Code 
field out of the existing Command Info field, so that the latter starts with the 
second byte of the second word of the TLV? The result would look like this:

   0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |     TLV Type = Command        |       Command-TLV Length      |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |  Command Code |                                               |
  +-+-+-+-+-+-+-+-+                                               +
  ~                         Command Info                          ~
  |                                                               |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |     Additional sub-TLV Type   |   Additional sub-TLV Length   |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |                                                               |
  ~                   Additional sub-TLV data                     ~
  |                                                               |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

The descriptive text would add that extensions to ANCP MAY add new values for 
the Command Code field.

Tom


From roberta.maglione@telecomitalia.it  Mon Feb 15 00:24:19 2010
Return-Path: <roberta.maglione@telecomitalia.it>
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 51FDD28C17E for <ancp@core3.amsl.com>; Mon, 15 Feb 2010 00:24:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.881
X-Spam-Level: *
X-Spam-Status: No, score=1.881 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OmVM4pt6HnBA for <ancp@core3.amsl.com>; Mon, 15 Feb 2010 00:24:18 -0800 (PST)
Received: from GRFEDG701BA020.telecomitalia.it (grfedg701ba020.telecomitalia.it [156.54.233.200]) by core3.amsl.com (Postfix) with ESMTP id D341B28C189 for <ancp@ietf.org>; Mon, 15 Feb 2010 00:24:15 -0800 (PST)
Received: from grfhub706ba020.griffon.local (10.188.101.119) by GRFEDG701BA020.telecomitalia.it (10.188.45.100) with Microsoft SMTP Server (TLS) id 8.2.176.0; Mon, 15 Feb 2010 09:25:25 +0100
Received: from GRFMBX704BA020.griffon.local ([10.188.101.16]) by grfhub706ba020.griffon.local ([10.188.101.119]) with mapi; Mon, 15 Feb 2010 09:25:25 +0100
From: Maglione Roberta <roberta.maglione@telecomitalia.it>
To: 'Tom Taylor' <tom111.taylor@bell.net>, "ancp@ietf.org" <ancp@ietf.org>
Date: Mon, 15 Feb 2010 09:25:24 +0100
Thread-Topic: [ANCP] New failure code value
Thread-Index: AcqrZFFRV9DuqIobRZeHjyG+K8ZHzQCsv7Hg
Message-ID: <282BBE8A501E1F4DA9C775F964BB21FE3E73D5C3B7@GRFMBX704BA020.griffon.local>
References: <BLU0-SMTP1593E62D89D76ED5914163D84E0@phx.gbl>
In-Reply-To: <BLU0-SMTP1593E62D89D76ED5914163D84E0@phx.gbl>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [ANCP] New failure code value
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list <ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>, <mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>, <mailto:ancp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Feb 2010 08:24:19 -0000

If nobody has any objection we can add this new value.
Regards,
Roberta

-----Original Message-----
From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of Tom=
 Taylor
Sent: Thursday, February 11, 2010 10:51 PM
To: ancp@ietf.org
Subject: [ANCP] New failure code value

We need a new failure code value that is not currently in the base protocol
document. Proposal:

85  Invalid value in TLV

Tom Taylor
_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp

Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle per=
sone indicate. La diffusione, copia o qualsiasi altra azione derivante dall=
a conoscenza di queste informazioni sono rigorosamente vietate. Qualora abb=
iate ricevuto questo documento per errore siete cortesemente pregati di dar=
ne immediata comunicazione al mittente e di provvedere alla sua distruzione=
, Grazie.

This e-mail and any attachments is confidential and may contain privileged =
information intended for the addressee(s) only. Dissemination, copying, pri=
nting or use by anybody else is unauthorised. If you are not the intended r=
ecipient, please delete this message and any attachments and advise the sen=
der by return e-mail, Thanks.


From roberta.maglione@telecomitalia.it  Mon Feb 15 01:26:53 2010
Return-Path: <roberta.maglione@telecomitalia.it>
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 541743A7AEC for <ancp@core3.amsl.com>; Mon, 15 Feb 2010 01:26:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.511
X-Spam-Level: *
X-Spam-Status: No, score=1.511 tagged_above=-999 required=5 tests=[AWL=0.371,  BAYES_20=-0.74, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SuCo4XCpBVQq for <ancp@core3.amsl.com>; Mon, 15 Feb 2010 01:26:52 -0800 (PST)
Received: from GRFEDG702BA020.telecomitalia.it (grfedg702ba020.telecomitalia.it [156.54.233.201]) by core3.amsl.com (Postfix) with ESMTP id E022D3A7AE8 for <ancp@ietf.org>; Mon, 15 Feb 2010 01:26:51 -0800 (PST)
Received: from GRFHUB703BA020.griffon.local (10.188.101.113) by GRFEDG702BA020.telecomitalia.it (10.188.45.101) with Microsoft SMTP Server (TLS) id 8.2.176.0; Mon, 15 Feb 2010 10:28:16 +0100
Received: from GRFMBX704BA020.griffon.local ([10.188.101.16]) by GRFHUB703BA020.griffon.local ([10.188.101.113]) with mapi; Mon, 15 Feb 2010 10:28:16 +0100
From: Maglione Roberta <roberta.maglione@telecomitalia.it>
To: 'Tom Taylor' <tom111.taylor@bell.net>, "Wojciech Dec (wdec)" <wdec@cisco.com>
Date: Mon, 15 Feb 2010 10:28:15 +0100
Thread-Topic: [ANCP] Small ANCP issues -- definition of sub-TLV
Thread-Index: AcqrI+64IeHIpE/9S0KPujI/KxOopAC/HYQQ
Message-ID: <282BBE8A501E1F4DA9C775F964BB21FE3E73D5C3BB@GRFMBX704BA020.griffon.local>
References: <4B71B61E.6000301@bell.net><BLU0-SMTP883E13C3EEC9F708E8C6FBD8500@phx.gbl> <BLU0-SMTP99403FACE684B095329E67D84F0@phx.gbl> <A16B9A4922C4A544A94565E870362B5001385580@XMB-AMS-111.cisco.com> <BLU0-SMTP987CC4C7A51BACFD64A89ED84E0@phx.gbl>
In-Reply-To: <BLU0-SMTP987CC4C7A51BACFD64A89ED84E0@phx.gbl>
Accept-Language: en-US, it-IT
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, it-IT
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ancp@ietf.org" <ancp@ietf.org>
Subject: Re: [ANCP] Small ANCP issues -- definition of sub-TLV
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list <ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>, <mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>, <mailto:ancp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Feb 2010 09:26:53 -0000

Hi Tom,
        I think I'm missing something here:
Last IANA section contains sub-TLVs like " Actual-Net-Data-Upstream", " Act=
ual-Net-Data-Rate-Downstream" and these sub-TLVs were present since the ini=
tial version of the document. Are you proposing to change these sub-TLVs to=
 TLVs?
I'm not familiar with this type of details but wouldn't such a change impac=
t current implementations?
Thanks,
Regards,
Roberta


-----Original Message-----
From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of Tom=
 Taylor
Sent: Thursday, February 11, 2010 3:10 PM
To: Wojciech Dec (wdec)
Cc: ancp@ietf.org
Subject: Re: [ANCP] Small ANCP issues -- definition of sub-TLV

The last entry in the current IANA section is a sub-TLV type registry. That
should be absorbed into the TLV registry.

Wojciech Dec (wdec) wrote:
>
>
>> -----Original Message-----
>> From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On
>> Behalf Of Tom Taylor
>> Sent: 10 February 2010 22:46
>> To: ancp@ietf.org
>> Subject: Re: [ANCP] Small ANCP issues -- definition of sub-TLV
>>
>> I've decided this is a bad idea. The basic problem is how the
>> receiver distinguishes between encapsulated TLVs and sub-TLVs
>> within the same TLV. My conclusion is that "sub-TLVs" should
>> all share the same type code space, which means changes in
>> presentation in the base document (I think the actual type
>> codes can stay the same) and changes in both type code values
>> and presentation in the multicast extensions document.
>>
>> The definition of a sub-TLV is a TLV that happens to be
>> encapsulated in another TLV. It may or may not occur on its
>> own in a different context.
>
> I believe that this is inline with the intent to try to get "re-usable"
> information elements (to avoid calling them TLVs or sub-TLVs). What
> changes in the base document you think will be required?
>
> Regards,
> Woj.
>
>> Tom Taylor
>> Multicast extensions co-editor
>>
>> Tom Taylor wrote:
>>> I forgot to say as part of my proposal for sub-TLVs that the type
>>> number for a sub-TLV is scoped to the specific TLV rather
>> than the set of TLVs.
>>> That is, the set of sub-TLV type numbers for any given TLV
>> always runs
>>> from 0x01 up.
>>>
>> ...
>> _______________________________________________
>> ANCP mailing list
>> ANCP@ietf.org
>> https://www.ietf.org/mailman/listinfo/ancp
>>
>
>
_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp

Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle per=
sone indicate. La diffusione, copia o qualsiasi altra azione derivante dall=
a conoscenza di queste informazioni sono rigorosamente vietate. Qualora abb=
iate ricevuto questo documento per errore siete cortesemente pregati di dar=
ne immediata comunicazione al mittente e di provvedere alla sua distruzione=
, Grazie.

This e-mail and any attachments is confidential and may contain privileged =
information intended for the addressee(s) only. Dissemination, copying, pri=
nting or use by anybody else is unauthorised. If you are not the intended r=
ecipient, please delete this message and any attachments and advise the sen=
der by return e-mail, Thanks.


From tom111.taylor@bell.net  Mon Feb 15 07:14:30 2010
Return-Path: <tom111.taylor@bell.net>
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 267913A7B73 for <ancp@core3.amsl.com>; Mon, 15 Feb 2010 07:14:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.132
X-Spam-Level: 
X-Spam-Status: No, score=-1.132 tagged_above=-999 required=5 tests=[AWL=0.664,  BAYES_00=-2.599, MSGID_FROM_MTA_HEADER=0.803]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EFjMrnzVd0Zm for <ancp@core3.amsl.com>; Mon, 15 Feb 2010 07:14:26 -0800 (PST)
Received: from blu0-omc2-s38.blu0.hotmail.com (blu0-omc2-s38.blu0.hotmail.com [65.55.111.113]) by core3.amsl.com (Postfix) with ESMTP id 96FB93A7B76 for <ancp@ietf.org>; Mon, 15 Feb 2010 07:14:22 -0800 (PST)
Received: from BLU0-SMTP7 ([65.55.111.73]) by blu0-omc2-s38.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 15 Feb 2010 07:15:53 -0800
X-Originating-IP: [76.64.156.247]
X-Originating-Email: [tom111.taylor@bell.net]
Message-ID: <BLU0-SMTP78E9CEA7E415D708D2582D84A0@phx.gbl>
Received: from [192.168.2.11] ([76.64.156.247]) by BLU0-SMTP7.blu0.hotmail.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 15 Feb 2010 07:15:52 -0800
Date: Mon, 15 Feb 2010 10:15:50 -0500
From: Tom Taylor <tom111.taylor@bell.net>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Maglione Roberta <roberta.maglione@telecomitalia.it>
References: <4B71B61E.6000301@bell.net><BLU0-SMTP883E13C3EEC9F708E8C6FBD8500@phx.gbl>	<BLU0-SMTP99403FACE684B095329E67D84F0@phx.gbl>	<A16B9A4922C4A544A94565E870362B5001385580@XMB-AMS-111.cisco.com> <BLU0-SMTP987CC4C7A51BACFD64A89ED84E0@phx.gbl> <282BBE8A501E1F4DA9C775F964BB21FE3E73D5C3BB@GRFMBX704BA020.griffon.local>
In-Reply-To: <282BBE8A501E1F4DA9C775F964BB21FE3E73D5C3BB@GRFMBX704BA020.griffon.local>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 15 Feb 2010 15:15:52.0998 (UTC) FILETIME=[C38ECC60:01CAAE51]
Cc: "ancp@ietf.org" <ancp@ietf.org>
Subject: Re: [ANCP] Small ANCP issues -- definition of sub-TLV
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list <ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>, <mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>, <mailto:ancp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Feb 2010 15:14:30 -0000

The change will have zero impact because the type codes don't overlap. The 
problem in distinguishing between TLVs and sub-TLVs came from something I did in 
the multicast extensions document. I declared some structures to be sub-TLVs, 
hence local to a particular TLV. I started assigning type codes beginning with 
0x01, figuring it was a local numbering space. But a receiver parsing the 
message can't tell whether that is TLV 0x01 (defined in the base document) or 
sub-TLV 0x01 (specific to the given TLV). The conclusion was that the TLVs and 
sub-TLVs had to share the same type code space. Hence there is no need to 
distinguish them. In fact, in my latest edit of the multicast extensions 
document, I redefined the sub-TLVs to have potentially broader usage.

Maglione Roberta wrote:
> Hi Tom,
>         I think I'm missing something here:
> Last IANA section contains sub-TLVs like " Actual-Net-Data-Upstream", " Actual-Net-Data-Rate-Downstream" and these sub-TLVs were present since the initial version of the document. Are you proposing to change these sub-TLVs to TLVs?
> I'm not familiar with this type of details but wouldn't such a change impact current implementations?
> Thanks,
> Regards,
> Roberta
> 
> 
> -----Original Message-----
> From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of Tom Taylor
> Sent: Thursday, February 11, 2010 3:10 PM
> To: Wojciech Dec (wdec)
> Cc: ancp@ietf.org
> Subject: Re: [ANCP] Small ANCP issues -- definition of sub-TLV
> 
> The last entry in the current IANA section is a sub-TLV type registry. That
> should be absorbed into the TLV registry.
> 
> Wojciech Dec (wdec) wrote:
>>
>>> -----Original Message-----
>>> From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On
>>> Behalf Of Tom Taylor
>>> Sent: 10 February 2010 22:46
>>> To: ancp@ietf.org
>>> Subject: Re: [ANCP] Small ANCP issues -- definition of sub-TLV
>>>
>>> I've decided this is a bad idea. The basic problem is how the
>>> receiver distinguishes between encapsulated TLVs and sub-TLVs
>>> within the same TLV. My conclusion is that "sub-TLVs" should
>>> all share the same type code space, which means changes in
>>> presentation in the base document (I think the actual type
>>> codes can stay the same) and changes in both type code values
>>> and presentation in the multicast extensions document.
>>>
>>> The definition of a sub-TLV is a TLV that happens to be
>>> encapsulated in another TLV. It may or may not occur on its
>>> own in a different context.
>> I believe that this is inline with the intent to try to get "re-usable"
>> information elements (to avoid calling them TLVs or sub-TLVs). What
>> changes in the base document you think will be required?
>>
>> Regards,
>> Woj.
>>
>>> Tom Taylor
>>> Multicast extensions co-editor
>>>
>>> Tom Taylor wrote:
>>>> I forgot to say as part of my proposal for sub-TLVs that the type
>>>> number for a sub-TLV is scoped to the specific TLV rather
>>> than the set of TLVs.
>>>> That is, the set of sub-TLV type numbers for any given TLV
>>> always runs
>>>> from 0x01 up.
>>>>
>>> ...
>>> _______________________________________________
>>> ANCP mailing list
>>> ANCP@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ancp
>>>
>>
> _______________________________________________
> ANCP mailing list
> ANCP@ietf.org
> https://www.ietf.org/mailman/listinfo/ancp
> 
> Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie.
> 
> This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks.
> 
> 
> 

From wwwrun@core3.amsl.com  Fri Feb 12 15:53:44 2010
Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: ancp@ietf.org
Delivered-To: ancp@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id 83FCA28C238; Fri, 12 Feb 2010 15:53:44 -0800 (PST)
To: swadhwa@juniper.net, norbert.voigt@nsn.com, sven.ooghe@alcatel-lucent.com, haagt@telekom.de, mplatnic@gmail.com
From: IETF Secretariat <ietf-ipr@ietf.org>
Message-Id: <20100212235344.83FCA28C238@core3.amsl.com>
Date: Fri, 12 Feb 2010 15:53:44 -0800 (PST)
X-Mailman-Approved-At: Mon, 15 Feb 2010 08:27:33 -0800
Cc: matthew.bocci@alcatel-lucent.com, jari.arkko@piuha.net, rdroms.ietf@gmail.com, ipr-announce@ietf.org, ancp@ietf.org
Subject: [ANCP] Posting of IPR Disclosure related to Cisco's Statement of IPR relating to draft-ietf-ancp-framework-13
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list <ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>, <mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>, <mailto:ancp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Feb 2010 23:53:44 -0000

Dear Sanjay Wadhwa, Norbert Voigt, Sven Ooghe, Thomas Haag, Michel Platnic:

An IPR disclosure that pertains to your Internet-Draft entitled "Framework and
Requirements for an Access Node Control Mechanism in Broadband Multi-Service
Networks" (draft-ietf-ancp-framework) was submitted to the IETF Secretariat on
2010-02-11 and has been posted on the "IETF Page of Intellectual Property Rights
Disclosures" (https://datatracker.ietf.org/ipr/1265/). The title of the IPR
disclosure is "Cisco's Statement of IPR relating to
draft-ietf-ancp-framework-13."

The IETF Secretariat



From HaagT@telekom.de  Tue Feb 16 04:31:18 2010
Return-Path: <HaagT@telekom.de>
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7DE6F28C121 for <ancp@core3.amsl.com>; Tue, 16 Feb 2010 04:31:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.949
X-Spam-Level: 
X-Spam-Status: No, score=-1.949 tagged_above=-999 required=5 tests=[AWL=1.300,  BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UP3dXbQHZwf3 for <ancp@core3.amsl.com>; Tue, 16 Feb 2010 04:31:17 -0800 (PST)
Received: from tcmail73.telekom.de (tcmail73.telekom.de [217.243.239.135]) by core3.amsl.com (Postfix) with ESMTP id D6D8528C13E for <ancp@ietf.org>; Tue, 16 Feb 2010 04:31:15 -0800 (PST)
Received: from s4de8psaans.blf.telekom.de (HELO s4de8psaans.mitte.t-com.de) ([10.151.180.168]) by tcmail71.telekom.de with ESMTP; 16 Feb 2010 13:32:44 +0100
Received: from S4DE8PSAAQC.mitte.t-com.de ([10.151.229.14]) by s4de8psaans.mitte.t-com.de with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 16 Feb 2010 13:32:44 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 16 Feb 2010 13:32:43 +0100
Message-ID: <5661758E3E93364685B91DD8272F287602839CDF@S4DE8PSAAQC.mitte.t-com.de>
In-Reply-To: <BLU0-SMTP78E9CEA7E415D708D2582D84A0@phx.gbl>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
thread-topic: [ANCP] Small ANCP issues -- definition of sub-TLV
thread-index: AcquUc5aan0dRyZ9TRa5Yfe+puyrMwAhwuQg
References: <4B71B61E.6000301@bell.net><BLU0-SMTP883E13C3EEC9F708E8C6FBD8500@phx.gbl>	<BLU0-SMTP99403FACE684B095329E67D84F0@phx.gbl>	<A16B9A4922C4A544A94565E870362B5001385580@XMB-AMS-111.cisco.com><BLU0-SMTP987CC4C7A51BACFD64A89ED84E0@phx.gbl><282BBE8A501E1F4DA9C775F964BB21FE3E73D5C3BB@GRFMBX704BA020.griffon.local> <BLU0-SMTP78E9CEA7E415D708D2582D84A0@phx.gbl>
From: <HaagT@telekom.de>
To: <tom111.taylor@bell.net>, <roberta.maglione@telecomitalia.it>
X-OriginalArrivalTime: 16 Feb 2010 12:32:44.0005 (UTC) FILETIME=[2346C150:01CAAF04]
Cc: B.Witschurke@telekom.de, ancp@ietf.org
Subject: Re: [ANCP] Small ANCP issues -- definition of sub-TLV
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list <ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>, <mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>, <mailto:ancp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Feb 2010 12:31:18 -0000

 All,

may be didn't get the whole issue. But as Roberta indicated a change in =
fundamental TLV structure of a port status message such as TLVs which =
are already used for basic port information like net data rates is not =
acceptable.=20

If changes only belong to multicast extensions may be considered because =
only one use case is affected.

Regards
Thomas

-----Urspr=FCngliche Nachricht-----
Von: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] Im Auftrag von =
Tom Taylor
Gesendet: Montag, 15. Februar 2010 16:16
An: Maglione Roberta
Cc: ancp@ietf.org
Betreff: Re: [ANCP] Small ANCP issues -- definition of sub-TLV

The change will have zero impact because the type codes don't overlap. =
The=20
problem in distinguishing between TLVs and sub-TLVs came from something =
I did in=20
the multicast extensions document. I declared some structures to be =
sub-TLVs,=20
hence local to a particular TLV. I started assigning type codes =
beginning with=20
0x01, figuring it was a local numbering space. But a receiver parsing =
the=20
message can't tell whether that is TLV 0x01 (defined in the base =
document) or=20
sub-TLV 0x01 (specific to the given TLV). The conclusion was that the =
TLVs and=20
sub-TLVs had to share the same type code space. Hence there is no need =
to=20
distinguish them. In fact, in my latest edit of the multicast extensions =

document, I redefined the sub-TLVs to have potentially broader usage.

Maglione Roberta wrote:
> Hi Tom,
>         I think I'm missing something here:
> Last IANA section contains sub-TLVs like " Actual-Net-Data-Upstream", =
" Actual-Net-Data-Rate-Downstream" and these sub-TLVs were present since =
the initial version of the document. Are you proposing to change these =
sub-TLVs to TLVs?
> I'm not familiar with this type of details but wouldn't such a change =
impact current implementations?
> Thanks,
> Regards,
> Roberta
>=20
>=20
> -----Original Message-----
> From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf =
Of Tom Taylor
> Sent: Thursday, February 11, 2010 3:10 PM
> To: Wojciech Dec (wdec)
> Cc: ancp@ietf.org
> Subject: Re: [ANCP] Small ANCP issues -- definition of sub-TLV
>=20
> The last entry in the current IANA section is a sub-TLV type registry. =
That
> should be absorbed into the TLV registry.
>=20
> Wojciech Dec (wdec) wrote:
>>
>>> -----Original Message-----
>>> From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On
>>> Behalf Of Tom Taylor
>>> Sent: 10 February 2010 22:46
>>> To: ancp@ietf.org
>>> Subject: Re: [ANCP] Small ANCP issues -- definition of sub-TLV
>>>
>>> I've decided this is a bad idea. The basic problem is how the
>>> receiver distinguishes between encapsulated TLVs and sub-TLVs
>>> within the same TLV. My conclusion is that "sub-TLVs" should
>>> all share the same type code space, which means changes in
>>> presentation in the base document (I think the actual type
>>> codes can stay the same) and changes in both type code values
>>> and presentation in the multicast extensions document.
>>>
>>> The definition of a sub-TLV is a TLV that happens to be
>>> encapsulated in another TLV. It may or may not occur on its
>>> own in a different context.
>> I believe that this is inline with the intent to try to get =
"re-usable"
>> information elements (to avoid calling them TLVs or sub-TLVs). What
>> changes in the base document you think will be required?
>>
>> Regards,
>> Woj.
>>
>>> Tom Taylor
>>> Multicast extensions co-editor
>>>
>>> Tom Taylor wrote:
>>>> I forgot to say as part of my proposal for sub-TLVs that the type
>>>> number for a sub-TLV is scoped to the specific TLV rather
>>> than the set of TLVs.
>>>> That is, the set of sub-TLV type numbers for any given TLV
>>> always runs
>>>> from 0x01 up.
>>>>
>>> ...
>>> _______________________________________________
>>> ANCP mailing list
>>> ANCP@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ancp
>>>
>>
> _______________________________________________
> ANCP mailing list
> ANCP@ietf.org
> https://www.ietf.org/mailman/listinfo/ancp
>=20
> Questo messaggio e i suoi allegati sono indirizzati esclusivamente =
alle persone indicate. La diffusione, copia o qualsiasi altra azione =
derivante dalla conoscenza di queste informazioni sono rigorosamente =
vietate. Qualora abbiate ricevuto questo documento per errore siete =
cortesemente pregati di darne immediata comunicazione al mittente e di =
provvedere alla sua distruzione, Grazie.
>=20
> This e-mail and any attachments is confidential and may contain =
privileged information intended for the addressee(s) only. =
Dissemination, copying, printing or use by anybody else is unauthorised. =
If you are not the intended recipient, please delete this message and =
any attachments and advise the sender by return e-mail, Thanks.
>=20
>=20
>=20
_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp

From tom111.taylor@bell.net  Tue Feb 16 08:34:42 2010
Return-Path: <tom111.taylor@bell.net>
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 60E293A7D58 for <ancp@core3.amsl.com>; Tue, 16 Feb 2010 08:34:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.129
X-Spam-Level: 
X-Spam-Status: No, score=0.129 tagged_above=-999 required=5 tests=[AWL=-0.675,  BAYES_50=0.001, MSGID_FROM_MTA_HEADER=0.803]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O-8faCi5-8mZ for <ancp@core3.amsl.com>; Tue, 16 Feb 2010 08:34:41 -0800 (PST)
Received: from blu0-omc2-s4.blu0.hotmail.com (blu0-omc2-s4.blu0.hotmail.com [65.55.111.79]) by core3.amsl.com (Postfix) with ESMTP id 8623B3A7D54 for <ancp@ietf.org>; Tue, 16 Feb 2010 08:34:41 -0800 (PST)
Received: from BLU0-SMTP79 ([65.55.111.71]) by blu0-omc2-s4.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 16 Feb 2010 08:36:16 -0800
X-Originating-IP: [76.64.156.247]
X-Originating-Email: [tom111.taylor@bell.net]
Message-ID: <BLU0-SMTP79DB448AB4CD4075A8C76DD8490@phx.gbl>
Received: from [192.168.2.11] ([76.64.156.247]) by BLU0-SMTP79.blu0.hotmail.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Tue, 16 Feb 2010 08:36:15 -0800
Date: Tue, 16 Feb 2010 11:36:12 -0500
From: Tom Taylor <tom111.taylor@bell.net>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: ancp@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 16 Feb 2010 16:36:16.0074 (UTC) FILETIME=[28BF8AA0:01CAAF26]
Subject: [ANCP] Redundant extension block length value in base protocol document
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list <ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>, <mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>, <mailto:ancp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Feb 2010 16:34:42 -0000

I'm trying to understand how to set the Block Length field following Tech Type 
in the Port Management message. This field is specified in section 5.4.1.1 of 
the base ANCP protocol document. Since this field is only eight bits wide, it 
limits the extension block length to 255 bytes.

The first word of the Extension Value also has a block length field, this time 
16 bits wide. Presumably this has a maximum value of 251 (255 bytes minus the 
Extension Value header width of 4 bytes). Can this be confirmed?

This length limit for the Extension Block has consequences for the stuff that 
has to fit in there. In particular, the multicast extensions document currently 
says that the Multicast-Service-Profile-Name value is limited to 255 bytes. 
Taking the above limits into account, that drops to 247 bytes (accounting for 
the TLV header). We probably want to drop this limit further to make sure there 
is enough space in the Extension Block for other service data that needs to be 
configured.

Alternatively, the Block Length field following the Tech Type field can be 
deprecated, allowing the Extension Block to be much larger.

Tom Taylor

From Sidd.Aanand@ecitele.com  Tue Feb 16 09:06:18 2010
Return-Path: <Sidd.Aanand@ecitele.com>
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1AC5D28C103 for <ancp@core3.amsl.com>; Tue, 16 Feb 2010 09:06:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.495
X-Spam-Level: 
X-Spam-Status: No, score=-0.495 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YSuKWACRgeSa for <ancp@core3.amsl.com>; Tue, 16 Feb 2010 09:06:17 -0800 (PST)
Received: from uspitbmg01.ecitele.com (unknown [63.94.127.136]) by core3.amsl.com (Postfix) with ESMTP id 1DBDE3A7AD4 for <ancp@ietf.org>; Tue, 16 Feb 2010 09:06:17 -0800 (PST)
X-AuditID: 3f5e7f87-b7c04ae000000790-07-4b7ad0910cf4
Received: from uspitexch01.ecitele.com (Unknown_Domain [10.0.0.71]) by uspitbmg01.ecitele.com (Symantec Brightmail Gateway) with SMTP id 38.FE.01936.190DA7B4; Tue, 16 Feb 2010 12:06:25 -0500 (EST)
Received: from USPITMAIL01.ecitele.com ([10.0.0.81]) by uspitexch01.ecitele.com ([10.0.0.71]) with mapi; Tue, 16 Feb 2010 12:07:51 -0500
From: Sidd Aanand <Sidd.Aanand@ecitele.com>
To: Tom Taylor <tom111.taylor@bell.net>, "ancp@ietf.org" <ancp@ietf.org>
Date: Tue, 16 Feb 2010 12:07:49 -0500
Thread-Topic: [ANCP] Redundant extension block length value in base protocol document
Thread-Index: AcqvJiyeDtd8mk44Qj2EgZ2qKq/97AAA+gow
Message-ID: <047B8373FDE6CE4BBAC116646F3547920A2006B2F9@USPITMAIL01.ecitele.com>
References: <BLU0-SMTP79DB448AB4CD4075A8C76DD8490@phx.gbl>
In-Reply-To: <BLU0-SMTP79DB448AB4CD4075A8C76DD8490@phx.gbl>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Cc: Robert Rennison <Robert.Rennison@ecitele.com>
Subject: Re: [ANCP] Redundant extension block length value in base protocol	document
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list <ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>, <mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>, <mailto:ancp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Feb 2010 17:06:18 -0000

Tom,

The Block length field seems redundant. The base document says the followin=
g:

***
First 2 byte of the "Extension Value" contains the number
of TLVs that follow.  The next 2 bytes contain the total length of
the TLVs carried in the extension block in bytes (existing "Block
Length" field in the GSMP message is limited to 255 bytes and is not
sufficient).=20
***

So, it seems like the whole idea behind the extension block length was to w=
ork around the 255-byte-max limit.

Even the Extension block length is redundant too, in my mind. The informati=
on contained is # of TLVs, along with the length field in each TLV is suffi=
cient for the receiver of the message to parse and read all the TLVs. Isn't=
 it? So, what is the benefit of having the extension block length?

Anyway, I am okay with deprecating the block-length field.

Thanks,
Sidd

-----Original Message-----
From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of Tom=
 Taylor
Sent: Tuesday, February 16, 2010 11:36 AM
To: ancp@ietf.org
Subject: [ANCP] Redundant extension block length value in base protocol doc=
ument

I'm trying to understand how to set the Block Length field following Tech T=
ype in the Port Management message. This field is specified in section 5.4.=
1.1 of the base ANCP protocol document. Since this field is only eight bits=
 wide, it limits the extension block length to 255 bytes.

The first word of the Extension Value also has a block length field, this t=
ime
16 bits wide. Presumably this has a maximum value of 251 (255 bytes minus t=
he Extension Value header width of 4 bytes). Can this be confirmed?

This length limit for the Extension Block has consequences for the stuff th=
at has to fit in there. In particular, the multicast extensions document cu=
rrently says that the Multicast-Service-Profile-Name value is limited to 25=
5 bytes.=20
Taking the above limits into account, that drops to 247 bytes (accounting f=
or the TLV header). We probably want to drop this limit further to make sur=
e there is enough space in the Extension Block for other service data that =
needs to be configured.

Alternatively, the Block Length field following the Tech Type field can be =
deprecated, allowing the Extension Block to be much larger.

Tom Taylor
_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp

From wdec@cisco.com  Mon Feb 22 01:23:34 2010
Return-Path: <wdec@cisco.com>
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BB99628C262 for <ancp@core3.amsl.com>; Mon, 22 Feb 2010 01:23:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.336
X-Spam-Level: 
X-Spam-Status: No, score=-10.336 tagged_above=-999 required=5 tests=[AWL=0.263, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HStBYHOSc0DY for <ancp@core3.amsl.com>; Mon, 22 Feb 2010 01:23:34 -0800 (PST)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id E636528C25E for <ancp@ietf.org>; Mon, 22 Feb 2010 01:23:33 -0800 (PST)
Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEANHbgUutJV2a/2dsb2JhbACbBnOjEJdDhGsE
X-IronPort-AV: E=Sophos;i="4.49,517,1262563200"; d="scan'208";a="87886999"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rtp-iport-2.cisco.com with ESMTP; 22 Feb 2010 09:25:31 +0000
Received: from xbh-ams-101.cisco.com (xbh-ams-101.cisco.com [144.254.74.71]) by rcdn-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id o1M9PKRE030369 for <ancp@ietf.org>; Mon, 22 Feb 2010 09:25:30 GMT
Received: from xmb-ams-111.cisco.com ([144.254.74.86]) by xbh-ams-101.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 22 Feb 2010 10:25:29 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 22 Feb 2010 10:25:26 +0100
Message-ID: <A16B9A4922C4A544A94565E870362B50014B68DE@XMB-AMS-111.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Agenda items for IETF77 ANCP WG meeting 
Thread-Index: Acn+6ltl92lm+d4MS0WQoGhkOfvVhRMJzVNgGiPS2OA=
From: "Wojciech Dec (wdec)" <wdec@cisco.com>
To: <ancp@ietf.org>
X-OriginalArrivalTime: 22 Feb 2010 09:25:30.0023 (UTC) FILETIME=[F9C7A370:01CAB3A0]
Subject: [ANCP] Agenda items for IETF77 ANCP WG meeting
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list <ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>, <mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>, <mailto:ancp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Feb 2010 09:23:34 -0000

Hi All,


We welcome requests for any agenda slots at our next ANCP WG meeting in
Anaheim. Please respond with any requests.

Thanks,
Matthew & Woj


From roberta.maglione@telecomitalia.it  Mon Feb 22 03:03:03 2010
Return-Path: <roberta.maglione@telecomitalia.it>
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4BE373A83B3 for <ancp@core3.amsl.com>; Mon, 22 Feb 2010 03:03:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.769
X-Spam-Level: 
X-Spam-Status: No, score=0.769 tagged_above=-999 required=5 tests=[AWL=-0.001,  BAYES_05=-1.11, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cGo2vf69+jdO for <ancp@core3.amsl.com>; Mon, 22 Feb 2010 03:03:02 -0800 (PST)
Received: from GRFEDG702BA020.telecomitalia.it (grfedg702ba020.telecomitalia.it [156.54.233.201]) by core3.amsl.com (Postfix) with ESMTP id A38AA3A83B2 for <ancp@ietf.org>; Mon, 22 Feb 2010 03:03:01 -0800 (PST)
Received: from GRFHUB703BA020.griffon.local (10.188.101.113) by GRFEDG702BA020.telecomitalia.it (10.188.45.101) with Microsoft SMTP Server (TLS) id 8.2.176.0; Mon, 22 Feb 2010 12:04:56 +0100
Received: from GRFMBX704BA020.griffon.local ([10.188.101.16]) by GRFHUB703BA020.griffon.local ([10.188.101.113]) with mapi; Mon, 22 Feb 2010 12:04:54 +0100
From: Maglione Roberta <roberta.maglione@telecomitalia.it>
To: "HaagT@telekom.de" <HaagT@telekom.de>, "tom111.taylor@bell.net" <tom111.taylor@bell.net>
Date: Mon, 22 Feb 2010 12:04:54 +0100
Thread-Topic: [ANCP] Small ANCP issues -- definition of sub-TLV
Thread-Index: AcquUc5aan0dRyZ9TRa5Yfe+puyrMwAhwuQgATVkHmA=
Message-ID: <282BBE8A501E1F4DA9C775F964BB21FE3E73D5C3E1@GRFMBX704BA020.griffon.local>
References: <4B71B61E.6000301@bell.net><BLU0-SMTP883E13C3EEC9F708E8C6FBD8500@phx.gbl> <BLU0-SMTP99403FACE684B095329E67D84F0@phx.gbl> <A16B9A4922C4A544A94565E870362B5001385580@XMB-AMS-111.cisco.com><BLU0-SMTP987CC4C7A51BACFD64A89ED84E0@phx.gbl><282BBE8A501E1F4DA9C775F964BB21FE3E73D5C3BB@GRFMBX704BA020.griffon.local> <BLU0-SMTP78E9CEA7E415D708D2582D84A0@phx.gbl> <5661758E3E93364685B91DD8272F287602839CDF@S4DE8PSAAQC.mitte.t-com.de>
In-Reply-To: <5661758E3E93364685B91DD8272F287602839CDF@S4DE8PSAAQC.mitte.t-com.de>
Accept-Language: en-US, it-IT
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, it-IT
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "B.Witschurke@telekom.de" <B.Witschurke@telekom.de>, "ancp@ietf.org" <ancp@ietf.org>
Subject: Re: [ANCP] Small ANCP issues -- definition of sub-TLV
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list <ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>, <mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>, <mailto:ancp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Feb 2010 11:03:03 -0000

Hi All,
        I am not sure I understood this discussion, because last entry of t=
he IANA section in the ancp-protocol does not contain any multicast specifi=
c sub-TLVs all the sub-TLVs are related to the other use cases.


Regards,
Roberta


-----Original Message-----
From: HaagT@telekom.de [mailto:HaagT@telekom.de]
Sent: Tuesday, February 16, 2010 1:33 PM
To: tom111.taylor@bell.net; Maglione Roberta
Cc: ancp@ietf.org; B.Witschurke@telekom.de
Subject: AW: [ANCP] Small ANCP issues -- definition of sub-TLV


 All,

may be didn't get the whole issue. But as Roberta indicated a change in fun=
damental TLV structure of a port status message such as TLVs which are alre=
ady used for basic port information like net data rates is not acceptable.

If changes only belong to multicast extensions may be considered because on=
ly one use case is affected.

Regards
Thomas

-----Urspr=FCngliche Nachricht-----
Von: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] Im Auftrag von To=
m Taylor
Gesendet: Montag, 15. Februar 2010 16:16
An: Maglione Roberta
Cc: ancp@ietf.org
Betreff: Re: [ANCP] Small ANCP issues -- definition of sub-TLV

The change will have zero impact because the type codes don't overlap. The
problem in distinguishing between TLVs and sub-TLVs came from something I d=
id in
the multicast extensions document. I declared some structures to be sub-TLV=
s,
hence local to a particular TLV. I started assigning type codes beginning w=
ith
0x01, figuring it was a local numbering space. But a receiver parsing the
message can't tell whether that is TLV 0x01 (defined in the base document) =
or
sub-TLV 0x01 (specific to the given TLV). The conclusion was that the TLVs =
and
sub-TLVs had to share the same type code space. Hence there is no need to
distinguish them. In fact, in my latest edit of the multicast extensions
document, I redefined the sub-TLVs to have potentially broader usage.

Maglione Roberta wrote:
> Hi Tom,
>         I think I'm missing something here:
> Last IANA section contains sub-TLVs like " Actual-Net-Data-Upstream", " A=
ctual-Net-Data-Rate-Downstream" and these sub-TLVs were present since the i=
nitial version of the document. Are you proposing to change these sub-TLVs =
to TLVs?
> I'm not familiar with this type of details but wouldn't such a change imp=
act current implementations?
> Thanks,
> Regards,
> Roberta
>
>
> -----Original Message-----
> From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of T=
om Taylor
> Sent: Thursday, February 11, 2010 3:10 PM
> To: Wojciech Dec (wdec)
> Cc: ancp@ietf.org
> Subject: Re: [ANCP] Small ANCP issues -- definition of sub-TLV
>
> The last entry in the current IANA section is a sub-TLV type registry. Th=
at
> should be absorbed into the TLV registry.
>
> Wojciech Dec (wdec) wrote:
>>
>>> -----Original Message-----
>>> From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On
>>> Behalf Of Tom Taylor
>>> Sent: 10 February 2010 22:46
>>> To: ancp@ietf.org
>>> Subject: Re: [ANCP] Small ANCP issues -- definition of sub-TLV
>>>
>>> I've decided this is a bad idea. The basic problem is how the
>>> receiver distinguishes between encapsulated TLVs and sub-TLVs
>>> within the same TLV. My conclusion is that "sub-TLVs" should
>>> all share the same type code space, which means changes in
>>> presentation in the base document (I think the actual type
>>> codes can stay the same) and changes in both type code values
>>> and presentation in the multicast extensions document.
>>>
>>> The definition of a sub-TLV is a TLV that happens to be
>>> encapsulated in another TLV. It may or may not occur on its
>>> own in a different context.
>> I believe that this is inline with the intent to try to get "re-usable"
>> information elements (to avoid calling them TLVs or sub-TLVs). What
>> changes in the base document you think will be required?
>>
>> Regards,
>> Woj.
>>
>>> Tom Taylor
>>> Multicast extensions co-editor
>>>
>>> Tom Taylor wrote:
>>>> I forgot to say as part of my proposal for sub-TLVs that the type
>>>> number for a sub-TLV is scoped to the specific TLV rather
>>> than the set of TLVs.
>>>> That is, the set of sub-TLV type numbers for any given TLV
>>> always runs
>>>> from 0x01 up.
>>>>
>>> ...
>>> _______________________________________________
>>> ANCP mailing list
>>> ANCP@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ancp
>>>
>>
> _______________________________________________
> ANCP mailing list
> ANCP@ietf.org
> https://www.ietf.org/mailman/listinfo/ancp
>
> Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle p=
ersone indicate. La diffusione, copia o qualsiasi altra azione derivante da=
lla conoscenza di queste informazioni sono rigorosamente vietate. Qualora a=
bbiate ricevuto questo documento per errore siete cortesemente pregati di d=
arne immediata comunicazione al mittente e di provvedere alla sua distruzio=
ne, Grazie.
>
> This e-mail and any attachments is confidential and may contain privilege=
d information intended for the addressee(s) only. Dissemination, copying, p=
rinting or use by anybody else is unauthorised. If you are not the intended=
 recipient, please delete this message and any attachments and advise the s=
ender by return e-mail, Thanks.
>
>
>
_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp

Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle per=
sone indicate. La diffusione, copia o qualsiasi altra azione derivante dall=
a conoscenza di queste informazioni sono rigorosamente vietate. Qualora abb=
iate ricevuto questo documento per errore siete cortesemente pregati di dar=
ne immediata comunicazione al mittente e di provvedere alla sua distruzione=
, Grazie.

This e-mail and any attachments is confidential and may contain privileged =
information intended for the addressee(s) only. Dissemination, copying, pri=
nting or use by anybody else is unauthorised. If you are not the intended r=
ecipient, please delete this message and any attachments and advise the sen=
der by return e-mail, Thanks.


From tom111.taylor@bell.net  Mon Feb 22 03:33:47 2010
Return-Path: <tom111.taylor@bell.net>
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0043428C22A for <ancp@core3.amsl.com>; Mon, 22 Feb 2010 03:33:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.133
X-Spam-Level: 
X-Spam-Status: No, score=0.133 tagged_above=-999 required=5 tests=[AWL=-0.671,  BAYES_50=0.001, MSGID_FROM_MTA_HEADER=0.803]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cGXz7t3y5A+P for <ancp@core3.amsl.com>; Mon, 22 Feb 2010 03:33:46 -0800 (PST)
Received: from blu0-omc3-s17.blu0.hotmail.com (blu0-omc3-s17.blu0.hotmail.com [65.55.116.92]) by core3.amsl.com (Postfix) with ESMTP id 387A628C1B7 for <ancp@ietf.org>; Mon, 22 Feb 2010 03:33:46 -0800 (PST)
Received: from BLU0-SMTP46 ([65.55.116.72]) by blu0-omc3-s17.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 22 Feb 2010 03:35:44 -0800
X-Originating-IP: [76.64.153.220]
X-Originating-Email: [tom111.taylor@bell.net]
Message-ID: <BLU0-SMTP46344DE47B2F70531F08B7D8430@phx.gbl>
Received: from [192.168.2.11] ([76.64.153.220]) by BLU0-SMTP46.blu0.hotmail.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Mon, 22 Feb 2010 03:35:44 -0800
Date: Mon, 22 Feb 2010 06:35:41 -0500
From: Tom Taylor <tom111.taylor@bell.net>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Maglione Roberta <roberta.maglione@telecomitalia.it>
References: <4B71B61E.6000301@bell.net><BLU0-SMTP883E13C3EEC9F708E8C6FBD8500@phx.gbl>	<BLU0-SMTP99403FACE684B095329E67D84F0@phx.gbl>	<A16B9A4922C4A544A94565E870362B5001385580@XMB-AMS-111.cisco.com><BLU0-SMTP987CC4C7A51BACFD64A89ED84E0@phx.gbl><282BBE8A501E1F4DA9C775F964BB21FE3E73D5C3BB@GRFMBX704BA020.griffon.local> <BLU0-SMTP78E9CEA7E415D708D2582D84A0@phx.gbl> <5661758E3E93364685B91DD8272F287602839CDF@S4DE8PSAAQC.mitte.t-com.de> <282BBE8A501E1F4DA9C775F964BB21FE3E73D5C3E1@GRFMBX704BA020.griffon.local>
In-Reply-To: <282BBE8A501E1F4DA9C775F964BB21FE3E73D5C3E1@GRFMBX704BA020.griffon.local>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 22 Feb 2010 11:35:44.0242 (UTC) FILETIME=[2B6AD520:01CAB3B3]
Cc: "HaagT@telekom.de" <HaagT@telekom.de>, "B.Witschurke@telekom.de" <B.Witschurke@telekom.de>, "ancp@ietf.org" <ancp@ietf.org>
Subject: Re: [ANCP] Small ANCP issues -- definition of sub-TLV
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list <ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>, <mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>, <mailto:ancp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Feb 2010 11:33:47 -0000

Let me state this again.

You need some way for the parser at the receiving end to determine what is next 
in the message body, and that something is the TLV/sub-TLV type code. Unless 
there is some other semantic means of distinguishing a TLV from a sub-TLV, that 
means the TLVs and sub-TLVs have to share the same type code space. In other 
words, a sub-TLV cannot have the same type code as a TLV.

In the base protocol document, that condition is met. In the -01 version of the 
multicast extensions document, that condition is not met.  Hence the multicast 
extensions document has to change. The base document does not have to change on 
that ground alone. (I should say that there are errors in the base document 
where sometimes an assignment is 10 (e.g), somewhere else it is 0x10.)

Now I don't know why the original authors of the base document took the trouble 
to distinguish sub-TLVs from TLVs, or was it my compilation of IANA requirements 
that was responsible? But if the type codes share the same numbering space, why 
bother to put them into a separate IANA registry? I would point out that the 
same data structure can be a TLV or a sub-TLV, for example, if it is appended to 
the Status-Info TLV as diagnostic information. There are lots of other examples.

There is one technical issue in all this. TLVs are padded to a word boundary. I 
seem to recall that somewhere some text said that sub-TLVs are run together 
without intervening padding. We'll have to decide which rule applies.

Tom


Maglione Roberta wrote:
> Hi All,
>         I am not sure I understood this discussion, because last entry of the IANA section in the ancp-protocol does not contain any multicast specific sub-TLVs all the sub-TLVs are related to the other use cases.
> 
...

From roberta.maglione@telecomitalia.it  Wed Feb 24 01:27:52 2010
Return-Path: <roberta.maglione@telecomitalia.it>
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 604183A818D for <ancp@core3.amsl.com>; Wed, 24 Feb 2010 01:27:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.094
X-Spam-Level: 
X-Spam-Status: No, score=-0.094 tagged_above=-999 required=5 tests=[AWL=0.625,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LKsQ7sppyFXS for <ancp@core3.amsl.com>; Wed, 24 Feb 2010 01:27:51 -0800 (PST)
Received: from GRFEDG701BA020.telecomitalia.it (grfedg701ba020.telecomitalia.it [156.54.233.200]) by core3.amsl.com (Postfix) with ESMTP id 0948D3A8210 for <ancp@ietf.org>; Wed, 24 Feb 2010 01:27:51 -0800 (PST)
Received: from grfhub704ba020.griffon.local (10.188.101.117) by GRFEDG701BA020.telecomitalia.it (10.188.45.100) with Microsoft SMTP Server (TLS) id 8.2.176.0; Wed, 24 Feb 2010 10:29:55 +0100
Received: from GRFMBX704BA020.griffon.local ([10.188.101.15]) by grfhub704ba020.griffon.local ([10.188.101.117]) with mapi; Wed, 24 Feb 2010 10:29:55 +0100
From: Maglione Roberta <roberta.maglione@telecomitalia.it>
To: 'Tom Taylor' <tom111.taylor@bell.net>
Date: Wed, 24 Feb 2010 10:29:55 +0100
Thread-Topic: [ANCP] Small ANCP issues -- definition of sub-TLV
Thread-Index: AcqzszxV3cVSGM2PQNSm+KlaE/x9swBf9k3w
Message-ID: <282BBE8A501E1F4DA9C775F964BB21FE3E7C351630@GRFMBX704BA020.griffon.local>
References: <4B71B61E.6000301@bell.net><BLU0-SMTP883E13C3EEC9F708E8C6FBD8500@phx.gbl> <BLU0-SMTP99403FACE684B095329E67D84F0@phx.gbl> <A16B9A4922C4A544A94565E870362B5001385580@XMB-AMS-111.cisco.com><BLU0-SMTP987CC4C7A51BACFD64A89ED84E0@phx.gbl><282BBE8A501E1F4DA9C775F964BB21FE3E73D5C3BB@GRFMBX704BA020.griffon.local> <BLU0-SMTP78E9CEA7E415D708D2582D84A0@phx.gbl> <5661758E3E93364685B91DD8272F287602839CDF@S4DE8PSAAQC.mitte.t-com.de> <282BBE8A501E1F4DA9C775F964BB21FE3E73D5C3E1@GRFMBX704BA020.griffon.local> <BLU0-SMTP46344DE47B2F70531F08B7D8430@phx.gbl>
In-Reply-To: <BLU0-SMTP46344DE47B2F70531F08B7D8430@phx.gbl>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "HaagT@telekom.de" <HaagT@telekom.de>, "B.Witschurke@telekom.de" <B.Witschurke@telekom.de>, "ancp@ietf.org" <ancp@ietf.org>
Subject: Re: [ANCP] Small ANCP issues -- definition of sub-TLV
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list <ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>, <mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>, <mailto:ancp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Feb 2010 09:27:52 -0000

Hi Tom,
    thanks  for the clarification, the issue is clear to me now.
As you pointed out that this change may imply one technical issue, I think =
we should get the WG consensus before modifying the ancp protocol draft.

Regards,
Roberta


-----Original Message-----
From: Tom Taylor [mailto:tom111.taylor@bell.net]
Sent: Monday, February 22, 2010 12:36 PM
To: Maglione Roberta
Cc: HaagT@telekom.de; ancp@ietf.org; B.Witschurke@telekom.de
Subject: Re: [ANCP] Small ANCP issues -- definition of sub-TLV

Let me state this again.

You need some way for the parser at the receiving end to determine what is =
next
in the message body, and that something is the TLV/sub-TLV type code. Unles=
s
there is some other semantic means of distinguishing a TLV from a sub-TLV, =
that
means the TLVs and sub-TLVs have to share the same type code space. In othe=
r
words, a sub-TLV cannot have the same type code as a TLV.

In the base protocol document, that condition is met. In the -01 version of=
 the
multicast extensions document, that condition is not met.  Hence the multic=
ast
extensions document has to change. The base document does not have to chang=
e on
that ground alone. (I should say that there are errors in the base document
where sometimes an assignment is 10 (e.g), somewhere else it is 0x10.)

Now I don't know why the original authors of the base document took the tro=
uble
to distinguish sub-TLVs from TLVs, or was it my compilation of IANA require=
ments
that was responsible? But if the type codes share the same numbering space,=
 why
bother to put them into a separate IANA registry? I would point out that th=
e
same data structure can be a TLV or a sub-TLV, for example, if it is append=
ed to
the Status-Info TLV as diagnostic information. There are lots of other exam=
ples.

There is one technical issue in all this. TLVs are padded to a word boundar=
y. I
seem to recall that somewhere some text said that sub-TLVs are run together
without intervening padding. We'll have to decide which rule applies.

Tom


Maglione Roberta wrote:
> Hi All,
>         I am not sure I understood this discussion, because last entry of=
 the IANA section in the ancp-protocol does not contain any multicast speci=
fic sub-TLVs all the sub-TLVs are related to the other use cases.
>
...

Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle per=
sone indicate. La diffusione, copia o qualsiasi altra azione derivante dall=
a conoscenza di queste informazioni sono rigorosamente vietate. Qualora abb=
iate ricevuto questo documento per errore siete cortesemente pregati di dar=
ne immediata comunicazione al mittente e di provvedere alla sua distruzione=
, Grazie.

This e-mail and any attachments is confidential and may contain privileged =
information intended for the addressee(s) only. Dissemination, copying, pri=
nting or use by anybody else is unauthorised. If you are not the intended r=
ecipient, please delete this message and any attachments and advise the sen=
der by return e-mail, Thanks.


From shrirao@cisco.com  Thu Feb 25 00:31:17 2010
Return-Path: <shrirao@cisco.com>
X-Original-To: ancp@core3.amsl.com
Delivered-To: ancp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3319B3A69BE for <ancp@core3.amsl.com>; Thu, 25 Feb 2010 00:31:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZgCxX3oGOMPY for <ancp@core3.amsl.com>; Thu, 25 Feb 2010 00:31:16 -0800 (PST)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id 03C5928C2D6 for <ancp@ietf.org>; Thu, 25 Feb 2010 00:31:03 -0800 (PST)
Authentication-Results: sj-iport-4.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAFPEhUtAaHte/2dsb2JhbACbFXOjD5hLhHMEgxU
X-IronPort-AV: E=Sophos;i="4.49,537,1262563200"; d="scan'208";a="92365773"
Received: from hkg-core-1.cisco.com ([64.104.123.94]) by sj-iport-4.cisco.com with ESMTP; 25 Feb 2010 08:33:12 +0000
Received: from xbh-bgl-411.cisco.com (xbh-bgl-411.cisco.com [72.163.129.201]) by hkg-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o1P8XBse022112 for <ancp@ietf.org>; Thu, 25 Feb 2010 08:33:11 GMT
Received: from xmb-bgl-416.cisco.com ([72.163.129.212]) by xbh-bgl-411.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 25 Feb 2010 14:03:10 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 25 Feb 2010 14:03:10 +0530
Message-ID: <C6720CBB6D4F684D9FB8417C685FE80C01C699FD@XMB-BGL-416.cisco.com>
In-Reply-To: <BLU0-SMTP79DB448AB4CD4075A8C76DD8490@phx.gbl>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ANCP] Soliciting feedback on the ANCP Graceful restart draft 
Thread-Index: AcqvJi4zf8hqNptQRp68s2CRNkcgTAGzYwAQ
References: <BLU0-SMTP79DB448AB4CD4075A8C76DD8490@phx.gbl>
From: "Shridhar Rao (shrirao)" <shrirao@cisco.com>
To: <ancp@ietf.org>
X-OriginalArrivalTime: 25 Feb 2010 08:33:11.0031 (UTC) FILETIME=[2A08B870:01CAB5F5]
Subject: [ANCP]  Soliciting feedback on the ANCP Graceful restart draft
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list <ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>, <mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>, <mailto:ancp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Feb 2010 08:31:17 -0000

=20
https://datatracker.ietf.org/doc/draft-ancp-restart/

Hello,
We are working on a update for this draft (which I will publish after
the Anaheim meeting) and like to get any feedback from the Working group
so I can consider them before publishing the new revision.=20
Please send your comments if any.
Regards,
-shridhar


From root@core3.amsl.com  Fri Feb 26 08:00:01 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: ancp@ietf.org
Delivered-To: ancp@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 840133A87F9; Fri, 26 Feb 2010 08:00:01 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100226160001.840133A87F9@core3.amsl.com>
Date: Fri, 26 Feb 2010 08:00:01 -0800 (PST)
Cc: ancp@ietf.org
Subject: [ANCP] I-D Action:draft-ietf-ancp-protocol-09.txt
X-BeenThere: ancp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Access Node Control Protocol working group mailing list <ancp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ancp>, <mailto:ancp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ancp>
List-Post: <mailto:ancp@ietf.org>
List-Help: <mailto:ancp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ancp>, <mailto:ancp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Feb 2010 16:00:01 -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           : Protocol for Access Node Control Mechanism in Broadband Networks
	Author(s)       : S. Wadhwa, et al.
	Filename        : draft-ietf-ancp-protocol-09.txt
	Pages           : 58
	Date            : 2010-02-26

This document describes proposed extensions to the GSMPv3 protocol to
allow its use in a broadband environment, as a control plane between
Access Nodes (e.g.  DSLAM) and Broadband Network Gateways (e.g.
NAS).  These proposed extensions are required to realize a protocol
for "Access Node Control" mechanism as described in [ANCP-FRAMEWORK].
The resulting protocol with the proposed extensions to GSMPv3
[RFC3292] is referred to as "Access Node Control Protocol" (ANCP).
This document currently focuses on specific use cases of access node
control mechanism for topology discovery, line configuration, and OAM
as described in ANCP framework document [ANCP-FRAMEWORK].  It is
intended to be augmented by additional protocol specification for
future use cases considered in scope by the ANCP charter.

ANCP framework document [ANCP-FRAMEWORK] describes the ANCP use-cases
in detail.  Illustrative text for the use-cases is included here to
help the protocol implementer understand the greater context of ANCP
protocol interactions.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ancp-protocol-09.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-protocol-09.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2010-02-26075739.I-D@ietf.org>


--NextPart--
