From ancp-bounces@ietf.org  Thu May  1 03:34:34 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id EA8323A68CA;
	Thu,  1 May 2008 03:34:34 -0700 (PDT)
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 B930B3A68CA
	for <ancp@core3.amsl.com>; Thu,  1 May 2008 03:34:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.39
X-Spam-Level: 
X-Spam-Status: No, score=0.39 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, 
	HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, 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 CumxXNpnkBoG for <ancp@core3.amsl.com>;
	Thu,  1 May 2008 03:34:26 -0700 (PDT)
Received: from szxga01-in.huawei.com (unknown [61.144.161.53])
	by core3.amsl.com (Postfix) with ESMTP id 2A9E03A6CE9
	for <ancp@ietf.org>; Thu,  1 May 2008 03:33:36 -0700 (PDT)
Received: from huawei.com (szxga01-in [172.24.2.3])
	by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0K060020DQNRWD@szxga01-in.huawei.com> for
	ancp@ietf.org; Thu, 01 May 2008 18:33:28 +0800 (CST)
Received: from huawei.com ([172.24.1.24])
	by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0K0600HKGQNR3W@szxga01-in.huawei.com> for
	ancp@ietf.org; Thu, 01 May 2008 18:33:27 +0800 (CST)
Received: from h36145c ([10.70.76.115])
	by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0K0600MJTQNQDY@szxml04-in.huawei.com> for
	ancp@ietf.org; Thu, 01 May 2008 18:33:27 +0800 (CST)
Date: Thu, 01 May 2008 18:33:25 +0800
From: Fortune HUANG <fqhuang@huawei.com>
To: Peter Arberg <parberg@redback.com>, Sanjay Wadhwa <swadhwa@juniper.net>,
	Tina TSOU <tena@huawei.com>,
	Maglione Roberta <roberta.maglione@telecomitalia.it>,
	"Wojciech Dec (wdec)" <wdec@cisco.com>
Message-id: <080101c8ab76$c991b800$734c460a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
X-Priority: 3
X-MSMail-priority: Normal
References: <48C276B536524E478C659685995F6AA539DBBBE370@RBSJX.ad.redback.com>
	<9BD5D7887235424FA97DFC223CAE3C280AB43A10@proton.jnpr.net>
	<48C276B536524E478C659685995F6AA539DBBBE577@RBSJX.ad.redback.com>
Cc: ancp@ietf.org
Subject: Re: [ANCP] question regarding  Labels in ANCP port up messages
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/pipermail/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>
Content-Type: multipart/mixed; boundary="===============1760556148=="
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1760556148==
Content-type: multipart/alternative;
 boundary="Boundary_(ID_IrSrLJGI/XZeLKrjlwhrPg)"

This is a multi-part message in MIME format.

--Boundary_(ID_IrSrLJGI/XZeLKrjlwhrPg)
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT

Peter,

I think ANCP and GSMP are independent with each other, and they can be developed parallelly.
RFC3292 is the only legal baseline version of GSMP which makes sense to ANCP, because ANCP
uses the contents of RFC3292 as a starting point.
However, after started, ANCP is developed independently with the development of GSMP. 
And the later versions of GSMP have nothing to do with ANCP.

Therefore, I think draft-ietf-gsmp-v3-base-spec-08 has nothing to do with ANCP because it
is not a legal starting point of ANCP.

Furthermore, I think it is the responsibility of the newer draft to keep compatible with the older one.
Since the draft-ietf-gsmp-v3-base-spec-08 is newer than RFC3292, I think we should make 
draft-ietf-gsmp-v3-base-spec-08 compatible with RFC3292, and accordingly the implementation
could be backward compatible.

cheers,
Fortune
  ----- Original Message ----- 
  From: Peter Arberg 
  To: Sanjay Wadhwa ; Tina TSOU ; Maglione Roberta ; Wojciech Dec (wdec) 
  Cc: ancp@ietf.org 
  Sent: Thursday, May 01, 2008 7:20 AM
  Subject: Re: [ANCP] question regarding Labels in ANCP port up messages


  Sanjay,

  What do you mean "why I reference an old draft"  ????????????

  I'm surprised you even ask...  please take a look at YOUR own internet-draft that most
  of the ANCP working implementations are based on, in case you do not have this old
  internet-draft, I have attached it to the document.

  If you look at the reference for this ancp-draft, you will see that in the reference section
  you point to this old gsmp-draft...  Yes and I know this has been changed in the later
  versions of the ANCP draft, but that do not change the fact that many of the implementations
  today was developed when the attached draft was current.

  I think a very good question is brought up here, and that is what is implemented and
  running in networks today ?

  My take on this is that when the reference was change from the old gsmp-draft to the older
  RFC3292, apparently no one paid any attention to the fact the label definition in the event
  message was different and not compatible.

  What current implementations do today is an important factor in this discussion, and I think
  it is time to come to realization that we might need a new version number for ANCP since
  it continues to look like there is big holes open for interpretation. So if I did a ANCP
  implementation there is bound to be interoperability issues with existing implementations
  runnig.

  cheers,
  Peter






----------------------------------------------------------------------------
    From: Sanjay Wadhwa [mailto:swadhwa@juniper.net] 
    Sent: 30. april 2008 14:42
    To: Peter Arberg; Tina TSOU; Maglione Roberta; Wojciech Dec (wdec)
    Cc: ancp@ietf.org
    Subject: RE: [ANCP] question regarding Labels in ANCP port up messages


    Peter
      The ANCP draft as it currently stands is based on RFC3292. It provides extensions and modifications to relevant constructs in RFC3292. There is no mention (implicit or explicit) of expired GSMP drafts in the ANCP draft. In order to implement the ANCP draft, I am not sure why one would look at the expired GSMP drafts. Do you see a reason to do this based on anything that you read in the ANCP draft? Bringing up reference to expired gsmp draft in this thread just adds to the confusion. For GSMPv3 objects in the messages (such as Label Type), one has to look at RFC3292 (this is clearly stated in the ANCP draft - section 2 and I am quoting it below) :

    ANCP uses a subset of GSMPv3 messages to implement currently defined use-cases. These relevant GSMPv3 messages are identified in section 5. GSMPv3 procedures with suitable extensions, as used by ANCP, are described in sections 5.1, 5.2 and 5.3. GSMPv3 general extensions and GSMPv3 message specific extensions required by ANCP are described in sub-sections of 5.4. In addition to specifying extensions and modifications to relevant GSMP messages applicable to ANCP, this draft also defines the usage of these messages by ANCP, and indicates the values that ANCP should set for relevant fields in these GSMP messages. However, to understand the basic semantics of various fields in GSMP messages, the reader is referred to [4]. => RFC 3292.

    What existing implementations currently do is an important but separate issue. These implementations for most part precede the current ANCP draft. It is fine to poll where these implementations diverge from the current draft. It is then upto the implementations (including the one that I am somewhat familiar with) to work towards compliance with the draft. 

    On the following points from  Woj:

    Woj>2) The current version of the spec is not accurate, and does not reflect the fact that the known implementations follow the label field definition from draft-gsmpv3-base-spec.

    It is not for the protocol draft to point out what current implementations do.  The best we can do is to further clarify in the draft that type and value fields of the Label object (defined in RFC3292) should be set to 0 in the port-up message (we already mention the lable object as a whole should be set to all 0s). 

    Woj> This would be a good thing for the WG to discuss. There most evidently is a fair amount of "dead wood" in the current spec, ie stuff that nobody yet implements or cares about.  In the former case, we could re-cast that material using the new notions/extensions, in the latter case simply chop it out.

    I agree. We are based on GSMPv3 (RFC3292)  messages, and obviously not everything in these messages is leveraged by ANCP.  However, the sync rate and OAM uses-cases are implemented and in use (ideally we should leave these alone...i.e. no change beyond adding more clarity if needed). For anything new (such as multicast) we are defining new messages (no legacy).  

    -Sanjay

    >-----Original Message-----
    >From: Peter Arberg [mailto:parberg@redback.com]
    >Sent: Wednesday, April 30, 2008 3:56 PM
    >To: Tina TSOU; Maglione Roberta; Sanjay Wadhwa; Wojciech Dec (wdec)
    >Cc: ancp@ietf.org
    >Subject: RE: [ANCP] question regarding Labels in ANCP port up messages
    >
    >
    >Hi,
    >
    >some times I think it is amazing we ever got interoperability
    >of ANCP :-)
    >because looking at the label discussion is a very good example that the
    >whole GSMP - ANCP reference have not worked very well.
    >
    >In the ANCP draft, section 5.4.2 the event message is shown like this:
    >
    >0                   1                   2                   3
    >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
    >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    >| Vers  |  Sub  | Message Type  | Result|        Code           |
    >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    >| Partition ID  |            Transaction Identifier             |
    >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    >|I|      SubMessage Number      |           Length              |
    >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    >|                             Port                              |
    >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    >|                      Port Session Number                      |
    >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    >|                     Event Sequence Number                     |
    >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    >|x|S|x|x|                                                       |
    >+-+-+-+-+                     Label                             |
    >~                                                               ~
    >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    >|x|x|x|x|x|x|x|x| Message Type  |   Tech Type   | Block Length  |
    >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    >|                                                               |
    >~                         Extension Value                       ~
    >|                                                               |
    >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    >
    >
    >This is the exact same event message defined in
    >draft-ietf-gsmp-v3-base-spec-08.txt  section 11.
    >
    >And in this gsmp-draft, section 5.1.3 the label space is defined
    >as minimum 8 bytes if the length=0 and as such no value, and this
    >is because the gsmp-draft has a new "label adaptaion" field.
    >
    >
    >
    >BUT in RFC3292 the event message is show in section 9, like this:
    >
    >0                   1                   2                   3
    >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
    >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    >|    Version    | Message Type  |    Result     |     Code      |
    >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    >| Partition ID  |            Transaction Identifier             |
    >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    >|I|      SubMessage Number      |           Length              |
    >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    >|                             Port                              |
    >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    >|                      Port Session Number                      |
    >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    >|                     Event Sequence Number                     |
    >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    >|x|S|x|x|                                                       |
    >+-+-+-+-+                     Label                             |
    >~                                                               ~
    >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    >
    >
    >So a different Event Message picture/definition than what is shown
    >in the ANCP draft, and in RFC3292 section 3.1.3 the label field
    >is defined as 4 bytes if length=0 and as such no value.
    >
    >
    >
    >So I very much agree with Woj that we need this issue to be resolved,
    >and proabably a show of hands what is actually done in different
    >implementations, so we can nail down how the event message is
    >suppose to look like in ANCP.
    >
    >
    >I know at least 1 implementation which uses 8 bytes for the
    >label field.
    >
    >
    >cheers,
    >Peter
    >
    >
    >
    >
    >
    >
    >________________________________
    >
    >        From: ancp-bounces@ietf.org
    >[mailto:ancp-bounces@ietf.org] On Behalf Of Tina TSOU
    >        Sent: 30. april 2008 00:19
    >        To: Maglione Roberta; Sanjay Wadhwa; Wojciech Dec (wdec)
    >        Cc: ancp@ietf.org
    >        Subject: Re: [ANCP] question regarding Labels in ANCP
    >port up messages
    >
    >
    >        Hi all,
    >        It is clear to me that if Label Length is filled as 0,
    >there is nothing to be filled into Label Value. The whole
    >Label part is 4 bytes, not 8 bytes.
    >
    >        Cheers from the last working day before Labor's Day
    >holidays in some countries:)
    >
    >        Tina
    >
    >                ----- Original Message -----
    >                From: Wojciech Dec (wdec) <mailto:wdec@cisco.com>
    >                To: Sanjay Wadhwa <mailto:swadhwa@juniper.net>
    > ; Maglione Roberta <mailto:roberta.maglione@telecomitalia.it>
    >                Cc: ancp@ietf.org
    >                Sent: Wednesday, April 30, 2008 1:12 AM
    >                Subject: Re: [ANCP] question regarding Labels
    >in ANCP port up messages
    >
    >                Sanjay, All,
    >
    >                What is stated below runs counter to at least
    >a handful of ANCP
    >                implementations, all of which are known to be
    >interoperable.
    >                There are really two options:
    >                1) The current version of the spec is correct,
    >and the known
    >                interoperable implementations do not follow it
    >                2) The current version of the spec is not
    >accurate, and does not reflect
    >                the fact that the known implementations follow
    >the label field
    >                definition from draft-gsmpv3-base-spec.
    >
    >                I would like to ask you, as the lead editor of
    >the spec, to work with
    >                the WG in resolving what the problem is, and
    >clearing up what the WG
    >                spec says about and if 1) holds to be true,
    >then proposing an
    >                interoperability fix.
    >
    >                In either case, the issue highlights the fact
    >that there is still
    >                lingering confusion as to the dependencies
    >ANCP has on rfc3292, or
    >                draft-gsmpv3-base-spec, or both. It seems to
    >be in the best interest of
    >                all to address these.
    >
    >                Regards,
    >                Woj.
    >
    >                > -----Original Message-----
    >                > From: Sanjay Wadhwa [mailto:swadhwa@juniper.net]
    >                > Sent: 29 April 2008 17:29
    >                > To: Maglione Roberta
    >                > Cc: Wojciech Dec (wdec); ancp@ietf.org;
    >Philippe Champagne (pchamp)
    >                > Subject: RE: question regarding Labels in
    >ANCP port up messages
    >                >
    >                > Hi Maglione
    >                >   Yes, the label format is as defined in RFC
    >3292. The ANCP draft is
    >                > based on RFC 3292 and proposes
    >extensions/modifications where
    >                > required.
    >                > This is clearly stated upfront both in the
    >abstract and in
    >                > section 2. In
    >                > section 5.4.2, it clearly  specifies the
    >format of "port up" message
    >                > (based on RFC 3292), and explicitly states
    >the label field
    >                > should be set
    >                > to 0. Following is what the draft currently states:
    >                >
    >                >
    >                > 5.4.2 Topology Discovery Extensions
    >                >
    >                > The GSMP Event message with PORT UP message
    >type (80) is used for
    >                > conveying DSL line attributes to the NAS.
    >The version field should be
    >                > set to 3, and the sub field should be set to
    >1. The I and subMessage
    >                > fields SHOULD be set to 1 to signify no
    >fragmentation. The Port and
    >                > Label fields should be set to 0.
    >                >
    >                >  0                   1                   2  
    >                3
    >                >          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
    >                >
    >                >
    >                >
    >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    >                >         | Vers  |  Sub  | Message Type  |
    >Result|        Code
    >                > |
    >                >
    >                >
    >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    >                >         | Partition ID  |           
    >Transaction Identifier
    >                > |
    >                >
    >                >
    >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    >                >         |I|      SubMessage Number      |   
    >       Length
    >                > |
    >                >
    >                >
    >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    >                >         |                             Port
    >                > |
    >                >
    >                >
    >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    >                >         |                      Port Session Number
    >                > |
    >                >
    >                >
    >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    >                >         |                     Event Sequence Number
    >                > |
    >                >
    >                >
    >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    >                >         |x|S|x|x|
    >                > |
    >                >         +-+-+-+-+                     Label
    >                > |
    >                >         ~
    >                > ~
    >                >
    >                >
    >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    >                >         |x|x|x|x|x|x|x|x| Message Type  |  
    >Tech Type   | Block Length
    >                > |
    >                >
    >                >
    >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    >                >         |
    >                > |
    >                >         ~                         Extension Value
    >                > ~
    >                >         |
    >                > |
    >                >
    >                >
    >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    >                >
    >                > When we say the label field should be set to
    >0, the intention
    >                > is for the
    >                > type and length fields in the label TLV to
    >be set to 0. We can
    >                > explicitly state this for clarity.
    >                >
    >                > -Sanjay
    >                >
    >                > >-----Original Message-----
    >                > >From: Maglione Roberta
    >[mailto:roberta.maglione@telecomitalia.it]
    >                > >Sent: Tuesday, April 29, 2008 8:06 AM
    >                > >To: Sanjay Wadhwa
    >                > >Cc: Wojciech Dec (wdec); ancp@ietf.org;
    >pchamp@cisco.com
    >                > >Subject: RE: question regarding Labels in
    >ANCP port up messages
    >                > >
    >                > >
    >                > >Hi Sanjay and All,
    >                > >     I was reading the current ancp
    >protocol draft in order to
    >                > > understand which should be the correct
    >format for the label
    >                > >field in the ancp port Up message.
    >                > >Actually as it was already pointed out in
    >the alias the draft
    >                > >in section 5.4.2 says "GSMP Event message
    >with PORT UP message
    >                > >type (80) is used"  thus I am assuming that
    >the label in the
    >                > >port UP message should follow the message
    >format defined in
    >                > >RFC 3292, section 3.1.3:
    >                > >
    >                > >    0                   1                  
    >2                   3
    >                > >    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
    >                > >  
    >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    >                > >   |x|S|x|x|       Label Type      |       
    >  Label Length         |
    >                > >  
    >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    >                > >   |                                       
    >                       |
    >                > >   ~                          Label Value  
    >                       ~
    >                > >   |                                       
    >                       |
    >                > >  
    >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    >                > >
    >                > >but from what I have seen different
    >implementations use
    >                > >different format for label field: in
    >particular several
    >                > >implementations use  a label format that is
    >similar to the one
    >                > >specified in the expired draft
    >draft-ietf-gsmp-v3-base-spec:
    >                > >
    >                > >     0                   1                 
    > 2                   3
    >                > >       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
    >                > >
    >                >
    >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    >                > >      |x|S|x|x|x|x|x|x|x|x|x|x|x|x|x|x|    
    >       Label
    >                > Type         |
    >                > >
    >                >
    >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    >                > >      |    Label Adaptation           |    
    >     Label
    >                > Length         |
    >                > >
    >                >
    >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    >                > >      |
    >                >          |
    >                > >      ~                          Label Value
    >                >          ~
    >                > >      |
    >                >          |
    >                > >
    >                >
    >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    >                > >
    >                > >
    >                > >Even if ancp does not care about the label
    >field, having this
    >                > >field somehow not clearly specified in the
    >current ancp draft
    >                > >can easily lead to interoperability issues,
    >thus I think it
    >                > >would be very helpful if you and/or the
    >other editors can
    >                > >clarify what should be the correct format
    >for the label field
    >                > >to be used in the ancp Port Up message.
    >                > >
    >                > >Thanks and best regards,
    >                > >Roberta
    >                > >
    >                > >________________________________________
    >                > >From: Philippe Champagne (pchamp) [pchamp@cisco.com]
    >                > >Sent: Thursday, April 24, 2008 7:14 PM
    >                > >To: Sanjay Wadhwa
    >                > >Cc: Maglione Roberta; Wojciech Dec (wdec);
    >ancp@ietf.org
    >                > >Subject: question regarding  Labels in ANCP
    >port up messages
    >                > >
    >                > >Hi Sanjay
    >                > >
    >                > >In section 5.4.2 of the draft, we have:
    >                > >
    >                > >
    >                > >         0                   1                   2
    >                >         3
    >                > >         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
    >                > >
    >                >
    >>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    >                > >        | Vers  |  Sub  | Message Type  |
    >Result|        Code
    >                > >         |
    >                > >
    >                >
    >>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    >                > >        | Partition ID  |           
    >Transaction Identifier
    >                > >         |
    >                > >
    >                >
    >>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    >                > >        |I|      SubMessage Number      |  
    >        Length
    >                > >         |
    >                > >
    >                >
    >>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    >                > >        |                             Port
    >                > >         |
    >                > >
    >                >
    >>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    >                > >        |                      Port Session Number
    >                > >         |
    >                > >
    >                >
    >>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    >                > >        |                     Event Sequence Number
    >                > >         |
    >                > >
    >                >
    >>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    >                > >        |x|S|x|x|
    >                > >         |
    >                > >        +-+-+-+-+                     Label
    >                > >         |
    >                > >        ~
    >                > >         ~
    >                > >
    >                >
    >>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    >                > >        |x|x|x|x|x|x|x|x| Message Type  |  
    >Tech Type   |
    >                > >Block Length  |
    >                > >
    >                >
    >>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    >                > >        |
    >                > >         |
    >                > >        ~                         Extension Value
    >                > >         ~
    >                > >        |
    >                > >         |
    >                > >
    >                >
    >>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    >                > >Where Label I suppose is taken from the RFC
    >3292, section
    >                > >3.1.3: (well, I'm guessing)
    >                > >
    >                > >   A summary of TLV labels supported in
    >this version of the
    >                > protocol is
    >                > >   listed below:
    >                > >
    >                > >      TLV Label      Type       Section Title
    >                > >      ---------      ----       -------------
    >                > >      ATM Label      0x100      ATM TLV Labels
    >                > >      FR Label       0x101      Frame Relay
    >TLV Labels
    >                > >      MPLS Gen Label 0x102      MPLS
    >Generic TLV Labels
    >                > >      FEC Label      0x103      FEC TLV Labels
    >                > >
    >                > >   All Labels will be designated as follow:
    >                > >
    >                > >    0                   1                  
    >2                   3
    >                > >    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
    >                > >  
    >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    >                > >   |x|S|x|x|       Label Type      |       
    >  Label Length         |
    >                > >  
    >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    >                > >   |                                       
    >                       |
    >                > >   ~                          Label Value  
    >                       ~
    >                > >   |                                       
    >                       |
    >                > >  
    >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
    >                > >
    >                > >      x: Reserved Flags.
    >                > >         These are generally used by
    >specific messages and will be
    >                > >         defined in those messages.
    >                > >
    >                > >      S: Stacked Label Indicator
    >                > >         Label Stacking is discussed below
    >in section 3.1.3.5
    >                > >
    >                > >      Label Type
    >                > >         A 12-bit field indicating the type
    >of label.
    >                > >
    >                > >      Label Length
    >                > >         A 16-bit field indicating the
    >length of the Label
    >                > Value field
    >                > >         in bytes.
    >                > >
    >                > >      Label Value
    >                > >         A variable length field that is an
    >integer number of 32 bit
    >                > >         words long.  The Label Value field
    >is interpreted
    >                > according to
    >                > >         the Label Type as described in the
    >following sections.
    >                > >
    >                > >
    >                > >The draft is a bit obscure about this and
    >since it doesn't
    >                > >specify much, it can lead to
    >misinterpretation for the unused
    >                > >part. Moreover, it would appear that
    >several implementations
    >                > >currently use another format for the label
    >field. Can you
    >                > >explain?  I mean, how come what's in the
    >current draft doesn't
    >                > >match what's known to be implemented?
    >                > >
    >                > >I'm still wondering why we carried over
    >pieces from GSMP that
    >                > >we do not intend to use.
    >                > >
    >                > >I would recommend that if we are to keep
    >them but not use
    >                > >them, we should mention precisely how we
    >intend not to use
    >                > >them: that is how many 0 filled bytes this
    >is expected to use
    >                > >
    >                > >The rfc 3292 doesn't cover the case where
    >this field is not used.
    >                > >
    >                > >Can you shed some ligths on this?
    >                > >
    >                > >Thanks
    >                > >Regards
    >                > >Phil
    >                > >
    >                > >
    >                > >
    >                >
    >>--------------------------------------------------------------------
    >                > >
    >                > >CONFIDENTIALITY NOTICE
    >                > >
    >                > >This message and its attachments are
    >addressed solely to the
    >                > >persons above and may contain confidential
    >information. If you
    >                > >have received the message in error, be
    >informed that any use
    >                > >of the content hereof is prohibited. Please
    >return it
    >                > >immediately to the sender and delete the
    >message. Should you
    >                > >have any questions, please contact us by replying to
    >                > >webmaster@telecomitalia.it.
    >                > >
    >                > >        Thank you
    >                > >
    >                > >                                       
    >www.telecomitalia.it
    >                > >
    >                >
    >>--------------------------------------------------------------------
    >                > >
    >                > >
    >                >
    >                _______________________________________________
    >                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

--Boundary_(ID_IrSrLJGI/XZeLKrjlwhrPg)
Content-type: text/html; charset=iso-8859-1
Content-transfer-encoding: 7BIT

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1561" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#cce8cf>
<DIV><FONT face=&#23435;&#20307; size=2>Peter,</FONT></DIV>
<DIV><FONT face=&#23435;&#20307; size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=&#23435;&#20307; size=2>I think ANCP and GSMP are independent with each other, 
and they can be developed parallelly.</FONT></DIV>
<DIV>
<DIV><FONT face=&#23435;&#20307; size=2>RFC3292 is&nbsp;the only&nbsp;legal baseline version 
of GSMP&nbsp;which makes sense&nbsp;to ANCP, because ANCP</FONT></DIV>
<DIV><FONT face=&#23435;&#20307; size=2>uses the contents of RFC3292 as a starting 
point.</FONT></DIV>
<DIV><FONT face=&#23435;&#20307; size=2>However, after&nbsp;started, </FONT><FONT face=&#23435;&#20307; 
size=2>ANCP is developed independently with the development of&nbsp;GSMP. 
</FONT></DIV>
<DIV><FONT face=&#23435;&#20307; size=2>And t</FONT><FONT face=&#23435;&#20307; size=2>he later </FONT><FONT 
face=&#23435;&#20307; size=2>versions of GSMP have nothing </FONT><FONT face=&#23435;&#20307; size=2>to do 
with ANCP.</FONT></DIV>
<DIV><FONT face=&#23435;&#20307; size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=&#23435;&#20307; size=2>Therefore, I think draft-ietf-gsmp-v3-base-spec-08 has 
nothing to do with ANCP because it</FONT></DIV>
<DIV><FONT face=&#23435;&#20307; size=2>is not a legal starting point of ANCP.</FONT></DIV>
<DIV><FONT face=&#23435;&#20307; size=2></FONT><FONT face=&#23435;&#20307; size=2><FONT face=&#23435;&#20307; size=2><FONT 
face=&#23435;&#20307; size=2></FONT></FONT>&nbsp;</DIV>
<DIV>
<DIV><FONT face=&#23435;&#20307; size=2><FONT face=&#23435;&#20307; size=2>Furthermore, I think it is the 
responsibility of the newer draft&nbsp;to keep&nbsp;compatible with the older 
one.</FONT></DIV>
<DIV>
<DIV></FONT><FONT face=&#23435;&#20307; size=2>Since the draft-ietf-gsmp-v3-base-spec-08 is 
newer than RFC3292, I think we should make </FONT></DIV>
<DIV><FONT face=&#23435;&#20307; size=2>draft-ietf-gsmp-v3-base-spec-08 compatible with 
RFC3292, and accordingly the implementation</FONT></DIV>
<DIV><FONT face=&#23435;&#20307; size=2>could be backward 
compatible.</FONT></DIV></DIV></FONT></DIV></DIV>
<DIV><FONT face=&#23435;&#20307; size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=&#23435;&#20307; size=2>cheers,</FONT></DIV>
<DIV><FONT face=&#23435;&#20307; size=2>Fortune</FONT></DIV>
<BLOCKQUOTE 
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
  <DIV style="FONT: 9pt &#23435;&#20307;">----- Original Message ----- </DIV>
  <DIV style="BACKGROUND: #e4e4e4; FONT: 9pt &#23435;&#20307;; font-color: black"><B>From:</B> 
  <A title=parberg@redback.com href="mailto:parberg@redback.com">Peter 
  Arberg</A> </DIV>
  <DIV style="FONT: 9pt &#23435;&#20307;"><B>To:</B> <A title=swadhwa@juniper.net 
  href="mailto:swadhwa@juniper.net">Sanjay Wadhwa</A> ; <A title=tena@huawei.com 
  href="mailto:tena@huawei.com">Tina TSOU</A> ; <A 
  title=roberta.maglione@telecomitalia.it 
  href="mailto:roberta.maglione@telecomitalia.it">Maglione Roberta</A> ; <A 
  title=wdec@cisco.com href="mailto:wdec@cisco.com">Wojciech Dec (wdec)</A> 
  </DIV>
  <DIV style="FONT: 9pt &#23435;&#20307;"><B>Cc:</B> <A title=ancp@ietf.org 
  href="mailto:ancp@ietf.org">ancp@ietf.org</A> </DIV>
  <DIV style="FONT: 9pt &#23435;&#20307;"><B>Sent:</B> Thursday, May 01, 2008 7:20 AM</DIV>
  <DIV style="FONT: 9pt &#23435;&#20307;"><B>Subject:</B> Re: [ANCP] question regarding Labels 
  in ANCP port up messages</DIV>
  <DIV><BR></DIV>
  <DIV dir=ltr align=left><SPAN class=062190723-30042008><FONT face=Arial 
  color=#0000ff size=2>Sanjay,</FONT></SPAN></DIV>
  <DIV dir=ltr align=left><SPAN class=062190723-30042008><FONT face=Arial 
  color=#0000ff size=2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=ltr align=left><SPAN class=062190723-30042008><FONT face=Arial 
  color=#0000ff size=2>What do you mean "why I reference an old draft"&nbsp; 
  ????????????</FONT></SPAN></DIV>
  <DIV dir=ltr align=left><SPAN class=062190723-30042008><FONT face=Arial 
  color=#0000ff size=2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=ltr align=left><SPAN class=062190723-30042008><FONT face=Arial 
  color=#0000ff size=2>I'm surprised you even ask...&nbsp; please take a look at 
  YOUR own internet-draft that most</FONT></SPAN></DIV>
  <DIV dir=ltr align=left><SPAN class=062190723-30042008><FONT face=Arial 
  color=#0000ff size=2>of the ANCP working implementations are based on, in case 
  you do not have this old</FONT></SPAN></DIV>
  <DIV dir=ltr align=left><SPAN class=062190723-30042008><FONT face=Arial 
  color=#0000ff size=2>internet-draft, I have attached it to the 
  document.</FONT></SPAN></DIV>
  <DIV dir=ltr align=left><SPAN class=062190723-30042008><FONT face=Arial 
  color=#0000ff size=2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=ltr align=left><SPAN class=062190723-30042008><FONT face=Arial 
  color=#0000ff size=2>If you look at the reference for this ancp-draft, you 
  will see that in the reference section</FONT></SPAN></DIV>
  <DIV dir=ltr align=left><SPAN class=062190723-30042008><FONT face=Arial 
  color=#0000ff size=2>you point to this old gsmp-draft...&nbsp; Yes and I know 
  this has been changed in the later</FONT></SPAN></DIV>
  <DIV dir=ltr align=left><SPAN class=062190723-30042008><FONT face=Arial 
  color=#0000ff size=2>versions of the ANCP draft, but that do not change the 
  fact that many of the implementations</FONT></SPAN></DIV>
  <DIV dir=ltr align=left><SPAN class=062190723-30042008><FONT face=Arial 
  color=#0000ff size=2>today was developed when the attached draft was 
  current.</FONT></SPAN></DIV>
  <DIV dir=ltr align=left><SPAN class=062190723-30042008><FONT face=Arial 
  color=#0000ff size=2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=ltr align=left><SPAN class=062190723-30042008><FONT face=Arial 
  color=#0000ff size=2>I think a very good question is brought up here, and that 
  is what is implemented and</FONT></SPAN></DIV>
  <DIV dir=ltr align=left><SPAN class=062190723-30042008><FONT face=Arial 
  color=#0000ff size=2>running in networks today ?</FONT></SPAN></DIV>
  <DIV dir=ltr align=left><SPAN class=062190723-30042008><FONT face=Arial 
  color=#0000ff size=2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=ltr align=left><SPAN class=062190723-30042008><FONT face=Arial 
  color=#0000ff size=2>My take on this is that when the reference was change 
  from the old gsmp-draft to the older</FONT></SPAN></DIV>
  <DIV dir=ltr align=left><SPAN class=062190723-30042008><FONT face=Arial 
  color=#0000ff size=2>RFC3292, apparently no one paid any attention to the fact 
  the label definition in the event</FONT></SPAN></DIV>
  <DIV dir=ltr align=left><SPAN class=062190723-30042008><FONT face=Arial 
  color=#0000ff size=2>message was different and not 
  compatible.</FONT></SPAN></DIV>
  <DIV dir=ltr align=left><SPAN class=062190723-30042008><FONT face=Arial 
  color=#0000ff size=2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=ltr align=left><SPAN class=062190723-30042008><FONT face=Arial 
  color=#0000ff size=2>What current implementations do today is an important 
  factor in this discussion, and I think</FONT></SPAN></DIV>
  <DIV dir=ltr align=left><SPAN class=062190723-30042008><FONT face=Arial 
  color=#0000ff size=2>it is time to come to realization that we might need a 
  new version number for ANCP since</FONT></SPAN></DIV>
  <DIV dir=ltr align=left><SPAN class=062190723-30042008><FONT face=Arial 
  color=#0000ff size=2>it continues to look like there is big holes open for 
  interpretation. So if I did a ANCP</FONT></SPAN></DIV>
  <DIV dir=ltr align=left><SPAN class=062190723-30042008><FONT face=Arial 
  color=#0000ff size=2>implementation there is bound to be interoperability 
  issues with existing implementations</FONT></SPAN></DIV>
  <DIV dir=ltr align=left><SPAN class=062190723-30042008><FONT face=Arial 
  color=#0000ff size=2>runnig.</FONT></SPAN></DIV>
  <DIV dir=ltr align=left><SPAN class=062190723-30042008><FONT face=Arial 
  color=#0000ff size=2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=ltr align=left><SPAN class=062190723-30042008><FONT face=Arial 
  color=#0000ff size=2>cheers,</FONT></SPAN></DIV>
  <DIV dir=ltr align=left><SPAN class=062190723-30042008><FONT face=Arial 
  color=#0000ff size=2>Peter</FONT></SPAN></DIV>
  <DIV dir=ltr align=left><SPAN class=062190723-30042008><FONT face=Arial 
  color=#0000ff size=2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=ltr align=left><SPAN class=062190723-30042008><FONT face=Arial 
  color=#0000ff size=2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=ltr align=left><SPAN class=062190723-30042008><FONT face=Arial 
  color=#0000ff size=2></FONT></SPAN>&nbsp;</DIV><FONT face=Arial color=#0000ff 
  size=2></FONT><BR>
  <BLOCKQUOTE dir=ltr 
  style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
    <DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
    <HR tabIndex=-1>
    <FONT face=Tahoma size=2><B>From:</B> Sanjay Wadhwa 
    [mailto:swadhwa@juniper.net] <BR><B>Sent:</B> 30. april 2008 
    14:42<BR><B>To:</B> Peter Arberg; Tina TSOU; Maglione Roberta; Wojciech Dec 
    (wdec)<BR><B>Cc:</B> ancp@ietf.org<BR><B>Subject:</B> RE: [ANCP] question 
    regarding Labels in ANCP port up messages<BR></FONT><BR></DIV>
    <DIV></DIV>
    <P><FONT size=2>Peter<BR>&nbsp; The ANCP draft as it currently stands is 
    based on RFC3292. It provides extensions and modifications to relevant 
    constructs in RFC3292. There is no mention (implicit or explicit) of expired 
    GSMP drafts in the ANCP draft. In order to implement the ANCP draft, I am 
    not sure why one would look at the expired GSMP drafts. Do you see a reason 
    to do this based on anything that you read in the ANCP draft? Bringing up 
    reference to expired gsmp draft in this thread&nbsp;just adds to the 
    confusion. For GSMPv3 objects in the messages (such as Label Type), one has 
    to look at RFC3292 (this is clearly stated in the ANCP draft - section 2 and 
    I am quoting it below) :</FONT></P>
    <P><FONT size=2><FONT color=#0000ff>ANCP uses a subset of GSMPv3 messages to 
    implement currently defined use-cases. These relevant GSMPv3 messages are 
    identified in section 5. GSMPv3 procedures with suitable extensions, as used 
    by ANCP, are described in sections 5.1, 5.2 and 5.3. GSMPv3 general 
    extensions and GSMPv3 message specific extensions required by ANCP are 
    described in sub-sections of 5.4. In addition to specifying extensions and 
    modifications to relevant GSMP messages applicable to ANCP, this draft also 
    defines the usage of these messages by ANCP, and indicates the values that 
    ANCP should set for relevant fields in these GSMP messages. However, to 
    understand the basic semantics of various fields in GSMP messages, the 
    reader is referred to [4].&nbsp;=&gt; RFC 3292.</FONT><BR><BR>What existing 
    implementations currently do is an important but separate issue. These 
    implementations for most part precede the current ANCP draft. It is fine to 
    poll where these implementations diverge from the current draft. It is then 
    upto the implementations (including the one that I am somewhat familiar 
    with) to work towards compliance with the draft. </FONT></P>
    <P><FONT size=2>On the following points&nbsp;from &nbsp;Woj:</FONT></P>
    <P><FONT size=2>Woj&gt;2) The current version of the spec is not accurate, 
    and does not reflect&nbsp;the fact that the known implementations follow the 
    label field definition from draft-gsmpv3-base-spec.</FONT></P>
    <P><FONT size=2>It is not for the protocol draft to point out what current 
    implementations do.&nbsp;&nbsp;The best we can do is to further clarify in 
    the draft that type and value fields of the Label object (defined in 
    RFC3292) should be set to 0 in the port-up message (we already&nbsp;mention 
    the lable object as a whole should be set to all 0s). </FONT></P>
    <P><SPAN class=364043506-24042008><FONT size=2><SPAN 
    class=709295811-24042008>Woj&gt; This would be a good thing for the WG to 
    discuss. There most evidently is a fair amount of&nbsp;"dead wood" in the 
    current spec, ie stuff that nobody yet&nbsp;implements or cares about. 
    &nbsp;In the former case, we could re-cast that material using the new 
    notions/extensions, in the latter case simply chop it 
    out.</SPAN></FONT></SPAN></P>
    <P><SPAN class=364043506-24042008><FONT size=2><SPAN 
    class=709295811-24042008>I agree. We are based on GSMPv3 (RFC3292) 
    &nbsp;messages, and obviously not everything in these messages is leveraged 
    by ANCP.&nbsp; However, the sync rate and OAM uses-cases are implemented and 
    in use (ideally we should leave these alone...i.e. no change beyond adding 
    more clarity if needed). For anything new (such as multicast) we are 
    defining new messages&nbsp;(no legacy).&nbsp; </SPAN></FONT></SPAN></P>
    <P><FONT size=2>-Sanjay<BR><BR>&gt;-----Original Message-----<BR>&gt;From: 
    Peter Arberg [</FONT><A href="mailto:parberg@redback.com"><FONT 
    size=2>mailto:parberg@redback.com</FONT></A><FONT size=2>]<BR>&gt;Sent: 
    Wednesday, April 30, 2008 3:56 PM<BR>&gt;To: Tina TSOU; Maglione Roberta; 
    Sanjay Wadhwa; Wojciech Dec (wdec)<BR>&gt;Cc: ancp@ietf.org<BR>&gt;Subject: 
    RE: [ANCP] question regarding Labels in ANCP port up 
    messages<BR>&gt;<BR>&gt;<BR>&gt;Hi,<BR>&gt;<BR>&gt;some times I think it is 
    amazing we ever got interoperability<BR>&gt;of ANCP :-)<BR>&gt;because 
    looking at the label discussion is a very good example that the<BR>&gt;whole 
    GSMP - ANCP reference have not worked very well.<BR>&gt;<BR>&gt;In the ANCP 
    draft, section 5.4.2 the event message is shown like 
    this:<BR>&gt;<BR>&gt;0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    3<BR>&gt;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<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;| 
    Vers&nbsp; |&nbsp; Sub&nbsp; | Message Type&nbsp; | 
    Result|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    Code&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;| 
    Partition ID&nbsp; 
    |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    Transaction 
    Identifier&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;|I|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    SubMessage Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    Port&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    Port Session 
    Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    Event Sequence 
    Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;|x|S|x|x|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |<BR>&gt;+-+-+-+-+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    Label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |<BR>&gt;~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    ~<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;|x|x|x|x|x|x|x|x| 
    Message Type&nbsp; |&nbsp;&nbsp; Tech Type&nbsp;&nbsp; | Block Length&nbsp; 
    |<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |<BR>&gt;~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    Extension 
    Value&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    ~<BR>&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;<BR>&gt;<BR>&gt;This 
    is the exact same event message defined 
    in<BR>&gt;draft-ietf-gsmp-v3-base-spec-08.txt&nbsp; section 
    11.<BR>&gt;<BR>&gt;And in this gsmp-draft, section 5.1.3 the label space is 
    defined<BR>&gt;as minimum 8 bytes if the length=0 and as such no value, and 
    this<BR>&gt;is because the gsmp-draft has a new "label adaptaion" 
    field.<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt;BUT in RFC3292 the event message is 
    show in section 9, like 
    this:<BR>&gt;<BR>&gt;0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    3<BR>&gt;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<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;|&nbsp;&nbsp;&nbsp; 
    Version&nbsp;&nbsp;&nbsp; | Message Type&nbsp; |&nbsp;&nbsp;&nbsp; 
    Result&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp; 
    Code&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;| 
    Partition ID&nbsp; 
    |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    Transaction 
    Identifier&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;|I|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    SubMessage Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    Port&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    Port Session 
    Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    Event Sequence 
    Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;|x|S|x|x|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |<BR>&gt;+-+-+-+-+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    Label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |<BR>&gt;~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    ~<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;<BR>&gt;<BR>&gt;So 
    a different Event Message picture/definition than what is shown<BR>&gt;in 
    the ANCP draft, and in RFC3292 section 3.1.3 the label field<BR>&gt;is 
    defined as 4 bytes if length=0 and as such no 
    value.<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt;So I very much agree with Woj that we 
    need this issue to be resolved,<BR>&gt;and proabably a show of hands what is 
    actually done in different<BR>&gt;implementations, so we can nail down how 
    the event message is<BR>&gt;suppose to look like in 
    ANCP.<BR>&gt;<BR>&gt;<BR>&gt;I know at least 1 implementation which uses 8 
    bytes for the<BR>&gt;label 
    field.<BR>&gt;<BR>&gt;<BR>&gt;cheers,<BR>&gt;Peter<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt;________________________________<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    From: ancp-bounces@ietf.org<BR>&gt;[</FONT><A 
    href="mailto:ancp-bounces@ietf.org"><FONT 
    size=2>mailto:ancp-bounces@ietf.org</FONT></A><FONT size=2>] On Behalf Of 
    Tina TSOU<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Sent: 30. april 
    2008 00:19<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; To: Maglione 
    Roberta; Sanjay Wadhwa; Wojciech Dec 
    (wdec)<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Cc: 
    ancp@ietf.org<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Subject: Re: 
    [ANCP] question regarding Labels in ANCP<BR>&gt;port up 
    messages<BR>&gt;<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    Hi all,<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; It is clear to me 
    that if Label Length is filled as 0,<BR>&gt;there is nothing to be filled 
    into Label Value. The whole<BR>&gt;Label part is 4 bytes, not 8 
    bytes.<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Cheers from 
    the last working day before Labor's Day<BR>&gt;holidays in some 
    countries:)<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    Tina<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    ----- Original Message 
    -----<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    From: Wojciech Dec (wdec) &lt;</FONT><A href="mailto:wdec@cisco.com"><FONT 
    size=2>mailto:wdec@cisco.com</FONT></A><FONT 
    size=2>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    To: Sanjay Wadhwa &lt;</FONT><A href="mailto:swadhwa@juniper.net"><FONT 
    size=2>mailto:swadhwa@juniper.net</FONT></A><FONT size=2>&gt;<BR>&gt; ; 
    Maglione Roberta &lt;</FONT><A 
    href="mailto:roberta.maglione@telecomitalia.it"><FONT 
    size=2>mailto:roberta.maglione@telecomitalia.it</FONT></A><FONT 
    size=2>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    Cc: 
    ancp@ietf.org<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    Sent: Wednesday, April 30, 2008 1:12 
    AM<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    Subject: Re: [ANCP] question regarding Labels<BR>&gt;in ANCP port up 
    messages<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    Sanjay, 
    All,<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    What is stated below runs counter to at least<BR>&gt;a handful of 
    ANCP<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    implementations, all of which are known to 
    be<BR>&gt;interoperable.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    There are really two 
    options:<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    1) The current version of the spec is correct,<BR>&gt;and the 
    known<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    interoperable implementations do not follow 
    it<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    2) The current version of the spec is not<BR>&gt;accurate, and does not 
    reflect<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    the fact that the known implementations follow<BR>&gt;the label 
    field<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    definition from 
    draft-gsmpv3-base-spec.<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    I would like to ask you, as the lead editor of<BR>&gt;the spec, to work 
    with<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    the WG in resolving what the problem is, and<BR>&gt;clearing up what the 
    WG<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    spec says about and if 1) holds to be true,<BR>&gt;then proposing 
    an<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    interoperability 
    fix.<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    In either case, the issue highlights the fact<BR>&gt;that there is 
    still<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    lingering confusion as to the dependencies<BR>&gt;ANCP has on rfc3292, 
    or<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    draft-gsmpv3-base-spec, or both. It seems to<BR>&gt;be in the best interest 
    of<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    all to address 
    these.<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    Regards,<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    Woj.<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; -----Original 
    Message-----<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; From: Sanjay Wadhwa [</FONT><A href="mailto:swadhwa@juniper.net"><FONT 
    size=2>mailto:swadhwa@juniper.net</FONT></A><FONT 
    size=2>]<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; Sent: 29 April 2008 
    17:29<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; To: Maglione 
    Roberta<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; Cc: Wojciech Dec (wdec); ancp@ietf.org;<BR>&gt;Philippe Champagne 
    (pchamp)<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; Subject: RE: question regarding Labels in<BR>&gt;ANCP port up 
    messages<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; Hi 
    Maglione<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;&nbsp;&nbsp; Yes, the label format is as defined in RFC<BR>&gt;3292. The 
    ANCP draft 
    is<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; based on RFC 3292 and proposes<BR>&gt;extensions/modifications 
    where<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    required.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; This is clearly stated upfront both in the<BR>&gt;abstract and 
    in<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; section 2. 
    In<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; section 5.4.2, it clearly&nbsp; specifies the<BR>&gt;format of "port 
    up" 
    message<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; (based on RFC 3292), and explicitly states<BR>&gt;the label 
    field<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; should be 
    set<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; to 0. Following is what the draft currently 
    states:<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 5.4.2 Topology Discovery 
    Extensions<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; The GSMP Event message with PORT UP message<BR>&gt;type (80) is used 
    for<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; conveying DSL line attributes to the NAS.<BR>&gt;The version field 
    should 
    be<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; set to 3, and the sub field should be set to<BR>&gt;1. The I and 
    subMessage<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; fields SHOULD be set to 1 to signify no<BR>&gt;fragmentation. The Port 
    and<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; Label fields should be set to 
    0.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;&nbsp; 
    0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    2&nbsp;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    3<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0 1 2 3 4 5 6 7 8 
    9 0 1 2 3 4 5 6 7<BR>&gt;8 9 0 1 2 3 4 
    5<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 6 7 8 9 0 
    1<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Vers&nbsp; |&nbsp; 
    Sub&nbsp; | Message Type&nbsp; 
    |<BR>&gt;Result|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    Code<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Partition ID&nbsp; 
    |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt;Transaction 
    Identifier<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |I|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SubMessage 
    Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |&nbsp;&nbsp;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    Length<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    Port<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    Port Session 
    Number<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    Event Sequence 
    Number<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |x|S|x|x|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    +-+-+-+-+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    Label<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    ~<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    ~<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |x|x|x|x|x|x|x|x| 
    Message Type&nbsp; |&nbsp;&nbsp;<BR>&gt;Tech Type&nbsp;&nbsp; | Block 
    Length<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    ~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    Extension 
    Value<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    ~<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; When we say the label field should be set to<BR>&gt;0, the 
    intention<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; is for 
    the<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; type and length fields in the label TLV to<BR>&gt;be set to 0. We 
    can<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; explicitly state this for 
    clarity.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    -Sanjay<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;-----Original 
    Message-----<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;From: Maglione Roberta<BR>&gt;[</FONT><A 
    href="mailto:roberta.maglione@telecomitalia.it"><FONT 
    size=2>mailto:roberta.maglione@telecomitalia.it</FONT></A><FONT 
    size=2>]<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;Sent: Tuesday, April 29, 2008 8:06 
    AM<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;To: Sanjay 
    Wadhwa<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;Cc: Wojciech Dec (wdec); 
    ancp@ietf.org;<BR>&gt;pchamp@cisco.com<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;Subject: RE: question regarding Labels in<BR>&gt;ANCP port up 
    messages<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;Hi Sanjay and 
    All,<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp; I was reading the current 
    ancp<BR>&gt;protocol draft in order 
    to<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt; understand which should be the correct<BR>&gt;format for the 
    label<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;field in the ancp port Up 
    message.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;Actually as it was already pointed out in<BR>&gt;the alias the 
    draft<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;in section 5.4.2 says "GSMP Event message<BR>&gt;with PORT UP 
    message<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;type (80) is used"&nbsp; thus I am assuming that<BR>&gt;the label 
    in 
    the<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;port UP message should follow the message<BR>&gt;format defined 
    in<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;RFC 3292, section 
    3.1.3:<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp;&nbsp; 
    0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt;2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    3<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp;&nbsp; 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9<BR>&gt;0 
    1 2 3 4 5 6 7 8 9 0 
    1<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;&nbsp;&nbsp;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp; |x|S|x|x|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Label 
    Type&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt;&nbsp; Label 
    Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;&nbsp;&nbsp;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp; 
    |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp; 
    ~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    Label 
    Value&nbsp;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    ~<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp; 
    |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;&nbsp;&nbsp;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;but from what I have seen different<BR>&gt;implementations 
    use<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;different format for label field: in<BR>&gt;particular 
    several<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;implementations use&nbsp; a label format that is<BR>&gt;similar to 
    the 
    one<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;specified in the expired 
    draft<BR>&gt;draft-ietf-gsmp-v3-base-spec:<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp; 
    0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt; 
    2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    3<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 
    5 6 7<BR>&gt;8 9 0 1 2 3 4 5 
    6<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 7 8 9 0 
    1<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |x|S|x|x|x|x|x|x|x|x|x|x|x|x|x|x|&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    Label<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; Type&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp; Label 
    Adaptation&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp; 
    Label<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    ~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    Label 
    Value<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    ~<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;Even if ancp does not care about the label<BR>&gt;field, having 
    this<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;field somehow not clearly specified in the<BR>&gt;current ancp 
    draft<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;can easily lead to interoperability issues,<BR>&gt;thus I think 
    it<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;would be very helpful if you and/or the<BR>&gt;other editors 
    can<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;clarify what should be the correct format<BR>&gt;for the label 
    field<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;to be used in the ancp Port Up 
    message.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;Thanks and best 
    regards,<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;Roberta<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;________________________________________<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;From: Philippe Champagne (pchamp) 
    [pchamp@cisco.com]<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;Sent: Thursday, April 24, 2008 7:14 
    PM<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;To: Sanjay 
    Wadhwa<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;Cc: Maglione Roberta; Wojciech Dec 
    (wdec);<BR>&gt;ancp@ietf.org<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;Subject: question regarding&nbsp; Labels in ANCP<BR>&gt;port up 
    messages<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;Hi 
    Sanjay<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;In section 5.4.2 of the draft, we 
    have:<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    2<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    3<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0 1 2 3 4 5 6 7 8 
    9 0 1 2 3 4 5 6<BR>&gt;7 8 9 0 1 2 3 4 5 
    6<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;7 8 9 0 
    1<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;<BR>&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Vers&nbsp; |&nbsp; 
    Sub&nbsp; | Message Type&nbsp; 
    |<BR>&gt;Result|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    Code<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;<BR>&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Partition ID&nbsp; 
    |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt;Transaction 
    Identifier<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;<BR>&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |I|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SubMessage 
    Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |&nbsp;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    Length<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;<BR>&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    Port<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;<BR>&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    Port Session 
    Number<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;<BR>&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    Event Sequence 
    Number<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;<BR>&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |x|S|x|x|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    +-+-+-+-+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    Label<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    ~<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    ~<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;<BR>&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |x|x|x|x|x|x|x|x| 
    Message Type&nbsp; |&nbsp;&nbsp;<BR>&gt;Tech Type&nbsp;&nbsp; 
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;Block Length&nbsp; 
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;<BR>&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    ~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    Extension 
    Value<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    ~<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;<BR>&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;Where Label I suppose is taken from the RFC<BR>&gt;3292, 
    section<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;3.1.3: (well, I'm 
    guessing)<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp; A summary of TLV labels supported in<BR>&gt;this 
    version of 
    the<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; protocol 
    is<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp; listed 
    below:<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; TLV 
    Label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Type&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    Section 
    Title<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    ---------&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    ----&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    -------------<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ATM 
    Label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0x100&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ATM 
    TLV 
    Labels<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; FR 
    Label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    0x101&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Frame Relay<BR>&gt;TLV 
    Labels<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MPLS Gen Label 
    0x102&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MPLS<BR>&gt;Generic TLV 
    Labels<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; FEC 
    Label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0x103&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; FEC 
    TLV 
    Labels<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp; All Labels will be designated as 
    follow:<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp;&nbsp; 
    0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt;2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    3<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp;&nbsp; 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9<BR>&gt;0 
    1 2 3 4 5 6 7 8 9 0 
    1<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;&nbsp;&nbsp;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp; |x|S|x|x|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Label 
    Type&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt;&nbsp; Label 
    Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;&nbsp;&nbsp;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp; 
    |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp; 
    ~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    Label 
    Value&nbsp;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    ~<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp; 
    |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;&nbsp;&nbsp;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; x: Reserved 
    Flags.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; These are 
    generally used by<BR>&gt;specific messages and will 
    be<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; defined in those 
    messages.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; S: Stacked Label 
    Indicator<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Label Stacking is 
    discussed below<BR>&gt;in section 
    3.1.3.5<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Label 
    Type<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A 12-bit field 
    indicating the type<BR>&gt;of 
    label.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Label 
    Length<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A 16-bit field 
    indicating the<BR>&gt;length of the 
    Label<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; Value 
    field<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; in 
    bytes.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Label 
    Value<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A variable length 
    field that is an<BR>&gt;integer number of 32 
    bit<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; words long.&nbsp; 
    The Label Value field<BR>&gt;is 
    interpreted<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; according 
    to<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the Label Type as 
    described in the<BR>&gt;following 
    sections.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;The draft is a bit obscure about this and<BR>&gt;since it 
    doesn't<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;specify much, it can lead to<BR>&gt;misinterpretation for the 
    unused<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;part. Moreover, it would appear that<BR>&gt;several 
    implementations<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;currently use another format for the label<BR>&gt;field. Can 
    you<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;explain?&nbsp; I mean, how come what's in the<BR>&gt;current draft 
    doesn't<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;match what's known to be 
    implemented?<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;I'm still wondering why we carried over<BR>&gt;pieces from GSMP 
    that<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;we do not intend to 
    use.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;I would recommend that if we are to keep<BR>&gt;them but not 
    use<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;them, we should mention precisely how we<BR>&gt;intend not to 
    use<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;them: that is how many 0 filled bytes this<BR>&gt;is expected to 
    use<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;The rfc 3292 doesn't cover the case where<BR>&gt;this field is not 
    used.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;Can you shed some ligths on 
    this?<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;Thanks<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;Regards<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;Phil<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;<BR>&gt;&gt;--------------------------------------------------------------------<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;CONFIDENTIALITY 
    NOTICE<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;This message and its attachments are<BR>&gt;addressed solely to 
    the<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;persons above and may contain confidential<BR>&gt;information. If 
    you<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;have received the message in error, be<BR>&gt;informed that any 
    use<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;of the content hereof is prohibited. Please<BR>&gt;return 
    it<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;immediately to the sender and delete the<BR>&gt;message. Should 
    you<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;have any questions, please contact us by replying 
    to<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;webmaster@telecomitalia.it.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Thank 
    you<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt;www.telecomitalia.it<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;<BR>&gt;&gt;--------------------------------------------------------------------<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    _______________________________________________<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    ANCP mailing 
    list<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    ANCP@ietf.org<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    </FONT><A href="https://www.ietf.org/mailman/listinfo/ancp" 
    target=_blank><FONT 
    size=2>https://www.ietf.org/mailman/listinfo/ancp</FONT></A><BR><FONT 
    size=2>&gt;<BR>&gt;</FONT> </P></BLOCKQUOTE>
  <P>
  <HR>

  <P></P>_______________________________________________<BR>ANCP mailing 
  list<BR>ANCP@ietf.org<BR>https://www.ietf.org/mailman/listinfo/ancp<BR></BLOCKQUOTE></BODY></HTML>

--Boundary_(ID_IrSrLJGI/XZeLKrjlwhrPg)--

--===============1760556148==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1760556148==--


From ancp-bounces@ietf.org  Thu May  1 08:56:57 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 699573A6D2A;
	Thu,  1 May 2008 08:56:57 -0700 (PDT)
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 F32D23A6E18
	for <ancp@core3.amsl.com>; Thu,  1 May 2008 08:56:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.976
X-Spam-Level: 
X-Spam-Status: No, score=-1.976 tagged_above=-999 required=5
	tests=[AWL=-0.262, BAYES_00=-2.599, HTML_FONT_FACE_BAD=0.884,
	HTML_MESSAGE=0.001]
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 upy5DPM1RKUs for <ancp@core3.amsl.com>;
	Thu,  1 May 2008 08:56:53 -0700 (PDT)
Received: from prattle.redback.com (prattle.redback.com [155.53.12.9])
	by core3.amsl.com (Postfix) with ESMTP id 253673A6D2A
	for <ancp@ietf.org>; Thu,  1 May 2008 08:56:53 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by prattle.redback.com (Postfix) with ESMTP id BDE4DBB7C14;
	Thu,  1 May 2008 08:56:55 -0700 (PDT)
Received: from prattle.redback.com ([127.0.0.1])
	by localhost (prattle [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
	id 10023-03; Thu,  1 May 2008 08:56:55 -0700 (PDT)
Received: from rbsjx.ad.redback.com (rbsjxh1.redback.com [155.53.14.105])
	by prattle.redback.com (Postfix) with ESMTP id 7C42ABB7C13;
	Thu,  1 May 2008 08:56:55 -0700 (PDT)
Received: from RBSJX.ad.redback.com ([155.53.14.103]) by
	rbsjxh1.ad.redback.com ([155.53.14.105]) with mapi;
	Thu, 1 May 2008 08:56:55 -0700
From: Peter Arberg <parberg@redback.com>
To: Fortune HUANG <fqhuang@huawei.com>,
	Sanjay Wadhwa <swadhwa@juniper.net>, Tina TSOU <tena@huawei.com>,
	Maglione Roberta <roberta.maglione@telecomitalia.it>,
	"Wojciech Dec (wdec)" <wdec@cisco.com>
Date: Thu, 1 May 2008 08:56:52 -0700
Thread-Topic: [ANCP] question regarding  Labels in ANCP port up messages
Thread-Index: AcirdtRnhNpgW3QCS9+RstJ5rWf04QAK+KXA
Message-ID: <48C276B536524E478C659685995F6AA539DBBBE720@RBSJX.ad.redback.com>
References: <48C276B536524E478C659685995F6AA539DBBBE370@RBSJX.ad.redback.com>
	<9BD5D7887235424FA97DFC223CAE3C280AB43A10@proton.jnpr.net>
	<48C276B536524E478C659685995F6AA539DBBBE577@RBSJX.ad.redback.com>
	<080101c8ab76$c991b800$734c460a@china.huawei.com>
In-Reply-To: <080101c8ab76$c991b800$734c460a@china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-Virus-Scanned: by amavisd-new at redback.com
Cc: "ancp@ietf.org" <ancp@ietf.org>
Subject: Re: [ANCP] question regarding  Labels in ANCP port up messages
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/pipermail/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>
Content-Type: multipart/mixed; boundary="===============1850680821=="
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org

--===============1850680821==
Content-Language: en-US
Content-Type: multipart/alternative;
	boundary="_000_48C276B536524E478C659685995F6AA539DBBBE720RBSJXadredbac_"

--_000_48C276B536524E478C659685995F6AA539DBBBE720RBSJXadredbac_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

As pointed out by both Philipe & Maglione in earlier emails we have a situa=
tion where
some ANCP implementations running in production networks today, do not use =
the
event message =3D label field, as it is currently defined in the draft.

I simply gave some historic input to why this is, and I support Woj when he=
 suggest
that the editors try and work a proposal how to solve this issue.

I think a good starting point is a show of hands to what is implemented, so=
 we can see
if it is easier to change the specs or the running code.

But I do not think we can get away from having to look at changing the vers=
ion number as
a minimum, no matter what direction we go.

As a show of hans, I have so far seen Tina say the label space is 4 bytes, =
and I said it
is 8 bytes in the implementation I know of..  So at the moment the score is=
 1 - 1 :-)

cheers,
Peter




________________________________
From: Fortune HUANG [mailto:fqhuang@huawei.com]
Sent: 1. maj 2008 03:33
To: Peter Arberg; Sanjay Wadhwa; Tina TSOU; Maglione Roberta; Wojciech Dec =
(wdec)
Cc: ancp@ietf.org
Subject: Re: [ANCP] question regarding Labels in ANCP port up messages

Peter,

I think ANCP and GSMP are independent with each other, and they can be deve=
loped parallelly.
RFC3292 is the only legal baseline version of GSMP which makes sense to ANC=
P, because ANCP
uses the contents of RFC3292 as a starting point.
However, after started, ANCP is developed independently with the developmen=
t of GSMP.
And the later versions of GSMP have nothing to do with ANCP.

Therefore, I think draft-ietf-gsmp-v3-base-spec-08 has nothing to do with A=
NCP because it
is not a legal starting point of ANCP.

Furthermore, I think it is the responsibility of the newer draft to keep co=
mpatible with the older one.
Since the draft-ietf-gsmp-v3-base-spec-08 is newer than RFC3292, I think we=
 should make
draft-ietf-gsmp-v3-base-spec-08 compatible with RFC3292, and accordingly th=
e implementation
could be backward compatible.

cheers,
Fortune
----- Original Message -----
From: Peter Arberg<mailto:parberg@redback.com>
To: Sanjay Wadhwa<mailto:swadhwa@juniper.net> ; Tina TSOU<mailto:tena@huawe=
i.com> ; Maglione Roberta<mailto:roberta.maglione@telecomitalia.it> ; Wojci=
ech Dec (wdec)<mailto:wdec@cisco.com>
Cc: ancp@ietf.org<mailto:ancp@ietf.org>
Sent: Thursday, May 01, 2008 7:20 AM
Subject: Re: [ANCP] question regarding Labels in ANCP port up messages

Sanjay,

What do you mean "why I reference an old draft"  ????????????

I'm surprised you even ask...  please take a look at YOUR own internet-draf=
t that most
of the ANCP working implementations are based on, in case you do not have t=
his old
internet-draft, I have attached it to the document.

If you look at the reference for this ancp-draft, you will see that in the =
reference section
you point to this old gsmp-draft...  Yes and I know this has been changed i=
n the later
versions of the ANCP draft, but that do not change the fact that many of th=
e implementations
today was developed when the attached draft was current.

I think a very good question is brought up here, and that is what is implem=
ented and
running in networks today ?

My take on this is that when the reference was change from the old gsmp-dra=
ft to the older
RFC3292, apparently no one paid any attention to the fact the label definit=
ion in the event
message was different and not compatible.

What current implementations do today is an important factor in this discus=
sion, and I think
it is time to come to realization that we might need a new version number f=
or ANCP since
it continues to look like there is big holes open for interpretation. So if=
 I did a ANCP
implementation there is bound to be interoperability issues with existing i=
mplementations
runnig.

cheers,
Peter




________________________________
From: Sanjay Wadhwa [mailto:swadhwa@juniper.net]
Sent: 30. april 2008 14:42
To: Peter Arberg; Tina TSOU; Maglione Roberta; Wojciech Dec (wdec)
Cc: ancp@ietf.org
Subject: RE: [ANCP] question regarding Labels in ANCP port up messages


Peter
  The ANCP draft as it currently stands is based on RFC3292. It provides ex=
tensions and modifications to relevant constructs in RFC3292. There is no m=
ention (implicit or explicit) of expired GSMP drafts in the ANCP draft. In =
order to implement the ANCP draft, I am not sure why one would look at the =
expired GSMP drafts. Do you see a reason to do this based on anything that =
you read in the ANCP draft? Bringing up reference to expired gsmp draft in =
this thread just adds to the confusion. For GSMPv3 objects in the messages =
(such as Label Type), one has to look at RFC3292 (this is clearly stated in=
 the ANCP draft - section 2 and I am quoting it below) :

ANCP uses a subset of GSMPv3 messages to implement currently defined use-ca=
ses. These relevant GSMPv3 messages are identified in section 5. GSMPv3 pro=
cedures with suitable extensions, as used by ANCP, are described in section=
s 5.1, 5.2 and 5.3. GSMPv3 general extensions and GSMPv3 message specific e=
xtensions required by ANCP are described in sub-sections of 5.4. In additio=
n to specifying extensions and modifications to relevant GSMP messages appl=
icable to ANCP, this draft also defines the usage of these messages by ANCP=
, and indicates the values that ANCP should set for relevant fields in thes=
e GSMP messages. However, to understand the basic semantics of various fiel=
ds in GSMP messages, the reader is referred to [4]. =3D> RFC 3292.

What existing implementations currently do is an important but separate iss=
ue. These implementations for most part precede the current ANCP draft. It =
is fine to poll where these implementations diverge from the current draft.=
 It is then upto the implementations (including the one that I am somewhat =
familiar with) to work towards compliance with the draft.

On the following points from  Woj:

Woj>2) The current version of the spec is not accurate, and does not reflec=
t the fact that the known implementations follow the label field definition=
 from draft-gsmpv3-base-spec.

It is not for the protocol draft to point out what current implementations =
do.  The best we can do is to further clarify in the draft that type and va=
lue fields of the Label object (defined in RFC3292) should be set to 0 in t=
he port-up message (we already mention the lable object as a whole should b=
e set to all 0s).

Woj> This would be a good thing for the WG to discuss. There most evidently=
 is a fair amount of "dead wood" in the current spec, ie stuff that nobody =
yet implements or cares about.  In the former case, we could re-cast that m=
aterial using the new notions/extensions, in the latter case simply chop it=
 out.

I agree. We are based on GSMPv3 (RFC3292)  messages, and obviously not ever=
ything in these messages is leveraged by ANCP.  However, the sync rate and =
OAM uses-cases are implemented and in use (ideally we should leave these al=
one...i.e. no change beyond adding more clarity if needed). For anything ne=
w (such as multicast) we are defining new messages (no legacy).

-Sanjay

>-----Original Message-----
>From: Peter Arberg [mailto:parberg@redback.com]
>Sent: Wednesday, April 30, 2008 3:56 PM
>To: Tina TSOU; Maglione Roberta; Sanjay Wadhwa; Wojciech Dec (wdec)
>Cc: ancp@ietf.org
>Subject: RE: [ANCP] question regarding Labels in ANCP port up messages
>
>
>Hi,
>
>some times I think it is amazing we ever got interoperability
>of ANCP :-)
>because looking at the label discussion is a very good example that the
>whole GSMP - ANCP reference have not worked very well.
>
>In the ANCP draft, section 5.4.2 the event message is shown like this:
>
>0                   1                   2                   3
>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
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>| Vers  |  Sub  | Message Type  | Result|        Code           |
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>| Partition ID  |            Transaction Identifier             |
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>|I|      SubMessage Number      |           Length              |
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>|                             Port                              |
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>|                      Port Session Number                      |
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>|                     Event Sequence Number                     |
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>|x|S|x|x|                                                       |
>+-+-+-+-+                     Label                             |
>~                                                               ~
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>|x|x|x|x|x|x|x|x| Message Type  |   Tech Type   | Block Length  |
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>|                                                               |
>~                         Extension Value                       ~
>|                                                               |
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
>
>This is the exact same event message defined in
>draft-ietf-gsmp-v3-base-spec-08.txt  section 11.
>
>And in this gsmp-draft, section 5.1.3 the label space is defined
>as minimum 8 bytes if the length=3D0 and as such no value, and this
>is because the gsmp-draft has a new "label adaptaion" field.
>
>
>
>BUT in RFC3292 the event message is show in section 9, like this:
>
>0                   1                   2                   3
>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
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>|    Version    | Message Type  |    Result     |     Code      |
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>| Partition ID  |            Transaction Identifier             |
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>|I|      SubMessage Number      |           Length              |
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>|                             Port                              |
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>|                      Port Session Number                      |
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>|                     Event Sequence Number                     |
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>|x|S|x|x|                                                       |
>+-+-+-+-+                     Label                             |
>~                                                               ~
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
>
>So a different Event Message picture/definition than what is shown
>in the ANCP draft, and in RFC3292 section 3.1.3 the label field
>is defined as 4 bytes if length=3D0 and as such no value.
>
>
>
>So I very much agree with Woj that we need this issue to be resolved,
>and proabably a show of hands what is actually done in different
>implementations, so we can nail down how the event message is
>suppose to look like in ANCP.
>
>
>I know at least 1 implementation which uses 8 bytes for the
>label field.
>
>
>cheers,
>Peter
>
>
>
>
>
>
>________________________________
>
>        From: ancp-bounces@ietf.org
>[mailto:ancp-bounces@ietf.org] On Behalf Of Tina TSOU
>        Sent: 30. april 2008 00:19
>        To: Maglione Roberta; Sanjay Wadhwa; Wojciech Dec (wdec)
>        Cc: ancp@ietf.org
>        Subject: Re: [ANCP] question regarding Labels in ANCP
>port up messages
>
>
>        Hi all,
>        It is clear to me that if Label Length is filled as 0,
>there is nothing to be filled into Label Value. The whole
>Label part is 4 bytes, not 8 bytes.
>
>        Cheers from the last working day before Labor's Day
>holidays in some countries:)
>
>        Tina
>
>                ----- Original Message -----
>                From: Wojciech Dec (wdec) <mailto:wdec@cisco.com>
>                To: Sanjay Wadhwa <mailto:swadhwa@juniper.net>
> ; Maglione Roberta <mailto:roberta.maglione@telecomitalia.it>
>                Cc: ancp@ietf.org
>                Sent: Wednesday, April 30, 2008 1:12 AM
>                Subject: Re: [ANCP] question regarding Labels
>in ANCP port up messages
>
>                Sanjay, All,
>
>                What is stated below runs counter to at least
>a handful of ANCP
>                implementations, all of which are known to be
>interoperable.
>                There are really two options:
>                1) The current version of the spec is correct,
>and the known
>                interoperable implementations do not follow it
>                2) The current version of the spec is not
>accurate, and does not reflect
>                the fact that the known implementations follow
>the label field
>                definition from draft-gsmpv3-base-spec.
>
>                I would like to ask you, as the lead editor of
>the spec, to work with
>                the WG in resolving what the problem is, and
>clearing up what the WG
>                spec says about and if 1) holds to be true,
>then proposing an
>                interoperability fix.
>
>                In either case, the issue highlights the fact
>that there is still
>                lingering confusion as to the dependencies
>ANCP has on rfc3292, or
>                draft-gsmpv3-base-spec, or both. It seems to
>be in the best interest of
>                all to address these.
>
>                Regards,
>                Woj.
>
>                > -----Original Message-----
>                > From: Sanjay Wadhwa [mailto:swadhwa@juniper.net]
>                > Sent: 29 April 2008 17:29
>                > To: Maglione Roberta
>                > Cc: Wojciech Dec (wdec); ancp@ietf.org;
>Philippe Champagne (pchamp)
>                > Subject: RE: question regarding Labels in
>ANCP port up messages
>                >
>                > Hi Maglione
>                >   Yes, the label format is as defined in RFC
>3292. The ANCP draft is
>                > based on RFC 3292 and proposes
>extensions/modifications where
>                > required.
>                > This is clearly stated upfront both in the
>abstract and in
>                > section 2. In
>                > section 5.4.2, it clearly  specifies the
>format of "port up" message
>                > (based on RFC 3292), and explicitly states
>the label field
>                > should be set
>                > to 0. Following is what the draft currently states:
>                >
>                >
>                > 5.4.2 Topology Discovery Extensions
>                >
>                > The GSMP Event message with PORT UP message
>type (80) is used for
>                > conveying DSL line attributes to the NAS.
>The version field should be
>                > set to 3, and the sub field should be set to
>1. The I and subMessage
>                > fields SHOULD be set to 1 to signify no
>fragmentation. The Port and
>                > Label fields should be set to 0.
>                >
>                >  0                   1                   2
>                3
>                >          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
>                >
>                >
>                >
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                >         | Vers  |  Sub  | Message Type  |
>Result|        Code
>                > |
>                >
>                >
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                >         | Partition ID  |
>Transaction Identifier
>                > |
>                >
>                >
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                >         |I|      SubMessage Number      |
>       Length
>                > |
>                >
>                >
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                >         |                             Port
>                > |
>                >
>                >
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                >         |                      Port Session Number
>                > |
>                >
>                >
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                >         |                     Event Sequence Number
>                > |
>                >
>                >
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                >         |x|S|x|x|
>                > |
>                >         +-+-+-+-+                     Label
>                > |
>                >         ~
>                > ~
>                >
>                >
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                >         |x|x|x|x|x|x|x|x| Message Type  |
>Tech Type   | Block Length
>                > |
>                >
>                >
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                >         |
>                > |
>                >         ~                         Extension Value
>                > ~
>                >         |
>                > |
>                >
>                >
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                >
>                > When we say the label field should be set to
>0, the intention
>                > is for the
>                > type and length fields in the label TLV to
>be set to 0. We can
>                > explicitly state this for clarity.
>                >
>                > -Sanjay
>                >
>                > >-----Original Message-----
>                > >From: Maglione Roberta
>[mailto:roberta.maglione@telecomitalia.it]
>                > >Sent: Tuesday, April 29, 2008 8:06 AM
>                > >To: Sanjay Wadhwa
>                > >Cc: Wojciech Dec (wdec); ancp@ietf.org;
>pchamp@cisco.com
>                > >Subject: RE: question regarding Labels in
>ANCP port up messages
>                > >
>                > >
>                > >Hi Sanjay and All,
>                > >     I was reading the current ancp
>protocol draft in order to
>                > > understand which should be the correct
>format for the label
>                > >field in the ancp port Up message.
>                > >Actually as it was already pointed out in
>the alias the draft
>                > >in section 5.4.2 says "GSMP Event message
>with PORT UP message
>                > >type (80) is used"  thus I am assuming that
>the label in the
>                > >port UP message should follow the message
>format defined in
>                > >RFC 3292, section 3.1.3:
>                > >
>                > >    0                   1
>2                   3
>                > >    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
>                > >
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                > >   |x|S|x|x|       Label Type      |
>  Label Length         |
>                > >
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                > >   |
>                       |
>                > >   ~                          Label Value
>                       ~
>                > >   |
>                       |
>                > >
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                > >
>                > >but from what I have seen different
>implementations use
>                > >different format for label field: in
>particular several
>                > >implementations use  a label format that is
>similar to the one
>                > >specified in the expired draft
>draft-ietf-gsmp-v3-base-spec:
>                > >
>                > >     0                   1
> 2                   3
>                > >       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
>                > >
>                >
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                > >      |x|S|x|x|x|x|x|x|x|x|x|x|x|x|x|x|
>       Label
>                > Type         |
>                > >
>                >
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                > >      |    Label Adaptation           |
>     Label
>                > Length         |
>                > >
>                >
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                > >      |
>                >          |
>                > >      ~                          Label Value
>                >          ~
>                > >      |
>                >          |
>                > >
>                >
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                > >
>                > >
>                > >Even if ancp does not care about the label
>field, having this
>                > >field somehow not clearly specified in the
>current ancp draft
>                > >can easily lead to interoperability issues,
>thus I think it
>                > >would be very helpful if you and/or the
>other editors can
>                > >clarify what should be the correct format
>for the label field
>                > >to be used in the ancp Port Up message.
>                > >
>                > >Thanks and best regards,
>                > >Roberta
>                > >
>                > >________________________________________
>                > >From: Philippe Champagne (pchamp) [pchamp@cisco.com]
>                > >Sent: Thursday, April 24, 2008 7:14 PM
>                > >To: Sanjay Wadhwa
>                > >Cc: Maglione Roberta; Wojciech Dec (wdec);
>ancp@ietf.org
>                > >Subject: question regarding  Labels in ANCP
>port up messages
>                > >
>                > >Hi Sanjay
>                > >
>                > >In section 5.4.2 of the draft, we have:
>                > >
>                > >
>                > >         0                   1                   2
>                >         3
>                > >         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
>                > >
>                >
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                > >        | Vers  |  Sub  | Message Type  |
>Result|        Code
>                > >         |
>                > >
>                >
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                > >        | Partition ID  |
>Transaction Identifier
>                > >         |
>                > >
>                >
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                > >        |I|      SubMessage Number      |
>        Length
>                > >         |
>                > >
>                >
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                > >        |                             Port
>                > >         |
>                > >
>                >
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                > >        |                      Port Session Number
>                > >         |
>                > >
>                >
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                > >        |                     Event Sequence Number
>                > >         |
>                > >
>                >
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                > >        |x|S|x|x|
>                > >         |
>                > >        +-+-+-+-+                     Label
>                > >         |
>                > >        ~
>                > >         ~
>                > >
>                >
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                > >        |x|x|x|x|x|x|x|x| Message Type  |
>Tech Type   |
>                > >Block Length  |
>                > >
>                >
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                > >        |
>                > >         |
>                > >        ~                         Extension Value
>                > >         ~
>                > >        |
>                > >         |
>                > >
>                >
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                > >Where Label I suppose is taken from the RFC
>3292, section
>                > >3.1.3: (well, I'm guessing)
>                > >
>                > >   A summary of TLV labels supported in
>this version of the
>                > protocol is
>                > >   listed below:
>                > >
>                > >      TLV Label      Type       Section Title
>                > >      ---------      ----       -------------
>                > >      ATM Label      0x100      ATM TLV Labels
>                > >      FR Label       0x101      Frame Relay
>TLV Labels
>                > >      MPLS Gen Label 0x102      MPLS
>Generic TLV Labels
>                > >      FEC Label      0x103      FEC TLV Labels
>                > >
>                > >   All Labels will be designated as follow:
>                > >
>                > >    0                   1
>2                   3
>                > >    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
>                > >
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                > >   |x|S|x|x|       Label Type      |
>  Label Length         |
>                > >
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                > >   |
>                       |
>                > >   ~                          Label Value
>                       ~
>                > >   |
>                       |
>                > >
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                > >
>                > >      x: Reserved Flags.
>                > >         These are generally used by
>specific messages and will be
>                > >         defined in those messages.
>                > >
>                > >      S: Stacked Label Indicator
>                > >         Label Stacking is discussed below
>in section 3.1.3.5
>                > >
>                > >      Label Type
>                > >         A 12-bit field indicating the type
>of label.
>                > >
>                > >      Label Length
>                > >         A 16-bit field indicating the
>length of the Label
>                > Value field
>                > >         in bytes.
>                > >
>                > >      Label Value
>                > >         A variable length field that is an
>integer number of 32 bit
>                > >         words long.  The Label Value field
>is interpreted
>                > according to
>                > >         the Label Type as described in the
>following sections.
>                > >
>                > >
>                > >The draft is a bit obscure about this and
>since it doesn't
>                > >specify much, it can lead to
>misinterpretation for the unused
>                > >part. Moreover, it would appear that
>several implementations
>                > >currently use another format for the label
>field. Can you
>                > >explain?  I mean, how come what's in the
>current draft doesn't
>                > >match what's known to be implemented?
>                > >
>                > >I'm still wondering why we carried over
>pieces from GSMP that
>                > >we do not intend to use.
>                > >
>                > >I would recommend that if we are to keep
>them but not use
>                > >them, we should mention precisely how we
>intend not to use
>                > >them: that is how many 0 filled bytes this
>is expected to use
>                > >
>                > >The rfc 3292 doesn't cover the case where
>this field is not used.
>                > >
>                > >Can you shed some ligths on this?
>                > >
>                > >Thanks
>                > >Regards
>                > >Phil
>                > >
>                > >
>                > >
>                >
>>--------------------------------------------------------------------
>                > >
>                > >CONFIDENTIALITY NOTICE
>                > >
>                > >This message and its attachments are
>addressed solely to the
>                > >persons above and may contain confidential
>information. If you
>                > >have received the message in error, be
>informed that any use
>                > >of the content hereof is prohibited. Please
>return it
>                > >immediately to the sender and delete the
>message. Should you
>                > >have any questions, please contact us by replying to
>                > >webmaster@telecomitalia.it.
>                > >
>                > >        Thank you
>                > >
>                > >
>www.telecomitalia.it
>                > >
>                >
>>--------------------------------------------------------------------
>                > >
>                > >
>                >
>                _______________________________________________
>                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

--_000_48C276B536524E478C659685995F6AA539DBBBE720RBSJXadredbac_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.6000.16640" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#cce8cf>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D344524715-01052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Hi,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D344524715-01052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D344524715-01052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>As pointed out by both Philipe &amp; Maglione in e=
arlier=20
emails we have a situation where</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D344524715-01052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>some ANCP implementations running in production ne=
tworks=20
today, do not </FONT></SPAN><SPAN class=3D344524715-01052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>use the </FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D344524715-01052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>event message =3D label field, as it is currently =
defined in=20
the draft.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D344524715-01052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D344524715-01052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>I simply gave some historic input to why this is, =
and I=20
support Woj when he suggest</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D344524715-01052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>that the editors try and work a proposal how to so=
lve this=20
issue.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D344524715-01052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D344524715-01052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>I think a good starting point is a show of hands t=
o what is=20
implemented, so we can see</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D344524715-01052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>if it is easier to change the specs or the running=
=20
code.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D344524715-01052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D344524715-01052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>But I do not think we can get away from having to =
look at=20
changing the version number as</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D344524715-01052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>a minimum, no matter what direction we=20
go.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D344524715-01052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D344524715-01052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>As a show of hans, I have so far seen Tina say the=
 label=20
space is 4 bytes, and I said it</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D344524715-01052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>is 8 bytes in the implementation I know of..&nbsp;=
 So at=20
the moment the score is 1 - 1 :-)</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D344524715-01052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D344524715-01052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>cheers,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D344524715-01052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Peter</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D344524715-01052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D344524715-01052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D344524715-01052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px soli=
d; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Fortune HUANG=20
  [mailto:fqhuang@huawei.com] <BR><B>Sent:</B> 1. maj 2008 03:33<BR><B>To:<=
/B>=20
  Peter Arberg; Sanjay Wadhwa; Tina TSOU; Maglione Roberta; Wojciech Dec=20
  (wdec)<BR><B>Cc:</B> ancp@ietf.org<BR><B>Subject:</B> Re: [ANCP] question=
=20
  regarding Labels in ANCP port up messages<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV><FONT face=3D&#23435;&#20307; size=3D2>Peter,</FONT></DIV>
  <DIV><FONT face=3D&#23435;&#20307; size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3D&#23435;&#20307; size=3D2>I think ANCP and GSMP are ind=
ependent with each=20
  other, and they can be developed parallelly.</FONT></DIV>
  <DIV>
  <DIV><FONT face=3D&#23435;&#20307; size=3D2>RFC3292 is&nbsp;the only&nbsp=
;legal baseline version=20
  of GSMP&nbsp;which makes sense&nbsp;to ANCP, because ANCP</FONT></DIV>
  <DIV><FONT face=3D&#23435;&#20307; size=3D2>uses the contents of RFC3292 =
as a starting=20
  point.</FONT></DIV>
  <DIV><FONT face=3D&#23435;&#20307; size=3D2>However, after&nbsp;started, =
</FONT><FONT face=3D&#23435;&#20307;=20
  size=3D2>ANCP is developed independently with the development of&nbsp;GSM=
P.=20
  </FONT></DIV>
  <DIV><FONT face=3D&#23435;&#20307; size=3D2>And t</FONT><FONT face=3D&#23=
435;&#20307; size=3D2>he later=20
  </FONT><FONT face=3D&#23435;&#20307; size=3D2>versions of GSMP have nothi=
ng </FONT><FONT face=3D&#23435;&#20307;=20
  size=3D2>to do with ANCP.</FONT></DIV>
  <DIV><FONT face=3D&#23435;&#20307; size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3D&#23435;&#20307; size=3D2>Therefore, I think draft-ietf=
-gsmp-v3-base-spec-08=20
  has nothing to do with ANCP because it</FONT></DIV>
  <DIV><FONT face=3D&#23435;&#20307; size=3D2>is not a legal starting point=
 of ANCP.</FONT></DIV>
  <DIV><FONT face=3D&#23435;&#20307; size=3D2></FONT><FONT face=3D&#23435;&=
#20307; size=3D2><FONT face=3D&#23435;&#20307;=20
  size=3D2><FONT face=3D&#23435;&#20307; size=3D2></FONT></FONT>&nbsp;</DIV=
>
  <DIV>
  <DIV><FONT face=3D&#23435;&#20307; size=3D2><FONT face=3D&#23435;&#20307;=
 size=3D2>Furthermore, I think it is the=20
  responsibility of the newer draft&nbsp;to keep&nbsp;compatible with the o=
lder=20
  one.</FONT></DIV>
  <DIV>
  <DIV></FONT><FONT face=3D&#23435;&#20307; size=3D2>Since the draft-ietf-g=
smp-v3-base-spec-08 is=20
  newer than RFC3292, I think we should make </FONT></DIV>
  <DIV><FONT face=3D&#23435;&#20307; size=3D2>draft-ietf-gsmp-v3-base-spec-=
08 compatible with=20
  RFC3292, and accordingly the implementation</FONT></DIV>
  <DIV><FONT face=3D&#23435;&#20307; size=3D2>could be backward=20
  compatible.</FONT></DIV></DIV></FONT></DIV></DIV>
  <DIV><FONT face=3D&#23435;&#20307; size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3D&#23435;&#20307; size=3D2>cheers,</FONT></DIV>
  <DIV><FONT face=3D&#23435;&#20307; size=3D2>Fortune</FONT></DIV>
  <BLOCKQUOTE=20
  style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-=
LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
    <DIV style=3D"FONT: 9pt &#23435;&#20307;">----- Original Message ----- =
</DIV>
    <DIV=20
    style=3D"BACKGROUND: #e4e4e4; FONT: 9pt &#23435;&#20307;; font-color: b=
lack"><B>From:</B> <A=20
    title=3Dparberg@redback.com href=3D"mailto:parberg@redback.com">Peter A=
rberg</A>=20
    </DIV>
    <DIV style=3D"FONT: 9pt &#23435;&#20307;"><B>To:</B> <A title=3Dswadhwa=
@juniper.net=20
    href=3D"mailto:swadhwa@juniper.net">Sanjay Wadhwa</A> ; <A=20
    title=3Dtena@huawei.com href=3D"mailto:tena@huawei.com">Tina TSOU</A> ;=
 <A=20
    title=3Droberta.maglione@telecomitalia.it=20
    href=3D"mailto:roberta.maglione@telecomitalia.it">Maglione Roberta</A> =
; <A=20
    title=3Dwdec@cisco.com href=3D"mailto:wdec@cisco.com">Wojciech Dec (wde=
c)</A>=20
    </DIV>
    <DIV style=3D"FONT: 9pt &#23435;&#20307;"><B>Cc:</B> <A title=3Dancp@ie=
tf.org=20
    href=3D"mailto:ancp@ietf.org">ancp@ietf.org</A> </DIV>
    <DIV style=3D"FONT: 9pt &#23435;&#20307;"><B>Sent:</B> Thursday, May 01=
, 2008 7:20 AM</DIV>
    <DIV style=3D"FONT: 9pt &#23435;&#20307;"><B>Subject:</B> Re: [ANCP] qu=
estion regarding=20
    Labels in ANCP port up messages</DIV>
    <DIV><BR></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D062190723-30042008><FONT face=
=3DArial=20
    color=3D#0000ff size=3D2>Sanjay,</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D062190723-30042008><FONT face=
=3DArial=20
    color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D062190723-30042008><FONT face=
=3DArial=20
    color=3D#0000ff size=3D2>What do you mean "why I reference an old draft=
"&nbsp;=20
    ????????????</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D062190723-30042008><FONT face=
=3DArial=20
    color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D062190723-30042008><FONT face=
=3DArial=20
    color=3D#0000ff size=3D2>I'm surprised you even ask...&nbsp; please tak=
e a look=20
    at YOUR own internet-draft that most</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D062190723-30042008><FONT face=
=3DArial=20
    color=3D#0000ff size=3D2>of the ANCP working implementations are based =
on, in=20
    case you do not have this old</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D062190723-30042008><FONT face=
=3DArial=20
    color=3D#0000ff size=3D2>internet-draft, I have attached it to the=20
    document.</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D062190723-30042008><FONT face=
=3DArial=20
    color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D062190723-30042008><FONT face=
=3DArial=20
    color=3D#0000ff size=3D2>If you look at the reference for this ancp-dra=
ft, you=20
    will see that in the reference section</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D062190723-30042008><FONT face=
=3DArial=20
    color=3D#0000ff size=3D2>you point to this old gsmp-draft...&nbsp; Yes =
and I=20
    know this has been changed in the later</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D062190723-30042008><FONT face=
=3DArial=20
    color=3D#0000ff size=3D2>versions of the ANCP draft, but that do not ch=
ange the=20
    fact that many of the implementations</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D062190723-30042008><FONT face=
=3DArial=20
    color=3D#0000ff size=3D2>today was developed when the attached draft wa=
s=20
    current.</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D062190723-30042008><FONT face=
=3DArial=20
    color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D062190723-30042008><FONT face=
=3DArial=20
    color=3D#0000ff size=3D2>I think a very good question is brought up her=
e, and=20
    that is what is implemented and</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D062190723-30042008><FONT face=
=3DArial=20
    color=3D#0000ff size=3D2>running in networks today ?</FONT></SPAN></DIV=
>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D062190723-30042008><FONT face=
=3DArial=20
    color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D062190723-30042008><FONT face=
=3DArial=20
    color=3D#0000ff size=3D2>My take on this is that when the reference was=
 change=20
    from the old gsmp-draft to the older</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D062190723-30042008><FONT face=
=3DArial=20
    color=3D#0000ff size=3D2>RFC3292, apparently no one paid any attention =
to the=20
    fact the label definition in the event</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D062190723-30042008><FONT face=
=3DArial=20
    color=3D#0000ff size=3D2>message was different and not=20
    compatible.</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D062190723-30042008><FONT face=
=3DArial=20
    color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D062190723-30042008><FONT face=
=3DArial=20
    color=3D#0000ff size=3D2>What current implementations do today is an im=
portant=20
    factor in this discussion, and I think</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D062190723-30042008><FONT face=
=3DArial=20
    color=3D#0000ff size=3D2>it is time to come to realization that we migh=
t need a=20
    new version number for ANCP since</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D062190723-30042008><FONT face=
=3DArial=20
    color=3D#0000ff size=3D2>it continues to look like there is big holes o=
pen for=20
    interpretation. So if I did a ANCP</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D062190723-30042008><FONT face=
=3DArial=20
    color=3D#0000ff size=3D2>implementation there is bound to be interopera=
bility=20
    issues with existing implementations</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D062190723-30042008><FONT face=
=3DArial=20
    color=3D#0000ff size=3D2>runnig.</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D062190723-30042008><FONT face=
=3DArial=20
    color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D062190723-30042008><FONT face=
=3DArial=20
    color=3D#0000ff size=3D2>cheers,</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D062190723-30042008><FONT face=
=3DArial=20
    color=3D#0000ff size=3D2>Peter</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D062190723-30042008><FONT face=
=3DArial=20
    color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D062190723-30042008><FONT face=
=3DArial=20
    color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D062190723-30042008><FONT face=
=3DArial=20
    color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV><FONT face=3DArial=20
    color=3D#0000ff size=3D2></FONT><BR>
    <BLOCKQUOTE dir=3Dltr=20
    style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
      <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft=
>
      <HR tabIndex=3D-1>
      <FONT face=3DTahoma size=3D2><B>From:</B> Sanjay Wadhwa=20
      [mailto:swadhwa@juniper.net] <BR><B>Sent:</B> 30. april 2008=20
      14:42<BR><B>To:</B> Peter Arberg; Tina TSOU; Maglione Roberta; Wojcie=
ch=20
      Dec (wdec)<BR><B>Cc:</B> ancp@ietf.org<BR><B>Subject:</B> RE: [ANCP]=
=20
      question regarding Labels in ANCP port up messages<BR></FONT><BR></DI=
V>
      <DIV></DIV>
      <P><FONT size=3D2>Peter<BR>&nbsp; The ANCP draft as it currently stan=
ds is=20
      based on RFC3292. It provides extensions and modifications to relevan=
t=20
      constructs in RFC3292. There is no mention (implicit or explicit) of=
=20
      expired GSMP drafts in the ANCP draft. In order to implement the ANCP=
=20
      draft, I am not sure why one would look at the expired GSMP drafts. D=
o you=20
      see a reason to do this based on anything that you read in the ANCP d=
raft?=20
      Bringing up reference to expired gsmp draft in this thread&nbsp;just =
adds=20
      to the confusion. For GSMPv3 objects in the messages (such as Label T=
ype),=20
      one has to look at RFC3292 (this is clearly stated in the ANCP draft =
-=20
      section 2 and I am quoting it below) :</FONT></P>
      <P><FONT size=3D2><FONT color=3D#0000ff>ANCP uses a subset of GSMPv3 =
messages=20
      to implement currently defined use-cases. These relevant GSMPv3 messa=
ges=20
      are identified in section 5. GSMPv3 procedures with suitable extensio=
ns,=20
      as used by ANCP, are described in sections 5.1, 5.2 and 5.3. GSMPv3=20
      general extensions and GSMPv3 message specific extensions required by=
 ANCP=20
      are described in sub-sections of 5.4. In addition to specifying exten=
sions=20
      and modifications to relevant GSMP messages applicable to ANCP, this =
draft=20
      also defines the usage of these messages by ANCP, and indicates the v=
alues=20
      that ANCP should set for relevant fields in these GSMP messages. Howe=
ver,=20
      to understand the basic semantics of various fields in GSMP messages,=
 the=20
      reader is referred to [4].&nbsp;=3D&gt; RFC 3292.</FONT><BR><BR>What=
=20
      existing implementations currently do is an important but separate is=
sue.=20
      These implementations for most part precede the current ANCP draft. I=
t is=20
      fine to poll where these implementations diverge from the current dra=
ft.=20
      It is then upto the implementations (including the one that I am some=
what=20
      familiar with) to work towards compliance with the draft. </FONT></P>
      <P><FONT size=3D2>On the following points&nbsp;from &nbsp;Woj:</FONT>=
</P>
      <P><FONT size=3D2>Woj&gt;2) The current version of the spec is not ac=
curate,=20
      and does not reflect&nbsp;the fact that the known implementations fol=
low=20
      the label field definition from draft-gsmpv3-base-spec.</FONT></P>
      <P><FONT size=3D2>It is not for the protocol draft to point out what =
current=20
      implementations do.&nbsp;&nbsp;The best we can do is to further clari=
fy in=20
      the draft that type and value fields of the Label object (defined in=
=20
      RFC3292) should be set to 0 in the port-up message (we=20
      already&nbsp;mention the lable object as a whole should be set to all=
 0s).=20
      </FONT></P>
      <P><SPAN class=3D364043506-24042008><FONT size=3D2><SPAN=20
      class=3D709295811-24042008>Woj&gt; This would be a good thing for the=
 WG to=20
      discuss. There most evidently is a fair amount of&nbsp;"dead wood" in=
 the=20
      current spec, ie stuff that nobody yet&nbsp;implements or cares about=
.=20
      &nbsp;In the former case, we could re-cast that material using the ne=
w=20
      notions/extensions, in the latter case simply chop it=20
      out.</SPAN></FONT></SPAN></P>
      <P><SPAN class=3D364043506-24042008><FONT size=3D2><SPAN=20
      class=3D709295811-24042008>I agree. We are based on GSMPv3 (RFC3292)=
=20
      &nbsp;messages, and obviously not everything in these messages is=20
      leveraged by ANCP.&nbsp; However, the sync rate and OAM uses-cases ar=
e=20
      implemented and in use (ideally we should leave these alone...i.e. no=
=20
      change beyond adding more clarity if needed). For anything new (such =
as=20
      multicast) we are defining new messages&nbsp;(no legacy).&nbsp;=20
      </SPAN></FONT></SPAN></P>
      <P><FONT size=3D2>-Sanjay<BR><BR>&gt;-----Original Message-----<BR>&g=
t;From:=20
      Peter Arberg [</FONT><A href=3D"mailto:parberg@redback.com"><FONT=20
      size=3D2>mailto:parberg@redback.com</FONT></A><FONT size=3D2>]<BR>&gt=
;Sent:=20
      Wednesday, April 30, 2008 3:56 PM<BR>&gt;To: Tina TSOU; Maglione Robe=
rta;=20
      Sanjay Wadhwa; Wojciech Dec (wdec)<BR>&gt;Cc:=20
      ancp@ietf.org<BR>&gt;Subject: RE: [ANCP] question regarding Labels in=
 ANCP=20
      port up messages<BR>&gt;<BR>&gt;<BR>&gt;Hi,<BR>&gt;<BR>&gt;some times=
 I=20
      think it is amazing we ever got interoperability<BR>&gt;of ANCP=20
      :-)<BR>&gt;because looking at the label discussion is a very good exa=
mple=20
      that the<BR>&gt;whole GSMP - ANCP reference have not worked very=20
      well.<BR>&gt;<BR>&gt;In the ANCP draft, section 5.4.2 the event messa=
ge is=20
      shown like=20
      this:<BR>&gt;<BR>&gt;0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      3<BR>&gt;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=20
      1<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+<BR>&gt;|=20
      Vers&nbsp; |&nbsp; Sub&nbsp; | Message Type&nbsp; |=20
      Result|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      Code&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      |<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+<BR>&gt;|=20
      Partition ID&nbsp;=20
      |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      Transaction=20
      Identifier&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;=20
      |<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+<BR>&gt;|I|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      SubMessage Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;=20
      |<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+<BR>&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      Port&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      |<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+<BR>&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      Port Session=20
      Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      |<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+<BR>&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      Event Sequence=20
      Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      |<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+<BR>&gt;|x|S|x|x|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      |<BR>&gt;+-+-+-+-+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      Label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      |<BR>&gt;~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;=20
      ~<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+<BR>&gt;|x|x|x|x|x|x|x|x|=20
      Message Type&nbsp; |&nbsp;&nbsp; Tech Type&nbsp;&nbsp; | Block=20
      Length&nbsp;=20
      |<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+<BR>&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;=20
      |<BR>&gt;~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;=20
      Extension=20
      Value&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      ~<BR>&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;=20
      |<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+<BR>&gt;<BR>&gt;<BR>&gt;This=20
      is the exact same event message defined=20
      in<BR>&gt;draft-ietf-gsmp-v3-base-spec-08.txt&nbsp; section=20
      11.<BR>&gt;<BR>&gt;And in this gsmp-draft, section 5.1.3 the label sp=
ace=20
      is defined<BR>&gt;as minimum 8 bytes if the length=3D0 and as such no=
 value,=20
      and this<BR>&gt;is because the gsmp-draft has a new "label adaptaion"=
=20
      field.<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt;BUT in RFC3292 the event messag=
e is=20
      show in section 9, like=20
      this:<BR>&gt;<BR>&gt;0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      3<BR>&gt;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=20
      1<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+<BR>&gt;|&nbsp;&nbsp;&nbsp;=20
      Version&nbsp;&nbsp;&nbsp; | Message Type&nbsp; |&nbsp;&nbsp;&nbsp;=20
      Result&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;=20
      Code&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      |<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+<BR>&gt;|=20
      Partition ID&nbsp;=20
      |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      Transaction=20
      Identifier&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;=20
      |<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+<BR>&gt;|I|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      SubMessage Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;=20
      |<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+<BR>&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      Port&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      |<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+<BR>&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      Port Session=20
      Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      |<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+<BR>&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      Event Sequence=20
      Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      |<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+<BR>&gt;|x|S|x|x|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      |<BR>&gt;+-+-+-+-+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      Label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      |<BR>&gt;~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;=20
      ~<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+<BR>&gt;<BR>&gt;<BR>&gt;So=20
      a different Event Message picture/definition than what is shown<BR>&g=
t;in=20
      the ANCP draft, and in RFC3292 section 3.1.3 the label field<BR>&gt;i=
s=20
      defined as 4 bytes if length=3D0 and as such no=20
      value.<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt;So I very much agree with Woj t=
hat=20
      we need this issue to be resolved,<BR>&gt;and proabably a show of han=
ds=20
      what is actually done in different<BR>&gt;implementations, so we can =
nail=20
      down how the event message is<BR>&gt;suppose to look like in=20
      ANCP.<BR>&gt;<BR>&gt;<BR>&gt;I know at least 1 implementation which u=
ses 8=20
      bytes for the<BR>&gt;label=20
      field.<BR>&gt;<BR>&gt;<BR>&gt;cheers,<BR>&gt;Peter<BR>&gt;<BR>&gt;<BR=
>&gt;<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt;________________________________<BR>&g=
t;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      From: ancp-bounces@ietf.org<BR>&gt;[</FONT><A=20
      href=3D"mailto:ancp-bounces@ietf.org"><FONT=20
      size=3D2>mailto:ancp-bounces@ietf.org</FONT></A><FONT size=3D2>] On B=
ehalf Of=20
      Tina TSOU<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Sent: 30.=
=20
      april 2008 00:19<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; To=
:=20
      Maglione Roberta; Sanjay Wadhwa; Wojciech Dec=20
      (wdec)<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Cc:=20
      ancp@ietf.org<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Subje=
ct:=20
      Re: [ANCP] question regarding Labels in ANCP<BR>&gt;port up=20
      messages<BR>&gt;<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;=20
      Hi all,<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; It is clear=
 to=20
      me that if Label Length is filled as 0,<BR>&gt;there is nothing to be=
=20
      filled into Label Value. The whole<BR>&gt;Label part is 4 bytes, not =
8=20
      bytes.<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Chee=
rs=20
      from the last working day before Labor's Day<BR>&gt;holidays in some=
=20
      countries:)<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
=20
      Tina<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      ----- Original Message=20
      -----<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      From: Wojciech Dec (wdec) &lt;</FONT><A href=3D"mailto:wdec@cisco.com=
"><FONT=20
      size=3D2>mailto:wdec@cisco.com</FONT></A><FONT=20
      size=3D2>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      To: Sanjay Wadhwa &lt;</FONT><A href=3D"mailto:swadhwa@juniper.net"><=
FONT=20
      size=3D2>mailto:swadhwa@juniper.net</FONT></A><FONT size=3D2>&gt;<BR>=
&gt; ;=20
      Maglione Roberta &lt;</FONT><A=20
      href=3D"mailto:roberta.maglione@telecomitalia.it"><FONT=20
      size=3D2>mailto:roberta.maglione@telecomitalia.it</FONT></A><FONT=20
      size=3D2>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      Cc:=20
      ancp@ietf.org<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      Sent: Wednesday, April 30, 2008 1:12=20
      AM<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      Subject: Re: [ANCP] question regarding Labels<BR>&gt;in ANCP port up=
=20
      messages<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      Sanjay,=20
      All,<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      What is stated below runs counter to at least<BR>&gt;a handful of=20
      ANCP<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      implementations, all of which are known to=20
      be<BR>&gt;interoperable.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      There are really two=20
      options:<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      1) The current version of the spec is correct,<BR>&gt;and the=20
      known<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      interoperable implementations do not follow=20
      it<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      2) The current version of the spec is not<BR>&gt;accurate, and does n=
ot=20
      reflect<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      the fact that the known implementations follow<BR>&gt;the label=20
      field<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      definition from=20
      draft-gsmpv3-base-spec.<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      I would like to ask you, as the lead editor of<BR>&gt;the spec, to wo=
rk=20
      with<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      the WG in resolving what the problem is, and<BR>&gt;clearing up what =
the=20
      WG<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      spec says about and if 1) holds to be true,<BR>&gt;then proposing=20
      an<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      interoperability=20
      fix.<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      In either case, the issue highlights the fact<BR>&gt;that there is=20
      still<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      lingering confusion as to the dependencies<BR>&gt;ANCP has on rfc3292=
,=20
      or<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      draft-gsmpv3-base-spec, or both. It seems to<BR>&gt;be in the best=20
      interest=20
      of<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      all to address=20
      these.<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      Regards,<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      Woj.<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; -----Original=20
      Message-----<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; From: Sanjay Wadhwa [</FONT><A=20
      href=3D"mailto:swadhwa@juniper.net"><FONT=20
      size=3D2>mailto:swadhwa@juniper.net</FONT></A><FONT=20
      size=3D2>]<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; Sent: 29 April 2008=20
      17:29<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; To: Maglione=20
      Roberta<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; Cc: Wojciech Dec (wdec); ancp@ietf.org;<BR>&gt;Philippe Champagn=
e=20
      (pchamp)<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; Subject: RE: question regarding Labels in<BR>&gt;ANCP port up=20
      messages<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; Hi=20
      Maglione<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;&nbsp;&nbsp; Yes, the label format is as defined in RFC<BR>&gt;32=
92.=20
      The ANCP draft=20
      is<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; based on RFC 3292 and proposes<BR>&gt;extensions/modifications=20
      where<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      required.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; This is clearly stated upfront both in the<BR>&gt;abstract and=20
      in<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; section 2.=20
      In<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; section 5.4.2, it clearly&nbsp; specifies the<BR>&gt;format of "=
port=20
      up"=20
      message<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; (based on RFC 3292), and explicitly states<BR>&gt;the label=20
      field<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; should be=20
      set<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; to 0. Following is what the draft currently=20
      states:<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; 5.4.2 Topology Discovery=20
      Extensions<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; The GSMP Event message with PORT UP message<BR>&gt;type (80) is =
used=20
      for<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; conveying DSL line attributes to the NAS.<BR>&gt;The version fie=
ld=20
      should=20
      be<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; set to 3, and the sub field should be set to<BR>&gt;1. The I and=
=20
      subMessage<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; fields SHOULD be set to 1 to signify no<BR>&gt;fragmentation. Th=
e=20
      Port=20
      and<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; Label fields should be set to=20
      0.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;&nbsp;=20
      0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      2&nbsp;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      3<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0 1 2 3 4 =
5 6 7=20
      8 9 0 1 2 3 4 5 6 7<BR>&gt;8 9 0 1 2 3 4=20
      5<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; 6 7 8 9 0=20
      1<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Vers&nbsp; |&n=
bsp;=20
      Sub&nbsp; | Message Type&nbsp;=20
      |<BR>&gt;Result|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      Code<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Partition ID&n=
bsp;=20
      |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<B=
R>&gt;Transaction=20
      Identifier<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      |I|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SubMessage=20
      Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      |&nbsp;&nbsp;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      Length<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;=20
      Port<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      Port Session=20
      Number<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      Event Sequence=20
      Number<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      |x|S|x|x|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      +-+-+-+-+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      Label<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      ~<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      ~<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |x|x|x|x|x|x|x|x=
|=20
      Message Type&nbsp; |&nbsp;&nbsp;<BR>&gt;Tech Type&nbsp;&nbsp; | Block=
=20
      Length<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      ~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;=20
      Extension=20
      Value<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      ~<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; When we say the label field should be set to<BR>&gt;0, the=20
      intention<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; is for=20
      the<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; type and length fields in the label TLV to<BR>&gt;be set to 0. W=
e=20
      can<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; explicitly state this for=20
      clarity.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      -Sanjay<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;-----Original=20
      Message-----<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;From: Maglione Roberta<BR>&gt;[</FONT><A=20
      href=3D"mailto:roberta.maglione@telecomitalia.it"><FONT=20
      size=3D2>mailto:roberta.maglione@telecomitalia.it</FONT></A><FONT=20
      size=3D2>]<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;Sent: Tuesday, April 29, 2008 8:06=20
      AM<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;To: Sanjay=20
      Wadhwa<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;Cc: Wojciech Dec (wdec);=20
      ancp@ietf.org;<BR>&gt;pchamp@cisco.com<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;Subject: RE: question regarding Labels in<BR>&gt;ANCP port u=
p=20
      messages<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;Hi Sanjay and=20
      All,<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp; I was reading the current=20
      ancp<BR>&gt;protocol draft in order=20
      to<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt; understand which should be the correct<BR>&gt;format for th=
e=20
      label<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;field in the ancp port Up=20
      message.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;Actually as it was already pointed out in<BR>&gt;the alias t=
he=20
      draft<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;in section 5.4.2 says "GSMP Event message<BR>&gt;with PORT U=
P=20
      message<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;type (80) is used"&nbsp; thus I am assuming that<BR>&gt;the =
label=20
      in=20
      the<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;port UP message should follow the message<BR>&gt;format defi=
ned=20
      in<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;RFC 3292, section=20
      3.1.3:<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;=20
      0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt;2&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;=20
      3<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp; 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8=20
      9<BR>&gt;0 1 2 3 4 5 6 7 8 9 0=20
      1<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;&nbsp;&nbsp;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp; |x|S|x|x|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; L=
abel=20
      Type&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt;&nbsp; Label=20
      Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;&nbsp;&nbsp;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;=20
      |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;=20
      |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;=20
      ~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;=20
      Label=20
      Value&nbsp;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;=20
      ~<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;=20
      |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;=20
      |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;&nbsp;&nbsp;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;but from what I have seen different<BR>&gt;implementations=20
      use<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;different format for label field: in<BR>&gt;particular=20
      several<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;implementations use&nbsp; a label format that is<BR>&gt;simi=
lar=20
      to the=20
      one<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;specified in the expired=20
      draft<BR>&gt;draft-ietf-gsmp-v3-base-spec:<BR>&gt;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;=20
      0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt;=20
      2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      3<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0 1 2 3 4 5 6 7 8 9 0 1=
 2 3=20
      4 5 6 7<BR>&gt;8 9 0 1 2 3 4 5=20
      6<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; 7 8 9 0=20
      1<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      |x|S|x|x|x|x|x|x|x|x|x|x|x|x|x|x|&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      Label<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; Type&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp; Label=20
      Adaptation&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;=20
      |&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;=20
      Label<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      ~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;=20
      Label=20
      Value<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      ~<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;Even if ancp does not care about the label<BR>&gt;field, hav=
ing=20
      this<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;field somehow not clearly specified in the<BR>&gt;current an=
cp=20
      draft<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;can easily lead to interoperability issues,<BR>&gt;thus I th=
ink=20
      it<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;would be very helpful if you and/or the<BR>&gt;other editors=
=20
      can<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;clarify what should be the correct format<BR>&gt;for the lab=
el=20
      field<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;to be used in the ancp Port Up=20
      message.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;Thanks and best=20
      regards,<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;Roberta<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;________________________________________<BR>&gt;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;From: Philippe Champagne (pchamp)=20
      [pchamp@cisco.com]<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;Sent: Thursday, April 24, 2008 7:14=20
      PM<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;To: Sanjay=20
      Wadhwa<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;Cc: Maglione Roberta; Wojciech Dec=20
      (wdec);<BR>&gt;ancp@ietf.org<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;Subject: question regarding&nbsp; Labels in ANCP<BR>&gt;port=
 up=20
      messages<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;Hi=20
      Sanjay<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;In section 5.4.2 of the draft, we=20
      have:<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      2<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      3<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0 1 2 3 4 5=
 6 7=20
      8 9 0 1 2 3 4 5 6<BR>&gt;7 8 9 0 1 2 3 4 5=20
      6<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;7 8 9 0=20
      1<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;<BR>&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Vers&nbsp; |&nb=
sp;=20
      Sub&nbsp; | Message Type&nbsp;=20
      |<BR>&gt;Result|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      Code<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;<BR>&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Partition ID&nb=
sp;=20
      |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<B=
R>&gt;Transaction=20
      Identifier<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;<BR>&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      |I|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SubMessage=20
      Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      |&nbsp;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      Length<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;<BR>&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;=20
      Port<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;<BR>&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      Port Session=20
      Number<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;<BR>&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      Event Sequence=20
      Number<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;<BR>&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      |x|S|x|x|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      +-+-+-+-+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      Label<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      ~<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      ~<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;<BR>&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |x|x|x|x|x|x|x|x|=
=20
      Message Type&nbsp; |&nbsp;&nbsp;<BR>&gt;Tech Type&nbsp;&nbsp;=20
      |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;Block Length&nbsp;=20
      |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;<BR>&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      ~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;=20
      Extension=20
      Value<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      ~<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;<BR>&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;Where Label I suppose is taken from the RFC<BR>&gt;3292,=20
      section<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;3.1.3: (well, I'm=20
      guessing)<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp; A summary of TLV labels supported in<BR>&gt;thi=
s=20
      version of=20
      the<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; protocol=20
      is<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp; listed=20
      below:<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; TLV=20
      Label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      Type&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Section=20
      Title<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      ---------&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      ----&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      -------------<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ATM=20
      Label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0x100&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;=20
      ATM TLV=20
      Labels<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; FR=20
      Label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      0x101&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Frame Relay<BR>&gt;TLV=20
      Labels<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MPLS Gen Label=20
      0x102&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MPLS<BR>&gt;Generic TLV=20
      Labels<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; FEC=20
      Label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0x103&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;=20
      FEC TLV=20
      Labels<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp; All Labels will be designated as=20
      follow:<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;=20
      0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt;2&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;=20
      3<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp; 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8=20
      9<BR>&gt;0 1 2 3 4 5 6 7 8 9 0=20
      1<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;&nbsp;&nbsp;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp; |x|S|x|x|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; L=
abel=20
      Type&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt;&nbsp; Label=20
      Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;&nbsp;&nbsp;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;=20
      |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;=20
      |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;=20
      ~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;=20
      Label=20
      Value&nbsp;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;=20
      ~<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;=20
      |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;=20
      |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;&nbsp;&nbsp;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; x: Reserved=20
      Flags.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; These are=20
      generally used by<BR>&gt;specific messages and will=20
      be<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; defined in =
those=20
      messages.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; S: Stacked Label=20
      Indicator<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Label Stack=
ing=20
      is discussed below<BR>&gt;in section=20
      3.1.3.5<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Label=20
      Type<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A 12-bit fi=
eld=20
      indicating the type<BR>&gt;of=20
      label.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Label=20
      Length<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A 16-bit fi=
eld=20
      indicating the<BR>&gt;length of the=20
      Label<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; Value=20
      field<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; in=20
      bytes.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Label=20
      Value<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A variable=
=20
      length field that is an<BR>&gt;integer number of 32=20
      bit<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; words=20
      long.&nbsp; The Label Value field<BR>&gt;is=20
      interpreted<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; according=20
      to<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the Label T=
ype=20
      as described in the<BR>&gt;following=20
      sections.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;The draft is a bit obscure about this and<BR>&gt;since it=20
      doesn't<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;specify much, it can lead to<BR>&gt;misinterpretation for th=
e=20
      unused<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;part. Moreover, it would appear that<BR>&gt;several=20
      implementations<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;currently use another format for the label<BR>&gt;field. Can=
=20
      you<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;explain?&nbsp; I mean, how come what's in the<BR>&gt;current=
=20
      draft=20
      doesn't<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;match what's known to be=20
      implemented?<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;I'm still wondering why we carried over<BR>&gt;pieces from G=
SMP=20
      that<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;we do not intend to=20
      use.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;I would recommend that if we are to keep<BR>&gt;them but not=
=20
      use<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;them, we should mention precisely how we<BR>&gt;intend not t=
o=20
      use<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;them: that is how many 0 filled bytes this<BR>&gt;is expecte=
d to=20
      use<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;The rfc 3292 doesn't cover the case where<BR>&gt;this field =
is=20
      not=20
      used.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;Can you shed some ligths on=20
      this?<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;Thanks<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;Regards<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;Phil<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;<BR>&gt;&gt;-----------------------------------------------------=
---------------<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;CONFIDENTIALITY=20
      NOTICE<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;This message and its attachments are<BR>&gt;addressed solely=
 to=20
      the<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;persons above and may contain confidential<BR>&gt;informatio=
n. If=20
      you<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;have received the message in error, be<BR>&gt;informed that =
any=20
      use<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;of the content hereof is prohibited. Please<BR>&gt;return=20
      it<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;immediately to the sender and delete the<BR>&gt;message. Sho=
uld=20
      you<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;have any questions, please contact us by replying=20
      to<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;webmaster@telecomitalia.it.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Thank=20
      you<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;<BR>&gt;www.telecomitalia.it<BR>&gt;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;<BR>&gt;&gt;-----------------------------------------------------=
---------------<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      _______________________________________________<BR>&gt;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;=20
      ANCP mailing=20
      list<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      ANCP@ietf.org<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      </FONT><A href=3D"https://www.ietf.org/mailman/listinfo/ancp"=20
      target=3D_blank><FONT=20
      size=3D2>https://www.ietf.org/mailman/listinfo/ancp</FONT></A><BR><FO=
NT=20
      size=3D2>&gt;<BR>&gt;</FONT> </P></BLOCKQUOTE>
    <P>
    <HR>

    <P></P>_______________________________________________<BR>ANCP mailing=
=20
    list<BR>ANCP@ietf.org<BR>https://www.ietf.org/mailman/listinfo/ancp<BR>=
</BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

--_000_48C276B536524E478C659685995F6AA539DBBBE720RBSJXadredbac_--

--===============1850680821==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1850680821==--


From ancp-bounces@ietf.org  Fri May  2 05:36:19 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 07AF23A6862;
	Fri,  2 May 2008 05:36:19 -0700 (PDT)
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 04C183A6806
	for <ancp@core3.amsl.com>; Fri,  2 May 2008 05:36:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.098
X-Spam-Level: 
X-Spam-Status: No, score=-1.098 tagged_above=-999 required=5
	tests=[AWL=-5.501, BAYES_00=-2.599, HTML_MESSAGE=0.001,
	HTML_OBFUSCATE_05_10=0.001, J_BACKHAIR_12=1, J_BACKHAIR_21=1,
	J_BACKHAIR_22=1, J_BACKHAIR_23=1, J_BACKHAIR_24=1, J_BACKHAIR_25=1,
	J_BACKHAIR_26=1, J_BACKHAIR_27=1, J_BACKHAIR_32=1, J_BACKHAIR_42=1,
	J_BACKHAIR_52=1, RCVD_IN_DNSWL_MED=-4]
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 MPuulk4LOAGo for <ancp@core3.amsl.com>;
	Fri,  2 May 2008 05:36:14 -0700 (PDT)
Received: from exprod7og111.obsmtp.com (exprod7og111.obsmtp.com [64.18.2.175])
	by core3.amsl.com (Postfix) with ESMTP id 0800D3A6963
	for <ancp@ietf.org>; Fri,  2 May 2008 05:36:07 -0700 (PDT)
Received: from source ([66.129.224.36]) by exprod7ob111.postini.com
	([64.18.6.12]) with SMTP; Fri, 02 May 2008 05:35:29 PDT
Received: from proton.jnpr.net ([10.10.2.37]) by gamma.jnpr.net with Microsoft
	SMTPSVC(6.0.3790.1830); Fri, 2 May 2008 05:35:25 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 2 May 2008 08:35:22 -0400
Message-ID: <9BD5D7887235424FA97DFC223CAE3C28102EB5AA@proton.jnpr.net>
In-Reply-To: <48C276B536524E478C659685995F6AA539DBBBE577@RBSJX.ad.redback.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ANCP] question regarding  Labels in ANCP port up messages
Thread-Index: Aciqkn5nSPBPuwuySsamcvxF1uU6kQAZ9dQQAAE415AABe3TAABN80lQ
References: <48C276B536524E478C659685995F6AA539DBBBE370@RBSJX.ad.redback.com>
	<9BD5D7887235424FA97DFC223CAE3C280AB43A10@proton.jnpr.net>
	<48C276B536524E478C659685995F6AA539DBBBE577@RBSJX.ad.redback.com>
From: "Sanjay Wadhwa" <swadhwa@juniper.net>
To: "Peter Arberg" <parberg@redback.com>, "Tina TSOU" <tena@huawei.com>,
	"Maglione Roberta" <roberta.maglione@telecomitalia.it>,
	"Wojciech Dec (wdec)" <wdec@cisco.com>
X-OriginalArrivalTime: 02 May 2008 12:35:25.0203 (UTC)
	FILETIME=[FEC95E30:01C8AC50]
Cc: ancp@ietf.org
Subject: Re: [ANCP] question regarding  Labels in ANCP port up messages
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/pipermail/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>
Content-Type: multipart/mixed; boundary="===============1730325901=="
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1730325901==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8AC50.FDF238B5"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8AC50.FDF238B5
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Peter

 You missed my point below. The ANCP draft since becoming a WG draft
does NOT refer to the old GSMP drafts. Any implementations based on this
WG-draft are expected to be interoperable. You are pointing to
pre-WG-draft versions of ANCP, and these were indeed based on expired
GSMP drafts that evolved past RFC3292.=20

There is incompatibility between the current ANCP WG-draft and previous
non-WG versions (TLV clash, label format..). As mentioned earlier it is
prudent for older implementations to start supporting the WG-draft
version as soon as possible.=20

=20

For interoperability of WG-draft with the older pre-WG versions, I see
the following options:

=20

1. Versioning starts with the WG-draft i.e. WG-draft is version =3D 3,
sub-version =3D 1. For any interop issues between older non-WG versions
and the WG-draft, one needs to look at solving it within implementations
(e.g. an AN that implements the WG-draft, could based on a configuration
knob, generate a PORT-UP message with old label format the will be
accepted by BNG implementing pre-WG versions of the draft).=20

=20

2. Change the WG-draft (current draft) to use version =3D 3 and
sub-version =3D 2. This is assuming there is no deployed implementation =
of
current WG-draft that already uses 3.1 as the version, and also assuming
the old pre-WG implementations use 3.1. There will be no backwards
compatibility i.e. version 3.1 BNG will not work with version 3.2 AN (we
will need to list this as caveat in the appendix section). AN and BNG
will need to negotiate the same version in order for ANCP adjacency to
come up. A BNG supporting both versions 3.1 and 3.2 could simultaneously
become adjacent with one AN supporting 3.1 and another AN supporting
3.2. (i.e. version compatibility is per adjacency).

Also, major version number change (e.g. from 3 to 4) should only
correspond to a major change in the protocol (e.g. different mechanism,
different transport etc).

=20

My vote would be to adopt option 2 above only if further changes to
WG-draft happen that render it incompatible with the current WG-draft.
Any interoperability issues with pre-WG versions could be handled via
option 1.

=20

Cheers

-Sanjay

=20

________________________________

From: Peter Arberg [mailto:parberg@redback.com]=20
Sent: Wednesday, April 30, 2008 7:20 PM
To: Sanjay Wadhwa; Tina TSOU; Maglione Roberta; Wojciech Dec (wdec)
Cc: ancp@ietf.org
Subject: RE: [ANCP] question regarding Labels in ANCP port up messages

=20

Sanjay,

=20

What do you mean "why I reference an old draft"  ????????????

=20

I'm surprised you even ask...  please take a look at YOUR own
internet-draft that most

of the ANCP working implementations are based on, in case you do not
have this old

internet-draft, I have attached it to the document.

=20

If you look at the reference for this ancp-draft, you will see that in
the reference section

you point to this old gsmp-draft...  Yes and I know this has been
changed in the later

versions of the ANCP draft, but that do not change the fact that many of
the implementations

today was developed when the attached draft was current.

=20

I think a very good question is brought up here, and that is what is
implemented and

running in networks today ?

=20

My take on this is that when the reference was change from the old
gsmp-draft to the older

RFC3292, apparently no one paid any attention to the fact the label
definition in the event

message was different and not compatible.

=20

What current implementations do today is an important factor in this
discussion, and I think

it is time to come to realization that we might need a new version
number for ANCP since

it continues to look like there is big holes open for interpretation. So
if I did a ANCP

implementation there is bound to be interoperability issues with
existing implementations

runnig.

=20

cheers,

Peter

=20

=20

=20

	=20

=09
________________________________


	From: Sanjay Wadhwa [mailto:swadhwa@juniper.net]=20
	Sent: 30. april 2008 14:42
	To: Peter Arberg; Tina TSOU; Maglione Roberta; Wojciech Dec
(wdec)
	Cc: ancp@ietf.org
	Subject: RE: [ANCP] question regarding Labels in ANCP port up
messages

	Peter
	  The ANCP draft as it currently stands is based on RFC3292. It
provides extensions and modifications to relevant constructs in RFC3292.
There is no mention (implicit or explicit) of expired GSMP drafts in the
ANCP draft. In order to implement the ANCP draft, I am not sure why one
would look at the expired GSMP drafts. Do you see a reason to do this
based on anything that you read in the ANCP draft? Bringing up reference
to expired gsmp draft in this thread just adds to the confusion. For
GSMPv3 objects in the messages (such as Label Type), one has to look at
RFC3292 (this is clearly stated in the ANCP draft - section 2 and I am
quoting it below) :

	ANCP uses a subset of GSMPv3 messages to implement currently
defined use-cases. These relevant GSMPv3 messages are identified in
section 5. GSMPv3 procedures with suitable extensions, as used by ANCP,
are described in sections 5.1, 5.2 and 5.3. GSMPv3 general extensions
and GSMPv3 message specific extensions required by ANCP are described in
sub-sections of 5.4. In addition to specifying extensions and
modifications to relevant GSMP messages applicable to ANCP, this draft
also defines the usage of these messages by ANCP, and indicates the
values that ANCP should set for relevant fields in these GSMP messages.
However, to understand the basic semantics of various fields in GSMP
messages, the reader is referred to [4]. =3D> RFC 3292.
=09
	What existing implementations currently do is an important but
separate issue. These implementations for most part precede the current
ANCP draft. It is fine to poll where these implementations diverge from
the current draft. It is then upto the implementations (including the
one that I am somewhat familiar with) to work towards compliance with
the draft.=20

	On the following points from  Woj:

	Woj>2) The current version of the spec is not accurate, and does
not reflect the fact that the known implementations follow the label
field definition from draft-gsmpv3-base-spec.

	It is not for the protocol draft to point out what current
implementations do.  The best we can do is to further clarify in the
draft that type and value fields of the Label object (defined in
RFC3292) should be set to 0 in the port-up message (we already mention
the lable object as a whole should be set to all 0s).=20

	Woj> This would be a good thing for the WG to discuss. There
most evidently is a fair amount of "dead wood" in the current spec, ie
stuff that nobody yet implements or cares about.  In the former case, we
could re-cast that material using the new notions/extensions, in the
latter case simply chop it out.

	I agree. We are based on GSMPv3 (RFC3292)  messages, and
obviously not everything in these messages is leveraged by ANCP.
However, the sync rate and OAM uses-cases are implemented and in use
(ideally we should leave these alone...i.e. no change beyond adding more
clarity if needed). For anything new (such as multicast) we are defining
new messages (no legacy). =20

	-Sanjay
=09
	>-----Original Message-----
	>From: Peter Arberg [mailto:parberg@redback.com
<mailto:parberg@redback.com> ]
	>Sent: Wednesday, April 30, 2008 3:56 PM
	>To: Tina TSOU; Maglione Roberta; Sanjay Wadhwa; Wojciech Dec
(wdec)
	>Cc: ancp@ietf.org
	>Subject: RE: [ANCP] question regarding Labels in ANCP port up
messages
	>
	>
	>Hi,
	>
	>some times I think it is amazing we ever got interoperability
	>of ANCP :-)
	>because looking at the label discussion is a very good example
that the
	>whole GSMP - ANCP reference have not worked very well.
	>
	>In the ANCP draft, section 5.4.2 the event message is shown
like this:
	>
	>0                   1                   2                   3
	>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
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	>| Vers  |  Sub  | Message Type  | Result|        Code
|
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	>| Partition ID  |            Transaction Identifier
|
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	>|I|      SubMessage Number      |           Length
|
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	>|                             Port
|
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	>|                      Port Session Number
|
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	>|                     Event Sequence Number
|
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	>|x|S|x|x|
|
	>+-+-+-+-+                     Label
|
	>~
~
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	>|x|x|x|x|x|x|x|x| Message Type  |   Tech Type   | Block Length
|
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	>|
|
	>~                         Extension Value
~
	>|
|
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	>
	>
	>This is the exact same event message defined in
	>draft-ietf-gsmp-v3-base-spec-08.txt  section 11.
	>
	>And in this gsmp-draft, section 5.1.3 the label space is
defined
	>as minimum 8 bytes if the length=3D0 and as such no value, and
this
	>is because the gsmp-draft has a new "label adaptaion" field.
	>
	>
	>
	>BUT in RFC3292 the event message is show in section 9, like
this:
	>
	>0                   1                   2                   3
	>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
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	>|    Version    | Message Type  |    Result     |     Code
|
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	>| Partition ID  |            Transaction Identifier
|
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	>|I|      SubMessage Number      |           Length
|
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	>|                             Port
|
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	>|                      Port Session Number
|
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	>|                     Event Sequence Number
|
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	>|x|S|x|x|
|
	>+-+-+-+-+                     Label
|
	>~
~
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	>
	>
	>So a different Event Message picture/definition than what is
shown
	>in the ANCP draft, and in RFC3292 section 3.1.3 the label field
	>is defined as 4 bytes if length=3D0 and as such no value.
	>
	>
	>
	>So I very much agree with Woj that we need this issue to be
resolved,
	>and proabably a show of hands what is actually done in
different
	>implementations, so we can nail down how the event message is
	>suppose to look like in ANCP.
	>
	>
	>I know at least 1 implementation which uses 8 bytes for the
	>label field.
	>
	>
	>cheers,
	>Peter
	>
	>
	>
	>
	>
	>
	>________________________________
	>
	>        From: ancp-bounces@ietf.org
	>[mailto:ancp-bounces@ietf.org <mailto:ancp-bounces@ietf.org> ]
On Behalf Of Tina TSOU
	>        Sent: 30. april 2008 00:19
	>        To: Maglione Roberta; Sanjay Wadhwa; Wojciech Dec
(wdec)
	>        Cc: ancp@ietf.org
	>        Subject: Re: [ANCP] question regarding Labels in ANCP
	>port up messages
	>
	>
	>        Hi all,
	>        It is clear to me that if Label Length is filled as 0,
	>there is nothing to be filled into Label Value. The whole
	>Label part is 4 bytes, not 8 bytes.
	>
	>        Cheers from the last working day before Labor's Day
	>holidays in some countries:)
	>
	>        Tina
	>
	>                ----- Original Message -----
	>                From: Wojciech Dec (wdec)
<mailto:wdec@cisco.com <mailto:wdec@cisco.com> >
	>                To: Sanjay Wadhwa <mailto:swadhwa@juniper.net
<mailto:swadhwa@juniper.net> >
	> ; Maglione Roberta <mailto:roberta.maglione@telecomitalia.it
<mailto:roberta.maglione@telecomitalia.it> >
	>                Cc: ancp@ietf.org
	>                Sent: Wednesday, April 30, 2008 1:12 AM
	>                Subject: Re: [ANCP] question regarding Labels
	>in ANCP port up messages
	>
	>                Sanjay, All,
	>
	>                What is stated below runs counter to at least
	>a handful of ANCP
	>                implementations, all of which are known to be
	>interoperable.
	>                There are really two options:
	>                1) The current version of the spec is correct,
	>and the known
	>                interoperable implementations do not follow it
	>                2) The current version of the spec is not
	>accurate, and does not reflect
	>                the fact that the known implementations follow
	>the label field
	>                definition from draft-gsmpv3-base-spec.
	>
	>                I would like to ask you, as the lead editor of
	>the spec, to work with
	>                the WG in resolving what the problem is, and
	>clearing up what the WG
	>                spec says about and if 1) holds to be true,
	>then proposing an
	>                interoperability fix.
	>
	>                In either case, the issue highlights the fact
	>that there is still
	>                lingering confusion as to the dependencies
	>ANCP has on rfc3292, or
	>                draft-gsmpv3-base-spec, or both. It seems to
	>be in the best interest of
	>                all to address these.
	>
	>                Regards,
	>                Woj.
	>
	>                > -----Original Message-----
	>                > From: Sanjay Wadhwa
[mailto:swadhwa@juniper.net <mailto:swadhwa@juniper.net> ]
	>                > Sent: 29 April 2008 17:29
	>                > To: Maglione Roberta
	>                > Cc: Wojciech Dec (wdec); ancp@ietf.org;
	>Philippe Champagne (pchamp)
	>                > Subject: RE: question regarding Labels in
	>ANCP port up messages
	>                >
	>                > Hi Maglione
	>                >   Yes, the label format is as defined in RFC
	>3292. The ANCP draft is
	>                > based on RFC 3292 and proposes
	>extensions/modifications where
	>                > required.
	>                > This is clearly stated upfront both in the
	>abstract and in
	>                > section 2. In
	>                > section 5.4.2, it clearly  specifies the
	>format of "port up" message
	>                > (based on RFC 3292), and explicitly states
	>the label field
	>                > should be set
	>                > to 0. Following is what the draft currently
states:
	>                >
	>                >
	>                > 5.4.2 Topology Discovery Extensions
	>                >
	>                > The GSMP Event message with PORT UP message
	>type (80) is used for
	>                > conveying DSL line attributes to the NAS.
	>The version field should be
	>                > set to 3, and the sub field should be set to
	>1. The I and subMessage
	>                > fields SHOULD be set to 1 to signify no
	>fragmentation. The Port and
	>                > Label fields should be set to 0.
	>                >
	>                >  0                   1                   2 =20
	>                3
	>                >          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
	>                >
	>                >
	>                >
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	>                >         | Vers  |  Sub  | Message Type  |
	>Result|        Code
	>                > |
	>                >
	>                >
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	>                >         | Partition ID  |          =20
	>Transaction Identifier
	>                > |
	>                >
	>                >
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	>                >         |I|      SubMessage Number      |  =20
	>       Length
	>                > |
	>                >
	>                >
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	>                >         |                             Port
	>                > |
	>                >
	>                >
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	>                >         |                      Port Session
Number
	>                > |
	>                >
	>                >
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	>                >         |                     Event Sequence
Number
	>                > |
	>                >
	>                >
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	>                >         |x|S|x|x|
	>                > |
	>                >         +-+-+-+-+                     Label
	>                > |
	>                >         ~
	>                > ~
	>                >
	>                >
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	>                >         |x|x|x|x|x|x|x|x| Message Type  | =20
	>Tech Type   | Block Length
	>                > |
	>                >
	>                >
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	>                >         |
	>                > |
	>                >         ~                         Extension
Value
	>                > ~
	>                >         |
	>                > |
	>                >
	>                >
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	>                >
	>                > When we say the label field should be set to
	>0, the intention
	>                > is for the
	>                > type and length fields in the label TLV to
	>be set to 0. We can
	>                > explicitly state this for clarity.
	>                >
	>                > -Sanjay
	>                >
	>                > >-----Original Message-----
	>                > >From: Maglione Roberta
	>[mailto:roberta.maglione@telecomitalia.it
<mailto:roberta.maglione@telecomitalia.it> ]
	>                > >Sent: Tuesday, April 29, 2008 8:06 AM
	>                > >To: Sanjay Wadhwa
	>                > >Cc: Wojciech Dec (wdec); ancp@ietf.org;
	>pchamp@cisco.com
	>                > >Subject: RE: question regarding Labels in
	>ANCP port up messages
	>                > >
	>                > >
	>                > >Hi Sanjay and All,
	>                > >     I was reading the current ancp
	>protocol draft in order to
	>                > > understand which should be the correct
	>format for the label
	>                > >field in the ancp port Up message.
	>                > >Actually as it was already pointed out in
	>the alias the draft
	>                > >in section 5.4.2 says "GSMP Event message
	>with PORT UP message
	>                > >type (80) is used"  thus I am assuming that
	>the label in the
	>                > >port UP message should follow the message
	>format defined in
	>                > >RFC 3292, section 3.1.3:
	>                > >
	>                > >    0                   1                 =20
	>2                   3
	>                > >    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
	>                > > =20
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	>                > >   |x|S|x|x|       Label Type      |      =20
	>  Label Length         |
	>                > > =20
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	>                > >   |                                      =20
	>                       |
	>                > >   ~                          Label Value =20
	>                       ~
	>                > >   |                                      =20
	>                       |
	>                > > =20
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	>                > >
	>                > >but from what I have seen different
	>implementations use
	>                > >different format for label field: in
	>particular several
	>                > >implementations use  a label format that is
	>similar to the one
	>                > >specified in the expired draft
	>draft-ietf-gsmp-v3-base-spec:
	>                > >
	>                > >     0                   1                =20
	> 2                   3
	>                > >       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
	>                > >
	>                >
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	>                > >      |x|S|x|x|x|x|x|x|x|x|x|x|x|x|x|x|   =20
	>       Label
	>                > Type         |
	>                > >
	>                >
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	>                > >      |    Label Adaptation           |   =20
	>     Label
	>                > Length         |
	>                > >
	>                >
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	>                > >      |
	>                >          |
	>                > >      ~                          Label Value
	>                >          ~
	>                > >      |
	>                >          |
	>                > >
	>                >
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	>                > >
	>                > >
	>                > >Even if ancp does not care about the label
	>field, having this
	>                > >field somehow not clearly specified in the
	>current ancp draft
	>                > >can easily lead to interoperability issues,
	>thus I think it
	>                > >would be very helpful if you and/or the
	>other editors can
	>                > >clarify what should be the correct format
	>for the label field
	>                > >to be used in the ancp Port Up message.
	>                > >
	>                > >Thanks and best regards,
	>                > >Roberta
	>                > >
	>                > >________________________________________
	>                > >From: Philippe Champagne (pchamp)
[pchamp@cisco.com]
	>                > >Sent: Thursday, April 24, 2008 7:14 PM
	>                > >To: Sanjay Wadhwa
	>                > >Cc: Maglione Roberta; Wojciech Dec (wdec);
	>ancp@ietf.org
	>                > >Subject: question regarding  Labels in ANCP
	>port up messages
	>                > >
	>                > >Hi Sanjay
	>                > >
	>                > >In section 5.4.2 of the draft, we have:
	>                > >
	>                > >
	>                > >         0                   1
2
	>                >         3
	>                > >         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
	>                > >
	>                >
=09
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	>                > >        | Vers  |  Sub  | Message Type  |
	>Result|        Code
	>                > >         |
	>                > >
	>                >
=09
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	>                > >        | Partition ID  |          =20
	>Transaction Identifier
	>                > >         |
	>                > >
	>                >
=09
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	>                > >        |I|      SubMessage Number      | =20
	>        Length
	>                > >         |
	>                > >
	>                >
=09
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	>                > >        |                             Port
	>                > >         |
	>                > >
	>                >
=09
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	>                > >        |                      Port Session
Number
	>                > >         |
	>                > >
	>                >
=09
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	>                > >        |                     Event Sequence
Number
	>                > >         |
	>                > >
	>                >
=09
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	>                > >        |x|S|x|x|
	>                > >         |
	>                > >        +-+-+-+-+                     Label
	>                > >         |
	>                > >        ~
	>                > >         ~
	>                > >
	>                >
=09
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	>                > >        |x|x|x|x|x|x|x|x| Message Type  | =20
	>Tech Type   |
	>                > >Block Length  |
	>                > >
	>                >
=09
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	>                > >        |
	>                > >         |
	>                > >        ~                         Extension
Value
	>                > >         ~
	>                > >        |
	>                > >         |
	>                > >
	>                >
=09
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	>                > >Where Label I suppose is taken from the RFC
	>3292, section
	>                > >3.1.3: (well, I'm guessing)
	>                > >
	>                > >   A summary of TLV labels supported in
	>this version of the
	>                > protocol is
	>                > >   listed below:
	>                > >
	>                > >      TLV Label      Type       Section
Title
	>                > >      ---------      ----
-------------
	>                > >      ATM Label      0x100      ATM TLV
Labels
	>                > >      FR Label       0x101      Frame Relay
	>TLV Labels
	>                > >      MPLS Gen Label 0x102      MPLS
	>Generic TLV Labels
	>                > >      FEC Label      0x103      FEC TLV
Labels
	>                > >
	>                > >   All Labels will be designated as follow:
	>                > >
	>                > >    0                   1                 =20
	>2                   3
	>                > >    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
	>                > > =20
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	>                > >   |x|S|x|x|       Label Type      |      =20
	>  Label Length         |
	>                > > =20
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	>                > >   |                                      =20
	>                       |
	>                > >   ~                          Label Value =20
	>                       ~
	>                > >   |                                      =20
	>                       |
	>                > > =20
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	>                > >
	>                > >      x: Reserved Flags.
	>                > >         These are generally used by
	>specific messages and will be
	>                > >         defined in those messages.
	>                > >
	>                > >      S: Stacked Label Indicator
	>                > >         Label Stacking is discussed below
	>in section 3.1.3.5
	>                > >
	>                > >      Label Type
	>                > >         A 12-bit field indicating the type
	>of label.
	>                > >
	>                > >      Label Length
	>                > >         A 16-bit field indicating the
	>length of the Label
	>                > Value field
	>                > >         in bytes.
	>                > >
	>                > >      Label Value
	>                > >         A variable length field that is an
	>integer number of 32 bit
	>                > >         words long.  The Label Value field
	>is interpreted
	>                > according to
	>                > >         the Label Type as described in the
	>following sections.
	>                > >
	>                > >
	>                > >The draft is a bit obscure about this and
	>since it doesn't
	>                > >specify much, it can lead to
	>misinterpretation for the unused
	>                > >part. Moreover, it would appear that
	>several implementations
	>                > >currently use another format for the label
	>field. Can you
	>                > >explain?  I mean, how come what's in the
	>current draft doesn't
	>                > >match what's known to be implemented?
	>                > >
	>                > >I'm still wondering why we carried over
	>pieces from GSMP that
	>                > >we do not intend to use.
	>                > >
	>                > >I would recommend that if we are to keep
	>them but not use
	>                > >them, we should mention precisely how we
	>intend not to use
	>                > >them: that is how many 0 filled bytes this
	>is expected to use
	>                > >
	>                > >The rfc 3292 doesn't cover the case where
	>this field is not used.
	>                > >
	>                > >Can you shed some ligths on this?
	>                > >
	>                > >Thanks
	>                > >Regards
	>                > >Phil
	>                > >
	>                > >
	>                > >
	>                >
=09
>>--------------------------------------------------------------------
	>                > >
	>                > >CONFIDENTIALITY NOTICE
	>                > >
	>                > >This message and its attachments are
	>addressed solely to the
	>                > >persons above and may contain confidential
	>information. If you
	>                > >have received the message in error, be
	>informed that any use
	>                > >of the content hereof is prohibited. Please
	>return it
	>                > >immediately to the sender and delete the
	>message. Should you
	>                > >have any questions, please contact us by
replying to
	>                > >webmaster@telecomitalia.it.
	>                > >
	>                > >        Thank you
	>                > >
	>                > >                                      =20
	>www.telecomitalia.it
	>                > >
	>                >
=09
>>--------------------------------------------------------------------
	>                > >
	>                > >
	>                >
	>                _______________________________________________
	>                ANCP mailing list
	>                ANCP@ietf.org
	>                https://www.ietf.org/mailman/listinfo/ancp
<https://www.ietf.org/mailman/listinfo/ancp>=20
	>
	>=20


------_=_NextPart_001_01C8AC50.FDF238B5
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
 namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" =
name=3D"PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;}
p
	{mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dblue>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Peter<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;You mis<st1:PersonName =
w:st=3D"on">se</st1:PersonName>d
my point below. The ANCP draft since becoming a WG draft does NOT refer =
to the
old GSMP drafts. Any implementations ba<st1:PersonName =
w:st=3D"on">se</st1:PersonName>d
on this WG-draft are expected to be interoperable. You are pointing to
pre-WG-draft versions of ANCP, and the<st1:PersonName =
w:st=3D"on">se</st1:PersonName>
were indeed ba<st1:PersonName w:st=3D"on">se</st1:PersonName>d on =
expired GSMP
drafts that evolved past RFC3292. <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>There is incompatibility between =
the
current ANCP WG-draft and previous non-WG versions (TLV clash, label =
format..).
As mentioned earlier it is prudent for older implementations to start
supporting the WG-draft version as soon as possible. =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>For interoperability of WG-draft =
with the
older pre-WG versions, I <st1:PersonName =
w:st=3D"on">se</st1:PersonName>e the
following options:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>1. Versioning starts with the =
WG-draft
i.e. WG-draft is version =3D 3, sub-version =3D 1. For any interop =
issues between
older non-WG versions and the WG-draft, one needs to look at solving it =
within
implementations (e.g. an AN that implements the WG-draft, could =
ba<st1:PersonName
w:st=3D"on">se</st1:PersonName>d on a configuration knob, generate a =
PORT-UP
message with old label format the will be accepted by BNG implementing =
pre-WG
versions of the draft). <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>2. Change the WG-draft (current =
draft) to
u<st1:PersonName w:st=3D"on">se</st1:PersonName> version =3D 3 and =
sub-version =3D 2.
This is assuming there is no deployed implementation of current WG-draft =
that
already u<st1:PersonName w:st=3D"on">se</st1:PersonName>s 3.1 as the =
version, and
also assuming the old pre-WG implementations u<st1:PersonName =
w:st=3D"on">se</st1:PersonName>
3.1. There will be no backwards compatibility i.e. version 3.1 BNG will =
not
work with version 3.2 AN (we will need to list this as caveat in the =
appendix <st1:PersonName
w:st=3D"on">se</st1:PersonName>ction). AN and BNG will need to negotiate =
the same
version in order for ANCP adjacency to come up. A BNG supporting both =
versions
3.1 and 3.2 could simultaneously become adjacent with one AN supporting =
3.1 and
another AN supporting 3.2. (i.e. version compatibility is per =
adjacency).<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Also, major version number change =
(e.g.
from 3 to 4) should only correspond to a major change in the protocol =
(e.g.
different mechanism, different transport =
etc).<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>My vote would be to adopt option 2 =
above
only if further changes to WG-draft happen that render it incompatible =
with the
current WG-draft. Any interoperability issues with pre-WG versions could =
be
handled via option 1.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Cheers<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>-Sanjay<o:p></o:p></span></font></p>=


<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> Peter =
Arberg
[mailto:parberg@redback.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Wednesday, April =
30, 2008
7:20 PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Sanjay Wadhwa; Tina =
TSOU;
Maglione Roberta; Wojciech Dec (wdec)<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> ancp@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [ANCP] =
question
regarding Labels in ANCP port up messages</span></font><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>Sanjay,</span></font><o:p></o:p></p>=


<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>What do you mean &quot;why I =
reference an old
draft&quot;&nbsp; ????????????</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>I'm surpri<st1:PersonName =
w:st=3D"on">se</st1:PersonName>d
you even ask...&nbsp; plea<st1:PersonName =
w:st=3D"on">se</st1:PersonName> take a
look at YOUR own internet-draft that most</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>of the ANCP working implementations =
are ba<st1:PersonName
w:st=3D"on">se</st1:PersonName>d on, in ca<st1:PersonName =
w:st=3D"on">se</st1:PersonName>
you do not have this old</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>internet-draft, I have attached it =
to the
document.</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>If you look at the reference for =
this
ancp-draft, you will <st1:PersonName w:st=3D"on">se</st1:PersonName>e =
that in the
reference <st1:PersonName =
w:st=3D"on">se</st1:PersonName>ction</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>you point to this old =
gsmp-draft...&nbsp;
Yes and I know this has been changed in the =
later</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>versions of the ANCP draft, but =
that do
not change the fact that many of the =
implementations</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>today was developed when the =
attached
draft was current.</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>I think a very good question is =
brought up
here, and that is what is implemented and</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>running in networks today =
?</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>My take on this is that when the =
reference
was change from the old gsmp-draft to the =
older</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>RFC3292, apparently no one paid any
attention to the fact the label definition in the =
event</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>message was different and not =
compatible.</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>What current implementations do =
today is
an important factor in this discussion, and I =
think</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>it is time to come to realization =
that we
might need a new version number for ANCP =
since</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>it continues to look like there is =
big
holes open for interpretation. So if I did a =
ANCP</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>implementation there is bound to be
interoperability issues with existing =
implementations</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>runnig.</span></font><o:p></o:p></p>=


<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>cheers,</span></font><o:p></o:p></p>=


<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>Peter</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

<blockquote style=3D'border:none;border-left:solid blue =
1.5pt;padding:0in 0in 0in 4.0pt;
margin-left:3.75pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'=
>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabIndex=3D-1>

</span></font></div>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><b><font size=3D2 =
face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma;font-weight:bold'>From:</spa=
n></font></b><font
size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'> Sanjay
Wadhwa [mailto:swadhwa@juniper.net] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> 30. april 2008 =
14:42<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Peter Arberg; Tina =
TSOU;
Maglione Roberta; Wojciech Dec (wdec)<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> ancp@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [ANCP] =
question regarding
Labels in ANCP port up messages</span></font><o:p></o:p></p>

<p><font size=3D2 face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt'>Peter<br>
&nbsp; The ANCP draft as it currently stands is ba<st1:PersonName =
w:st=3D"on">se</st1:PersonName>d
on RFC3292. It provides extensions and modifications to relevant =
constructs in
RFC3292. There is no mention (implicit or explicit) of expired GSMP =
drafts in
the ANCP draft. In order to implement the ANCP draft, I am not sure why =
one
would look at the expired GSMP drafts. Do you <st1:PersonName =
w:st=3D"on">se</st1:PersonName>e
a reason to do this ba<st1:PersonName w:st=3D"on">se</st1:PersonName>d =
on
anything that you read in the ANCP draft? Bringing up reference to =
expired gsmp
draft in this thread&nbsp;just adds to the confusion. For GSMPv3 objects =
in the
messages (such as Label Type), one has to look at RFC3292 (this is =
clearly
stated in the ANCP draft - <st1:PersonName =
w:st=3D"on">se</st1:PersonName>ction 2
and I am quoting it below) :</span></font><o:p></o:p></p>

<p><font size=3D2 color=3Dblue face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt;
color:blue'>ANCP u<st1:PersonName w:st=3D"on">se</st1:PersonName>s a =
sub<st1:PersonName
w:st=3D"on">se</st1:PersonName>t of GSMPv3 messages to implement =
currently defined
u<st1:PersonName w:st=3D"on">se</st1:PersonName>-ca<st1:PersonName =
w:st=3D"on">se</st1:PersonName>s.
The<st1:PersonName w:st=3D"on">se</st1:PersonName> relevant GSMPv3 =
messages are
identified in <st1:PersonName w:st=3D"on">se</st1:PersonName>ction 5. =
GSMPv3
procedures with suitable extensions, as u<st1:PersonName =
w:st=3D"on">se</st1:PersonName>d
by ANCP, are described in <st1:PersonName =
w:st=3D"on">se</st1:PersonName>ctions
5.1, 5.2 and 5.3. GSMPv3 general extensions and GSMPv3 message specific
extensions required by ANCP are described in sub-<st1:PersonName =
w:st=3D"on">se</st1:PersonName>ctions
of 5.4. In addition to specifying extensions and modifications to =
relevant GSMP
messages applicable to ANCP, this draft also defines the usage of =
the<st1:PersonName
w:st=3D"on">se</st1:PersonName> messages by ANCP, and indicates the =
values that
ANCP should <st1:PersonName w:st=3D"on">se</st1:PersonName>t for =
relevant fields
in the<st1:PersonName w:st=3D"on">se</st1:PersonName> GSMP messages. =
However, to
understand the basic <st1:PersonName =
w:st=3D"on">se</st1:PersonName>mantics of
various fields in GSMP messages, the reader is referred to =
[4].&nbsp;=3D&gt; RFC
3292.</span></font><font size=3D2><span style=3D'font-size:10.0pt'><br>
<br>
What existing implementations currently do is an important but =
<st1:PersonName
w:st=3D"on">se</st1:PersonName>parate issue. The<st1:PersonName =
w:st=3D"on">se</st1:PersonName>
implementations for most part precede the current ANCP draft. It is fine =
to
poll where the<st1:PersonName w:st=3D"on">se</st1:PersonName> =
implementations
diverge from the current draft. It is then upto the implementations =
(including
the one that I am somewhat familiar with) to work towards compliance =
with the
draft. </span></font><o:p></o:p></p>

<p><font size=3D2 face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt'>On the
following points&nbsp;from &nbsp;Woj:</span></font><o:p></o:p></p>

<p><font size=3D2 face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt'>Woj&gt;2)
The current version of the spec is not accurate, and does not =
reflect&nbsp;the
fact that the known implementations follow the label field definition =
from
draft-gsmpv3-ba<st1:PersonName =
w:st=3D"on">se</st1:PersonName>-spec.</span></font><o:p></o:p></p>

<p><font size=3D2 face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt'>It is not
for the protocol draft to point out what current implementations
do.&nbsp;&nbsp;The best we can do is to further clarify in the draft =
that type
and value fields of the Label object (defined in RFC3292) should be =
<st1:PersonName
w:st=3D"on">se</st1:PersonName>t to 0 in the port-up message (we
already&nbsp;mention the lable object as a whole should be =
<st1:PersonName
w:st=3D"on">se</st1:PersonName>t to all 0s). =
</span></font><o:p></o:p></p>

<p><font size=3D2 face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt'>Woj&gt;
This would be a good thing for the WG to discuss. There most evidently =
is a
fair amount of&nbsp;&quot;dead wood&quot; in the current spec, ie stuff =
that
nobody yet&nbsp;implements or cares about. &nbsp;In the former =
ca<st1:PersonName
w:st=3D"on">se</st1:PersonName>, we could re-cast that material using =
the new
notions/extensions, in the latter ca<st1:PersonName =
w:st=3D"on">se</st1:PersonName>
simply chop it out.</span></font><o:p></o:p></p>

<p><font size=3D2 face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt'>I agree.
We are ba<st1:PersonName w:st=3D"on">se</st1:PersonName>d on GSMPv3 =
(RFC3292)
&nbsp;messages, and obviously not everything in the<st1:PersonName =
w:st=3D"on">se</st1:PersonName>
messages is leveraged by ANCP.&nbsp; However, the sync rate and OAM =
u<st1:PersonName
w:st=3D"on">se</st1:PersonName>s-ca<st1:PersonName =
w:st=3D"on">se</st1:PersonName>s
are implemented and in u<st1:PersonName w:st=3D"on">se</st1:PersonName> =
(ideally
we should leave the<st1:PersonName w:st=3D"on">se</st1:PersonName> =
alone...i.e.
no change beyond adding more clarity if needed). For anything new (such =
as
multicast) we are defining new messages&nbsp;(no legacy).&nbsp; =
</span></font><o:p></o:p></p>

<p><font size=3D2 face=3D"Times New Roman"><span =
style=3D'font-size:10.0pt'>-Sanjay<br>
<br>
&gt;-----Original Message-----<br>
&gt;From: Peter Arberg [</span></font><a =
href=3D"mailto:parberg@redback.com"><font
size=3D2><span =
style=3D'font-size:10.0pt'>mailto:parberg@redback.com</span></font></a><f=
ont
size=3D2><span style=3D'font-size:10.0pt'>]<br>
&gt;Sent: Wednesday, April 30, 2008 3:56 PM<br>
&gt;To: Tina TSOU; Maglione Roberta; Sanjay Wadhwa; Wojciech Dec =
(wdec)<br>
&gt;Cc: ancp@ietf.org<br>
&gt;Subject: RE: [ANCP] question regarding Labels in ANCP port up =
messages<br>
&gt;<br>
&gt;<br>
&gt;Hi,<br>
&gt;<br>
&gt;some times I think it is amazing we ever got interoperability<br>
&gt;of ANCP :-)<br>
&gt;becau<st1:PersonName w:st=3D"on">se</st1:PersonName> looking at the =
label
discussion is a very good example that the<br>
&gt;whole GSMP - ANCP reference have not worked very well.<br>
&gt;<br>
&gt;In the ANCP draft, <st1:PersonName =
w:st=3D"on">se</st1:PersonName>ction 5.4.2
the event message is shown like this:<br>
&gt;<br>
&gt;0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
3<br>
&gt;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<br>
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&gt;| Vers&nbsp; |&nbsp; Sub&nbsp; | Message Type&nbsp; |
Result|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Code&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&gt;| Partition ID&nbsp;
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Transaction
Identifier&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;
|<br>
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&gt;|I|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SubMessage
Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;
|<br>
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;
Port&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|<br>
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Port Session
Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|<br>
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Event Sequence
Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|<br>
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&gt;|x|S|x|x|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|<br>
&gt;+-+-+-+-+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;
|<br>
&gt;~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;
~<br>
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&gt;|x|x|x|x|x|x|x|x| Message Type&nbsp; |&nbsp;&nbsp; Tech =
Type&nbsp;&nbsp; |
Block Length&nbsp; |<br>
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;
|<br>
&gt;~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;
Extension
Value&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
~<br>
&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;
|<br>
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&gt;<br>
&gt;<br>
&gt;This is the exact same event message defined in<br>
&gt;draft-ietf-gsmp-v3-ba<st1:PersonName =
w:st=3D"on">se</st1:PersonName>-spec-08.txt&nbsp;
<st1:PersonName w:st=3D"on">se</st1:PersonName>ction 11.<br>
&gt;<br>
&gt;And in this gsmp-draft, <st1:PersonName =
w:st=3D"on">se</st1:PersonName>ction
5.1.3 the label space is defined<br>
&gt;as minimum 8 bytes if the length=3D0 and as such no value, and =
this<br>
&gt;is becau<st1:PersonName w:st=3D"on">se</st1:PersonName> the =
gsmp-draft has a
new &quot;label adaptaion&quot; field.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;BUT in RFC3292 the event message is show in <st1:PersonName =
w:st=3D"on">se</st1:PersonName>ction
9, like this:<br>
&gt;<br>
&gt;0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
3<br>
&gt;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<br>
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&gt;|&nbsp;&nbsp;&nbsp; Version&nbsp;&nbsp;&nbsp; | Message Type&nbsp;
|&nbsp;&nbsp;&nbsp; Result&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;
Code&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&gt;| Partition ID&nbsp;
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Transaction
Identifier&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;
|<br>
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&gt;|I|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SubMessage
Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;
|<br>
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;
Port&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|<br>
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Port Session
Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|<br>
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Event Sequence
Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|<br>
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&gt;|x|S|x|x|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|<br>
&gt;+-+-+-+-+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;
|<br>
&gt;~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;
~<br>
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&gt;<br>
&gt;<br>
&gt;So a different Event Message picture/definition than what is =
shown<br>
&gt;in the ANCP draft, and in RFC3292 <st1:PersonName =
w:st=3D"on">se</st1:PersonName>ction
3.1.3 the label field<br>
&gt;is defined as 4 bytes if length=3D0 and as such no value.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;So I very much agree with Woj that we need this issue to be =
resolved,<br>
&gt;and proabably a show of hands what is actually done in different<br>
&gt;implementations, so we can nail down how the event message is<br>
&gt;suppo<st1:PersonName w:st=3D"on">se</st1:PersonName> to look like in =
ANCP.<br>
&gt;<br>
&gt;<br>
&gt;I know at least 1 implementation which u<st1:PersonName =
w:st=3D"on">se</st1:PersonName>s
8 bytes for the<br>
&gt;label field.<br>
&gt;<br>
&gt;<br>
&gt;cheers,<br>
&gt;Peter<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;________________________________<br>
&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; From: =
ancp-bounces@ietf.org<br>
&gt;[</span></font><a href=3D"mailto:ancp-bounces@ietf.org"><font =
size=3D2><span
style=3D'font-size:10.0pt'>mailto:ancp-bounces@ietf.org</span></font></a>=
<font
size=3D2><span style=3D'font-size:10.0pt'>] On Behalf Of Tina TSOU<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Sent: 30. april 2008 =
00:19<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; To: Maglione Roberta; =
Sanjay
Wadhwa; Wojciech Dec (wdec)<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Cc: ancp@ietf.org<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Subject: Re: [ANCP] =
question
regarding Labels in ANCP<br>
&gt;port up messages<br>
&gt;<br>
&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Hi all,<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; It is clear to me that if =
Label
Length is filled as 0,<br>
&gt;there is nothing to be filled into Label Value. The whole<br>
&gt;Label part is 4 bytes, not 8 bytes.<br>
&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Cheers from the last =
working day
before Labor's Day<br>
&gt;holidays in some countries:)<br>
&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Tina<br>
&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
----- Original Message -----<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
From: Wojciech Dec (wdec) &lt;</span></font><a =
href=3D"mailto:wdec@cisco.com"><font
size=3D2><span =
style=3D'font-size:10.0pt'>mailto:wdec@cisco.com</span></font></a><font
size=3D2><span style=3D'font-size:10.0pt'>&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
To: Sanjay Wadhwa &lt;</span></font><a =
href=3D"mailto:swadhwa@juniper.net"><font
size=3D2><span =
style=3D'font-size:10.0pt'>mailto:swadhwa@juniper.net</span></font></a><f=
ont
size=3D2><span style=3D'font-size:10.0pt'>&gt;<br>
&gt; ; Maglione Roberta &lt;</span></font><a
href=3D"mailto:roberta.maglione@telecomitalia.it"><font size=3D2><span
style=3D'font-size:10.0pt'>mailto:roberta.maglione@telecomitalia.it</span=
></font></a><font
size=3D2><span style=3D'font-size:10.0pt'>&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
Cc: ancp@ietf.org<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
Sent: Wednesday, April 30, 2008 1:12 AM<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
Subject: Re: [ANCP] question regarding Labels<br>
&gt;in ANCP port up messages<br>
&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
Sanjay, All,<br>
&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
What is stated below runs counter to at least<br>
&gt;a handful of ANCP<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
implementations, all of which are known to be<br>
&gt;interoperable.<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
There are really two options:<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
1) The current version of the spec is correct,<br>
&gt;and the known<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
interoperable implementations do not follow it<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
2) The current version of the spec is not<br>
&gt;accurate, and does not reflect<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
the fact that the known implementations follow<br>
&gt;the label field<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
definition from draft-gsmpv3-ba<st1:PersonName =
w:st=3D"on">se</st1:PersonName>-spec.<br>
&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
I would like to ask you, as the lead editor of<br>
&gt;the spec, to work with<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
the WG in resolving what the problem is, and<br>
&gt;clearing up what the WG<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
spec says about and if 1) holds to be true,<br>
&gt;then proposing an<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
interoperability fix.<br>
&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
In either ca<st1:PersonName w:st=3D"on">se</st1:PersonName>, the issue =
highlights
the fact<br>
&gt;that there is still<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
lingering confusion as to the dependencies<br>
&gt;ANCP has on rfc3292, or<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
draft-gsmpv3-ba<st1:PersonName w:st=3D"on">se</st1:PersonName>-spec, or =
both. It <st1:PersonName
w:st=3D"on">se</st1:PersonName>ems to<br>
&gt;be in the best interest of<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
all to address the<st1:PersonName w:st=3D"on">se</st1:PersonName>.<br>
&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
Regards,<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
Woj.<br>
&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; -----Original Message-----<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; From: Sanjay Wadhwa [</span></font><a =
href=3D"mailto:swadhwa@juniper.net"><font
size=3D2><span =
style=3D'font-size:10.0pt'>mailto:swadhwa@juniper.net</span></font></a><f=
ont
size=3D2><span style=3D'font-size:10.0pt'>]<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; Sent: 29 April 2008 17:29<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; To: Maglione Roberta<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; Cc: Wojciech Dec (wdec); ancp@ietf.org;<br>
&gt;Philippe Champagne (pchamp)<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; Subject: RE: question regarding Labels in<br>
&gt;ANCP port up messages<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; Hi Maglione<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp; Yes, the label format is as defined in RFC<br>
&gt;3292. The ANCP draft is<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; ba<st1:PersonName w:st=3D"on">se</st1:PersonName>d on RFC 3292 and =
propo<st1:PersonName
w:st=3D"on">se</st1:PersonName>s<br>
&gt;extensions/modifications where<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; required.<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; This is clearly stated upfront both in the<br>
&gt;abstract and in<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; <st1:PersonName w:st=3D"on">se</st1:PersonName>ction 2. In<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; <st1:PersonName w:st=3D"on">se</st1:PersonName>ction 5.4.2, it =
clearly&nbsp;
specifies the<br>
&gt;format of &quot;port up&quot; message<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; (ba<st1:PersonName w:st=3D"on">se</st1:PersonName>d on RFC 3292), =
and
explicitly states<br>
&gt;the label field<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; should be <st1:PersonName w:st=3D"on">se</st1:PersonName>t<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; to 0. Following is what the draft currently states:<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; 5.4.2 Topology Discovery Extensions<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; The GSMP Event message with PORT UP message<br>
&gt;type (80) is u<st1:PersonName w:st=3D"on">se</st1:PersonName>d =
for<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; conveying DSL line attributes to the NAS.<br>
&gt;The version field should be<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; <st1:PersonName w:st=3D"on">se</st1:PersonName>t to 3, and the sub =
field
should be <st1:PersonName w:st=3D"on">se</st1:PersonName>t to<br>
&gt;1. The I and subMessage<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; fields SHOULD be <st1:PersonName w:st=3D"on">se</st1:PersonName>t =
to 1 to
signify no<br>
&gt;fragmentation. The Port and<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; Label fields should be <st1:PersonName =
w:st=3D"on">se</st1:PersonName>t to
0.<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;
0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
2&nbsp;&nbsp;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
3<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0 1 2 3 4 5 6 =
7 8 9
0 1 2 3 4 5 6 7<br>
&gt;8 9 0 1 2 3 4 5<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; 6 7 8 9 0 1<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Vers&nbsp; =
|&nbsp;
Sub&nbsp; | Message Type&nbsp; |<br>
&gt;Result|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Code<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; |<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Partition =
ID&nbsp;
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<br>
&gt;Transaction Identifier<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; |<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|I|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SubMessage
Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Length<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; |<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;
Port<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; |<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Port Session Number<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; |<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Event Sequence Number<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; |<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |x|S|x|x|<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; |<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+-+-+-+-+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Label<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; |<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ~<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; ~<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |x|x|x|x|x|x|x|x| =
Message
Type&nbsp; |&nbsp;&nbsp;<br>
&gt;Tech Type&nbsp;&nbsp; | Block Length<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; |<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; |<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Extension Value<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; ~<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; |<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; When we say the label field should be <st1:PersonName =
w:st=3D"on">se</st1:PersonName>t
to<br>
&gt;0, the intention<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; is for the<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; type and length fields in the label TLV to<br>
&gt;be <st1:PersonName w:st=3D"on">se</st1:PersonName>t to 0. We can<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; explicitly state this for clarity.<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; -Sanjay<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;-----Original Message-----<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;From: Maglione Roberta<br>
&gt;[</span></font><a =
href=3D"mailto:roberta.maglione@telecomitalia.it"><font
size=3D2><span =
style=3D'font-size:10.0pt'>mailto:roberta.maglione@telecomitalia.it</span=
></font></a><font
size=3D2><span style=3D'font-size:10.0pt'>]<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;Sent: Tuesday, April 29, 2008 8:06 AM<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;To: Sanjay Wadhwa<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;Cc: Wojciech Dec (wdec); ancp@ietf.org;<br>
&gt;pchamp@cisco.com<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;Subject: RE: question regarding Labels in<br>
&gt;ANCP port up messages<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;Hi Sanjay and All,<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp; I was reading the current ancp<br>
&gt;protocol draft in order to<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt; understand which should be the correct<br>
&gt;format for the label<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;field in the ancp port Up message.<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;Actually as it was already pointed out in<br>
&gt;the alias the draft<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;in <st1:PersonName w:st=3D"on">se</st1:PersonName>ction 5.4.2 =
says
&quot;GSMP Event message<br>
&gt;with PORT UP message<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;type (80) is u<st1:PersonName =
w:st=3D"on">se</st1:PersonName>d&quot;&nbsp;
thus I am assuming that<br>
&gt;the label in the<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;port UP message should follow the message<br>
&gt;format defined in<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;RFC 3292, <st1:PersonName w:st=3D"on">se</st1:PersonName>ction =
3.1.3:<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;
0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<br>
&gt;2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
3<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp; 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9<br>
&gt;0 1 2 3 4 5 6 7 8 9 0 1<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;<br>
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp; |x|S|x|x|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Label
Type&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<br>
&gt;&nbsp; Label Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;<br>
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;
~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;
Label Value&nbsp;&nbsp;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
~<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;<br>
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;but from what I have <st1:PersonName =
w:st=3D"on">se</st1:PersonName>en
different<br>
&gt;implementations u<st1:PersonName w:st=3D"on">se</st1:PersonName><br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;different format for label field: in<br>
&gt;particular <st1:PersonName w:st=3D"on">se</st1:PersonName>veral<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;implementations u<st1:PersonName =
w:st=3D"on">se</st1:PersonName>&nbsp; a
label format that is<br>
&gt;similar to the one<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;specified in the expired draft<br>
&gt;draft-ietf-gsmp-v3-ba<st1:PersonName =
w:st=3D"on">se</st1:PersonName>-spec:<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;
0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<br>
&gt;
2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
3<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0 1 2 3 4 5 6 7 8 9 0 1 2 =
3 4 5 6
7<br>
&gt;8 9 0 1 2 3 4 5 6<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; 7 8 9 0 1<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|x|S|x|x|x|x|x|x|x|x|x|x|x|x|x|x|&nbsp;&nbsp;&nbsp;&nbsp;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Label<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; Type&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp; Label
Adaptation&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|&nbsp;&nbsp;&nbsp;&nbsp;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp; Label<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;
Label Value<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ~<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;Even if ancp does not care about the label<br>
&gt;field, having this<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;field somehow not clearly specified in the<br>
&gt;current ancp draft<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;can easily lead to interoperability issues,<br>
&gt;thus I think it<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;would be very helpful if you and/or the<br>
&gt;other editors can<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;clarify what should be the correct format<br>
&gt;for the label field<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;to be u<st1:PersonName w:st=3D"on">se</st1:PersonName>d in the =
ancp Port
Up message.<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;Thanks and best regards,<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;Roberta<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;________________________________________<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;From: Philippe Champagne (pchamp) [pchamp@cisco.com]<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;Sent: Thursday, April 24, 2008 7:14 PM<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;To: Sanjay Wadhwa<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;Cc: Maglione Roberta; Wojciech Dec (wdec);<br>
&gt;ancp@ietf.org<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;Subject: question regarding&nbsp; Labels in ANCP<br>
&gt;port up messages<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;Hi Sanjay<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;In <st1:PersonName w:st=3D"on">se</st1:PersonName>ction 5.4.2 =
of the
draft, we have:<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
2<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 3<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0 1 2 3 4 5 6 =
7 8 9 0
1 2 3 4 5 6<br>
&gt;7 8 9 0 1 2 3 4 5 6<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;7 8 9 0 1<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Vers&nbsp; |&nbsp;
Sub&nbsp; | Message Type&nbsp; |<br>
&gt;Result|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Code<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Partition ID&nbsp;
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<br>
&gt;Transaction Identifier<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|I|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SubMessage
Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Length<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;
Port<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Port Session Number<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Event Sequence Number<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |x|S|x|x|<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+-+-+-+-+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Label<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ~<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ~<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |x|x|x|x|x|x|x|x| =
Message
Type&nbsp; |&nbsp;&nbsp;<br>
&gt;Tech Type&nbsp;&nbsp; |<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;Block Length&nbsp; |<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Extension Value<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ~<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;Where Label I suppo<st1:PersonName =
w:st=3D"on">se</st1:PersonName> is
taken from the RFC<br>
&gt;3292, <st1:PersonName w:st=3D"on">se</st1:PersonName>ction<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;3.1.3: (well, I'm guessing)<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp; A summary of TLV labels supported in<br>
&gt;this version of the<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; protocol is<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp; listed below:<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; TLV =
Label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Type&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Section Title<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
---------&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
----&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -------------<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ATM =
Label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
0x100&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ATM TLV Labels<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; FR
Label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
0x101&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Frame Relay<br>
&gt;TLV Labels<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MPLS Gen Label
0x102&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MPLS<br>
&gt;Generic TLV Labels<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; FEC =
Label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
0x103&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; FEC TLV Labels<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp; All Labels will be designated as follow:<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;
0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<br>
&gt;2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
3<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp; 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9<br>
&gt;0 1 2 3 4 5 6 7 8 9 0 1<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;<br>
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp; |x|S|x|x|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Label
Type&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<br>
&gt;&nbsp; Label Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;<br>
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;
~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;
Label Value&nbsp;&nbsp;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
~<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;<br>
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; x: Re<st1:PersonName =
w:st=3D"on">se</st1:PersonName>rved
Flags.<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
The<st1:PersonName
w:st=3D"on">se</st1:PersonName> are generally u<st1:PersonName =
w:st=3D"on">se</st1:PersonName>d
by<br>
&gt;specific messages and will be<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; defined in =
tho<st1:PersonName
w:st=3D"on">se</st1:PersonName> messages.<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; S: Stacked Label Indicator<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Label Stacking =
is
discus<st1:PersonName w:st=3D"on">se</st1:PersonName>d below<br>
&gt;in <st1:PersonName w:st=3D"on">se</st1:PersonName>ction 3.1.3.5<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Label Type<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A 12-bit field
indicating the type<br>
&gt;of label.<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Label Length<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A 16-bit field
indicating the<br>
&gt;length of the Label<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; Value field<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; in bytes.<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Label Value<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A variable =
length
field that is an<br>
&gt;integer number of 32 bit<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; words =
long.&nbsp; The
Label Value field<br>
&gt;is interpreted<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; according to<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the Label Type =
as
described in the<br>
&gt;following <st1:PersonName w:st=3D"on">se</st1:PersonName>ctions.<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;The draft is a bit obscure about this and<br>
&gt;since it doesn't<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;specify much, it can lead to<br>
&gt;misinterpretation for the unu<st1:PersonName =
w:st=3D"on">se</st1:PersonName>d<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;part. Moreover, it would appear that<br>
&gt;<st1:PersonName w:st=3D"on">se</st1:PersonName>veral =
implementations<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;currently u<st1:PersonName w:st=3D"on">se</st1:PersonName> =
another
format for the label<br>
&gt;field. Can you<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;explain?&nbsp; I mean, how come what's in the<br>
&gt;current draft doesn't<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;match what's known to be implemented?<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;I'm still wondering why we carried over<br>
&gt;pieces from GSMP that<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;we do not intend to u<st1:PersonName =
w:st=3D"on">se</st1:PersonName>.<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;I would recommend that if we are to keep<br>
&gt;them but not u<st1:PersonName w:st=3D"on">se</st1:PersonName><br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;them, we should mention preci<st1:PersonName =
w:st=3D"on">se</st1:PersonName>ly
how we<br>
&gt;intend not to u<st1:PersonName w:st=3D"on">se</st1:PersonName><br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;them: that is how many 0 filled bytes this<br>
&gt;is expected to u<st1:PersonName w:st=3D"on">se</st1:PersonName><br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;The rfc 3292 doesn't cover the ca<st1:PersonName =
w:st=3D"on">se</st1:PersonName>
where<br>
&gt;this field is not u<st1:PersonName =
w:st=3D"on">se</st1:PersonName>d.<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;Can you shed some ligths on this?<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;Thanks<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;Regards<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;Phil<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&gt;&gt;-----------------------------------------------------------------=
---<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;CONFIDENTIALITY NOTICE<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;This message and its attachments are<br>
&gt;addres<st1:PersonName w:st=3D"on">se</st1:PersonName>d solely to =
the<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;persons above and may contain confidential<br>
&gt;information. If you<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;have received the message in error, be<br>
&gt;informed that any u<st1:PersonName =
w:st=3D"on">se</st1:PersonName><br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;of the content hereof is prohibited. Plea<st1:PersonName =
w:st=3D"on">se</st1:PersonName><br>
&gt;return it<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;immediately to the <st1:PersonName =
w:st=3D"on">se</st1:PersonName>nder
and delete the<br>
&gt;message. Should you<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;have any questions, plea<st1:PersonName =
w:st=3D"on">se</st1:PersonName>
contact us by replying to<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;webmaster@telecomitalia.it.<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Thank you<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;<br>
&gt;www.telecomitalia.it<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&gt;&gt;-----------------------------------------------------------------=
---<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
_______________________________________________<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
ANCP mailing list<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
ANCP@ietf.org<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
</span></font><a href=3D"https://www.ietf.org/mailman/listinfo/ancp"
target=3D"_blank"><font size=3D2><span =
style=3D'font-size:10.0pt'>https://www.ietf.org/mailman/listinfo/ancp</sp=
an></font></a><br>
<font size=3D2><span style=3D'font-size:10.0pt'>&gt;<br>
&gt;</span></font> <o:p></o:p></p>

</blockquote>

</div>

</body>

</html>

------_=_NextPart_001_01C8AC50.FDF238B5--

--===============1730325901==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1730325901==--


From ancp-bounces@ietf.org  Fri May  2 11:52:53 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BBFC23A6E13;
	Fri,  2 May 2008 11:52:53 -0700 (PDT)
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 914783A6DEB
	for <ancp@core3.amsl.com>; Fri,  2 May 2008 11:52:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.126
X-Spam-Level: ***
X-Spam-Status: No, score=3.126 tagged_above=-999 required=5 tests=[AWL=-5.277, 
	BAYES_00=-2.599, HTML_MESSAGE=0.001, HTML_OBFUSCATE_05_10=0.001,
	J_BACKHAIR_12=1, J_BACKHAIR_21=1, J_BACKHAIR_22=1, J_BACKHAIR_23=1,
	J_BACKHAIR_24=1, J_BACKHAIR_25=1, J_BACKHAIR_26=1, J_BACKHAIR_27=1,
	J_BACKHAIR_32=1, J_BACKHAIR_42=1, J_BACKHAIR_52=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 iFtY73CjnSEW for <ancp@core3.amsl.com>;
	Fri,  2 May 2008 11:52:48 -0700 (PDT)
Received: from prattle.redback.com (prattle.redback.com [155.53.12.9])
	by core3.amsl.com (Postfix) with ESMTP id 9189E3A6A80
	for <ancp@ietf.org>; Fri,  2 May 2008 11:52:48 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by prattle.redback.com (Postfix) with ESMTP id D35371632E6;
	Fri,  2 May 2008 11:52:46 -0700 (PDT)
Received: from prattle.redback.com ([127.0.0.1])
	by localhost (prattle [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
	id 19753-07; Fri,  2 May 2008 11:52:45 -0700 (PDT)
Received: from rbsjx.ad.redback.com (rbsjxh2.redback.com [155.53.14.106])
	by prattle.redback.com (Postfix) with ESMTP id 6931EB49808;
	Fri,  2 May 2008 11:52:43 -0700 (PDT)
Received: from RBSJX.ad.redback.com ([155.53.14.103]) by
	rbsjxh2.ad.redback.com ([155.53.14.106]) with mapi;
	Fri, 2 May 2008 11:52:29 -0700
From: Peter Arberg <parberg@redback.com>
To: Sanjay Wadhwa <swadhwa@juniper.net>, Tina TSOU <tena@huawei.com>,
	Maglione Roberta <roberta.maglione@telecomitalia.it>,
	"Wojciech Dec (wdec)" <wdec@cisco.com>
Date: Fri, 2 May 2008 11:52:27 -0700
Thread-Topic: [ANCP] question regarding  Labels in ANCP port up messages
Thread-Index: Aciqkn5nSPBPuwuySsamcvxF1uU6kQAZ9dQQAAE415AABe3TAABN80lQAA1w7OA=
Message-ID: <48C276B536524E478C659685995F6AA539DBBBEF99@RBSJX.ad.redback.com>
References: <48C276B536524E478C659685995F6AA539DBBBE370@RBSJX.ad.redback.com>
	<9BD5D7887235424FA97DFC223CAE3C280AB43A10@proton.jnpr.net>
	<48C276B536524E478C659685995F6AA539DBBBE577@RBSJX.ad.redback.com>
	<9BD5D7887235424FA97DFC223CAE3C28102EB5AA@proton.jnpr.net>
In-Reply-To: <9BD5D7887235424FA97DFC223CAE3C28102EB5AA@proton.jnpr.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-Virus-Scanned: by amavisd-new at redback.com
Cc: "ancp@ietf.org" <ancp@ietf.org>
Subject: Re: [ANCP] question regarding  Labels in ANCP port up messages
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/pipermail/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>
Content-Type: multipart/mixed; boundary="===============1018556323=="
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org

--===============1018556323==
Content-Language: en-US
Content-Type: multipart/alternative;
	boundary="_000_48C276B536524E478C659685995F6AA539DBBBEF99RBSJXadredbac_"

--_000_48C276B536524E478C659685995F6AA539DBBBEF99RBSJXadredbac_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Sanjay,

yes apparently I missed your point in the last email, but I'm glad we agree=
 something is needed
to make existing ANCP implementations and the current draft to co-exist.

I do not like your option 1) as if you need a config knob for interoperabil=
ity, it is too easy to
get into trouble.

I think option 2) is the best way forward with the differences already iden=
tified, or we can
continue to get a show of hands of ANCP implementations, and see if anyone =
is actually
deployed based on the WG-draft.

There is no beneficial reasons to base the event-message of RFC3292, it cou=
ld as well be a message
described bit by bit in the ANCP draft, and then we can keep the label spac=
e at 8 as many
implementations alreday do.

cheers,
Peter




________________________________
From: Sanjay Wadhwa [mailto:swadhwa@juniper.net]
Sent: 2. maj 2008 05:35
To: Peter Arberg; Tina TSOU; Maglione Roberta; Wojciech Dec (wdec)
Cc: ancp@ietf.org
Subject: RE: [ANCP] question regarding Labels in ANCP port up messages

Peter
 You missed my point below. The ANCP draft since becoming a WG draft does N=
OT refer to the old GSMP drafts. Any implementations based on this WG-draft=
 are expected to be interoperable. You are pointing to pre-WG-draft version=
s of ANCP, and these were indeed based on expired GSMP drafts that evolved =
past RFC3292.
There is incompatibility between the current ANCP WG-draft and previous non=
-WG versions (TLV clash, label format..). As mentioned earlier it is pruden=
t for older implementations to start supporting the WG-draft version as soo=
n as possible.

For interoperability of WG-draft with the older pre-WG versions, I see the =
following options:

1. Versioning starts with the WG-draft i.e. WG-draft is version =3D 3, sub-=
version =3D 1. For any interop issues between older non-WG versions and the=
 WG-draft, one needs to look at solving it within implementations (e.g. an =
AN that implements the WG-draft, could based on a configuration knob, gener=
ate a PORT-UP message with old label format the will be accepted by BNG imp=
lementing pre-WG versions of the draft).

2. Change the WG-draft (current draft) to use version =3D 3 and sub-version=
 =3D 2. This is assuming there is no deployed implementation of current WG-=
draft that already uses 3.1 as the version, and also assuming the old pre-W=
G implementations use 3.1. There will be no backwards compatibility i.e. ve=
rsion 3.1 BNG will not work with version 3.2 AN (we will need to list this =
as caveat in the appendix section). AN and BNG will need to negotiate the s=
ame version in order for ANCP adjacency to come up. A BNG supporting both v=
ersions 3.1 and 3.2 could simultaneously become adjacent with one AN suppor=
ting 3.1 and another AN supporting 3.2. (i.e. version compatibility is per =
adjacency).
Also, major version number change (e.g. from 3 to 4) should only correspond=
 to a major change in the protocol (e.g. different mechanism, different tra=
nsport etc).

My vote would be to adopt option 2 above only if further changes to WG-draf=
t happen that render it incompatible with the current WG-draft. Any interop=
erability issues with pre-WG versions could be handled via option 1.

Cheers
-Sanjay

________________________________
From: Peter Arberg [mailto:parberg@redback.com]
Sent: Wednesday, April 30, 2008 7:20 PM
To: Sanjay Wadhwa; Tina TSOU; Maglione Roberta; Wojciech Dec (wdec)
Cc: ancp@ietf.org
Subject: RE: [ANCP] question regarding Labels in ANCP port up messages

Sanjay,

What do you mean "why I reference an old draft"  ????????????

I'm surprised you even ask...  please take a look at YOUR own internet-draf=
t that most
of the ANCP working implementations are based on, in case you do not have t=
his old
internet-draft, I have attached it to the document.

If you look at the reference for this ancp-draft, you will see that in the =
reference section
you point to this old gsmp-draft...  Yes and I know this has been changed i=
n the later
versions of the ANCP draft, but that do not change the fact that many of th=
e implementations
today was developed when the attached draft was current.

I think a very good question is brought up here, and that is what is implem=
ented and
running in networks today ?

My take on this is that when the reference was change from the old gsmp-dra=
ft to the older
RFC3292, apparently no one paid any attention to the fact the label definit=
ion in the event
message was different and not compatible.

What current implementations do today is an important factor in this discus=
sion, and I think
it is time to come to realization that we might need a new version number f=
or ANCP since
it continues to look like there is big holes open for interpretation. So if=
 I did a ANCP
implementation there is bound to be interoperability issues with existing i=
mplementations
runnig.

cheers,
Peter




________________________________
From: Sanjay Wadhwa [mailto:swadhwa@juniper.net]
Sent: 30. april 2008 14:42
To: Peter Arberg; Tina TSOU; Maglione Roberta; Wojciech Dec (wdec)
Cc: ancp@ietf.org
Subject: RE: [ANCP] question regarding Labels in ANCP port up messages

Peter
  The ANCP draft as it currently stands is based on RFC3292. It provides ex=
tensions and modifications to relevant constructs in RFC3292. There is no m=
ention (implicit or explicit) of expired GSMP drafts in the ANCP draft. In =
order to implement the ANCP draft, I am not sure why one would look at the =
expired GSMP drafts. Do you see a reason to do this based on anything that =
you read in the ANCP draft? Bringing up reference to expired gsmp draft in =
this thread just adds to the confusion. For GSMPv3 objects in the messages =
(such as Label Type), one has to look at RFC3292 (this is clearly stated in=
 the ANCP draft - section 2 and I am quoting it below) :

ANCP uses a subset of GSMPv3 messages to implement currently defined use-ca=
ses. These relevant GSMPv3 messages are identified in section 5. GSMPv3 pro=
cedures with suitable extensions, as used by ANCP, are described in section=
s 5.1, 5.2 and 5.3. GSMPv3 general extensions and GSMPv3 message specific e=
xtensions required by ANCP are described in sub-sections of 5.4. In additio=
n to specifying extensions and modifications to relevant GSMP messages appl=
icable to ANCP, this draft also defines the usage of these messages by ANCP=
, and indicates the values that ANCP should set for relevant fields in thes=
e GSMP messages. However, to understand the basic semantics of various fiel=
ds in GSMP messages, the reader is referred to [4]. =3D> RFC 3292.

What existing implementations currently do is an important but separate iss=
ue. These implementations for most part precede the current ANCP draft. It =
is fine to poll where these implementations diverge from the current draft.=
 It is then upto the implementations (including the one that I am somewhat =
familiar with) to work towards compliance with the draft.

On the following points from  Woj:

Woj>2) The current version of the spec is not accurate, and does not reflec=
t the fact that the known implementations follow the label field definition=
 from draft-gsmpv3-base-spec.

It is not for the protocol draft to point out what current implementations =
do.  The best we can do is to further clarify in the draft that type and va=
lue fields of the Label object (defined in RFC3292) should be set to 0 in t=
he port-up message (we already mention the lable object as a whole should b=
e set to all 0s).

Woj> This would be a good thing for the WG to discuss. There most evidently=
 is a fair amount of "dead wood" in the current spec, ie stuff that nobody =
yet implements or cares about.  In the former case, we could re-cast that m=
aterial using the new notions/extensions, in the latter case simply chop it=
 out.

I agree. We are based on GSMPv3 (RFC3292)  messages, and obviously not ever=
ything in these messages is leveraged by ANCP.  However, the sync rate and =
OAM uses-cases are implemented and in use (ideally we should leave these al=
one...i.e. no change beyond adding more clarity if needed). For anything ne=
w (such as multicast) we are defining new messages (no legacy).

-Sanjay

>-----Original Message-----
>From: Peter Arberg [mailto:parberg@redback.com]
>Sent: Wednesday, April 30, 2008 3:56 PM
>To: Tina TSOU; Maglione Roberta; Sanjay Wadhwa; Wojciech Dec (wdec)
>Cc: ancp@ietf.org
>Subject: RE: [ANCP] question regarding Labels in ANCP port up messages
>
>
>Hi,
>
>some times I think it is amazing we ever got interoperability
>of ANCP :-)
>because looking at the label discussion is a very good example that the
>whole GSMP - ANCP reference have not worked very well.
>
>In the ANCP draft, section 5.4.2 the event message is shown like this:
>
>0                   1                   2                   3
>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
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>| Vers  |  Sub  | Message Type  | Result|        Code           |
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>| Partition ID  |            Transaction Identifier             |
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>|I|      SubMessage Number      |           Length              |
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>|                             Port                              |
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>|                      Port Session Number                      |
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>|                     Event Sequence Number                     |
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>|x|S|x|x|                                                       |
>+-+-+-+-+                     Label                             |
>~                                                               ~
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>|x|x|x|x|x|x|x|x| Message Type  |   Tech Type   | Block Length  |
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>|                                                               |
>~                         Extension Value                       ~
>|                                                               |
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
>
>This is the exact same event message defined in
>draft-ietf-gsmp-v3-base-spec-08.txt  section 11.
>
>And in this gsmp-draft, section 5.1.3 the label space is defined
>as minimum 8 bytes if the length=3D0 and as such no value, and this
>is because the gsmp-draft has a new "label adaptaion" field.
>
>
>
>BUT in RFC3292 the event message is show in section 9, like this:
>
>0                   1                   2                   3
>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
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>|    Version    | Message Type  |    Result     |     Code      |
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>| Partition ID  |            Transaction Identifier             |
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>|I|      SubMessage Number      |           Length              |
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>|                             Port                              |
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>|                      Port Session Number                      |
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>|                     Event Sequence Number                     |
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>|x|S|x|x|                                                       |
>+-+-+-+-+                     Label                             |
>~                                                               ~
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
>
>So a different Event Message picture/definition than what is shown
>in the ANCP draft, and in RFC3292 section 3.1.3 the label field
>is defined as 4 bytes if length=3D0 and as such no value.
>
>
>
>So I very much agree with Woj that we need this issue to be resolved,
>and proabably a show of hands what is actually done in different
>implementations, so we can nail down how the event message is
>suppose to look like in ANCP.
>
>
>I know at least 1 implementation which uses 8 bytes for the
>label field.
>
>
>cheers,
>Peter
>
>
>
>
>
>
>________________________________
>
>        From: ancp-bounces@ietf.org
>[mailto:ancp-bounces@ietf.org] On Behalf Of Tina TSOU
>        Sent: 30. april 2008 00:19
>        To: Maglione Roberta; Sanjay Wadhwa; Wojciech Dec (wdec)
>        Cc: ancp@ietf.org
>        Subject: Re: [ANCP] question regarding Labels in ANCP
>port up messages
>
>
>        Hi all,
>        It is clear to me that if Label Length is filled as 0,
>there is nothing to be filled into Label Value. The whole
>Label part is 4 bytes, not 8 bytes.
>
>        Cheers from the last working day before Labor's Day
>holidays in some countries:)
>
>        Tina
>
>                ----- Original Message -----
>                From: Wojciech Dec (wdec) <mailto:wdec@cisco.com>
>                To: Sanjay Wadhwa <mailto:swadhwa@juniper.net>
> ; Maglione Roberta <mailto:roberta.maglione@telecomitalia.it>
>                Cc: ancp@ietf.org
>                Sent: Wednesday, April 30, 2008 1:12 AM
>                Subject: Re: [ANCP] question regarding Labels
>in ANCP port up messages
>
>                Sanjay, All,
>
>                What is stated below runs counter to at least
>a handful of ANCP
>                implementations, all of which are known to be
>interoperable.
>                There are really two options:
>                1) The current version of the spec is correct,
>and the known
>                interoperable implementations do not follow it
>                2) The current version of the spec is not
>accurate, and does not reflect
>                the fact that the known implementations follow
>the label field
>                definition from draft-gsmpv3-base-spec.
>
>                I would like to ask you, as the lead editor of
>the spec, to work with
>                the WG in resolving what the problem is, and
>clearing up what the WG
>                spec says about and if 1) holds to be true,
>then proposing an
>                interoperability fix.
>
>                In either case, the issue highlights the fact
>that there is still
>                lingering confusion as to the dependencies
>ANCP has on rfc3292, or
>                draft-gsmpv3-base-spec, or both. It seems to
>be in the best interest of
>                all to address these.
>
>                Regards,
>                Woj.
>
>                > -----Original Message-----
>                > From: Sanjay Wadhwa [mailto:swadhwa@juniper.net]
>                > Sent: 29 April 2008 17:29
>                > To: Maglione Roberta
>                > Cc: Wojciech Dec (wdec); ancp@ietf.org;
>Philippe Champagne (pchamp)
>                > Subject: RE: question regarding Labels in
>ANCP port up messages
>                >
>                > Hi Maglione
>                >   Yes, the label format is as defined in RFC
>3292. The ANCP draft is
>                > based on RFC 3292 and proposes
>extensions/modifications where
>                > required.
>                > This is clearly stated upfront both in the
>abstract and in
>                > section 2. In
>                > section 5.4.2, it clearly  specifies the
>format of "port up" message
>                > (based on RFC 3292), and explicitly states
>the label field
>                > should be set
>                > to 0. Following is what the draft currently states:
>                >
>                >
>                > 5.4.2 Topology Discovery Extensions
>                >
>                > The GSMP Event message with PORT UP message
>type (80) is used for
>                > conveying DSL line attributes to the NAS.
>The version field should be
>                > set to 3, and the sub field should be set to
>1. The I and subMessage
>                > fields SHOULD be set to 1 to signify no
>fragmentation. The Port and
>                > Label fields should be set to 0.
>                >
>                >  0                   1                   2
>                3
>                >          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
>                >
>                >
>                >
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                >         | Vers  |  Sub  | Message Type  |
>Result|        Code
>                > |
>                >
>                >
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                >         | Partition ID  |
>Transaction Identifier
>                > |
>                >
>                >
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                >         |I|      SubMessage Number      |
>       Length
>                > |
>                >
>                >
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                >         |                             Port
>                > |
>                >
>                >
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                >         |                      Port Session Number
>                > |
>                >
>                >
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                >         |                     Event Sequence Number
>                > |
>                >
>                >
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                >         |x|S|x|x|
>                > |
>                >         +-+-+-+-+                     Label
>                > |
>                >         ~
>                > ~
>                >
>                >
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                >         |x|x|x|x|x|x|x|x| Message Type  |
>Tech Type   | Block Length
>                > |
>                >
>                >
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                >         |
>                > |
>                >         ~                         Extension Value
>                > ~
>                >         |
>                > |
>                >
>                >
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                >
>                > When we say the label field should be set to
>0, the intention
>                > is for the
>                > type and length fields in the label TLV to
>be set to 0. We can
>                > explicitly state this for clarity.
>                >
>                > -Sanjay
>                >
>                > >-----Original Message-----
>                > >From: Maglione Roberta
>[mailto:roberta.maglione@telecomitalia.it]
>                > >Sent: Tuesday, April 29, 2008 8:06 AM
>                > >To: Sanjay Wadhwa
>                > >Cc: Wojciech Dec (wdec); ancp@ietf.org;
>pchamp@cisco.com
>                > >Subject: RE: question regarding Labels in
>ANCP port up messages
>                > >
>                > >
>                > >Hi Sanjay and All,
>                > >     I was reading the current ancp
>protocol draft in order to
>                > > understand which should be the correct
>format for the label
>                > >field in the ancp port Up message.
>                > >Actually as it was already pointed out in
>the alias the draft
>                > >in section 5.4.2 says "GSMP Event message
>with PORT UP message
>                > >type (80) is used"  thus I am assuming that
>the label in the
>                > >port UP message should follow the message
>format defined in
>                > >RFC 3292, section 3.1.3:
>                > >
>                > >    0                   1
>2                   3
>                > >    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
>                > >
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                > >   |x|S|x|x|       Label Type      |
>  Label Length         |
>                > >
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                > >   |
>                       |
>                > >   ~                          Label Value
>                       ~
>                > >   |
>                       |
>                > >
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                > >
>                > >but from what I have seen different
>implementations use
>                > >different format for label field: in
>particular several
>                > >implementations use  a label format that is
>similar to the one
>                > >specified in the expired draft
>draft-ietf-gsmp-v3-base-spec:
>                > >
>                > >     0                   1
> 2                   3
>                > >       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
>                > >
>                >
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                > >      |x|S|x|x|x|x|x|x|x|x|x|x|x|x|x|x|
>       Label
>                > Type         |
>                > >
>                >
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                > >      |    Label Adaptation           |
>     Label
>                > Length         |
>                > >
>                >
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                > >      |
>                >          |
>                > >      ~                          Label Value
>                >          ~
>                > >      |
>                >          |
>                > >
>                >
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                > >
>                > >
>                > >Even if ancp does not care about the label
>field, having this
>                > >field somehow not clearly specified in the
>current ancp draft
>                > >can easily lead to interoperability issues,
>thus I think it
>                > >would be very helpful if you and/or the
>other editors can
>                > >clarify what should be the correct format
>for the label field
>                > >to be used in the ancp Port Up message.
>                > >
>                > >Thanks and best regards,
>                > >Roberta
>                > >
>                > >________________________________________
>                > >From: Philippe Champagne (pchamp) [pchamp@cisco.com]
>                > >Sent: Thursday, April 24, 2008 7:14 PM
>                > >To: Sanjay Wadhwa
>                > >Cc: Maglione Roberta; Wojciech Dec (wdec);
>ancp@ietf.org
>                > >Subject: question regarding  Labels in ANCP
>port up messages
>                > >
>                > >Hi Sanjay
>                > >
>                > >In section 5.4.2 of the draft, we have:
>                > >
>                > >
>                > >         0                   1                   2
>                >         3
>                > >         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
>                > >
>                >
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                > >        | Vers  |  Sub  | Message Type  |
>Result|        Code
>                > >         |
>                > >
>                >
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                > >        | Partition ID  |
>Transaction Identifier
>                > >         |
>                > >
>                >
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                > >        |I|      SubMessage Number      |
>        Length
>                > >         |
>                > >
>                >
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                > >        |                             Port
>                > >         |
>                > >
>                >
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                > >        |                      Port Session Number
>                > >         |
>                > >
>                >
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                > >        |                     Event Sequence Number
>                > >         |
>                > >
>                >
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                > >        |x|S|x|x|
>                > >         |
>                > >        +-+-+-+-+                     Label
>                > >         |
>                > >        ~
>                > >         ~
>                > >
>                >
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                > >        |x|x|x|x|x|x|x|x| Message Type  |
>Tech Type   |
>                > >Block Length  |
>                > >
>                >
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                > >        |
>                > >         |
>                > >        ~                         Extension Value
>                > >         ~
>                > >        |
>                > >         |
>                > >
>                >
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                > >Where Label I suppose is taken from the RFC
>3292, section
>                > >3.1.3: (well, I'm guessing)
>                > >
>                > >   A summary of TLV labels supported in
>this version of the
>                > protocol is
>                > >   listed below:
>                > >
>                > >      TLV Label      Type       Section Title
>                > >      ---------      ----       -------------
>                > >      ATM Label      0x100      ATM TLV Labels
>                > >      FR Label       0x101      Frame Relay
>TLV Labels
>                > >      MPLS Gen Label 0x102      MPLS
>Generic TLV Labels
>                > >      FEC Label      0x103      FEC TLV Labels
>                > >
>                > >   All Labels will be designated as follow:
>                > >
>                > >    0                   1
>2                   3
>                > >    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
>                > >
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                > >   |x|S|x|x|       Label Type      |
>  Label Length         |
>                > >
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                > >   |
>                       |
>                > >   ~                          Label Value
>                       ~
>                > >   |
>                       |
>                > >
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                > >
>                > >      x: Reserved Flags.
>                > >         These are generally used by
>specific messages and will be
>                > >         defined in those messages.
>                > >
>                > >      S: Stacked Label Indicator
>                > >         Label Stacking is discussed below
>in section 3.1.3.5
>                > >
>                > >      Label Type
>                > >         A 12-bit field indicating the type
>of label.
>                > >
>                > >      Label Length
>                > >         A 16-bit field indicating the
>length of the Label
>                > Value field
>                > >         in bytes.
>                > >
>                > >      Label Value
>                > >         A variable length field that is an
>integer number of 32 bit
>                > >         words long.  The Label Value field
>is interpreted
>                > according to
>                > >         the Label Type as described in the
>following sections.
>                > >
>                > >
>                > >The draft is a bit obscure about this and
>since it doesn't
>                > >specify much, it can lead to
>misinterpretation for the unused
>                > >part. Moreover, it would appear that
>several implementations
>                > >currently use another format for the label
>field. Can you
>                > >explain?  I mean, how come what's in the
>current draft doesn't
>                > >match what's known to be implemented?
>                > >
>                > >I'm still wondering why we carried over
>pieces from GSMP that
>                > >we do not intend to use.
>                > >
>                > >I would recommend that if we are to keep
>them but not use
>                > >them, we should mention precisely how we
>intend not to use
>                > >them: that is how many 0 filled bytes this
>is expected to use
>                > >
>                > >The rfc 3292 doesn't cover the case where
>this field is not used.
>                > >
>                > >Can you shed some ligths on this?
>                > >
>                > >Thanks
>                > >Regards
>                > >Phil
>                > >
>                > >
>                > >
>                >
>>--------------------------------------------------------------------
>                > >
>                > >CONFIDENTIALITY NOTICE
>                > >
>                > >This message and its attachments are
>addressed solely to the
>                > >persons above and may contain confidential
>information. If you
>                > >have received the message in error, be
>informed that any use
>                > >of the content hereof is prohibited. Please
>return it
>                > >immediately to the sender and delete the
>message. Should you
>                > >have any questions, please contact us by replying to
>                > >webmaster@telecomitalia.it.
>                > >
>                > >        Thank you
>                > >
>                > >
>www.telecomitalia.it
>                > >
>                >
>>--------------------------------------------------------------------
>                > >
>                > >
>                >
>                _______________________________________________
>                ANCP mailing list
>                ANCP@ietf.org
>                https://www.ietf.org/mailman/listinfo/ancp
>
>

--_000_48C276B536524E478C659685995F6AA539DBBBEF99RBSJXadredbac_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:st1 =3D=20
"urn:schemas-microsoft-com:office:smarttags"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.6000.16640" name=3DGENERATOR><!--[if !mso]>
<STYLE>v\:* {
	BEHAVIOR: url(#default#VML)
}
o\:* {
	BEHAVIOR: url(#default#VML)
}
w\:* {
	BEHAVIOR: url(#default#VML)
}
.shape {
	BEHAVIOR: url(#default#VML)
}
</STYLE>
<![endif]--><o:SmartTagType name=3D"PersonName"=20
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"></o:SmartTagTyp=
e><!--[if !mso]>
<STYLE>st1\:* {
	BEHAVIOR: url(#default#ieooui)
}
</STYLE>
<![endif]-->
<STYLE>@font-face {
	font-family: Tahoma;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: blue; TEXT-DECORATION: underline
}
P {
	FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: "Times =
New Roman"; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto
}
SPAN.EmailStyle18 {
	COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal-reply
}
DIV.Section1 {
	page: Section1
}
</STYLE>
</HEAD>
<BODY lang=3DEN-US vLink=3Dblue link=3Dblue>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Hi Sanjay,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>yes apparently I missed your point in the last ema=
il, but=20
I'm glad we agree something is needed</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>to make existing ANCP implementations and the curr=
ent draft=20
to co-exist.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>I do not like your option 1) as if you need a conf=
ig knob=20
for interoperability, it is too easy to</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>get into trouble.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>I think option 2) is the best way forward with the=
=20
differences already identified, or we can </FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>continue to get a show of hands of ANCP implementa=
tions,=20
and see if anyone is actually</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>deployed based on the WG-draft.</FONT></SPAN></DIV=
>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>There is no beneficial reasons to base the event-m=
essage of=20
RFC3292, it could as well be a message</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>described bit by bit in the ANCP draft, and then w=
e can=20
keep the label space at 8 as many</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>implementations alreday do.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>cheers,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Peter</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px soli=
d; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Sanjay Wadhwa=20
  [mailto:swadhwa@juniper.net] <BR><B>Sent:</B> 2. maj 2008 05:35<BR><B>To:=
</B>=20
  Peter Arberg; Tina TSOU; Maglione Roberta; Wojciech Dec (wdec)<BR><B>Cc:<=
/B>=20
  ancp@ietf.org<BR><B>Subject:</B> RE: [ANCP] question regarding Labels in =
ANCP=20
  port up messages<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV class=3DSection1>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Peter<o:p></o:=
p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">&nbsp;You=20
  mis<st1:PersonName w:st=3D"on">se</st1:PersonName>d my point below. The A=
NCP=20
  draft since becoming a WG draft does NOT refer to the old GSMP drafts. An=
y=20
  implementations ba<st1:PersonName w:st=3D"on">se</st1:PersonName>d on thi=
s=20
  WG-draft are expected to be interoperable. You are pointing to pre-WG-dra=
ft=20
  versions of ANCP, and the<st1:PersonName w:st=3D"on">se</st1:PersonName> =
were=20
  indeed ba<st1:PersonName w:st=3D"on">se</st1:PersonName>d on expired GSMP=
 drafts=20
  that evolved past RFC3292. <o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">There is=20
  incompatibility between the current ANCP WG-draft and previous non-WG ver=
sions=20
  (TLV clash, label format..). As mentioned earlier it is prudent for older=
=20
  implementations to start supporting the WG-draft version as soon as possi=
ble.=20
  <o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p>&nbsp;</o=
:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">For interopera=
bility=20
  of WG-draft with the older pre-WG versions, I <st1:PersonName=20
  w:st=3D"on">se</st1:PersonName>e the following=20
  options:<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p>&nbsp;</o=
:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">1. Versioning =
starts=20
  with the WG-draft i.e. WG-draft is version =3D 3, sub-version =3D 1. For =
any=20
  interop issues between older non-WG versions and the WG-draft, one needs =
to=20
  look at solving it within implementations (e.g. an AN that implements the=
=20
  WG-draft, could ba<st1:PersonName w:st=3D"on">se</st1:PersonName>d on a=20
  configuration knob, generate a PORT-UP message with old label format the =
will=20
  be accepted by BNG implementing pre-WG versions of the draft).=20
  <o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p>&nbsp;</o=
:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">2. Change the=
=20
  WG-draft (current draft) to u<st1:PersonName w:st=3D"on">se</st1:PersonNa=
me>=20
  version =3D 3 and sub-version =3D 2. This is assuming there is no deploye=
d=20
  implementation of current WG-draft that already u<st1:PersonName=20
  w:st=3D"on">se</st1:PersonName>s 3.1 as the version, and also assuming th=
e old=20
  pre-WG implementations u<st1:PersonName w:st=3D"on">se</st1:PersonName> 3=
.1.=20
  There will be no backwards compatibility i.e. version 3.1 BNG will not wo=
rk=20
  with version 3.2 AN (we will need to list this as caveat in the appendix=
=20
  <st1:PersonName w:st=3D"on">se</st1:PersonName>ction). AN and BNG will ne=
ed to=20
  negotiate the same version in order for ANCP adjacency to come up. A BNG=
=20
  supporting both versions 3.1 and 3.2 could simultaneously become adjacent=
 with=20
  one AN supporting 3.1 and another AN supporting 3.2. (i.e. version=20
  compatibility is per adjacency).<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Also, major ve=
rsion=20
  number change (e.g. from 3 to 4) should only correspond to a major change=
 in=20
  the protocol (e.g. different mechanism, different transport=20
  etc).<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p>&nbsp;</o=
:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">My vote would =
be to=20
  adopt option 2 above only if further changes to WG-draft happen that rend=
er it=20
  incompatible with the current WG-draft. Any interoperability issues with=
=20
  pre-WG versions could be handled via option 1.<o:p></o:p></SPAN></FONT></=
P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p>&nbsp;</o=
:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Cheers<o:p></o=
:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">-Sanjay<o:p></=
o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p>&nbsp;</o=
:p></SPAN></FONT></P>
  <DIV>
  <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" align=3Dcenter><FONT=
=20
  face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
  <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
  </SPAN></FONT></DIV>
  <P class=3DMsoNormal><B><FONT face=3DTahoma size=3D2><SPAN=20
  style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">From:</=
SPAN></FONT></B><FONT=20
  face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahom=
a"> Peter=20
  Arberg [mailto:parberg@redback.com] <BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Wednesday, April 30, 2008 7:=
20=20
  PM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Sanjay Wadhwa; =
Tina=20
  TSOU; Maglione Roberta; Wojciech Dec (wdec)<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B> ancp@ietf.org<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [ANCP] question regar=
ding=20
  Labels in ANCP port up messages</SPAN></FONT><o:p></o:p></P></DIV>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">Sanjay,</SPAN>=
</FONT><o:p></o:p></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">What do you me=
an "why=20
  I reference an old draft"&nbsp; ????????????</SPAN></FONT><o:p></o:p></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">I'm=20
  surpri<st1:PersonName w:st=3D"on">se</st1:PersonName>d you even ask...&nb=
sp;=20
  plea<st1:PersonName w:st=3D"on">se</st1:PersonName> take a look at YOUR o=
wn=20
  internet-draft that most</SPAN></FONT><o:p></o:p></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">of the ANCP wo=
rking=20
  implementations are ba<st1:PersonName w:st=3D"on">se</st1:PersonName>d on=
, in=20
  ca<st1:PersonName w:st=3D"on">se</st1:PersonName> you do not have this=20
  old</SPAN></FONT><o:p></o:p></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">internet-draft=
, I=20
  have attached it to the document.</SPAN></FONT><o:p></o:p></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">If you look at=
 the=20
  reference for this ancp-draft, you will <st1:PersonName=20
  w:st=3D"on">se</st1:PersonName>e that in the reference <st1:PersonName=20
  w:st=3D"on">se</st1:PersonName>ction</SPAN></FONT><o:p></o:p></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">you point to t=
his old=20
  gsmp-draft...&nbsp; Yes and I know this has been changed in the=20
  later</SPAN></FONT><o:p></o:p></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">versions of th=
e ANCP=20
  draft, but that do not change the fact that many of the=20
  implementations</SPAN></FONT><o:p></o:p></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">today was deve=
loped=20
  when the attached draft was current.</SPAN></FONT><o:p></o:p></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">I think a very=
 good=20
  question is brought up here, and that is what is implemented=20
  and</SPAN></FONT><o:p></o:p></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">running in net=
works=20
  today ?</SPAN></FONT><o:p></o:p></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">My take on thi=
s is=20
  that when the reference was change from the old gsmp-draft to the=20
  older</SPAN></FONT><o:p></o:p></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">RFC3292, appar=
ently=20
  no one paid any attention to the fact the label definition in the=20
  event</SPAN></FONT><o:p></o:p></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">message was di=
fferent=20
  and not compatible.</SPAN></FONT><o:p></o:p></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">What current=20
  implementations do today is an important factor in this discussion, and I=
=20
  think</SPAN></FONT><o:p></o:p></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">it is time to =
come to=20
  realization that we might need a new version number for ANCP=20
  since</SPAN></FONT><o:p></o:p></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">it continues t=
o look=20
  like there is big holes open for interpretation. So if I did a=20
  ANCP</SPAN></FONT><o:p></o:p></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">implementation=
 there=20
  is bound to be interoperability issues with existing=20
  implementations</SPAN></FONT><o:p></o:p></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">runnig.</SPAN>=
</FONT><o:p></o:p></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">cheers,</SPAN>=
</FONT><o:p></o:p></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">Peter</SPAN></=
FONT><o:p></o:p></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
  <BLOCKQUOTE=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: mediu=
m none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: 5pt 0in 5pt 3.75pt;=
 BORDER-LEFT: blue 1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: medium non=
e">
    <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
    style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
    <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" align=3Dcenter><FON=
T=20
    face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
    <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
    </SPAN></FONT></DIV>
    <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><B><FONT face=3DTaho=
ma=20
    size=3D2><SPAN=20
    style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">From:=
</SPAN></FONT></B><FONT=20
    face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tah=
oma">=20
    Sanjay Wadhwa [mailto:swadhwa@juniper.net] <BR><B><SPAN=20
    style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> 30. april 2008 14:42<BR><B=
><SPAN=20
    style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Peter Arberg; Tina TSOU; Mag=
lione=20
    Roberta; Wojciech Dec (wdec)<BR><B><SPAN=20
    style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B> ancp@ietf.org<BR><B><SPAN=20
    style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [ANCP] question reg=
arding=20
    Labels in ANCP port up messages</SPAN></FONT><o:p></o:p></P>
    <P><FONT face=3D"Times New Roman" size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt">Peter<BR>&nbsp; The ANCP draft as it currentl=
y=20
    stands is ba<st1:PersonName w:st=3D"on">se</st1:PersonName>d on RFC3292=
. It=20
    provides extensions and modifications to relevant constructs in RFC3292=
.=20
    There is no mention (implicit or explicit) of expired GSMP drafts in th=
e=20
    ANCP draft. In order to implement the ANCP draft, I am not sure why one=
=20
    would look at the expired GSMP drafts. Do you <st1:PersonName=20
    w:st=3D"on">se</st1:PersonName>e a reason to do this ba<st1:PersonName=
=20
    w:st=3D"on">se</st1:PersonName>d on anything that you read in the ANCP =
draft?=20
    Bringing up reference to expired gsmp draft in this thread&nbsp;just ad=
ds to=20
    the confusion. For GSMPv3 objects in the messages (such as Label Type),=
 one=20
    has to look at RFC3292 (this is clearly stated in the ANCP draft -=20
    <st1:PersonName w:st=3D"on">se</st1:PersonName>ction 2 and I am quoting=
 it=20
    below) :</SPAN></FONT><o:p></o:p></P>
    <P><FONT face=3D"Times New Roman" color=3Dblue size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue">ANCP u<st1:PersonName=20
    w:st=3D"on">se</st1:PersonName>s a sub<st1:PersonName=20
    w:st=3D"on">se</st1:PersonName>t of GSMPv3 messages to implement curren=
tly=20
    defined u<st1:PersonName w:st=3D"on">se</st1:PersonName>-ca<st1:PersonN=
ame=20
    w:st=3D"on">se</st1:PersonName>s. The<st1:PersonName=20
    w:st=3D"on">se</st1:PersonName> relevant GSMPv3 messages are identified=
 in=20
    <st1:PersonName w:st=3D"on">se</st1:PersonName>ction 5. GSMPv3 procedur=
es with=20
    suitable extensions, as u<st1:PersonName w:st=3D"on">se</st1:PersonName=
>d by=20
    ANCP, are described in <st1:PersonName w:st=3D"on">se</st1:PersonName>c=
tions=20
    5.1, 5.2 and 5.3. GSMPv3 general extensions and GSMPv3 message specific=
=20
    extensions required by ANCP are described in sub-<st1:PersonName=20
    w:st=3D"on">se</st1:PersonName>ctions of 5.4. In addition to specifying=
=20
    extensions and modifications to relevant GSMP messages applicable to AN=
CP,=20
    this draft also defines the usage of the<st1:PersonName=20
    w:st=3D"on">se</st1:PersonName> messages by ANCP, and indicates the val=
ues=20
    that ANCP should <st1:PersonName w:st=3D"on">se</st1:PersonName>t for r=
elevant=20
    fields in the<st1:PersonName w:st=3D"on">se</st1:PersonName> GSMP messa=
ges.=20
    However, to understand the basic <st1:PersonName=20
    w:st=3D"on">se</st1:PersonName>mantics of various fields in GSMP messag=
es, the=20
    reader is referred to [4].&nbsp;=3D&gt; RFC 3292.</SPAN></FONT><FONT=20
    size=3D2><SPAN style=3D"FONT-SIZE: 10pt"><BR><BR>What existing implemen=
tations=20
    currently do is an important but <st1:PersonName=20
    w:st=3D"on">se</st1:PersonName>parate issue. The<st1:PersonName=20
    w:st=3D"on">se</st1:PersonName> implementations for most part precede t=
he=20
    current ANCP draft. It is fine to poll where the<st1:PersonName=20
    w:st=3D"on">se</st1:PersonName> implementations diverge from the curren=
t=20
    draft. It is then upto the implementations (including the one that I am=
=20
    somewhat familiar with) to work towards compliance with the draft.=20
    </SPAN></FONT><o:p></o:p></P>
    <P><FONT face=3D"Times New Roman" size=3D2><SPAN style=3D"FONT-SIZE: 10=
pt">On the=20
    following points&nbsp;from &nbsp;Woj:</SPAN></FONT><o:p></o:p></P>
    <P><FONT face=3D"Times New Roman" size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt">Woj&gt;2) The current version of the spec is =
not=20
    accurate, and does not reflect&nbsp;the fact that the known implementat=
ions=20
    follow the label field definition from draft-gsmpv3-ba<st1:PersonName=20
    w:st=3D"on">se</st1:PersonName>-spec.</SPAN></FONT><o:p></o:p></P>
    <P><FONT face=3D"Times New Roman" size=3D2><SPAN style=3D"FONT-SIZE: 10=
pt">It is=20
    not for the protocol draft to point out what current implementations=20
    do.&nbsp;&nbsp;The best we can do is to further clarify in the draft th=
at=20
    type and value fields of the Label object (defined in RFC3292) should b=
e=20
    <st1:PersonName w:st=3D"on">se</st1:PersonName>t to 0 in the port-up me=
ssage=20
    (we already&nbsp;mention the lable object as a whole should be=20
    <st1:PersonName w:st=3D"on">se</st1:PersonName>t to all 0s).=20
    </SPAN></FONT><o:p></o:p></P>
    <P><FONT face=3D"Times New Roman" size=3D2><SPAN style=3D"FONT-SIZE: 10=
pt">Woj&gt;=20
    This would be a good thing for the WG to discuss. There most evidently =
is a=20
    fair amount of&nbsp;"dead wood" in the current spec, ie stuff that nobo=
dy=20
    yet&nbsp;implements or cares about. &nbsp;In the former ca<st1:PersonNa=
me=20
    w:st=3D"on">se</st1:PersonName>, we could re-cast that material using t=
he new=20
    notions/extensions, in the latter ca<st1:PersonName=20
    w:st=3D"on">se</st1:PersonName> simply chop it=20
    out.</SPAN></FONT><o:p></o:p></P>
    <P><FONT face=3D"Times New Roman" size=3D2><SPAN style=3D"FONT-SIZE: 10=
pt">I=20
    agree. We are ba<st1:PersonName w:st=3D"on">se</st1:PersonName>d on GSM=
Pv3=20
    (RFC3292) &nbsp;messages, and obviously not everything in the<st1:Perso=
nName=20
    w:st=3D"on">se</st1:PersonName> messages is leveraged by ANCP.&nbsp; Ho=
wever,=20
    the sync rate and OAM u<st1:PersonName=20
    w:st=3D"on">se</st1:PersonName>s-ca<st1:PersonName=20
    w:st=3D"on">se</st1:PersonName>s are implemented and in u<st1:PersonNam=
e=20
    w:st=3D"on">se</st1:PersonName> (ideally we should leave the<st1:Person=
Name=20
    w:st=3D"on">se</st1:PersonName> alone...i.e. no change beyond adding mo=
re=20
    clarity if needed). For anything new (such as multicast) we are definin=
g new=20
    messages&nbsp;(no legacy).&nbsp; </SPAN></FONT><o:p></o:p></P>
    <P><FONT face=3D"Times New Roman" size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt">-Sanjay<BR><BR>&gt;-----Original=20
    Message-----<BR>&gt;From: Peter Arberg [</SPAN></FONT><A=20
    href=3D"mailto:parberg@redback.com"><FONT size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt">mailto:parberg@redback.com</SPAN></FONT></A><=
FONT=20
    size=3D2><SPAN style=3D"FONT-SIZE: 10pt">]<BR>&gt;Sent: Wednesday, Apri=
l 30,=20
    2008 3:56 PM<BR>&gt;To: Tina TSOU; Maglione Roberta; Sanjay Wadhwa; Woj=
ciech=20
    Dec (wdec)<BR>&gt;Cc: ancp@ietf.org<BR>&gt;Subject: RE: [ANCP] question=
=20
    regarding Labels in ANCP port up=20
    messages<BR>&gt;<BR>&gt;<BR>&gt;Hi,<BR>&gt;<BR>&gt;some times I think i=
t is=20
    amazing we ever got interoperability<BR>&gt;of ANCP=20
    :-)<BR>&gt;becau<st1:PersonName w:st=3D"on">se</st1:PersonName> looking=
 at the=20
    label discussion is a very good example that the<BR>&gt;whole GSMP - AN=
CP=20
    reference have not worked very well.<BR>&gt;<BR>&gt;In the ANCP draft,=
=20
    <st1:PersonName w:st=3D"on">se</st1:PersonName>ction 5.4.2 the event me=
ssage=20
    is shown like=20
    this:<BR>&gt;<BR>&gt;0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    3<BR>&gt;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=
=20
    1<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+<BR>&gt;|=20
    Vers&nbsp; |&nbsp; Sub&nbsp; | Message Type&nbsp; |=20
    Result|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Code&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    |<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+<BR>&gt;|=20
    Partition ID&nbsp;=20
    |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Transaction=20
    Identifier&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;=20
    |<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+<BR>&gt;|I|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    SubMessage Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;=20
    |<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+<BR>&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Port&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    |<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+<BR>&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Port Session=20
    Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    |<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+<BR>&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Event Sequence=20
    Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    |<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+<BR>&gt;|x|S|x|x|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    |<BR>&gt;+-+-+-+-+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    |<BR>&gt;~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;=20
    ~<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+<BR>&gt;|x|x|x|x|x|x|x|x|=20
    Message Type&nbsp; |&nbsp;&nbsp; Tech Type&nbsp;&nbsp; | Block Length&n=
bsp;=20
    |<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+<BR>&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;=20
    |<BR>&gt;~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;=20
    Extension=20
    Value&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    ~<BR>&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;=20
    |<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+<BR>&gt;<BR>&gt;<BR>&gt;This=20
    is the exact same event message defined=20
    in<BR>&gt;draft-ietf-gsmp-v3-ba<st1:PersonName=20
    w:st=3D"on">se</st1:PersonName>-spec-08.txt&nbsp; <st1:PersonName=20
    w:st=3D"on">se</st1:PersonName>ction 11.<BR>&gt;<BR>&gt;And in this=20
    gsmp-draft, <st1:PersonName w:st=3D"on">se</st1:PersonName>ction 5.1.3 =
the=20
    label space is defined<BR>&gt;as minimum 8 bytes if the length=3D0 and =
as such=20
    no value, and this<BR>&gt;is becau<st1:PersonName=20
    w:st=3D"on">se</st1:PersonName> the gsmp-draft has a new "label adaptai=
on"=20
    field.<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt;BUT in RFC3292 the event message =
is=20
    show in <st1:PersonName w:st=3D"on">se</st1:PersonName>ction 9, like=20
    this:<BR>&gt;<BR>&gt;0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    3<BR>&gt;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=
=20
    1<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+<BR>&gt;|&nbsp;&nbsp;&nbsp;=20
    Version&nbsp;&nbsp;&nbsp; | Message Type&nbsp; |&nbsp;&nbsp;&nbsp;=20
    Result&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;=20
    Code&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    |<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+<BR>&gt;|=20
    Partition ID&nbsp;=20
    |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Transaction=20
    Identifier&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;=20
    |<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+<BR>&gt;|I|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    SubMessage Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;=20
    |<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+<BR>&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Port&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    |<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+<BR>&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Port Session=20
    Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    |<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+<BR>&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Event Sequence=20
    Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    |<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+<BR>&gt;|x|S|x|x|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    |<BR>&gt;+-+-+-+-+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    |<BR>&gt;~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;=20
    ~<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+<BR>&gt;<BR>&gt;<BR>&gt;So=20
    a different Event Message picture/definition than what is shown<BR>&gt;=
in=20
    the ANCP draft, and in RFC3292 <st1:PersonName=20
    w:st=3D"on">se</st1:PersonName>ction 3.1.3 the label field<BR>&gt;is de=
fined=20
    as 4 bytes if length=3D0 and as such no=20
    value.<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt;So I very much agree with Woj tha=
t we=20
    need this issue to be resolved,<BR>&gt;and proabably a show of hands wh=
at is=20
    actually done in different<BR>&gt;implementations, so we can nail down =
how=20
    the event message is<BR>&gt;suppo<st1:PersonName=20
    w:st=3D"on">se</st1:PersonName> to look like in ANCP.<BR>&gt;<BR>&gt;<B=
R>&gt;I=20
    know at least 1 implementation which u<st1:PersonName=20
    w:st=3D"on">se</st1:PersonName>s 8 bytes for the<BR>&gt;label=20
    field.<BR>&gt;<BR>&gt;<BR>&gt;cheers,<BR>&gt;Peter<BR>&gt;<BR>&gt;<BR>&=
gt;<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt;________________________________<BR>&gt;=
<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    From: ancp-bounces@ietf.org<BR>&gt;[</SPAN></FONT><A=20
    href=3D"mailto:ancp-bounces@ietf.org"><FONT size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt">mailto:ancp-bounces@ietf.org</SPAN></FONT></A=
><FONT=20
    size=3D2><SPAN style=3D"FONT-SIZE: 10pt">] On Behalf Of Tina=20
    TSOU<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Sent: 30. april =
2008=20
    00:19<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; To: Maglione=20
    Roberta; Sanjay Wadhwa; Wojciech Dec=20
    (wdec)<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Cc:=20
    ancp@ietf.org<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Subject=
: Re:=20
    [ANCP] question regarding Labels in ANCP<BR>&gt;port up=20
    messages<BR>&gt;<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;=20
    Hi all,<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; It is clear t=
o me=20
    that if Label Length is filled as 0,<BR>&gt;there is nothing to be fill=
ed=20
    into Label Value. The whole<BR>&gt;Label part is 4 bytes, not 8=20
    bytes.<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Cheers=
 from=20
    the last working day before Labor's Day<BR>&gt;holidays in some=20
    countries:)<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Tina<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    ----- Original Message=20
    -----<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    From: Wojciech Dec (wdec) &lt;</SPAN></FONT><A=20
    href=3D"mailto:wdec@cisco.com"><FONT size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt">mailto:wdec@cisco.com</SPAN></FONT></A><FONT=
=20
    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt">&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    To: Sanjay Wadhwa &lt;</SPAN></FONT><A=20
    href=3D"mailto:swadhwa@juniper.net"><FONT size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt">mailto:swadhwa@juniper.net</SPAN></FONT></A><=
FONT=20
    size=3D2><SPAN style=3D"FONT-SIZE: 10pt">&gt;<BR>&gt; ; Maglione Robert=
a=20
    &lt;</SPAN></FONT><A href=3D"mailto:roberta.maglione@telecomitalia.it">=
<FONT=20
    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt">mailto:roberta.maglione@telecomitalia.it</SPA=
N></FONT></A><FONT=20
    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt">&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Cc:=20
    ancp@ietf.org<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Sent: Wednesday, April 30, 2008 1:12=20
    AM<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Subject: Re: [ANCP] question regarding Labels<BR>&gt;in ANCP port up=20
    messages<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Sanjay,=20
    All,<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    What is stated below runs counter to at least<BR>&gt;a handful of=20
    ANCP<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    implementations, all of which are known to=20
    be<BR>&gt;interoperable.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    There are really two=20
    options:<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    1) The current version of the spec is correct,<BR>&gt;and the=20
    known<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    interoperable implementations do not follow=20
    it<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    2) The current version of the spec is not<BR>&gt;accurate, and does not=
=20
    reflect<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    the fact that the known implementations follow<BR>&gt;the label=20
    field<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    definition from draft-gsmpv3-ba<st1:PersonName=20
    w:st=3D"on">se</st1:PersonName>-spec.<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    I would like to ask you, as the lead editor of<BR>&gt;the spec, to work=
=20
    with<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    the WG in resolving what the problem is, and<BR>&gt;clearing up what th=
e=20
    WG<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    spec says about and if 1) holds to be true,<BR>&gt;then proposing=20
    an<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    interoperability=20
    fix.<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    In either ca<st1:PersonName w:st=3D"on">se</st1:PersonName>, the issue=
=20
    highlights the fact<BR>&gt;that there is=20
    still<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    lingering confusion as to the dependencies<BR>&gt;ANCP has on rfc3292,=
=20
    or<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    draft-gsmpv3-ba<st1:PersonName w:st=3D"on">se</st1:PersonName>-spec, or=
 both.=20
    It <st1:PersonName w:st=3D"on">se</st1:PersonName>ems to<BR>&gt;be in t=
he best=20
    interest=20
    of<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    all to address the<st1:PersonName=20
    w:st=3D"on">se</st1:PersonName>.<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Regards,<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Woj.<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; -----Original=20
    Message-----<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; From: Sanjay Wadhwa [</SPAN></FONT><A=20
    href=3D"mailto:swadhwa@juniper.net"><FONT size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt">mailto:swadhwa@juniper.net</SPAN></FONT></A><=
FONT=20
    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt">]<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; Sent: 29 April 2008=20
    17:29<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; To: Maglione=20
    Roberta<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; Cc: Wojciech Dec (wdec); ancp@ietf.org;<BR>&gt;Philippe Champagne=
=20
    (pchamp)<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; Subject: RE: question regarding Labels in<BR>&gt;ANCP port up=20
    messages<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; Hi=20
    Maglione<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;&nbsp;&nbsp; Yes, the label format is as defined in RFC<BR>&gt;3292=
. The=20
    ANCP draft=20
    is<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; ba<st1:PersonName w:st=3D"on">se</st1:PersonName>d on RFC 3292 and=
=20
    propo<st1:PersonName=20
    w:st=3D"on">se</st1:PersonName>s<BR>&gt;extensions/modifications=20
    where<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    required.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; This is clearly stated upfront both in the<BR>&gt;abstract and=20
    in<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; <st1:PersonName w:st=3D"on">se</st1:PersonName>ction 2.=20
    In<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; <st1:PersonName w:st=3D"on">se</st1:PersonName>ction 5.4.2, it=20
    clearly&nbsp; specifies the<BR>&gt;format of "port up"=20
    message<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; (ba<st1:PersonName w:st=3D"on">se</st1:PersonName>d on RFC 3292), =
and=20
    explicitly states<BR>&gt;the label=20
    field<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; should be <st1:PersonName=20
    w:st=3D"on">se</st1:PersonName>t<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; to 0. Following is what the draft currently=20
    states:<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; 5.4.2 Topology Discovery=20
    Extensions<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; The GSMP Event message with PORT UP message<BR>&gt;type (80) is=20
    u<st1:PersonName w:st=3D"on">se</st1:PersonName>d=20
    for<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; conveying DSL line attributes to the NAS.<BR>&gt;The version field=
=20
    should=20
    be<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; <st1:PersonName w:st=3D"on">se</st1:PersonName>t to 3, and the sub=
 field=20
    should be <st1:PersonName w:st=3D"on">se</st1:PersonName>t to<BR>&gt;1.=
 The I=20
    and=20
    subMessage<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; fields SHOULD be <st1:PersonName w:st=3D"on">se</st1:PersonName>t =
to 1 to=20
    signify no<BR>&gt;fragmentation. The Port=20
    and<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; Label fields should be <st1:PersonName w:st=3D"on">se</st1:PersonN=
ame>t=20
    to=20
    0.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;&nbsp;=20
    0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    2&nbsp;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    3<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0 1 2 3 4 5 =
6 7 8=20
    9 0 1 2 3 4 5 6 7<BR>&gt;8 9 0 1 2 3 4=20
    5<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; 6 7 8 9 0=20
    1<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Vers&nbsp; |&nbs=
p;=20
    Sub&nbsp; | Message Type&nbsp;=20
    |<BR>&gt;Result|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Code<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Partition ID&nbs=
p;=20
    |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>=
&gt;Transaction=20
    Identifier<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    |I|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SubMessage=20
    Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    |&nbsp;&nbsp;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Length<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;=20
    Port<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Port Session=20
    Number<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Event Sequence=20
    Number<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    |x|S|x|x|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    +-+-+-+-+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Label<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    ~<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    ~<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |x|x|x|x|x|x|x|x|=
=20
    Message Type&nbsp; |&nbsp;&nbsp;<BR>&gt;Tech Type&nbsp;&nbsp; | Block=20
    Length<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    ~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
=20
    Extension=20
    Value<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    ~<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; When we say the label field should be <st1:PersonName=20
    w:st=3D"on">se</st1:PersonName>t to<BR>&gt;0, the=20
    intention<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; is for=20
    the<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; type and length fields in the label TLV to<BR>&gt;be <st1:PersonNa=
me=20
    w:st=3D"on">se</st1:PersonName>t to 0. We=20
    can<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; explicitly state this for=20
    clarity.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    -Sanjay<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;-----Original=20
    Message-----<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;From: Maglione Roberta<BR>&gt;[</SPAN></FONT><A=20
    href=3D"mailto:roberta.maglione@telecomitalia.it"><FONT size=3D2><SPAN=
=20
    style=3D"FONT-SIZE: 10pt">mailto:roberta.maglione@telecomitalia.it</SPA=
N></FONT></A><FONT=20
    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt">]<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;Sent: Tuesday, April 29, 2008 8:06=20
    AM<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;To: Sanjay=20
    Wadhwa<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;Cc: Wojciech Dec (wdec);=20
    ancp@ietf.org;<BR>&gt;pchamp@cisco.com<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;Subject: RE: question regarding Labels in<BR>&gt;ANCP port up=
=20
    messages<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;Hi Sanjay and=20
    All,<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp; I was reading the current=20
    ancp<BR>&gt;protocol draft in order=20
    to<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt; understand which should be the correct<BR>&gt;format for the=
=20
    label<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;field in the ancp port Up=20
    message.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;Actually as it was already pointed out in<BR>&gt;the alias the=
=20
    draft<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;in <st1:PersonName w:st=3D"on">se</st1:PersonName>ction 5.4.2 =
says=20
    "GSMP Event message<BR>&gt;with PORT UP=20
    message<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;type (80) is u<st1:PersonName w:st=3D"on">se</st1:PersonName>d=
"&nbsp;=20
    thus I am assuming that<BR>&gt;the label in=20
    the<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;port UP message should follow the message<BR>&gt;format define=
d=20
    in<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;RFC 3292, <st1:PersonName w:st=3D"on">se</st1:PersonName>ction=
=20
    3.1.3:<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;=20
    0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt;2&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;=20
    3<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp; 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9<BR>=
&gt;0=20
    1 2 3 4 5 6 7 8 9 0=20
    1<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;&nbsp;&nbsp;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp; |x|S|x|x|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Lab=
el=20
    Type&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt;&nbsp; Label=20
    Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;&nbsp;&nbsp;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;=20
    |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;=20
    ~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;=20
    Label=20
    Value&nbsp;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;=20
    ~<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;=20
    |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;&nbsp;&nbsp;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;but from what I have <st1:PersonName=20
    w:st=3D"on">se</st1:PersonName>en different<BR>&gt;implementations=20
    u<st1:PersonName=20
    w:st=3D"on">se</st1:PersonName><BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;different format for label field: in<BR>&gt;particular=20
    <st1:PersonName=20
    w:st=3D"on">se</st1:PersonName>veral<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;implementations u<st1:PersonName=20
    w:st=3D"on">se</st1:PersonName>&nbsp; a label format that is<BR>&gt;sim=
ilar to=20
    the=20
    one<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;specified in the expired=20
    draft<BR>&gt;draft-ietf-gsmp-v3-ba<st1:PersonName=20
    w:st=3D"on">se</st1:PersonName>-spec:<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;=20
    0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt;=20
    2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    3<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0 1 2 3 4 5 6 7 8 9 0 1 2=
 3 4=20
    5 6 7<BR>&gt;8 9 0 1 2 3 4 5=20
    6<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; 7 8 9 0=20
    1<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    |x|S|x|x|x|x|x|x|x|x|x|x|x|x|x|x|&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Label<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; Type&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp; Label=20
    Adaptation&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
=20
    |&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Label<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    ~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;=20
    Label=20
    Value<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    ~<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;Even if ancp does not care about the label<BR>&gt;field, havin=
g=20
    this<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;field somehow not clearly specified in the<BR>&gt;current ancp=
=20
    draft<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;can easily lead to interoperability issues,<BR>&gt;thus I thin=
k=20
    it<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;would be very helpful if you and/or the<BR>&gt;other editors=20
    can<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;clarify what should be the correct format<BR>&gt;for the label=
=20
    field<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;to be u<st1:PersonName w:st=3D"on">se</st1:PersonName>d in the=
 ancp=20
    Port Up=20
    message.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;Thanks and best=20
    regards,<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;Roberta<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;________________________________________<BR>&gt;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;From: Philippe Champagne (pchamp)=20
    [pchamp@cisco.com]<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;Sent: Thursday, April 24, 2008 7:14=20
    PM<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;To: Sanjay=20
    Wadhwa<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;Cc: Maglione Roberta; Wojciech Dec=20
    (wdec);<BR>&gt;ancp@ietf.org<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;Subject: question regarding&nbsp; Labels in ANCP<BR>&gt;port u=
p=20
    messages<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;Hi=20
    Sanjay<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;In <st1:PersonName w:st=3D"on">se</st1:PersonName>ction 5.4.2 =
of the=20
    draft, we=20
    have:<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    2<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    3<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0 1 2 3 4 5 6=
 7 8=20
    9 0 1 2 3 4 5 6<BR>&gt;7 8 9 0 1 2 3 4 5=20
    6<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;7 8 9 0=20
    1<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;<BR>&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Vers&nbsp; |&nbsp=
;=20
    Sub&nbsp; | Message Type&nbsp;=20
    |<BR>&gt;Result|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Code<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;<BR>&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Partition ID&nbsp=
;=20
    |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>=
&gt;Transaction=20
    Identifier<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;<BR>&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    |I|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SubMessage=20
    Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    |&nbsp;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Length<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;<BR>&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;=20
    Port<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;<BR>&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Port Session=20
    Number<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;<BR>&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Event Sequence=20
    Number<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;<BR>&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    |x|S|x|x|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    +-+-+-+-+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Label<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    ~<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    ~<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;<BR>&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |x|x|x|x|x|x|x|x|=20
    Message Type&nbsp; |&nbsp;&nbsp;<BR>&gt;Tech Type&nbsp;&nbsp;=20
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;Block Length&nbsp;=20
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;<BR>&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    ~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
=20
    Extension=20
    Value<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    ~<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;<BR>&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;Where Label I suppo<st1:PersonName w:st=3D"on">se</st1:PersonN=
ame> is=20
    taken from the RFC<BR>&gt;3292, <st1:PersonName=20
    w:st=3D"on">se</st1:PersonName>ction<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;3.1.3: (well, I'm=20
    guessing)<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp; A summary of TLV labels supported in<BR>&gt;this=
=20
    version of=20
    the<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; protocol=20
    is<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp; listed=20
    below:<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; TLV=20
    Label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Type&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;=20
    Section=20
    Title<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    ---------&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    ----&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    -------------<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ATM=20
    Label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0x100&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 ATM=20
    TLV=20
    Labels<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; FR=20
    Label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    0x101&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Frame Relay<BR>&gt;TLV=20
    Labels<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MPLS Gen Label=20
    0x102&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MPLS<BR>&gt;Generic TLV=20
    Labels<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; FEC=20
    Label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0x103&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 FEC=20
    TLV=20
    Labels<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp; All Labels will be designated as=20
    follow:<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;=20
    0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt;2&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;=20
    3<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp; 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9<BR>=
&gt;0=20
    1 2 3 4 5 6 7 8 9 0=20
    1<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;&nbsp;&nbsp;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp; |x|S|x|x|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Lab=
el=20
    Type&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt;&nbsp; Label=20
    Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;&nbsp;&nbsp;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;=20
    |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;=20
    ~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;=20
    Label=20
    Value&nbsp;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;=20
    ~<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;=20
    |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
    |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;&nbsp;&nbsp;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; x: Re<st1:PersonName=20
    w:st=3D"on">se</st1:PersonName>rved=20
    Flags.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The<st1:Perso=
nName=20
    w:st=3D"on">se</st1:PersonName> are generally u<st1:PersonName=20
    w:st=3D"on">se</st1:PersonName>d by<BR>&gt;specific messages and will=20
    be<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; defined in=20
    tho<st1:PersonName w:st=3D"on">se</st1:PersonName>=20
    messages.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; S: Stacked Label=20
    Indicator<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Label Stackin=
g is=20
    discus<st1:PersonName w:st=3D"on">se</st1:PersonName>d below<BR>&gt;in=
=20
    <st1:PersonName w:st=3D"on">se</st1:PersonName>ction=20
    3.1.3.5<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Label=20
    Type<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A 12-bit fiel=
d=20
    indicating the type<BR>&gt;of=20
    label.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Label=20
    Length<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A 16-bit fiel=
d=20
    indicating the<BR>&gt;length of the=20
    Label<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; Value=20
    field<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; in=20
    bytes.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Label=20
    Value<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A variable le=
ngth=20
    field that is an<BR>&gt;integer number of 32=20
    bit<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; words long.&n=
bsp;=20
    The Label Value field<BR>&gt;is=20
    interpreted<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; according=20
    to<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the Label Typ=
e as=20
    described in the<BR>&gt;following <st1:PersonName=20
    w:st=3D"on">se</st1:PersonName>ctions.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;The draft is a bit obscure about this and<BR>&gt;since it=20
    doesn't<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;specify much, it can lead to<BR>&gt;misinterpretation for the=
=20
    unu<st1:PersonName=20
    w:st=3D"on">se</st1:PersonName>d<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;part. Moreover, it would appear that<BR>&gt;<st1:PersonName=20
    w:st=3D"on">se</st1:PersonName>veral=20
    implementations<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;currently u<st1:PersonName w:st=3D"on">se</st1:PersonName> ano=
ther=20
    format for the label<BR>&gt;field. Can=20
    you<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;explain?&nbsp; I mean, how come what's in the<BR>&gt;current d=
raft=20
    doesn't<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;match what's known to be=20
    implemented?<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;I'm still wondering why we carried over<BR>&gt;pieces from GSM=
P=20
    that<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;we do not intend to u<st1:PersonName=20
    w:st=3D"on">se</st1:PersonName>.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;I would recommend that if we are to keep<BR>&gt;them but not=20
    u<st1:PersonName=20
    w:st=3D"on">se</st1:PersonName><BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;them, we should mention preci<st1:PersonName=20
    w:st=3D"on">se</st1:PersonName>ly how we<BR>&gt;intend not to u<st1:Per=
sonName=20
    w:st=3D"on">se</st1:PersonName><BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;them: that is how many 0 filled bytes this<BR>&gt;is expected =
to=20
    u<st1:PersonName=20
    w:st=3D"on">se</st1:PersonName><BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;The rfc 3292 doesn't cover the ca<st1:PersonName=20
    w:st=3D"on">se</st1:PersonName> where<BR>&gt;this field is not=20
    u<st1:PersonName=20
    w:st=3D"on">se</st1:PersonName>d.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;Can you shed some ligths on=20
    this?<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;Thanks<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;Regards<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;Phil<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;<BR>&gt;&gt;-------------------------------------------------------=
-------------<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;CONFIDENTIALITY=20
    NOTICE<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;This message and its attachments are<BR>&gt;addres<st1:PersonN=
ame=20
    w:st=3D"on">se</st1:PersonName>d solely to=20
    the<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;persons above and may contain confidential<BR>&gt;information.=
 If=20
    you<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;have received the message in error, be<BR>&gt;informed that an=
y=20
    u<st1:PersonName=20
    w:st=3D"on">se</st1:PersonName><BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;of the content hereof is prohibited. Plea<st1:PersonName=20
    w:st=3D"on">se</st1:PersonName><BR>&gt;return=20
    it<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;immediately to the <st1:PersonName=20
    w:st=3D"on">se</st1:PersonName>nder and delete the<BR>&gt;message. Shou=
ld=20
    you<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;have any questions, plea<st1:PersonName=20
    w:st=3D"on">se</st1:PersonName> contact us by replying=20
    to<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;webmaster@telecomitalia.it.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Thank=20
    you<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;<BR>&gt;www.telecomitalia.it<BR>&gt;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;<BR>&gt;&gt;-------------------------------------------------------=
-------------<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    _______________________________________________<BR>&gt;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
=20
    ANCP mailing=20
    list<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    ANCP@ietf.org<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    </SPAN></FONT><A href=3D"https://www.ietf.org/mailman/listinfo/ancp"=20
    target=3D_blank><FONT size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt">https://www.ietf.org/mailman/listinfo/ancp</S=
PAN></FONT></A><BR><FONT=20
    size=3D2><SPAN style=3D"FONT-SIZE: 10pt">&gt;<BR>&gt;</SPAN></FONT>=20
    <o:p></o:p></P></BLOCKQUOTE></DIV></BLOCKQUOTE></BODY></HTML>

--_000_48C276B536524E478C659685995F6AA539DBBBEF99RBSJXadredbac_--

--===============1018556323==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1018556323==--


From ancp-bounces@ietf.org  Sat May  3 12:39:03 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id A287A3A6CC4;
	Sat,  3 May 2008 12:39:03 -0700 (PDT)
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 E9B153A6BA1
	for <ancp@core3.amsl.com>; Sat,  3 May 2008 12:39:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 4.322
X-Spam-Level: ****
X-Spam-Status: No, score=4.322 tagged_above=-999 required=5 tests=[AWL=-4.965, 
	BAYES_00=-2.599, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, 
	HTML_OBFUSCATE_05_10=0.001, J_BACKHAIR_12=1, J_BACKHAIR_21=1,
	J_BACKHAIR_22=1, J_BACKHAIR_23=1, J_BACKHAIR_24=1, J_BACKHAIR_25=1,
	J_BACKHAIR_26=1, J_BACKHAIR_27=1, J_BACKHAIR_32=1, J_BACKHAIR_42=1,
	J_BACKHAIR_52=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 qYDdiXsjmwlN for <ancp@core3.amsl.com>;
	Sat,  3 May 2008 12:38:57 -0700 (PDT)
Received: from prattle.redback.com (prattle.redback.com [155.53.12.9])
	by core3.amsl.com (Postfix) with ESMTP id 750AB3A6E64
	for <ancp@ietf.org>; Sat,  3 May 2008 12:38:47 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by prattle.redback.com (Postfix) with ESMTP id 330A1269841;
	Sat,  3 May 2008 12:38:49 -0700 (PDT)
Received: from prattle.redback.com ([127.0.0.1])
	by localhost (prattle [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
	id 27078-01; Sat,  3 May 2008 12:38:48 -0700 (PDT)
Received: from rbsjx.ad.redback.com (rbsjxh2.redback.com [155.53.14.106])
	by prattle.redback.com (Postfix) with ESMTP id 3A41A269843;
	Sat,  3 May 2008 12:38:46 -0700 (PDT)
Received: from RBSJX.ad.redback.com ([155.53.14.103]) by
	rbsjxh2.ad.redback.com ([155.53.14.106]) with mapi;
	Sat, 3 May 2008 12:38:46 -0700
From: Peter Arberg <parberg@redback.com>
To: Fortune HUANG <fqhuang@huawei.com>,
	Sanjay Wadhwa <swadhwa@juniper.net>, Tina TSOU <tena@huawei.com>,
	Maglione Roberta <roberta.maglione@telecomitalia.it>,
	"Wojciech Dec (wdec)" <wdec@cisco.com>
Date: Sat, 3 May 2008 12:38:43 -0700
Thread-Topic: [ANCP] question regarding  Labels in ANCP port up messages
Thread-Index: AcitImoguQOwbwDmTgSP9VmHU5AnxgAMaQvQ
Message-ID: <48C276B536524E478C659685995F6AA53B5959219F@RBSJX.ad.redback.com>
References: <48C276B536524E478C659685995F6AA539DBBBE370@RBSJX.ad.redback.com>
	<9BD5D7887235424FA97DFC223CAE3C280AB43A10@proton.jnpr.net>
	<48C276B536524E478C659685995F6AA539DBBBE577@RBSJX.ad.redback.com>
	<9BD5D7887235424FA97DFC223CAE3C28102EB5AA@proton.jnpr.net>
	<48C276B536524E478C659685995F6AA539DBBBEF99@RBSJX.ad.redback.com>
	<002901c8ad1a$0137d3d0$9001a8c0@xxxx87e842e29b>
In-Reply-To: <002901c8ad1a$0137d3d0$9001a8c0@xxxx87e842e29b>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-Virus-Scanned: by amavisd-new at redback.com
Cc: "ancp@ietf.org" <ancp@ietf.org>
Subject: Re: [ANCP] question regarding  Labels in ANCP port up messages
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/pipermail/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>
Content-Type: multipart/mixed; boundary="===============0551845500=="
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org

--===============0551845500==
Content-Language: en-US
Content-Type: multipart/alternative;
	boundary="_000_48C276B536524E478C659685995F6AA53B5959219FRBSJXadredbac_"

--_000_48C276B536524E478C659685995F6AA53B5959219FRBSJXadredbac_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Fortune,

I don't think you get my point, that ANCP was started and implemented in li=
ve
networks before it turned into an ANCP WG draft.

My only point is we have to find a way to make sure these ANCP implementati=
ons
are compatible with new WG ANCP implementations, as it seems pretty stupid =
to
make a standards draft which is in conflict with running code, without spec=
ifying a
way to avoid interoperability problems in networks.

I really don't think there is a matter of right or wrong in this discussion=
, it is a matter
of problems arising when a draft is evolving without people paying attentio=
n to
backwards compatibility.

As a working group it is our responsibility to make sure what we define wil=
l live together
in networks with already implemented versions of the protocol, without caus=
ing major
headaches for carriers using the protocol.

cheers,
Peter



________________________________
From: Fortune HUANG [mailto:fqhuang@huawei.com]
Sent: 3. maj 2008 05:34
To: Peter Arberg; Sanjay Wadhwa; Tina TSOU; Maglione Roberta; Wojciech Dec =
(wdec)
Cc: ancp@ietf.org
Subject: Re: [ANCP] question regarding Labels in ANCP port up messages

Peter,

Since ANCP draft has already based the event-message of RFC3292, I don't th=
ink it appropriate
to define the message bit by bit again.

In some implementations the label space is 4 while in others it is 8.
However, it is obvious that 4 is correct according to the current ANCP draf=
t.
8 is the result that does not obey the ANCP draft strictly because of maybe=
 carelessness in implementation.
I don't know why we need a show of hands, because we can already tell right=
 from wrong through simple analysis.

Furthermore, it is very strange to change the ANCP draft just because some =
implementations implemented it incorrectly.

Best Regards,
Fortune
----- Original Message -----
From: Peter Arberg<mailto:parberg@redback.com>
To: Sanjay Wadhwa<mailto:swadhwa@juniper.net> ; Tina TSOU<mailto:tena@huawe=
i.com> ; Maglione Roberta<mailto:roberta.maglione@telecomitalia.it> ; Wojci=
ech Dec (wdec)<mailto:wdec@cisco.com>
Cc: ancp@ietf.org<mailto:ancp@ietf.org>
Sent: Saturday, May 03, 2008 2:52 AM
Subject: Re: [ANCP] question regarding Labels in ANCP port up messages

Hi Sanjay,

yes apparently I missed your point in the last email, but I'm glad we agree=
 something is needed
to make existing ANCP implementations and the current draft to co-exist.

I do not like your option 1) as if you need a config knob for interoperabil=
ity, it is too easy to
get into trouble.

I think option 2) is the best way forward with the differences already iden=
tified, or we can
continue to get a show of hands of ANCP implementations, and see if anyone =
is actually
deployed based on the WG-draft.

There is no beneficial reasons to base the event-message of RFC3292, it cou=
ld as well be a message
described bit by bit in the ANCP draft, and then we can keep the label spac=
e at 8 as many
implementations alreday do.

cheers,
Peter




________________________________
From: Sanjay Wadhwa [mailto:swadhwa@juniper.net]
Sent: 2. maj 2008 05:35
To: Peter Arberg; Tina TSOU; Maglione Roberta; Wojciech Dec (wdec)
Cc: ancp@ietf.org
Subject: RE: [ANCP] question regarding Labels in ANCP port up messages

Peter
 You missed my point below. The ANCP draft since becoming a WG draft does N=
OT refer to the old GSMP drafts. Any implementations based on this WG-draft=
 are expected to be interoperable. You are pointing to pre-WG-draft version=
s of ANCP, and these were indeed based on expired GSMP drafts that evolved =
past RFC3292.
There is incompatibility between the current ANCP WG-draft and previous non=
-WG versions (TLV clash, label format..). As mentioned earlier it is pruden=
t for older implementations to start supporting the WG-draft version as soo=
n as possible.

For interoperability of WG-draft with the older pre-WG versions, I see the =
following options:

1. Versioning starts with the WG-draft i.e. WG-draft is version =3D 3, sub-=
version =3D 1. For any interop issues between older non-WG versions and the=
 WG-draft, one needs to look at solving it within implementations (e.g. an =
AN that implements the WG-draft, could based on a configuration knob, gener=
ate a PORT-UP message with old label format the will be accepted by BNG imp=
lementing pre-WG versions of the draft).

2. Change the WG-draft (current draft) to use version =3D 3 and sub-version=
 =3D 2. This is assuming there is no deployed implementation of current WG-=
draft that already uses 3.1 as the version, and also assuming the old pre-W=
G implementations use 3.1. There will be no backwards compatibility i.e. ve=
rsion 3.1 BNG will not work with version 3.2 AN (we will need to list this =
as caveat in the appendix section). AN and BNG will need to negotiate the s=
ame version in order for ANCP adjacency to come up. A BNG supporting both v=
ersions 3.1 and 3.2 could simultaneously become adjacent with one AN suppor=
ting 3.1 and another AN supporting 3.2. (i.e. version compatibility is per =
adjacency).
Also, major version number change (e.g. from 3 to 4) should only correspond=
 to a major change in the protocol (e.g. different mechanism, different tra=
nsport etc).

My vote would be to adopt option 2 above only if further changes to WG-draf=
t happen that render it incompatible with the current WG-draft. Any interop=
erability issues with pre-WG versions could be handled via option 1.

Cheers
-Sanjay

________________________________
From: Peter Arberg [mailto:parberg@redback.com]
Sent: Wednesday, April 30, 2008 7:20 PM
To: Sanjay Wadhwa; Tina TSOU; Maglione Roberta; Wojciech Dec (wdec)
Cc: ancp@ietf.org
Subject: RE: [ANCP] question regarding Labels in ANCP port up messages

Sanjay,

What do you mean "why I reference an old draft"  ????????????

I'm surprised you even ask...  please take a look at YOUR own internet-draf=
t that most
of the ANCP working implementations are based on, in case you do not have t=
his old
internet-draft, I have attached it to the document.

If you look at the reference for this ancp-draft, you will see that in the =
reference section
you point to this old gsmp-draft...  Yes and I know this has been changed i=
n the later
versions of the ANCP draft, but that do not change the fact that many of th=
e implementations
today was developed when the attached draft was current.

I think a very good question is brought up here, and that is what is implem=
ented and
running in networks today ?

My take on this is that when the reference was change from the old gsmp-dra=
ft to the older
RFC3292, apparently no one paid any attention to the fact the label definit=
ion in the event
message was different and not compatible.

What current implementations do today is an important factor in this discus=
sion, and I think
it is time to come to realization that we might need a new version number f=
or ANCP since
it continues to look like there is big holes open for interpretation. So if=
 I did a ANCP
implementation there is bound to be interoperability issues with existing i=
mplementations
runnig.

cheers,
Peter




________________________________
From: Sanjay Wadhwa [mailto:swadhwa@juniper.net]
Sent: 30. april 2008 14:42
To: Peter Arberg; Tina TSOU; Maglione Roberta; Wojciech Dec (wdec)
Cc: ancp@ietf.org
Subject: RE: [ANCP] question regarding Labels in ANCP port up messages

Peter
  The ANCP draft as it currently stands is based on RFC3292. It provides ex=
tensions and modifications to relevant constructs in RFC3292. There is no m=
ention (implicit or explicit) of expired GSMP drafts in the ANCP draft. In =
order to implement the ANCP draft, I am not sure why one would look at the =
expired GSMP drafts. Do you see a reason to do this based on anything that =
you read in the ANCP draft? Bringing up reference to expired gsmp draft in =
this thread just adds to the confusion. For GSMPv3 objects in the messages =
(such as Label Type), one has to look at RFC3292 (this is clearly stated in=
 the ANCP draft - section 2 and I am quoting it below) :

ANCP uses a subset of GSMPv3 messages to implement currently defined use-ca=
ses. These relevant GSMPv3 messages are identified in section 5. GSMPv3 pro=
cedures with suitable extensions, as used by ANCP, are described in section=
s 5.1, 5.2 and 5.3. GSMPv3 general extensions and GSMPv3 message specific e=
xtensions required by ANCP are described in sub-sections of 5.4. In additio=
n to specifying extensions and modifications to relevant GSMP messages appl=
icable to ANCP, this draft also defines the usage of these messages by ANCP=
, and indicates the values that ANCP should set for relevant fields in thes=
e GSMP messages. However, to understand the basic semantics of various fiel=
ds in GSMP messages, the reader is referred to [4]. =3D> RFC 3292.

What existing implementations currently do is an important but separate iss=
ue. These implementations for most part precede the current ANCP draft. It =
is fine to poll where these implementations diverge from the current draft.=
 It is then upto the implementations (including the one that I am somewhat =
familiar with) to work towards compliance with the draft.

On the following points from  Woj:

Woj>2) The current version of the spec is not accurate, and does not reflec=
t the fact that the known implementations follow the label field definition=
 from draft-gsmpv3-base-spec.

It is not for the protocol draft to point out what current implementations =
do.  The best we can do is to further clarify in the draft that type and va=
lue fields of the Label object (defined in RFC3292) should be set to 0 in t=
he port-up message (we already mention the lable object as a whole should b=
e set to all 0s).

Woj> This would be a good thing for the WG to discuss. There most evidently=
 is a fair amount of "dead wood" in the current spec, ie stuff that nobody =
yet implements or cares about.  In the former case, we could re-cast that m=
aterial using the new notions/extensions, in the latter case simply chop it=
 out.

I agree. We are based on GSMPv3 (RFC3292)  messages, and obviously not ever=
ything in these messages is leveraged by ANCP.  However, the sync rate and =
OAM uses-cases are implemented and in use (ideally we should leave these al=
one...i.e. no change beyond adding more clarity if needed). For anything ne=
w (such as multicast) we are defining new messages (no legacy).

-Sanjay

>-----Original Message-----
>From: Peter Arberg [mailto:parberg@redback.com]
>Sent: Wednesday, April 30, 2008 3:56 PM
>To: Tina TSOU; Maglione Roberta; Sanjay Wadhwa; Wojciech Dec (wdec)
>Cc: ancp@ietf.org
>Subject: RE: [ANCP] question regarding Labels in ANCP port up messages
>
>
>Hi,
>
>some times I think it is amazing we ever got interoperability
>of ANCP :-)
>because looking at the label discussion is a very good example that the
>whole GSMP - ANCP reference have not worked very well.
>
>In the ANCP draft, section 5.4.2 the event message is shown like this:
>
>0                   1                   2                   3
>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
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>| Vers  |  Sub  | Message Type  | Result|        Code           |
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>| Partition ID  |            Transaction Identifier             |
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>|I|      SubMessage Number      |           Length              |
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>|                             Port                              |
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>|                      Port Session Number                      |
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>|                     Event Sequence Number                     |
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>|x|S|x|x|                                                       |
>+-+-+-+-+                     Label                             |
>~                                                               ~
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>|x|x|x|x|x|x|x|x| Message Type  |   Tech Type   | Block Length  |
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>|                                                               |
>~                         Extension Value                       ~
>|                                                               |
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
>
>This is the exact same event message defined in
>draft-ietf-gsmp-v3-base-spec-08.txt  section 11.
>
>And in this gsmp-draft, section 5.1.3 the label space is defined
>as minimum 8 bytes if the length=3D0 and as such no value, and this
>is because the gsmp-draft has a new "label adaptaion" field.
>
>
>
>BUT in RFC3292 the event message is show in section 9, like this:
>
>0                   1                   2                   3
>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
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>|    Version    | Message Type  |    Result     |     Code      |
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>| Partition ID  |            Transaction Identifier             |
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>|I|      SubMessage Number      |           Length              |
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>|                             Port                              |
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>|                      Port Session Number                      |
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>|                     Event Sequence Number                     |
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>|x|S|x|x|                                                       |
>+-+-+-+-+                     Label                             |
>~                                                               ~
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
>
>So a different Event Message picture/definition than what is shown
>in the ANCP draft, and in RFC3292 section 3.1.3 the label field
>is defined as 4 bytes if length=3D0 and as such no value.
>
>
>
>So I very much agree with Woj that we need this issue to be resolved,
>and proabably a show of hands what is actually done in different
>implementations, so we can nail down how the event message is
>suppose to look like in ANCP.
>
>
>I know at least 1 implementation which uses 8 bytes for the
>label field.
>
>
>cheers,
>Peter
>
>
>
>
>
>
>________________________________
>
>        From: ancp-bounces@ietf.org
>[mailto:ancp-bounces@ietf.org] On Behalf Of Tina TSOU
>        Sent: 30. april 2008 00:19
>        To: Maglione Roberta; Sanjay Wadhwa; Wojciech Dec (wdec)
>        Cc: ancp@ietf.org
>        Subject: Re: [ANCP] question regarding Labels in ANCP
>port up messages
>
>
>        Hi all,
>        It is clear to me that if Label Length is filled as 0,
>there is nothing to be filled into Label Value. The whole
>Label part is 4 bytes, not 8 bytes.
>
>        Cheers from the last working day before Labor's Day
>holidays in some countries:)
>
>        Tina
>
>                ----- Original Message -----
>                From: Wojciech Dec (wdec) <mailto:wdec@cisco.com>
>                To: Sanjay Wadhwa <mailto:swadhwa@juniper.net>
> ; Maglione Roberta <mailto:roberta.maglione@telecomitalia.it>
>                Cc: ancp@ietf.org
>                Sent: Wednesday, April 30, 2008 1:12 AM
>                Subject: Re: [ANCP] question regarding Labels
>in ANCP port up messages
>
>                Sanjay, All,
>
>                What is stated below runs counter to at least
>a handful of ANCP
>                implementations, all of which are known to be
>interoperable.
>                There are really two options:
>                1) The current version of the spec is correct,
>and the known
>                interoperable implementations do not follow it
>                2) The current version of the spec is not
>accurate, and does not reflect
>                the fact that the known implementations follow
>the label field
>                definition from draft-gsmpv3-base-spec.
>
>                I would like to ask you, as the lead editor of
>the spec, to work with
>                the WG in resolving what the problem is, and
>clearing up what the WG
>                spec says about and if 1) holds to be true,
>then proposing an
>                interoperability fix.
>
>                In either case, the issue highlights the fact
>that there is still
>                lingering confusion as to the dependencies
>ANCP has on rfc3292, or
>                draft-gsmpv3-base-spec, or both. It seems to
>be in the best interest of
>                all to address these.
>
>                Regards,
>                Woj.
>
>                > -----Original Message-----
>                > From: Sanjay Wadhwa [mailto:swadhwa@juniper.net]
>                > Sent: 29 April 2008 17:29
>                > To: Maglione Roberta
>                > Cc: Wojciech Dec (wdec); ancp@ietf.org;
>Philippe Champagne (pchamp)
>                > Subject: RE: question regarding Labels in
>ANCP port up messages
>                >
>                > Hi Maglione
>                >   Yes, the label format is as defined in RFC
>3292. The ANCP draft is
>                > based on RFC 3292 and proposes
>extensions/modifications where
>                > required.
>                > This is clearly stated upfront both in the
>abstract and in
>                > section 2. In
>                > section 5.4.2, it clearly  specifies the
>format of "port up" message
>                > (based on RFC 3292), and explicitly states
>the label field
>                > should be set
>                > to 0. Following is what the draft currently states:
>                >
>                >
>                > 5.4.2 Topology Discovery Extensions
>                >
>                > The GSMP Event message with PORT UP message
>type (80) is used for
>                > conveying DSL line attributes to the NAS.
>The version field should be
>                > set to 3, and the sub field should be set to
>1. The I and subMessage
>                > fields SHOULD be set to 1 to signify no
>fragmentation. The Port and
>                > Label fields should be set to 0.
>                >
>                >  0                   1                   2
>                3
>                >          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
>                >
>                >
>                >
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                >         | Vers  |  Sub  | Message Type  |
>Result|        Code
>                > |
>                >
>                >
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                >         | Partition ID  |
>Transaction Identifier
>                > |
>                >
>                >
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                >         |I|      SubMessage Number      |
>       Length
>                > |
>                >
>                >
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                >         |                             Port
>                > |
>                >
>                >
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                >         |                      Port Session Number
>                > |
>                >
>                >
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                >         |                     Event Sequence Number
>                > |
>                >
>                >
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                >         |x|S|x|x|
>                > |
>                >         +-+-+-+-+                     Label
>                > |
>                >         ~
>                > ~
>                >
>                >
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                >         |x|x|x|x|x|x|x|x| Message Type  |
>Tech Type   | Block Length
>                > |
>                >
>                >
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                >         |
>                > |
>                >         ~                         Extension Value
>                > ~
>                >         |
>                > |
>                >
>                >
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                >
>                > When we say the label field should be set to
>0, the intention
>                > is for the
>                > type and length fields in the label TLV to
>be set to 0. We can
>                > explicitly state this for clarity.
>                >
>                > -Sanjay
>                >
>                > >-----Original Message-----
>                > >From: Maglione Roberta
>[mailto:roberta.maglione@telecomitalia.it]
>                > >Sent: Tuesday, April 29, 2008 8:06 AM
>                > >To: Sanjay Wadhwa
>                > >Cc: Wojciech Dec (wdec); ancp@ietf.org;
>pchamp@cisco.com
>                > >Subject: RE: question regarding Labels in
>ANCP port up messages
>                > >
>                > >
>                > >Hi Sanjay and All,
>                > >     I was reading the current ancp
>protocol draft in order to
>                > > understand which should be the correct
>format for the label
>                > >field in the ancp port Up message.
>                > >Actually as it was already pointed out in
>the alias the draft
>                > >in section 5.4.2 says "GSMP Event message
>with PORT UP message
>                > >type (80) is used"  thus I am assuming that
>the label in the
>                > >port UP message should follow the message
>format defined in
>                > >RFC 3292, section 3.1.3:
>                > >
>                > >    0                   1
>2                   3
>                > >    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
>                > >
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                > >   |x|S|x|x|       Label Type      |
>  Label Length         |
>                > >
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                > >   |
>                       |
>                > >   ~                          Label Value
>                       ~
>                > >   |
>                       |
>                > >
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                > >
>                > >but from what I have seen different
>implementations use
>                > >different format for label field: in
>particular several
>                > >implementations use  a label format that is
>similar to the one
>                > >specified in the expired draft
>draft-ietf-gsmp-v3-base-spec:
>                > >
>                > >     0                   1
> 2                   3
>                > >       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
>                > >
>                >
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                > >      |x|S|x|x|x|x|x|x|x|x|x|x|x|x|x|x|
>       Label
>                > Type         |
>                > >
>                >
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                > >      |    Label Adaptation           |
>     Label
>                > Length         |
>                > >
>                >
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                > >      |
>                >          |
>                > >      ~                          Label Value
>                >          ~
>                > >      |
>                >          |
>                > >
>                >
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                > >
>                > >
>                > >Even if ancp does not care about the label
>field, having this
>                > >field somehow not clearly specified in the
>current ancp draft
>                > >can easily lead to interoperability issues,
>thus I think it
>                > >would be very helpful if you and/or the
>other editors can
>                > >clarify what should be the correct format
>for the label field
>                > >to be used in the ancp Port Up message.
>                > >
>                > >Thanks and best regards,
>                > >Roberta
>                > >
>                > >________________________________________
>                > >From: Philippe Champagne (pchamp) [pchamp@cisco.com]
>                > >Sent: Thursday, April 24, 2008 7:14 PM
>                > >To: Sanjay Wadhwa
>                > >Cc: Maglione Roberta; Wojciech Dec (wdec);
>ancp@ietf.org
>                > >Subject: question regarding  Labels in ANCP
>port up messages
>                > >
>                > >Hi Sanjay
>                > >
>                > >In section 5.4.2 of the draft, we have:
>                > >
>                > >
>                > >         0                   1                   2
>                >         3
>                > >         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
>                > >
>                >
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                > >        | Vers  |  Sub  | Message Type  |
>Result|        Code
>                > >         |
>                > >
>                >
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                > >        | Partition ID  |
>Transaction Identifier
>                > >         |
>                > >
>                >
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                > >        |I|      SubMessage Number      |
>        Length
>                > >         |
>                > >
>                >
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                > >        |                             Port
>                > >         |
>                > >
>                >
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                > >        |                      Port Session Number
>                > >         |
>                > >
>                >
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                > >        |                     Event Sequence Number
>                > >         |
>                > >
>                >
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                > >        |x|S|x|x|
>                > >         |
>                > >        +-+-+-+-+                     Label
>                > >         |
>                > >        ~
>                > >         ~
>                > >
>                >
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                > >        |x|x|x|x|x|x|x|x| Message Type  |
>Tech Type   |
>                > >Block Length  |
>                > >
>                >
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                > >        |
>                > >         |
>                > >        ~                         Extension Value
>                > >         ~
>                > >        |
>                > >         |
>                > >
>                >
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                > >Where Label I suppose is taken from the RFC
>3292, section
>                > >3.1.3: (well, I'm guessing)
>                > >
>                > >   A summary of TLV labels supported in
>this version of the
>                > protocol is
>                > >   listed below:
>                > >
>                > >      TLV Label      Type       Section Title
>                > >      ---------      ----       -------------
>                > >      ATM Label      0x100      ATM TLV Labels
>                > >      FR Label       0x101      Frame Relay
>TLV Labels
>                > >      MPLS Gen Label 0x102      MPLS
>Generic TLV Labels
>                > >      FEC Label      0x103      FEC TLV Labels
>                > >
>                > >   All Labels will be designated as follow:
>                > >
>                > >    0                   1
>2                   3
>                > >    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
>                > >
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                > >   |x|S|x|x|       Label Type      |
>  Label Length         |
>                > >
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                > >   |
>                       |
>                > >   ~                          Label Value
>                       ~
>                > >   |
>                       |
>                > >
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>                > >
>                > >      x: Reserved Flags.
>                > >         These are generally used by
>specific messages and will be
>                > >         defined in those messages.
>                > >
>                > >      S: Stacked Label Indicator
>                > >         Label Stacking is discussed below
>in section 3.1.3.5
>                > >
>                > >      Label Type
>                > >         A 12-bit field indicating the type
>of label.
>                > >
>                > >      Label Length
>                > >         A 16-bit field indicating the
>length of the Label
>                > Value field
>                > >         in bytes.
>                > >
>                > >      Label Value
>                > >         A variable length field that is an
>integer number of 32 bit
>                > >         words long.  The Label Value field
>is interpreted
>                > according to
>                > >         the Label Type as described in the
>following sections.
>                > >
>                > >
>                > >The draft is a bit obscure about this and
>since it doesn't
>                > >specify much, it can lead to
>misinterpretation for the unused
>                > >part. Moreover, it would appear that
>several implementations
>                > >currently use another format for the label
>field. Can you
>                > >explain?  I mean, how come what's in the
>current draft doesn't
>                > >match what's known to be implemented?
>                > >
>                > >I'm still wondering why we carried over
>pieces from GSMP that
>                > >we do not intend to use.
>                > >
>                > >I would recommend that if we are to keep
>them but not use
>                > >them, we should mention precisely how we
>intend not to use
>                > >them: that is how many 0 filled bytes this
>is expected to use
>                > >
>                > >The rfc 3292 doesn't cover the case where
>this field is not used.
>                > >
>                > >Can you shed some ligths on this?
>                > >
>                > >Thanks
>                > >Regards
>                > >Phil
>                > >
>                > >
>                > >
>                >
>>--------------------------------------------------------------------
>                > >
>                > >CONFIDENTIALITY NOTICE
>                > >
>                > >This message and its attachments are
>addressed solely to the
>                > >persons above and may contain confidential
>information. If you
>                > >have received the message in error, be
>informed that any use
>                > >of the content hereof is prohibited. Please
>return it
>                > >immediately to the sender and delete the
>message. Should you
>                > >have any questions, please contact us by replying to
>                > >webmaster@telecomitalia.it.
>                > >
>                > >        Thank you
>                > >
>                > >
>www.telecomitalia.it
>                > >
>                >
>>--------------------------------------------------------------------
>                > >
>                > >
>                >
>                _______________________________________________
>                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

--_000_48C276B536524E478C659685995F6AA53B5959219FRBSJXadredbac_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:st1 =3D=20
"urn:schemas-microsoft-com:office:smarttags"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.6000.16640" name=3DGENERATOR><!--[if !mso]>
<STYLE>v\:* {
	BEHAVIOR: url(#default#VML)
}
o\:* {
	BEHAVIOR: url(#default#VML)
}
w\:* {
	BEHAVIOR: url(#default#VML)
}
.shape {
	BEHAVIOR: url(#default#VML)
}
</STYLE>
<![endif]--><o:SmartTagType name=3D"PersonName"=20
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"></o:SmartTagTyp=
e><!--[if !mso]>
<STYLE>st1\:* {
	BEHAVIOR: url(#default#ieooui)
}
</STYLE>
<![endif]-->
<STYLE>@font-face {
	font-family: Tahoma;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: blue; TEXT-DECORATION: underline
}
P {
	FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: "Times =
New Roman"; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto
}
SPAN.EmailStyle18 {
	COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal-reply
}
DIV.Section1 {
	page: Section1
}
</STYLE>
</HEAD>
<BODY lang=3DEN-US vLink=3Dblue link=3Dblue bgColor=3D#cce8cf>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D896502919-03052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Hi Fortune,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D896502919-03052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D896502919-03052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>I don't think you get my point, that ANCP was star=
ted and=20
implemented in live</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D896502919-03052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>networks before it turned into an ANCP WG=20
draft.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D896502919-03052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D896502919-03052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>My only point is we have to find a way to make sur=
e these=20
ANCP implementations</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D896502919-03052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>are compatible with new WG ANCP implementations, a=
s it=20
seems pretty stupid to</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D896502919-03052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>make a standards draft which is in conflict with r=
unning=20
code, without specifying a</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D896502919-03052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>way to avoid interoperability problems in=20
networks.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D896502919-03052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D896502919-03052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>I really don't think there is a matter of right or=
 wrong in=20
this discussion, it is a matter</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D896502919-03052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>of problems arising when a draft is evolving witho=
ut people=20
paying attention to </FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D896502919-03052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>backwards compatibility.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D896502919-03052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D896502919-03052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>As a working group it is our responsibility to mak=
e sure=20
what we define will live together</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D896502919-03052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>in networks with already implemented versions of t=
he=20
protocol, without causing major </FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D896502919-03052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>headaches for carriers using the=20
protocol.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D896502919-03052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D896502919-03052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>cheers,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D896502919-03052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Peter</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D896502919-03052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D896502919-03052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px soli=
d; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Fortune HUANG=20
  [mailto:fqhuang@huawei.com] <BR><B>Sent:</B> 3. maj 2008 05:34<BR><B>To:<=
/B>=20
  Peter Arberg; Sanjay Wadhwa; Tina TSOU; Maglione Roberta; Wojciech Dec=20
  (wdec)<BR><B>Cc:</B> ancp@ietf.org<BR><B>Subject:</B> Re: [ANCP] question=
=20
  regarding Labels in ANCP port up messages<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV><FONT face=3D&#23435;&#20307; size=3D2>
  <DIV><FONT face=3D&#23435;&#20307; size=3D2>Peter,</FONT></DIV>
  <DIV><FONT face=3D&#23435;&#20307; size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3D&#23435;&#20307; size=3D2>Since ANCP draft&nbsp;has alr=
eady based the=20
  event-message of RFC3292, I don't think it appropriate </FONT></DIV>
  <DIV><FONT face=3D&#23435;&#20307; size=3D2>to define the message bit by =
bit again.</FONT></DIV>
  <DIV><FONT face=3D&#23435;&#20307; size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3D&#23435;&#20307; size=3D2>In some implementations the l=
abel space is 4 while=20
  in others it is 8. </FONT></DIV>
  <DIV><FONT face=3D&#23435;&#20307; size=3D2>However, it is obvious that 4=
 is correct according=20
  to the current ANCP draft. </FONT></DIV>
  <DIV><FONT face=3D&#23435;&#20307; size=3D2>8 is the result that does not=
 obey the ANCP draft=20
  strictly because of maybe carelessness in implementation.</FONT></DIV>
  <DIV><FONT face=3D&#23435;&#20307; size=3D2>I don't know why we need a sh=
ow of hands, because we=20
  can already tell right from wrong through simple analysis.</FONT></DIV>
  <DIV><FONT face=3D&#23435;&#20307; size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3D&#23435;&#20307; size=3D2>Furthermore, it is very stran=
ge to change the ANCP=20
  draft </FONT><FONT face=3D&#23435;&#20307; size=3D2>just </FONT><FONT fac=
e=3D&#23435;&#20307; size=3D2>because=20
  some implementations implemented it incorrectly.</FONT></DIV>
  <DIV><FONT face=3D&#23435;&#20307; size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT face=3D&#23435;&#20307; size=3D2>Best=20
  Regards,<BR>Fortune<BR></FONT></DIV></FONT></DIV>
  <BLOCKQUOTE=20
  style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-=
LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
    <DIV style=3D"FONT: 9pt &#23435;&#20307;">----- Original Message ----- =
</DIV>
    <DIV=20
    style=3D"BACKGROUND: #e4e4e4; FONT: 9pt &#23435;&#20307;; font-color: b=
lack"><B>From:</B> <A=20
    title=3Dparberg@redback.com href=3D"mailto:parberg@redback.com">Peter A=
rberg</A>=20
    </DIV>
    <DIV style=3D"FONT: 9pt &#23435;&#20307;"><B>To:</B> <A title=3Dswadhwa=
@juniper.net=20
    href=3D"mailto:swadhwa@juniper.net">Sanjay Wadhwa</A> ; <A=20
    title=3Dtena@huawei.com href=3D"mailto:tena@huawei.com">Tina TSOU</A> ;=
 <A=20
    title=3Droberta.maglione@telecomitalia.it=20
    href=3D"mailto:roberta.maglione@telecomitalia.it">Maglione Roberta</A> =
; <A=20
    title=3Dwdec@cisco.com href=3D"mailto:wdec@cisco.com">Wojciech Dec (wde=
c)</A>=20
    </DIV>
    <DIV style=3D"FONT: 9pt &#23435;&#20307;"><B>Cc:</B> <A title=3Dancp@ie=
tf.org=20
    href=3D"mailto:ancp@ietf.org">ancp@ietf.org</A> </DIV>
    <DIV style=3D"FONT: 9pt &#23435;&#20307;"><B>Sent:</B> Saturday, May 03=
, 2008 2:52 AM</DIV>
    <DIV style=3D"FONT: 9pt &#23435;&#20307;"><B>Subject:</B> Re: [ANCP] qu=
estion regarding=20
    Labels in ANCP port up messages</DIV>
    <DIV><BR></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT face=
=3DArial=20
    color=3D#0000ff size=3D2>Hi Sanjay,</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT face=
=3DArial=20
    color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT face=
=3DArial=20
    color=3D#0000ff size=3D2>yes apparently I missed your point in the last=
 email,=20
    but I'm glad we agree something is needed</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT face=
=3DArial=20
    color=3D#0000ff size=3D2>to make existing ANCP implementations and the =
current=20
    draft to co-exist.</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT face=
=3DArial=20
    color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT face=
=3DArial=20
    color=3D#0000ff size=3D2>I do not like your option 1) as if you need a =
config=20
    knob for interoperability, it is too easy to</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT face=
=3DArial=20
    color=3D#0000ff size=3D2>get into trouble.</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT face=
=3DArial=20
    color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT face=
=3DArial=20
    color=3D#0000ff size=3D2>I think option 2) is the best way forward with=
 the=20
    differences already identified, or we can </FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT face=
=3DArial=20
    color=3D#0000ff size=3D2>continue to get a show of hands of ANCP=20
    implementations, and see if anyone is actually</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT face=
=3DArial=20
    color=3D#0000ff size=3D2>deployed based on the WG-draft.</FONT></SPAN><=
/DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT face=
=3DArial=20
    color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT face=
=3DArial=20
    color=3D#0000ff size=3D2>There is no beneficial reasons to base the=20
    event-message of RFC3292, it could as well be a message</FONT></SPAN></=
DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT face=
=3DArial=20
    color=3D#0000ff size=3D2>described bit by bit in the ANCP draft, and th=
en we can=20
    keep the label space at 8 as many</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT face=
=3DArial=20
    color=3D#0000ff size=3D2>implementations alreday do.</FONT></SPAN></DIV=
>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT face=
=3DArial=20
    color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT face=
=3DArial=20
    color=3D#0000ff size=3D2>cheers,</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT face=
=3DArial=20
    color=3D#0000ff size=3D2>Peter</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT face=
=3DArial=20
    color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT face=
=3DArial=20
    color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT face=
=3DArial=20
    color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV><BR>
    <BLOCKQUOTE dir=3Dltr=20
    style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
      <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft=
>
      <HR tabIndex=3D-1>
      <FONT face=3DTahoma size=3D2><B>From:</B> Sanjay Wadhwa=20
      [mailto:swadhwa@juniper.net] <BR><B>Sent:</B> 2. maj 2008=20
      05:35<BR><B>To:</B> Peter Arberg; Tina TSOU; Maglione Roberta; Wojcie=
ch=20
      Dec (wdec)<BR><B>Cc:</B> ancp@ietf.org<BR><B>Subject:</B> RE: [ANCP]=
=20
      question regarding Labels in ANCP port up messages<BR></FONT><BR></DI=
V>
      <DIV></DIV>
      <DIV class=3DSection1>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Peter<o:p>=
</o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">&nbsp;You=
=20
      mis<st1:PersonName w:st=3D"on">se</st1:PersonName>d my point below. T=
he ANCP=20
      draft since becoming a WG draft does NOT refer to the old GSMP drafts=
. Any=20
      implementations ba<st1:PersonName w:st=3D"on">se</st1:PersonName>d on=
 this=20
      WG-draft are expected to be interoperable. You are pointing to=20
      pre-WG-draft versions of ANCP, and the<st1:PersonName=20
      w:st=3D"on">se</st1:PersonName> were indeed ba<st1:PersonName=20
      w:st=3D"on">se</st1:PersonName>d on expired GSMP drafts that evolved =
past=20
      RFC3292. <o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">There is=20
      incompatibility between the current ANCP WG-draft and previous non-WG=
=20
      versions (TLV clash, label format..). As mentioned earlier it is prud=
ent=20
      for older implementations to start supporting the WG-draft version as=
 soon=20
      as possible. <o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p>&nbsp=
;</o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">For=20
      interoperability of WG-draft with the older pre-WG versions, I=20
      <st1:PersonName w:st=3D"on">se</st1:PersonName>e the following=20
      options:<o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p>&nbsp=
;</o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">1. Version=
ing=20
      starts with the WG-draft i.e. WG-draft is version =3D 3, sub-version =
=3D 1.=20
      For any interop issues between older non-WG versions and the WG-draft=
, one=20
      needs to look at solving it within implementations (e.g. an AN that=20
      implements the WG-draft, could ba<st1:PersonName=20
      w:st=3D"on">se</st1:PersonName>d on a configuration knob, generate a =
PORT-UP=20
      message with old label format the will be accepted by BNG implementin=
g=20
      pre-WG versions of the draft). <o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p>&nbsp=
;</o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">2. Change =
the=20
      WG-draft (current draft) to u<st1:PersonName w:st=3D"on">se</st1:Pers=
onName>=20
      version =3D 3 and sub-version =3D 2. This is assuming there is no dep=
loyed=20
      implementation of current WG-draft that already u<st1:PersonName=20
      w:st=3D"on">se</st1:PersonName>s 3.1 as the version, and also assumin=
g the=20
      old pre-WG implementations u<st1:PersonName w:st=3D"on">se</st1:Perso=
nName>=20
      3.1. There will be no backwards compatibility i.e. version 3.1 BNG wi=
ll=20
      not work with version 3.2 AN (we will need to list this as caveat in =
the=20
      appendix <st1:PersonName w:st=3D"on">se</st1:PersonName>ction). AN an=
d BNG=20
      will need to negotiate the same version in order for ANCP adjacency t=
o=20
      come up. A BNG supporting both versions 3.1 and 3.2 could simultaneou=
sly=20
      become adjacent with one AN supporting 3.1 and another AN supporting =
3.2.=20
      (i.e. version compatibility is per=20
adjacency).<o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Also, majo=
r=20
      version number change (e.g. from 3 to 4) should only correspond to a =
major=20
      change in the protocol (e.g. different mechanism, different transport=
=20
      etc).<o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p>&nbsp=
;</o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">My vote wo=
uld be=20
      to adopt option 2 above only if further changes to WG-draft happen th=
at=20
      render it incompatible with the current WG-draft. Any interoperabilit=
y=20
      issues with pre-WG versions could be handled via option=20
      1.<o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p>&nbsp=
;</o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Cheers<o:p=
></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">-Sanjay<o:=
p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p>&nbsp=
;</o:p></SPAN></FONT></P>
      <DIV>
      <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" align=3Dcenter><F=
ONT=20
      face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
      <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
      </SPAN></FONT></DIV>
      <P class=3DMsoNormal><B><FONT face=3DTahoma size=3D2><SPAN=20
      style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">Fro=
m:</SPAN></FONT></B><FONT=20
      face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: T=
ahoma">=20
      Peter Arberg [mailto:parberg@redback.com] <BR><B><SPAN=20
      style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Wednesday, April 30, 200=
8 7:20=20
      PM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Sanjay Wadh=
wa;=20
      Tina TSOU; Maglione Roberta; Wojciech Dec (wdec)<BR><B><SPAN=20
      style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B> ancp@ietf.org<BR><B><SPAN=
=20
      style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [ANCP] question=20
      regarding Labels in ANCP port up=20
      messages</SPAN></FONT><o:p></o:p></P></DIV>
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
      style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">Sanjay,</S=
PAN></FONT><o:p></o:p></P>
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
      style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">What do yo=
u mean=20
      "why I reference an old draft"&nbsp;=20
      ????????????</SPAN></FONT><o:p></o:p></P>
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
      style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">I'm=20
      surpri<st1:PersonName w:st=3D"on">se</st1:PersonName>d you even ask..=
.&nbsp;=20
      plea<st1:PersonName w:st=3D"on">se</st1:PersonName> take a look at YO=
UR own=20
      internet-draft that most</SPAN></FONT><o:p></o:p></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">of the ANC=
P=20
      working implementations are ba<st1:PersonName=20
      w:st=3D"on">se</st1:PersonName>d on, in ca<st1:PersonName=20
      w:st=3D"on">se</st1:PersonName> you do not have this=20
      old</SPAN></FONT><o:p></o:p></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">internet-d=
raft, I=20
      have attached it to the document.</SPAN></FONT><o:p></o:p></P>
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
      style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">If you loo=
k at=20
      the reference for this ancp-draft, you will <st1:PersonName=20
      w:st=3D"on">se</st1:PersonName>e that in the reference <st1:PersonNam=
e=20
      w:st=3D"on">se</st1:PersonName>ction</SPAN></FONT><o:p></o:p></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">you point =
to this=20
      old gsmp-draft...&nbsp; Yes and I know this has been changed in the=20
      later</SPAN></FONT><o:p></o:p></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">versions o=
f the=20
      ANCP draft, but that do not change the fact that many of the=20
      implementations</SPAN></FONT><o:p></o:p></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">today was=
=20
      developed when the attached draft was=20
current.</SPAN></FONT><o:p></o:p></P>
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
      style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">I think a =
very=20
      good question is brought up here, and that is what is implemented=20
      and</SPAN></FONT><o:p></o:p></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">running in=
=20
      networks today ?</SPAN></FONT><o:p></o:p></P>
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
      style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">My take on=
 this=20
      is that when the reference was change from the old gsmp-draft to the=
=20
      older</SPAN></FONT><o:p></o:p></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">RFC3292,=20
      apparently no one paid any attention to the fact the label definition=
 in=20
      the event</SPAN></FONT><o:p></o:p></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">message wa=
s=20
      different and not compatible.</SPAN></FONT><o:p></o:p></P>
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
      style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">What curre=
nt=20
      implementations do today is an important factor in this discussion, a=
nd I=20
      think</SPAN></FONT><o:p></o:p></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">it is time=
 to=20
      come to realization that we might need a new version number for ANCP=
=20
      since</SPAN></FONT><o:p></o:p></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">it continu=
es to=20
      look like there is big holes open for interpretation. So if I did a=20
      ANCP</SPAN></FONT><o:p></o:p></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">implementa=
tion=20
      there is bound to be interoperability issues with existing=20
      implementations</SPAN></FONT><o:p></o:p></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">runnig.</S=
PAN></FONT><o:p></o:p></P>
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
      style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">cheers,</S=
PAN></FONT><o:p></o:p></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">Peter</SPA=
N></FONT><o:p></o:p></P>
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
      style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
      style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
      style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
      <BLOCKQUOTE=20
      style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: m=
edium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: 5pt 0in 5pt 3.7=
5pt; BORDER-LEFT: blue 1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: medium=
 none">
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=
=20
        style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
        <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" align=3Dcenter>=
<FONT=20
        face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
        <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
        </SPAN></FONT></DIV>
        <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><B><FONT face=3D=
Tahoma=20
        size=3D2><SPAN=20
        style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">F=
rom:</SPAN></FONT></B><FONT=20
        face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY:=
 Tahoma">=20
        Sanjay Wadhwa [mailto:swadhwa@juniper.net] <BR><B><SPAN=20
        style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> 30. april 2008=20
        14:42<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Peter =
Arberg;=20
        Tina TSOU; Maglione Roberta; Wojciech Dec (wdec)<BR><B><SPAN=20
        style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B> ancp@ietf.org<BR><B><SPA=
N=20
        style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [ANCP] question=
=20
        regarding Labels in ANCP port up messages</SPAN></FONT><o:p></o:p><=
/P>
        <P><FONT face=3D"Times New Roman" size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt">Peter<BR>&nbsp; The ANCP draft as it curr=
ently=20
        stands is ba<st1:PersonName w:st=3D"on">se</st1:PersonName>d on RFC=
3292.=20
        It provides extensions and modifications to relevant constructs in=
=20
        RFC3292. There is no mention (implicit or explicit) of expired GSMP=
=20
        drafts in the ANCP draft. In order to implement the ANCP draft, I a=
m not=20
        sure why one would look at the expired GSMP drafts. Do you=20
        <st1:PersonName w:st=3D"on">se</st1:PersonName>e a reason to do thi=
s=20
        ba<st1:PersonName w:st=3D"on">se</st1:PersonName>d on anything that=
 you=20
        read in the ANCP draft? Bringing up reference to expired gsmp draft=
 in=20
        this thread&nbsp;just adds to the confusion. For GSMPv3 objects in =
the=20
        messages (such as Label Type), one has to look at RFC3292 (this is=
=20
        clearly stated in the ANCP draft - <st1:PersonName=20
        w:st=3D"on">se</st1:PersonName>ction 2 and I am quoting it below)=20
        :</SPAN></FONT><o:p></o:p></P>
        <P><FONT face=3D"Times New Roman" color=3Dblue size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: blue">ANCP u<st1:PersonName=20
        w:st=3D"on">se</st1:PersonName>s a sub<st1:PersonName=20
        w:st=3D"on">se</st1:PersonName>t of GSMPv3 messages to implement cu=
rrently=20
        defined u<st1:PersonName w:st=3D"on">se</st1:PersonName>-ca<st1:Per=
sonName=20
        w:st=3D"on">se</st1:PersonName>s. The<st1:PersonName=20
        w:st=3D"on">se</st1:PersonName> relevant GSMPv3 messages are identi=
fied in=20
        <st1:PersonName w:st=3D"on">se</st1:PersonName>ction 5. GSMPv3 proc=
edures=20
        with suitable extensions, as u<st1:PersonName=20
        w:st=3D"on">se</st1:PersonName>d by ANCP, are described in <st1:Per=
sonName=20
        w:st=3D"on">se</st1:PersonName>ctions 5.1, 5.2 and 5.3. GSMPv3 gene=
ral=20
        extensions and GSMPv3 message specific extensions required by ANCP =
are=20
        described in sub-<st1:PersonName w:st=3D"on">se</st1:PersonName>cti=
ons of=20
        5.4. In addition to specifying extensions and modifications to rele=
vant=20
        GSMP messages applicable to ANCP, this draft also defines the usage=
 of=20
        the<st1:PersonName w:st=3D"on">se</st1:PersonName> messages by ANCP=
, and=20
        indicates the values that ANCP should <st1:PersonName=20
        w:st=3D"on">se</st1:PersonName>t for relevant fields in the<st1:Per=
sonName=20
        w:st=3D"on">se</st1:PersonName> GSMP messages. However, to understa=
nd the=20
        basic <st1:PersonName w:st=3D"on">se</st1:PersonName>mantics of var=
ious=20
        fields in GSMP messages, the reader is referred to [4].&nbsp;=3D&gt=
; RFC=20
        3292.</SPAN></FONT><FONT size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt"><BR><BR>What existing implementations cur=
rently=20
        do is an important but <st1:PersonName=20
        w:st=3D"on">se</st1:PersonName>parate issue. The<st1:PersonName=20
        w:st=3D"on">se</st1:PersonName> implementations for most part prece=
de the=20
        current ANCP draft. It is fine to poll where the<st1:PersonName=20
        w:st=3D"on">se</st1:PersonName> implementations diverge from the cu=
rrent=20
        draft. It is then upto the implementations (including the one that =
I am=20
        somewhat familiar with) to work towards compliance with the draft.=
=20
        </SPAN></FONT><o:p></o:p></P>
        <P><FONT face=3D"Times New Roman" size=3D2><SPAN style=3D"FONT-SIZE=
: 10pt">On=20
        the following points&nbsp;from &nbsp;Woj:</SPAN></FONT><o:p></o:p><=
/P>
        <P><FONT face=3D"Times New Roman" size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt">Woj&gt;2) The current version of the spec=
 is not=20
        accurate, and does not reflect&nbsp;the fact that the known=20
        implementations follow the label field definition from=20
        draft-gsmpv3-ba<st1:PersonName=20
        w:st=3D"on">se</st1:PersonName>-spec.</SPAN></FONT><o:p></o:p></P>
        <P><FONT face=3D"Times New Roman" size=3D2><SPAN style=3D"FONT-SIZE=
: 10pt">It=20
        is not for the protocol draft to point out what current implementat=
ions=20
        do.&nbsp;&nbsp;The best we can do is to further clarify in the draf=
t=20
        that type and value fields of the Label object (defined in RFC3292)=
=20
        should be <st1:PersonName w:st=3D"on">se</st1:PersonName>t to 0 in =
the=20
        port-up message (we already&nbsp;mention the lable object as a whol=
e=20
        should be <st1:PersonName w:st=3D"on">se</st1:PersonName>t to all 0=
s).=20
        </SPAN></FONT><o:p></o:p></P>
        <P><FONT face=3D"Times New Roman" size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt">Woj&gt; This would be a good thing for th=
e WG to=20
        discuss. There most evidently is a fair amount of&nbsp;"dead wood" =
in=20
        the current spec, ie stuff that nobody yet&nbsp;implements or cares=
=20
        about. &nbsp;In the former ca<st1:PersonName=20
        w:st=3D"on">se</st1:PersonName>, we could re-cast that material usi=
ng the=20
        new notions/extensions, in the latter ca<st1:PersonName=20
        w:st=3D"on">se</st1:PersonName> simply chop it=20
        out.</SPAN></FONT><o:p></o:p></P>
        <P><FONT face=3D"Times New Roman" size=3D2><SPAN style=3D"FONT-SIZE=
: 10pt">I=20
        agree. We are ba<st1:PersonName w:st=3D"on">se</st1:PersonName>d on=
 GSMPv3=20
        (RFC3292) &nbsp;messages, and obviously not everything in=20
        the<st1:PersonName w:st=3D"on">se</st1:PersonName> messages is leve=
raged=20
        by ANCP.&nbsp; However, the sync rate and OAM u<st1:PersonName=20
        w:st=3D"on">se</st1:PersonName>s-ca<st1:PersonName=20
        w:st=3D"on">se</st1:PersonName>s are implemented and in u<st1:Perso=
nName=20
        w:st=3D"on">se</st1:PersonName> (ideally we should leave=20
        the<st1:PersonName w:st=3D"on">se</st1:PersonName> alone...i.e. no =
change=20
        beyond adding more clarity if needed). For anything new (such as=20
        multicast) we are defining new messages&nbsp;(no legacy).&nbsp;=20
        </SPAN></FONT><o:p></o:p></P>
        <P><FONT face=3D"Times New Roman" size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt">-Sanjay<BR><BR>&gt;-----Original=20
        Message-----<BR>&gt;From: Peter Arberg [</SPAN></FONT><A=20
        href=3D"mailto:parberg@redback.com"><FONT size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt">mailto:parberg@redback.com</SPAN></FONT><=
/A><FONT=20
        size=3D2><SPAN style=3D"FONT-SIZE: 10pt">]<BR>&gt;Sent: Wednesday, =
April 30,=20
        2008 3:56 PM<BR>&gt;To: Tina TSOU; Maglione Roberta; Sanjay Wadhwa;=
=20
        Wojciech Dec (wdec)<BR>&gt;Cc: ancp@ietf.org<BR>&gt;Subject: RE: [A=
NCP]=20
        question regarding Labels in ANCP port up=20
        messages<BR>&gt;<BR>&gt;<BR>&gt;Hi,<BR>&gt;<BR>&gt;some times I thi=
nk it=20
        is amazing we ever got interoperability<BR>&gt;of ANCP=20
        :-)<BR>&gt;becau<st1:PersonName w:st=3D"on">se</st1:PersonName> loo=
king at=20
        the label discussion is a very good example that the<BR>&gt;whole G=
SMP -=20
        ANCP reference have not worked very well.<BR>&gt;<BR>&gt;In the ANC=
P=20
        draft, <st1:PersonName w:st=3D"on">se</st1:PersonName>ction 5.4.2 t=
he=20
        event message is shown like=20
        this:<BR>&gt;<BR>&gt;0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        3<BR>&gt;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=20
        1<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+-+<BR>&gt;|=20
        Vers&nbsp; |&nbsp; Sub&nbsp; | Message Type&nbsp; |=20
        Result|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        Code&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        |<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+-+<BR>&gt;|=20
        Partition ID&nbsp;=20
        |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
=20
        Transaction=20
        Identifier&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;=20
        |<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+-+<BR>&gt;|I|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        SubMessage Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;=20
        |<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+-+<BR>&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        Port&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        |<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+-+<BR>&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        Port Session=20
        Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        |<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+-+<BR>&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        Event Sequence=20
        Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        |<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+-+<BR>&gt;|x|S|x|x|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        |<BR>&gt;+-+-+-+-+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        Label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        |<BR>&gt;~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;=20
        ~<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+-+<BR>&gt;|x|x|x|x|x|x|x|x|=20
        Message Type&nbsp; |&nbsp;&nbsp; Tech Type&nbsp;&nbsp; | Block=20
        Length&nbsp;=20
        |<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+-+<BR>&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;=20
        |<BR>&gt;~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;=20
        Extension=20
        Value&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        ~<BR>&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;=20
        |<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+-+<BR>&gt;<BR>&gt;<BR>&gt;This=20
        is the exact same event message defined=20
        in<BR>&gt;draft-ietf-gsmp-v3-ba<st1:PersonName=20
        w:st=3D"on">se</st1:PersonName>-spec-08.txt&nbsp; <st1:PersonName=20
        w:st=3D"on">se</st1:PersonName>ction 11.<BR>&gt;<BR>&gt;And in this=
=20
        gsmp-draft, <st1:PersonName w:st=3D"on">se</st1:PersonName>ction 5.=
1.3 the=20
        label space is defined<BR>&gt;as minimum 8 bytes if the length=3D0 =
and as=20
        such no value, and this<BR>&gt;is becau<st1:PersonName=20
        w:st=3D"on">se</st1:PersonName> the gsmp-draft has a new "label ada=
ptaion"=20
        field.<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt;BUT in RFC3292 the event mess=
age=20
        is show in <st1:PersonName w:st=3D"on">se</st1:PersonName>ction 9, =
like=20
        this:<BR>&gt;<BR>&gt;0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        3<BR>&gt;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=20
        1<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+-+<BR>&gt;|&nbsp;&nbsp;&nbsp;=20
        Version&nbsp;&nbsp;&nbsp; | Message Type&nbsp; |&nbsp;&nbsp;&nbsp;=
=20
        Result&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;=20
        Code&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        |<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+-+<BR>&gt;|=20
        Partition ID&nbsp;=20
        |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
=20
        Transaction=20
        Identifier&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;=20
        |<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+-+<BR>&gt;|I|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        SubMessage Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;=20
        |<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+-+<BR>&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        Port&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        |<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+-+<BR>&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        Port Session=20
        Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        |<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+-+<BR>&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        Event Sequence=20
        Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        |<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+-+<BR>&gt;|x|S|x|x|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        |<BR>&gt;+-+-+-+-+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        Label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        |<BR>&gt;~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;=20
        ~<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+-+-+-+<BR>&gt;<BR>&gt;<BR>&gt;So=20
        a different Event Message picture/definition than what is=20
        shown<BR>&gt;in the ANCP draft, and in RFC3292 <st1:PersonName=20
        w:st=3D"on">se</st1:PersonName>ction 3.1.3 the label field<BR>&gt;i=
s=20
        defined as 4 bytes if length=3D0 and as such no=20
        value.<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt;So I very much agree with Woj=
 that=20
        we need this issue to be resolved,<BR>&gt;and proabably a show of h=
ands=20
        what is actually done in different<BR>&gt;implementations, so we ca=
n=20
        nail down how the event message is<BR>&gt;suppo<st1:PersonName=20
        w:st=3D"on">se</st1:PersonName> to look like in=20
        ANCP.<BR>&gt;<BR>&gt;<BR>&gt;I know at least 1 implementation which=
=20
        u<st1:PersonName w:st=3D"on">se</st1:PersonName>s 8 bytes for=20
        the<BR>&gt;label=20
        field.<BR>&gt;<BR>&gt;<BR>&gt;cheers,<BR>&gt;Peter<BR>&gt;<BR>&gt;<=
BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt;________________________________<BR>=
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        From: ancp-bounces@ietf.org<BR>&gt;[</SPAN></FONT><A=20
        href=3D"mailto:ancp-bounces@ietf.org"><FONT size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt">mailto:ancp-bounces@ietf.org</SPAN></FONT=
></A><FONT=20
        size=3D2><SPAN style=3D"FONT-SIZE: 10pt">] On Behalf Of Tina=20
        TSOU<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Sent: 30. ap=
ril=20
        2008 00:19<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; To:=20
        Maglione Roberta; Sanjay Wadhwa; Wojciech Dec=20
        (wdec)<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Cc:=20
        ancp@ietf.org<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Sub=
ject:=20
        Re: [ANCP] question regarding Labels in ANCP<BR>&gt;port up=20
        messages<BR>&gt;<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;=20
        Hi all,<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; It is cle=
ar to=20
        me that if Label Length is filled as 0,<BR>&gt;there is nothing to =
be=20
        filled into Label Value. The whole<BR>&gt;Label part is 4 bytes, no=
t 8=20
        bytes.<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Ch=
eers=20
        from the last working day before Labor's Day<BR>&gt;holidays in som=
e=20
        countries:)<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;=20
        Tina<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        ----- Original Message=20
        -----<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        From: Wojciech Dec (wdec) &lt;</SPAN></FONT><A=20
        href=3D"mailto:wdec@cisco.com"><FONT size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt">mailto:wdec@cisco.com</SPAN></FONT></A><F=
ONT=20
        size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt">&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        To: Sanjay Wadhwa &lt;</SPAN></FONT><A=20
        href=3D"mailto:swadhwa@juniper.net"><FONT size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt">mailto:swadhwa@juniper.net</SPAN></FONT><=
/A><FONT=20
        size=3D2><SPAN style=3D"FONT-SIZE: 10pt">&gt;<BR>&gt; ; Maglione Ro=
berta=20
        &lt;</SPAN></FONT><A=20
        href=3D"mailto:roberta.maglione@telecomitalia.it"><FONT size=3D2><S=
PAN=20
        style=3D"FONT-SIZE: 10pt">mailto:roberta.maglione@telecomitalia.it<=
/SPAN></FONT></A><FONT=20
        size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt">&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        Cc:=20
        ancp@ietf.org<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        Sent: Wednesday, April 30, 2008 1:12=20
        AM<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        Subject: Re: [ANCP] question regarding Labels<BR>&gt;in ANCP port u=
p=20
        messages<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        Sanjay,=20
        All,<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        What is stated below runs counter to at least<BR>&gt;a handful of=20
        ANCP<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        implementations, all of which are known to=20
        be<BR>&gt;interoperable.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        There are really two=20
        options:<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        1) The current version of the spec is correct,<BR>&gt;and the=20
        known<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        interoperable implementations do not follow=20
        it<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        2) The current version of the spec is not<BR>&gt;accurate, and does=
 not=20
        reflect<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        the fact that the known implementations follow<BR>&gt;the label=20
        field<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        definition from draft-gsmpv3-ba<st1:PersonName=20
        w:st=3D"on">se</st1:PersonName>-spec.<BR>&gt;<BR>&gt;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;=20
        I would like to ask you, as the lead editor of<BR>&gt;the spec, to =
work=20
        with<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        the WG in resolving what the problem is, and<BR>&gt;clearing up wha=
t the=20
        WG<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        spec says about and if 1) holds to be true,<BR>&gt;then proposing=20
        an<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        interoperability=20
        fix.<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        In either ca<st1:PersonName w:st=3D"on">se</st1:PersonName>, the is=
sue=20
        highlights the fact<BR>&gt;that there is=20
        still<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        lingering confusion as to the dependencies<BR>&gt;ANCP has on rfc32=
92,=20
        or<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        draft-gsmpv3-ba<st1:PersonName w:st=3D"on">se</st1:PersonName>-spec=
, or=20
        both. It <st1:PersonName w:st=3D"on">se</st1:PersonName>ems to<BR>&=
gt;be=20
        in the best interest=20
        of<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        all to address the<st1:PersonName=20
        w:st=3D"on">se</st1:PersonName>.<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        Regards,<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        Woj.<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; -----Original=20
        Message-----<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; From: Sanjay Wadhwa [</SPAN></FONT><A=20
        href=3D"mailto:swadhwa@juniper.net"><FONT size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt">mailto:swadhwa@juniper.net</SPAN></FONT><=
/A><FONT=20
        size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt">]<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; Sent: 29 April 2008=20
        17:29<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; To: Maglione=20
        Roberta<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; Cc: Wojciech Dec (wdec); ancp@ietf.org;<BR>&gt;Philippe Champa=
gne=20
        (pchamp)<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; Subject: RE: question regarding Labels in<BR>&gt;ANCP port up=
=20
        messages<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; Hi=20
        Maglione<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;&nbsp;&nbsp; Yes, the label format is as defined in RFC<BR>&gt;=
3292.=20
        The ANCP draft=20
        is<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; ba<st1:PersonName w:st=3D"on">se</st1:PersonName>d on RFC 3292=
 and=20
        propo<st1:PersonName=20
        w:st=3D"on">se</st1:PersonName>s<BR>&gt;extensions/modifications=20
        where<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        required.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; This is clearly stated upfront both in the<BR>&gt;abstract and=
=20
        in<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; <st1:PersonName w:st=3D"on">se</st1:PersonName>ction 2.=20
        In<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; <st1:PersonName w:st=3D"on">se</st1:PersonName>ction 5.4.2, it=
=20
        clearly&nbsp; specifies the<BR>&gt;format of "port up"=20
        message<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; (ba<st1:PersonName w:st=3D"on">se</st1:PersonName>d on RFC 329=
2), and=20
        explicitly states<BR>&gt;the label=20
        field<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; should be <st1:PersonName=20
        w:st=3D"on">se</st1:PersonName>t<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; to 0. Following is what the draft currently=20
        states:<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; 5.4.2 Topology Discovery=20
        Extensions<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; The GSMP Event message with PORT UP message<BR>&gt;type (80) i=
s=20
        u<st1:PersonName w:st=3D"on">se</st1:PersonName>d=20
        for<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; conveying DSL line attributes to the NAS.<BR>&gt;The version f=
ield=20
        should=20
        be<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; <st1:PersonName w:st=3D"on">se</st1:PersonName>t to 3, and the=
 sub=20
        field should be <st1:PersonName w:st=3D"on">se</st1:PersonName>t=20
        to<BR>&gt;1. The I and=20
        subMessage<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; fields SHOULD be <st1:PersonName w:st=3D"on">se</st1:PersonNam=
e>t to=20
        1 to signify no<BR>&gt;fragmentation. The Port=20
        and<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; Label fields should be <st1:PersonName=20
        w:st=3D"on">se</st1:PersonName>t to=20
        0.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;&nbsp;=20
        0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        2&nbsp;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        3<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0 1 2 3 =
4 5 6=20
        7 8 9 0 1 2 3 4 5 6 7<BR>&gt;8 9 0 1 2 3 4=20
        5<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; 6 7 8 9 0=20
        1<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Vers&nbsp;=20
        |&nbsp; Sub&nbsp; | Message Type&nbsp;=20
        |<BR>&gt;Result|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        Code<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Partition=20
        ID&nbsp;=20
        |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
<BR>&gt;Transaction=20
        Identifier<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        |I|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SubMessage=20
        Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        |&nbsp;&nbsp;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        Length<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        Port<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        Port Session=20
        Number<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        Event Sequence=20
        Number<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        |x|S|x|x|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        +-+-+-+-+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        Label<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        ~<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        ~<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |x|x|x|x|x|x|x=
|x|=20
        Message Type&nbsp; |&nbsp;&nbsp;<BR>&gt;Tech Type&nbsp;&nbsp; | Blo=
ck=20
        Length<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        ~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;=20
        Extension=20
        Value<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        ~<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; When we say the label field should be <st1:PersonName=20
        w:st=3D"on">se</st1:PersonName>t to<BR>&gt;0, the=20
        intention<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; is for=20
        the<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; type and length fields in the label TLV to<BR>&gt;be=20
        <st1:PersonName w:st=3D"on">se</st1:PersonName>t to 0. We=20
        can<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; explicitly state this for=20
        clarity.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        -Sanjay<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;-----Original=20
        Message-----<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;From: Maglione Roberta<BR>&gt;[</SPAN></FONT><A=20
        href=3D"mailto:roberta.maglione@telecomitalia.it"><FONT size=3D2><S=
PAN=20
        style=3D"FONT-SIZE: 10pt">mailto:roberta.maglione@telecomitalia.it<=
/SPAN></FONT></A><FONT=20
        size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt">]<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;Sent: Tuesday, April 29, 2008 8:06=20
        AM<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;To: Sanjay=20
        Wadhwa<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;Cc: Wojciech Dec (wdec);=20
        ancp@ietf.org;<BR>&gt;pchamp@cisco.com<BR>&gt;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;Subject: RE: question regarding Labels in<BR>&gt;ANCP port=
 up=20
        messages<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;Hi Sanjay and=20
        All,<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp; I was reading the current=20
        ancp<BR>&gt;protocol draft in order=20
        to<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt; understand which should be the correct<BR>&gt;format for =
the=20
        label<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;field in the ancp port Up=20
        message.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;Actually as it was already pointed out in<BR>&gt;the alias=
 the=20
        draft<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;in <st1:PersonName w:st=3D"on">se</st1:PersonName>ction 5.=
4.2=20
        says "GSMP Event message<BR>&gt;with PORT UP=20
        message<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;type (80) is u<st1:PersonName=20
        w:st=3D"on">se</st1:PersonName>d"&nbsp; thus I am assuming that<BR>=
&gt;the=20
        label in=20
        the<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;port UP message should follow the message<BR>&gt;format de=
fined=20
        in<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;RFC 3292, <st1:PersonName w:st=3D"on">se</st1:PersonName>c=
tion=20
        3.1.3:<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;&nbsp;=20
        0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt;2&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;=20
        3<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;&nbsp; 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8=20
        9<BR>&gt;0 1 2 3 4 5 6 7 8 9 0=20
        1<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;&nbsp;&nbsp;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp; |x|S|x|x|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
=20
        Label Type&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt;&nbsp; Label=20
        Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;&nbsp;&nbsp;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;=20
        |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;=20
        |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;=20
        ~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;=20
        Label=20
        Value&nbsp;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;=20
        ~<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;=20
        |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;=20
        |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;&nbsp;&nbsp;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;but from what I have <st1:PersonName=20
        w:st=3D"on">se</st1:PersonName>en different<BR>&gt;implementations=
=20
        u<st1:PersonName=20
        w:st=3D"on">se</st1:PersonName><BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;different format for label field: in<BR>&gt;particular=20
        <st1:PersonName=20
        w:st=3D"on">se</st1:PersonName>veral<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;implementations u<st1:PersonName=20
        w:st=3D"on">se</st1:PersonName>&nbsp; a label format that=20
        is<BR>&gt;similar to the=20
        one<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;specified in the expired=20
        draft<BR>&gt;draft-ietf-gsmp-v3-ba<st1:PersonName=20
        w:st=3D"on">se</st1:PersonName>-spec:<BR>&gt;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;=20
        0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt;=20
        2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        3<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0 1 2 3 4 5 6 7 8 9 0=
 1 2=20
        3 4 5 6 7<BR>&gt;8 9 0 1 2 3 4 5=20
        6<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; 7 8 9 0=20
        1<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        |x|S|x|x|x|x|x|x|x|x|x|x|x|x|x|x|&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        Label<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; Type&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp; Label=20
        Adaptation&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;=20
        |&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;=20
        Label<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        ~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;=20
        Label=20
        Value<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        ~<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;Even if ancp does not care about the label<BR>&gt;field, h=
aving=20
        this<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;field somehow not clearly specified in the<BR>&gt;current =
ancp=20
        draft<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;can easily lead to interoperability issues,<BR>&gt;thus I =
think=20
        it<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;would be very helpful if you and/or the<BR>&gt;other edito=
rs=20
        can<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;clarify what should be the correct format<BR>&gt;for the l=
abel=20
        field<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;to be u<st1:PersonName w:st=3D"on">se</st1:PersonName>d in=
 the=20
        ancp Port Up=20
        message.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;Thanks and best=20
        regards,<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;Roberta<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;________________________________________<BR>&gt;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
=20
        &gt; &gt;From: Philippe Champagne (pchamp)=20
        [pchamp@cisco.com]<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;Sent: Thursday, April 24, 2008 7:14=20
        PM<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;To: Sanjay=20
        Wadhwa<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;Cc: Maglione Roberta; Wojciech Dec=20
        (wdec);<BR>&gt;ancp@ietf.org<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;Subject: question regarding&nbsp; Labels in ANCP<BR>&gt;po=
rt up=20
        messages<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;Hi=20
        Sanjay<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;In <st1:PersonName w:st=3D"on">se</st1:PersonName>ction 5.=
4.2 of=20
        the draft, we=20
        have:<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        2<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        3<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0 1 2 3 4=
 5 6=20
        7 8 9 0 1 2 3 4 5 6<BR>&gt;7 8 9 0 1 2 3 4 5=20
        6<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;7 8 9 0=20
        1<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;<BR>&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Vers&nbsp; |&=
nbsp;=20
        Sub&nbsp; | Message Type&nbsp;=20
        |<BR>&gt;Result|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        Code<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;<BR>&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Partition ID&=
nbsp;=20
        |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
<BR>&gt;Transaction=20
        Identifier<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;<BR>&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        |I|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SubMessage=20
        Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        |&nbsp;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        Length<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;<BR>&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        Port<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;<BR>&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        Port Session=20
        Number<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;<BR>&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        Event Sequence=20
        Number<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;<BR>&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        |x|S|x|x|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        +-+-+-+-+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        Label<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        ~<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        ~<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;<BR>&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |x|x|x|x|x|x|x|=
x|=20
        Message Type&nbsp; |&nbsp;&nbsp;<BR>&gt;Tech Type&nbsp;&nbsp;=20
        |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;Block Length&nbsp;=20
        |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;<BR>&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        ~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;=20
        Extension=20
        Value<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        ~<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;<BR>&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;Where Label I suppo<st1:PersonName=20
        w:st=3D"on">se</st1:PersonName> is taken from the RFC<BR>&gt;3292,=
=20
        <st1:PersonName=20
        w:st=3D"on">se</st1:PersonName>ction<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;3.1.3: (well, I'm=20
        guessing)<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp; A summary of TLV labels supported in<BR>&gt;t=
his=20
        version of=20
        the<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; protocol=20
        is<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp; listed=20
        below:<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; TLV=20
        Label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        Type&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Section=20
        Title<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        ---------&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        ----&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        -------------<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ATM=20
        Label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0x100&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
        ATM TLV=20
        Labels<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; FR=20
        Label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        0x101&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Frame Relay<BR>&gt;TLV=20
        Labels<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MPLS Gen Label=20
        0x102&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MPLS<BR>&gt;Generic TLV=20
        Labels<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; FEC=20
        Label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0x103&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
        FEC TLV=20
        Labels<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp; All Labels will be designated as=20
        follow:<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;&nbsp;=20
        0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt;2&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;=20
        3<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;&nbsp; 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8=20
        9<BR>&gt;0 1 2 3 4 5 6 7 8 9 0=20
        1<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;&nbsp;&nbsp;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp; |x|S|x|x|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
=20
        Label Type&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt;&nbsp; Label=20
        Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;&nbsp;&nbsp;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;=20
        |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;=20
        |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;=20
        ~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;=20
        Label=20
        Value&nbsp;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;=20
        ~<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;=20
        |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;=20
        |<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;&nbsp;&nbsp;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; x: Re<st1:PersonName=20
        w:st=3D"on">se</st1:PersonName>rved=20
        Flags.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        The<st1:PersonName w:st=3D"on">se</st1:PersonName> are generally=20
        u<st1:PersonName w:st=3D"on">se</st1:PersonName>d by<BR>&gt;specifi=
c=20
        messages and will=20
        be<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; defined i=
n=20
        tho<st1:PersonName w:st=3D"on">se</st1:PersonName>=20
        messages.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; S: Stacked Label=20
        Indicator<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Label Sta=
cking=20
        is discus<st1:PersonName w:st=3D"on">se</st1:PersonName>d below<BR>=
&gt;in=20
        <st1:PersonName w:st=3D"on">se</st1:PersonName>ction=20
        3.1.3.5<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Label=20
        Type<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A 12-bit =
field=20
        indicating the type<BR>&gt;of=20
        label.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Label=20
        Length<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A 16-bit =
field=20
        indicating the<BR>&gt;length of the=20
        Label<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; Value=20
        field<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; in=20
        bytes.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Label=20
        Value<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A variabl=
e=20
        length field that is an<BR>&gt;integer number of 32=20
        bit<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; words=20
        long.&nbsp; The Label Value field<BR>&gt;is=20
        interpreted<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; according=20
        to<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the Label=
 Type=20
        as described in the<BR>&gt;following <st1:PersonName=20
        w:st=3D"on">se</st1:PersonName>ctions.<BR>&gt;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;The draft is a bit obscure about this and<BR>&gt;since it=
=20
        doesn't<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;specify much, it can lead to<BR>&gt;misinterpretation for =
the=20
        unu<st1:PersonName=20
        w:st=3D"on">se</st1:PersonName>d<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;part. Moreover, it would appear that<BR>&gt;<st1:PersonNam=
e=20
        w:st=3D"on">se</st1:PersonName>veral=20
        implementations<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;currently u<st1:PersonName w:st=3D"on">se</st1:PersonName>=
=20
        another format for the label<BR>&gt;field. Can=20
        you<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;explain?&nbsp; I mean, how come what's in the<BR>&gt;curre=
nt=20
        draft=20
        doesn't<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;match what's known to be=20
        implemented?<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;I'm still wondering why we carried over<BR>&gt;pieces from=
 GSMP=20
        that<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;we do not intend to u<st1:PersonName=20
        w:st=3D"on">se</st1:PersonName>.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;I would recommend that if we are to keep<BR>&gt;them but n=
ot=20
        u<st1:PersonName=20
        w:st=3D"on">se</st1:PersonName><BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;them, we should mention preci<st1:PersonName=20
        w:st=3D"on">se</st1:PersonName>ly how we<BR>&gt;intend not to=20
        u<st1:PersonName=20
        w:st=3D"on">se</st1:PersonName><BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;them: that is how many 0 filled bytes this<BR>&gt;is expec=
ted=20
        to u<st1:PersonName=20
        w:st=3D"on">se</st1:PersonName><BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;The rfc 3292 doesn't cover the ca<st1:PersonName=20
        w:st=3D"on">se</st1:PersonName> where<BR>&gt;this field is not=20
        u<st1:PersonName=20
        w:st=3D"on">se</st1:PersonName>d.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;Can you shed some ligths on=20
        this?<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;Thanks<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;Regards<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;Phil<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;<BR>&gt;&gt;---------------------------------------------------=
-----------------<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;CONFIDENTIALITY=20
        NOTICE<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;This message and its attachments=20
        are<BR>&gt;addres<st1:PersonName w:st=3D"on">se</st1:PersonName>d s=
olely=20
        to=20
        the<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;persons above and may contain confidential<BR>&gt;informat=
ion.=20
        If=20
        you<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;have received the message in error, be<BR>&gt;informed tha=
t any=20
        u<st1:PersonName=20
        w:st=3D"on">se</st1:PersonName><BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;of the content hereof is prohibited. Plea<st1:PersonName=20
        w:st=3D"on">se</st1:PersonName><BR>&gt;return=20
        it<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;immediately to the <st1:PersonName=20
        w:st=3D"on">se</st1:PersonName>nder and delete the<BR>&gt;message. =
Should=20
        you<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;have any questions, plea<st1:PersonName=20
        w:st=3D"on">se</st1:PersonName> contact us by replying=20
        to<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;webmaster@telecomitalia.it.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Thank=20
        you<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;<BR>&gt;www.telecomitalia.it<BR>&gt;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;<BR>&gt;&gt;---------------------------------------------------=
-----------------<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        &gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        _______________________________________________<BR>&gt;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;=20
        ANCP mailing=20
        list<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        ANCP@ietf.org<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
        </SPAN></FONT><A href=3D"https://www.ietf.org/mailman/listinfo/ancp=
"=20
        target=3D_blank><FONT size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt">https://www.ietf.org/mailman/listinfo/anc=
p</SPAN></FONT></A><BR><FONT=20
        size=3D2><SPAN style=3D"FONT-SIZE: 10pt">&gt;<BR>&gt;</SPAN></FONT>=
=20
        <o:p></o:p></P></BLOCKQUOTE></DIV></BLOCKQUOTE>
    <P>
    <HR>

    <P></P>_______________________________________________<BR>ANCP mailing=
=20
    list<BR>ANCP@ietf.org<BR>https://www.ietf.org/mailman/listinfo/ancp<BR>=
</BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

--_000_48C276B536524E478C659685995F6AA53B5959219FRBSJXadredbac_--

--===============0551845500==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============0551845500==--


From ancp-bounces@ietf.org  Tue May  6 05:04:16 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id BE9303A6CF2;
	Tue,  6 May 2008 05:04:15 -0700 (PDT)
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 6E69F3A6EB9
	for <ancp@core3.amsl.com>; Tue,  6 May 2008 05:04:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.353
X-Spam-Level: ***
X-Spam-Status: No, score=3.353 tagged_above=-999 required=5
	tests=[BAYES_50=0.001, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001,
	HTML_OBFUSCATE_05_10=0.001, J_BACKHAIR_21=1, J_BACKHAIR_22=1,
	J_BACKHAIR_23=1, J_BACKHAIR_24=1, J_BACKHAIR_25=1, J_BACKHAIR_26=1,
	J_BACKHAIR_27=1, RCVD_IN_DNSWL_MED=-4]
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 VvOP5zPA9RqS for <ancp@core3.amsl.com>;
	Tue,  6 May 2008 05:04:05 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60])
	by core3.amsl.com (Postfix) with ESMTP id 79D5F28C3BF
	for <ancp@ietf.org>; Tue,  6 May 2008 05:03:58 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	8664C20887; Tue,  6 May 2008 14:03:55 +0200 (CEST)
X-AuditID: c1b4fb3c-af89ebb00000193b-51-4820492bf8fc
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	1CF4D2082A; Tue,  6 May 2008 14:03:55 +0200 (CEST)
Received: from esealmw104.eemea.ericsson.se ([153.88.200.67]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 6 May 2008 14:03:54 +0200
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 6 May 2008 14:03:53 +0200
Message-ID: <BAC301C0C1697C4EBDF97C805A273CBC9909C5@esealmw104.eemea.ericsson.se>
In-Reply-To: <48C276B536524E478C659685995F6AA539DBBBEF99@RBSJX.ad.redback.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ANCP] question regarding  Labels in ANCP port up messages
Thread-Index: Aciqkn5nSPBPuwuySsamcvxF1uU6kQAZ9dQQAAE415AABe3TAABN80lQAA1w7OAAutMtAA==
References: <48C276B536524E478C659685995F6AA539DBBBE370@RBSJX.ad.redback.com><9BD5D7887235424FA97DFC223CAE3C280AB43A10@proton.jnpr.net><48C276B536524E478C659685995F6AA539DBBBE577@RBSJX.ad.redback.com><9BD5D7887235424FA97DFC223CAE3C28102EB5AA@proton.jnpr.net>
	<48C276B536524E478C659685995F6AA539DBBBEF99@RBSJX.ad.redback.com>
From: "Ole Helleberg Andersen" <ole.helleberg.andersen@ericsson.com>
To: "Peter Arberg" <parberg@redback.com>,
	"Sanjay Wadhwa" <swadhwa@juniper.net>, "Tina TSOU" <tena@huawei.com>,
	"Maglione Roberta" <roberta.maglione@telecomitalia.it>,
	"Wojciech Dec (wdec)" <wdec@cisco.com>
X-OriginalArrivalTime: 06 May 2008 12:03:54.0732 (UTC)
	FILETIME=[41A162C0:01C8AF71]
X-Brightmail-Tracker: AAAAAA==
Cc: ancp@ietf.org
Subject: Re: [ANCP] question regarding  Labels in ANCP port up messages
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/pipermail/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>
Content-Type: multipart/mixed; boundary="===============0840661864=="
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0840661864==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8AF71.41687A2C"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8AF71.41687A2C
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi All,
=20
I think the main issue is to ensure interoperability with existing
implementations, and to allow for upgrading nodes that are already in
service to a WG-draft compliant version. To do that in a manageable way
we must allow for version negotiation per adjacency. We therefore need
to change the WG-draft as suggested by Sanjay in his option 2.
=20
Concerning the encoding issue I prefer to make the WG-draft in line with
existing implementations. However, if the WG decides to change it,
differences in this encoding would also be solved by choosing Sanjay's
option 2.
=20
Cheers,
Ole

________________________________

From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of
Peter Arberg
Sent: 2. maj 2008 20:52
To: Sanjay Wadhwa; Tina TSOU; Maglione Roberta; Wojciech Dec (wdec)
Cc: ancp@ietf.org
Subject: Re: [ANCP] question regarding Labels in ANCP port up messages


Hi Sanjay,
=20
yes apparently I missed your point in the last email, but I'm glad we
agree something is needed
to make existing ANCP implementations and the current draft to co-exist.
=20
I do not like your option 1) as if you need a config knob for
interoperability, it is too easy to
get into trouble.
=20
I think option 2) is the best way forward with the differences already
identified, or we can=20
continue to get a show of hands of ANCP implementations, and see if
anyone is actually
deployed based on the WG-draft.
=20
There is no beneficial reasons to base the event-message of RFC3292, it
could as well be a message
described bit by bit in the ANCP draft, and then we can keep the label
space at 8 as many
implementations alreday do.
=20
cheers,
Peter
=20
=20
=20


________________________________

	From: Sanjay Wadhwa [mailto:swadhwa@juniper.net]=20
	Sent: 2. maj 2008 05:35
	To: Peter Arberg; Tina TSOU; Maglione Roberta; Wojciech Dec
(wdec)
	Cc: ancp@ietf.org
	Subject: RE: [ANCP] question regarding Labels in ANCP port up
messages
=09
=09

	Peter

	 You missed my point below. The ANCP draft since becoming a WG
draft does NOT refer to the old GSMP drafts. Any implementations based
on this WG-draft are expected to be interoperable. You are pointing to
pre-WG-draft versions of ANCP, and these were indeed based on expired
GSMP drafts that evolved past RFC3292.=20

	There is incompatibility between the current ANCP WG-draft and
previous non-WG versions (TLV clash, label format..). As mentioned
earlier it is prudent for older implementations to start supporting the
WG-draft version as soon as possible.=20

	=20

	For interoperability of WG-draft with the older pre-WG versions,
I see the following options:

	=20

	1. Versioning starts with the WG-draft i.e. WG-draft is version
=3D 3, sub-version =3D 1. For any interop issues between older non-WG
versions and the WG-draft, one needs to look at solving it within
implementations (e.g. an AN that implements the WG-draft, could based on
a configuration knob, generate a PORT-UP message with old label format
the will be accepted by BNG implementing pre-WG versions of the draft).=20

	=20

	2. Change the WG-draft (current draft) to use version =3D 3 and
sub-version =3D 2. This is assuming there is no deployed implementation =
of
current WG-draft that already uses 3.1 as the version, and also assuming
the old pre-WG implementations use 3.1. There will be no backwards
compatibility i.e. version 3.1 BNG will not work with version 3.2 AN (we
will need to list this as caveat in the appendix section). AN and BNG
will need to negotiate the same version in order for ANCP adjacency to
come up. A BNG supporting both versions 3.1 and 3.2 could simultaneously
become adjacent with one AN supporting 3.1 and another AN supporting
3.2. (i.e. version compatibility is per adjacency).

	Also, major version number change (e.g. from 3 to 4) should only
correspond to a major change in the protocol (e.g. different mechanism,
different transport etc).

	=20

	My vote would be to adopt option 2 above only if further changes
to WG-draft happen that render it incompatible with the current
WG-draft. Any interoperability issues with pre-WG versions could be
handled via option 1.

	=20

	Cheers

	-Sanjay

	=20

=09
________________________________


	From: Peter Arberg [mailto:parberg@redback.com]=20
	Sent: Wednesday, April 30, 2008 7:20 PM
	To: Sanjay Wadhwa; Tina TSOU; Maglione Roberta; Wojciech Dec
(wdec)
	Cc: ancp@ietf.org
	Subject: RE: [ANCP] question regarding Labels in ANCP port up
messages

	=20

	Sanjay,

	=20

	What do you mean "why I reference an old draft"  ????????????

	=20

	I'm surprised you even ask...  please take a look at YOUR own
internet-draft that most

	of the ANCP working implementations are based on, in case you do
not have this old

	internet-draft, I have attached it to the document.

	=20

	If you look at the reference for this ancp-draft, you will see
that in the reference section

	you point to this old gsmp-draft...  Yes and I know this has
been changed in the later

	versions of the ANCP draft, but that do not change the fact that
many of the implementations

	today was developed when the attached draft was current.

	=20

	I think a very good question is brought up here, and that is
what is implemented and

	running in networks today ?

	=20

	My take on this is that when the reference was change from the
old gsmp-draft to the older

	RFC3292, apparently no one paid any attention to the fact the
label definition in the event

	message was different and not compatible.

	=20

	What current implementations do today is an important factor in
this discussion, and I think

	it is time to come to realization that we might need a new
version number for ANCP since

	it continues to look like there is big holes open for
interpretation. So if I did a ANCP

	implementation there is bound to be interoperability issues with
existing implementations

	runnig.

	=20

	cheers,

	Peter

	=20

	=20

	=20

		=20

	=09
________________________________


		From: Sanjay Wadhwa [mailto:swadhwa@juniper.net]=20
		Sent: 30. april 2008 14:42
		To: Peter Arberg; Tina TSOU; Maglione Roberta; Wojciech
Dec (wdec)
		Cc: ancp@ietf.org
		Subject: RE: [ANCP] question regarding Labels in ANCP
port up messages

		Peter
		  The ANCP draft as it currently stands is based on
RFC3292. It provides extensions and modifications to relevant constructs
in RFC3292. There is no mention (implicit or explicit) of expired GSMP
drafts in the ANCP draft. In order to implement the ANCP draft, I am not
sure why one would look at the expired GSMP drafts. Do you see a reason
to do this based on anything that you read in the ANCP draft? Bringing
up reference to expired gsmp draft in this thread just adds to the
confusion. For GSMPv3 objects in the messages (such as Label Type), one
has to look at RFC3292 (this is clearly stated in the ANCP draft -
section 2 and I am quoting it below) :

		ANCP uses a subset of GSMPv3 messages to implement
currently defined use-cases. These relevant GSMPv3 messages are
identified in section 5. GSMPv3 procedures with suitable extensions, as
used by ANCP, are described in sections 5.1, 5.2 and 5.3. GSMPv3 general
extensions and GSMPv3 message specific extensions required by ANCP are
described in sub-sections of 5.4. In addition to specifying extensions
and modifications to relevant GSMP messages applicable to ANCP, this
draft also defines the usage of these messages by ANCP, and indicates
the values that ANCP should set for relevant fields in these GSMP
messages. However, to understand the basic semantics of various fields
in GSMP messages, the reader is referred to [4]. =3D> RFC 3292.
	=09
		What existing implementations currently do is an
important but separate issue. These implementations for most part
precede the current ANCP draft. It is fine to poll where these
implementations diverge from the current draft. It is then upto the
implementations (including the one that I am somewhat familiar with) to
work towards compliance with the draft.=20

		On the following points from  Woj:

		Woj>2) The current version of the spec is not accurate,
and does not reflect the fact that the known implementations follow the
label field definition from draft-gsmpv3-base-spec.

		It is not for the protocol draft to point out what
current implementations do.  The best we can do is to further clarify in
the draft that type and value fields of the Label object (defined in
RFC3292) should be set to 0 in the port-up message (we already mention
the lable object as a whole should be set to all 0s).=20

		Woj> This would be a good thing for the WG to discuss.
There most evidently is a fair amount of "dead wood" in the current
spec, ie stuff that nobody yet implements or cares about.  In the former
case, we could re-cast that material using the new notions/extensions,
in the latter case simply chop it out.

		I agree. We are based on GSMPv3 (RFC3292)  messages, and
obviously not everything in these messages is leveraged by ANCP.
However, the sync rate and OAM uses-cases are implemented and in use
(ideally we should leave these alone...i.e. no change beyond adding more
clarity if needed). For anything new (such as multicast) we are defining
new messages (no legacy). =20

		-Sanjay
	=09
		>-----Original Message-----
		>From: Peter Arberg [mailto:parberg@redback.com
<mailto:parberg@redback.com> ]
		>Sent: Wednesday, April 30, 2008 3:56 PM
		>To: Tina TSOU; Maglione Roberta; Sanjay Wadhwa;
Wojciech Dec (wdec)
		>Cc: ancp@ietf.org
		>Subject: RE: [ANCP] question regarding Labels in ANCP
port up messages
		>
		>
		>Hi,
		>
		>some times I think it is amazing we ever got
interoperability
		>of ANCP :-)
		>because looking at the label discussion is a very good
example that the
		>whole GSMP - ANCP reference have not worked very well.
		>
		>In the ANCP draft, section 5.4.2 the event message is
shown like this:
		>
		>0                   1                   2
3
		>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
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
		>| Vers  |  Sub  | Message Type  | Result|        Code
|
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
		>| Partition ID  |            Transaction Identifier
|
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
		>|I|      SubMessage Number      |           Length
|
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
		>|                             Port
|
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
		>|                      Port Session Number
|
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
		>|                     Event Sequence Number
|
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
		>|x|S|x|x|
|
		>+-+-+-+-+                     Label
|
		>~
~
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
		>|x|x|x|x|x|x|x|x| Message Type  |   Tech Type   | Block
Length  |
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
		>|
|
		>~                         Extension Value
~
		>|
|
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
		>
		>
		>This is the exact same event message defined in
		>draft-ietf-gsmp-v3-base-spec-08.txt  section 11.
		>
		>And in this gsmp-draft, section 5.1.3 the label space
is defined
		>as minimum 8 bytes if the length=3D0 and as such no
value, and this
		>is because the gsmp-draft has a new "label adaptaion"
field.
		>
		>
		>
		>BUT in RFC3292 the event message is show in section 9,
like this:
		>
		>0                   1                   2
3
		>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
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
		>|    Version    | Message Type  |    Result     |
Code      |
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
		>| Partition ID  |            Transaction Identifier
|
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
		>|I|      SubMessage Number      |           Length
|
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
		>|                             Port
|
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
		>|                      Port Session Number
|
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
		>|                     Event Sequence Number
|
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
		>|x|S|x|x|
|
		>+-+-+-+-+                     Label
|
		>~
~
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
		>
		>
		>So a different Event Message picture/definition than
what is shown
		>in the ANCP draft, and in RFC3292 section 3.1.3 the
label field
		>is defined as 4 bytes if length=3D0 and as such no value.
		>
		>
		>
		>So I very much agree with Woj that we need this issue
to be resolved,
		>and proabably a show of hands what is actually done in
different
		>implementations, so we can nail down how the event
message is
		>suppose to look like in ANCP.
		>
		>
		>I know at least 1 implementation which uses 8 bytes for
the
		>label field.
		>
		>
		>cheers,
		>Peter
		>
		>
		>
		>
		>
		>
		>________________________________
		>
		>        From: ancp-bounces@ietf.org
		>[mailto:ancp-bounces@ietf.org
<mailto:ancp-bounces@ietf.org> ] On Behalf Of Tina TSOU
		>        Sent: 30. april 2008 00:19
		>        To: Maglione Roberta; Sanjay Wadhwa; Wojciech
Dec (wdec)
		>        Cc: ancp@ietf.org
		>        Subject: Re: [ANCP] question regarding Labels
in ANCP
		>port up messages
		>
		>
		>        Hi all,
		>        It is clear to me that if Label Length is
filled as 0,
		>there is nothing to be filled into Label Value. The
whole
		>Label part is 4 bytes, not 8 bytes.
		>
		>        Cheers from the last working day before Labor's
Day
		>holidays in some countries:)
		>
		>        Tina
		>
		>                ----- Original Message -----
		>                From: Wojciech Dec (wdec)
<mailto:wdec@cisco.com <mailto:wdec@cisco.com> >
		>                To: Sanjay Wadhwa
<mailto:swadhwa@juniper.net <mailto:swadhwa@juniper.net> >
		> ; Maglione Roberta
<mailto:roberta.maglione@telecomitalia.it
<mailto:roberta.maglione@telecomitalia.it> >
		>                Cc: ancp@ietf.org
		>                Sent: Wednesday, April 30, 2008 1:12 AM
		>                Subject: Re: [ANCP] question regarding
Labels
		>in ANCP port up messages
		>
		>                Sanjay, All,
		>
		>                What is stated below runs counter to at
least
		>a handful of ANCP
		>                implementations, all of which are known
to be
		>interoperable.
		>                There are really two options:
		>                1) The current version of the spec is
correct,
		>and the known
		>                interoperable implementations do not
follow it
		>                2) The current version of the spec is
not
		>accurate, and does not reflect
		>                the fact that the known implementations
follow
		>the label field
		>                definition from draft-gsmpv3-base-spec.
		>
		>                I would like to ask you, as the lead
editor of
		>the spec, to work with
		>                the WG in resolving what the problem
is, and
		>clearing up what the WG
		>                spec says about and if 1) holds to be
true,
		>then proposing an
		>                interoperability fix.
		>
		>                In either case, the issue highlights
the fact
		>that there is still
		>                lingering confusion as to the
dependencies
		>ANCP has on rfc3292, or
		>                draft-gsmpv3-base-spec, or both. It
seems to
		>be in the best interest of
		>                all to address these.
		>
		>                Regards,
		>                Woj.
		>
		>                > -----Original Message-----
		>                > From: Sanjay Wadhwa
[mailto:swadhwa@juniper.net <mailto:swadhwa@juniper.net> ]
		>                > Sent: 29 April 2008 17:29
		>                > To: Maglione Roberta
		>                > Cc: Wojciech Dec (wdec);
ancp@ietf.org;
		>Philippe Champagne (pchamp)
		>                > Subject: RE: question regarding
Labels in
		>ANCP port up messages
		>                >
		>                > Hi Maglione
		>                >   Yes, the label format is as defined
in RFC
		>3292. The ANCP draft is
		>                > based on RFC 3292 and proposes
		>extensions/modifications where
		>                > required.
		>                > This is clearly stated upfront both
in the
		>abstract and in
		>                > section 2. In
		>                > section 5.4.2, it clearly  specifies
the
		>format of "port up" message
		>                > (based on RFC 3292), and explicitly
states
		>the label field
		>                > should be set
		>                > to 0. Following is what the draft
currently states:
		>                >
		>                >
		>                > 5.4.2 Topology Discovery Extensions
		>                >
		>                > The GSMP Event message with PORT UP
message
		>type (80) is used for
		>                > conveying DSL line attributes to the
NAS.
		>The version field should be
		>                > set to 3, and the sub field should be
set to
		>1. The I and subMessage
		>                > fields SHOULD be set to 1 to signify
no
		>fragmentation. The Port and
		>                > Label fields should be set to 0.
		>                >
		>                >  0                   1
2 =20
		>                3
		>                >          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
		>                >
		>                >
		>                >
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
		>                >         | Vers  |  Sub  | Message
Type  |
		>Result|        Code
		>                > |
		>                >
		>                >
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
		>                >         | Partition ID  |          =20
		>Transaction Identifier
		>                > |
		>                >
		>                >
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
		>                >         |I|      SubMessage Number
|  =20
		>       Length
		>                > |
		>                >
		>                >
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
		>                >         |
Port
		>                > |
		>                >
		>                >
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
		>                >         |                      Port
Session Number
		>                > |
		>                >
		>                >
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
		>                >         |                     Event
Sequence Number
		>                > |
		>                >
		>                >
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
		>                >         |x|S|x|x|
		>                > |
		>                >         +-+-+-+-+
Label
		>                > |
		>                >         ~
		>                > ~
		>                >
		>                >
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
		>                >         |x|x|x|x|x|x|x|x| Message
Type  | =20
		>Tech Type   | Block Length
		>                > |
		>                >
		>                >
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
		>                >         |
		>                > |
		>                >         ~
Extension Value
		>                > ~
		>                >         |
		>                > |
		>                >
		>                >
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
		>                >
		>                > When we say the label field should be
set to
		>0, the intention
		>                > is for the
		>                > type and length fields in the label
TLV to
		>be set to 0. We can
		>                > explicitly state this for clarity.
		>                >
		>                > -Sanjay
		>                >
		>                > >-----Original Message-----
		>                > >From: Maglione Roberta
		>[mailto:roberta.maglione@telecomitalia.it
<mailto:roberta.maglione@telecomitalia.it> ]
		>                > >Sent: Tuesday, April 29, 2008 8:06
AM
		>                > >To: Sanjay Wadhwa
		>                > >Cc: Wojciech Dec (wdec);
ancp@ietf.org;
		>pchamp@cisco.com
		>                > >Subject: RE: question regarding
Labels in
		>ANCP port up messages
		>                > >
		>                > >
		>                > >Hi Sanjay and All,
		>                > >     I was reading the current ancp
		>protocol draft in order to
		>                > > understand which should be the
correct
		>format for the label
		>                > >field in the ancp port Up message.
		>                > >Actually as it was already pointed
out in
		>the alias the draft
		>                > >in section 5.4.2 says "GSMP Event
message
		>with PORT UP message
		>                > >type (80) is used"  thus I am
assuming that
		>the label in the
		>                > >port UP message should follow the
message
		>format defined in
		>                > >RFC 3292, section 3.1.3:
		>                > >
		>                > >    0                   1

		>2                   3
		>                > >    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
		>                > > =20
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
		>                > >   |x|S|x|x|       Label Type      |

		>  Label Length         |
		>                > > =20
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
		>                > >   |

		>                       |
		>                > >   ~                          Label
Value =20
		>                       ~
		>                > >   |

		>                       |
		>                > > =20
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
		>                > >
		>                > >but from what I have seen different
		>implementations use
		>                > >different format for label field: in
		>particular several
		>                > >implementations use  a label format
that is
		>similar to the one
		>                > >specified in the expired draft
		>draft-ietf-gsmp-v3-base-spec:
		>                > >
		>                > >     0                   1

		> 2                   3
		>                > >       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
		>                > >
		>                >
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
		>                > >
|x|S|x|x|x|x|x|x|x|x|x|x|x|x|x|x|   =20
		>       Label
		>                > Type         |
		>                > >
		>                >
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
		>                > >      |    Label Adaptation
|   =20
		>     Label
		>                > Length         |
		>                > >
		>                >
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
		>                > >      |
		>                >          |
		>                > >      ~
Label Value
		>                >          ~
		>                > >      |
		>                >          |
		>                > >
		>                >
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
		>                > >
		>                > >
		>                > >Even if ancp does not care about the
label
		>field, having this
		>                > >field somehow not clearly specified
in the
		>current ancp draft
		>                > >can easily lead to interoperability
issues,
		>thus I think it
		>                > >would be very helpful if you and/or
the
		>other editors can
		>                > >clarify what should be the correct
format
		>for the label field
		>                > >to be used in the ancp Port Up
message.
		>                > >
		>                > >Thanks and best regards,
		>                > >Roberta
		>                > >
		>                >
>________________________________________
		>                > >From: Philippe Champagne (pchamp)
[pchamp@cisco.com]
		>                > >Sent: Thursday, April 24, 2008 7:14
PM
		>                > >To: Sanjay Wadhwa
		>                > >Cc: Maglione Roberta; Wojciech Dec
(wdec);
		>ancp@ietf.org
		>                > >Subject: question regarding  Labels
in ANCP
		>port up messages
		>                > >
		>                > >Hi Sanjay
		>                > >
		>                > >In section 5.4.2 of the draft, we
have:
		>                > >
		>                > >
		>                > >         0                   1
2
		>                >         3
		>                > >         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
		>                > >
		>                >
=09
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
		>                > >        | Vers  |  Sub  | Message
Type  |
		>Result|        Code
		>                > >         |
		>                > >
		>                >
=09
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
		>                > >        | Partition ID  |          =20
		>Transaction Identifier
		>                > >         |
		>                > >
		>                >
=09
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
		>                > >        |I|      SubMessage Number
| =20
		>        Length
		>                > >         |
		>                > >
		>                >
=09
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
		>                > >        |
Port
		>                > >         |
		>                > >
		>                >
=09
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
		>                > >        |                      Port
Session Number
		>                > >         |
		>                > >
		>                >
=09
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
		>                > >        |                     Event
Sequence Number
		>                > >         |
		>                > >
		>                >
=09
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
		>                > >        |x|S|x|x|
		>                > >         |
		>                > >        +-+-+-+-+
Label
		>                > >         |
		>                > >        ~
		>                > >         ~
		>                > >
		>                >
=09
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
		>                > >        |x|x|x|x|x|x|x|x| Message
Type  | =20
		>Tech Type   |
		>                > >Block Length  |
		>                > >
		>                >
=09
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
		>                > >        |
		>                > >         |
		>                > >        ~
Extension Value
		>                > >         ~
		>                > >        |
		>                > >         |
		>                > >
		>                >
=09
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
		>                > >Where Label I suppose is taken from
the RFC
		>3292, section
		>                > >3.1.3: (well, I'm guessing)
		>                > >
		>                > >   A summary of TLV labels supported
in
		>this version of the
		>                > protocol is
		>                > >   listed below:
		>                > >
		>                > >      TLV Label      Type
Section Title
		>                > >      ---------      ----
-------------
		>                > >      ATM Label      0x100      ATM
TLV Labels
		>                > >      FR Label       0x101
Frame Relay
		>TLV Labels
		>                > >      MPLS Gen Label 0x102      MPLS
		>Generic TLV Labels
		>                > >      FEC Label      0x103      FEC
TLV Labels
		>                > >
		>                > >   All Labels will be designated as
follow:
		>                > >
		>                > >    0                   1

		>2                   3
		>                > >    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
		>                > > =20
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
		>                > >   |x|S|x|x|       Label Type      |

		>  Label Length         |
		>                > > =20
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
		>                > >   |

		>                       |
		>                > >   ~                          Label
Value =20
		>                       ~
		>                > >   |

		>                       |
		>                > > =20
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
		>                > >
		>                > >      x: Reserved Flags.
		>                > >         These are generally used by
		>specific messages and will be
		>                > >         defined in those messages.
		>                > >
		>                > >      S: Stacked Label Indicator
		>                > >         Label Stacking is discussed
below
		>in section 3.1.3.5
		>                > >
		>                > >      Label Type
		>                > >         A 12-bit field indicating
the type
		>of label.
		>                > >
		>                > >      Label Length
		>                > >         A 16-bit field indicating
the
		>length of the Label
		>                > Value field
		>                > >         in bytes.
		>                > >
		>                > >      Label Value
		>                > >         A variable length field
that is an
		>integer number of 32 bit
		>                > >         words long.  The Label
Value field
		>is interpreted
		>                > according to
		>                > >         the Label Type as described
in the
		>following sections.
		>                > >
		>                > >
		>                > >The draft is a bit obscure about
this and
		>since it doesn't
		>                > >specify much, it can lead to
		>misinterpretation for the unused
		>                > >part. Moreover, it would appear that
		>several implementations
		>                > >currently use another format for the
label
		>field. Can you
		>                > >explain?  I mean, how come what's in
the
		>current draft doesn't
		>                > >match what's known to be
implemented?
		>                > >
		>                > >I'm still wondering why we carried
over
		>pieces from GSMP that
		>                > >we do not intend to use.
		>                > >
		>                > >I would recommend that if we are to
keep
		>them but not use
		>                > >them, we should mention precisely
how we
		>intend not to use
		>                > >them: that is how many 0 filled
bytes this
		>is expected to use
		>                > >
		>                > >The rfc 3292 doesn't cover the case
where
		>this field is not used.
		>                > >
		>                > >Can you shed some ligths on this?
		>                > >
		>                > >Thanks
		>                > >Regards
		>                > >Phil
		>                > >
		>                > >
		>                > >
		>                >
=09
>>--------------------------------------------------------------------
		>                > >
		>                > >CONFIDENTIALITY NOTICE
		>                > >
		>                > >This message and its attachments are
		>addressed solely to the
		>                > >persons above and may contain
confidential
		>information. If you
		>                > >have received the message in error,
be
		>informed that any use
		>                > >of the content hereof is prohibited.
Please
		>return it
		>                > >immediately to the sender and delete
the
		>message. Should you
		>                > >have any questions, please contact
us by replying to
		>                > >webmaster@telecomitalia.it.
		>                > >
		>                > >        Thank you
		>                > >
		>                > >

		>www.telecomitalia.it
		>                > >
		>                >
=09
>>--------------------------------------------------------------------
		>                > >
		>                > >
		>                >
		>
_______________________________________________
		>                ANCP mailing list
		>                ANCP@ietf.org
		>
https://www.ietf.org/mailman/listinfo/ancp
<https://www.ietf.org/mailman/listinfo/ancp>=20
		>
		>=20


------_=_NextPart_001_01C8AF71.41687A2C
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:st1 =3D=20
"urn:schemas-microsoft-com:office:smarttags"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2800.1609" name=3DGENERATOR><!--[if !mso]>
<STYLE>v\:* {
	BEHAVIOR: url(#default#VML)
}
o\:* {
	BEHAVIOR: url(#default#VML)
}
w\:* {
	BEHAVIOR: url(#default#VML)
}
.shape {
	BEHAVIOR: url(#default#VML)
}
</STYLE>
<![endif]--><o:SmartTagType=20
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"=20
name=3D"PersonName"></o:SmartTagType><!--[if !mso]>
<STYLE>st1\:* {
	BEHAVIOR: url(#default#ieooui)
}
</STYLE>
<![endif]-->
<STYLE>@font-face {
	font-family: Tahoma;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: blue; TEXT-DECORATION: underline
}
P {
	FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: =
"Times New Roman"; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto
}
SPAN.EmailStyle18 {
	COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal-reply
}
DIV.Section1 {
	page: Section1
}
</STYLE>
</HEAD>
<BODY lang=3DEN-US vLink=3Dblue link=3Dblue>
<DIV><SPAN class=3D093315311-06052008><FONT face=3DArial color=3D#0000ff =
size=3D2>Hi=20
All,</FONT></SPAN></DIV>
<DIV><SPAN class=3D093315311-06052008><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D093315311-06052008>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D531344506-06052008>I=20
think the main issue is to ensure interoperability with existing=20
implementations, and to allow for upgrading nodes that are already in =
service to=20
a WG-draft compliant version. To do that in a manageable way we must =
allow for=20
version negotiation per adjacency. </SPAN></FONT><FONT face=3DArial =
color=3D#0000ff=20
size=3D2><SPAN class=3D531344506-06052008>We therefore need to change =
the WG-draft=20
as suggested by Sanjay in his option 2.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D531344506-06052008></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D531344506-06052008>Concerning the encoding issue I prefer to =
make the=20
WG-draft in line with existing implementations. However, if the WG =
decides to=20
change it, differences in this encoding would also be solved by choosing =

Sanjay's option 2.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D531344506-06052008></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D531344506-06052008><SPAN=20
class=3D093315311-06052008>Cheers,</SPAN></SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D531344506-06052008><SPAN=20
class=3D093315311-06052008>Ole</SPAN></SPAN></FONT></DIV></SPAN></DIV><BR=
>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> ancp-bounces@ietf.org=20
[mailto:ancp-bounces@ietf.org] <B>On Behalf Of </B>Peter =
Arberg<BR><B>Sent:</B>=20
2. maj 2008 20:52<BR><B>To:</B> Sanjay Wadhwa; Tina TSOU; Maglione =
Roberta;=20
Wojciech Dec (wdec)<BR><B>Cc:</B> ancp@ietf.org<BR><B>Subject:</B> Re: =
[ANCP]=20
question regarding Labels in ANCP port up messages<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Hi Sanjay,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>yes apparently I missed your point in the last =
email, but=20
I'm glad we agree something is needed</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>to make existing ANCP implementations and the =
current draft=20
to co-exist.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>I do not like your option 1) as if you need a =
config knob=20
for interoperability, it is too easy to</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>get into trouble.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>I think option 2) is the best way forward with =
the=20
differences already identified, or we can </FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>continue to get a show of hands of ANCP =
implementations,=20
and see if anyone is actually</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>deployed based on the =
WG-draft.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>There is no beneficial reasons to base the =
event-message of=20
RFC3292, it could as well be a message</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>described bit by bit in the ANCP draft, and =
then we can=20
keep the label space at 8 as many</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>implementations alreday do.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>cheers,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Peter</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Sanjay Wadhwa=20
  [mailto:swadhwa@juniper.net] <BR><B>Sent:</B> 2. maj 2008 =
05:35<BR><B>To:</B>=20
  Peter Arberg; Tina TSOU; Maglione Roberta; Wojciech Dec =
(wdec)<BR><B>Cc:</B>=20
  ancp@ietf.org<BR><B>Subject:</B> RE: [ANCP] question regarding Labels =
in ANCP=20
  port up messages<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV class=3DSection1>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial">Peter<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">&nbsp;You=20
  mis<st1:PersonName=20
  style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
  tabIndex=3D0 w:st=3D"on">se</st1:PersonName>d my point below. The ANCP =
draft since=20
  becoming a WG draft does NOT refer to the old GSMP drafts. Any =
implementations=20
  ba<st1:PersonName=20
  style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
  tabIndex=3D0 w:st=3D"on">se</st1:PersonName>d on this WG-draft are =
expected to be=20
  interoperable. You are pointing to pre-WG-draft versions of ANCP, and=20
  the<st1:PersonName=20
  style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
  tabIndex=3D0 w:st=3D"on">se</st1:PersonName> were indeed =
ba<st1:PersonName=20
  style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
  tabIndex=3D0 w:st=3D"on">se</st1:PersonName>d on expired GSMP drafts =
that evolved=20
  past RFC3292. <o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">There is=20
  incompatibility between the current ANCP WG-draft and previous non-WG =
versions=20
  (TLV clash, label format..). As mentioned earlier it is prudent for =
older=20
  implementations to start supporting the WG-draft version as soon as =
possible.=20
  <o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">For =
interoperability=20
  of WG-draft with the older pre-WG versions, I <st1:PersonName=20
  style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
  tabIndex=3D0 w:st=3D"on">se</st1:PersonName>e the following=20
  options:<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">1. =
Versioning starts=20
  with the WG-draft i.e. WG-draft is version =3D 3, sub-version =3D 1. =
For any=20
  interop issues between older non-WG versions and the WG-draft, one =
needs to=20
  look at solving it within implementations (e.g. an AN that implements =
the=20
  WG-draft, could ba<st1:PersonName=20
  style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
  tabIndex=3D0 w:st=3D"on">se</st1:PersonName>d on a configuration knob, =
generate a=20
  PORT-UP message with old label format the will be accepted by BNG =
implementing=20
  pre-WG versions of the draft). <o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">2. Change =
the=20
  WG-draft (current draft) to u<st1:PersonName=20
  style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
  tabIndex=3D0 w:st=3D"on">se</st1:PersonName> version =3D 3 and =
sub-version =3D 2. This=20
  is assuming there is no deployed implementation of current WG-draft =
that=20
  already u<st1:PersonName=20
  style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
  tabIndex=3D0 w:st=3D"on">se</st1:PersonName>s 3.1 as the version, and =
also=20
  assuming the old pre-WG implementations u<st1:PersonName=20
  style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
  tabIndex=3D0 w:st=3D"on">se</st1:PersonName> 3.1. There will be no =
backwards=20
  compatibility i.e. version 3.1 BNG will not work with version 3.2 AN =
(we will=20
  need to list this as caveat in the appendix <st1:PersonName=20
  style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
  tabIndex=3D0 w:st=3D"on">se</st1:PersonName>ction). AN and BNG will =
need to=20
  negotiate the same version in order for ANCP adjacency to come up. A =
BNG=20
  supporting both versions 3.1 and 3.2 could simultaneously become =
adjacent with=20
  one AN supporting 3.1 and another AN supporting 3.2. (i.e. version=20
  compatibility is per adjacency).<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Also, major =
version=20
  number change (e.g. from 3 to 4) should only correspond to a major =
change in=20
  the protocol (e.g. different mechanism, different transport=20
  etc).<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">My vote =
would be to=20
  adopt option 2 above only if further changes to WG-draft happen that =
render it=20
  incompatible with the current WG-draft. Any interoperability issues =
with=20
  pre-WG versions could be handled via option =
1.<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial">Cheers<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial">-Sanjay<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <DIV>
  <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
  face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
  <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
  </SPAN></FONT></DIV>
  <P class=3DMsoNormal><B><FONT face=3DTahoma size=3D2><SPAN=20
  style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
  face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma"> Peter=20
  Arberg [mailto:parberg@redback.com] <BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Wednesday, April 30, 2008 =
7:20=20
  PM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Sanjay =
Wadhwa; Tina=20
  TSOU; Maglione Roberta; Wojciech Dec (wdec)<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B> ancp@ietf.org<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [ANCP] question =
regarding=20
  Labels in ANCP port up messages</SPAN></FONT><o:p></o:p></P></DIV>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Sanjay,</SPAN></FONT><o:p></o:p></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">What do you =
mean "why=20
  I reference an old draft"&nbsp; =
????????????</SPAN></FONT><o:p></o:p></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">I'm=20
  surpri<st1:PersonName=20
  style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
  tabIndex=3D0 w:st=3D"on">se</st1:PersonName>d you even ask...&nbsp;=20
  plea<st1:PersonName=20
  style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
  tabIndex=3D0 w:st=3D"on">se</st1:PersonName> take a look at YOUR own=20
  internet-draft that most</SPAN></FONT><o:p></o:p></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">of the ANCP =
working=20
  implementations are ba<st1:PersonName=20
  style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
  tabIndex=3D0 w:st=3D"on">se</st1:PersonName>d on, in ca<st1:PersonName =

  style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
  tabIndex=3D0 w:st=3D"on">se</st1:PersonName> you do not have this=20
  old</SPAN></FONT><o:p></o:p></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">internet-draft, I=20
  have attached it to the document.</SPAN></FONT><o:p></o:p></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">If you look =
at the=20
  reference for this ancp-draft, you will <st1:PersonName=20
  style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
  tabIndex=3D0 w:st=3D"on">se</st1:PersonName>e that in the reference=20
  <st1:PersonName=20
  style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
  tabIndex=3D0 =
w:st=3D"on">se</st1:PersonName>ction</SPAN></FONT><o:p></o:p></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">you point =
to this old=20
  gsmp-draft...&nbsp; Yes and I know this has been changed in the=20
  later</SPAN></FONT><o:p></o:p></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">versions of =
the ANCP=20
  draft, but that do not change the fact that many of the=20
  implementations</SPAN></FONT><o:p></o:p></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">today was =
developed=20
  when the attached draft was current.</SPAN></FONT><o:p></o:p></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">I think a =
very good=20
  question is brought up here, and that is what is implemented=20
  and</SPAN></FONT><o:p></o:p></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">running in =
networks=20
  today ?</SPAN></FONT><o:p></o:p></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">My take on =
this is=20
  that when the reference was change from the old gsmp-draft to the=20
  older</SPAN></FONT><o:p></o:p></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">RFC3292, =
apparently=20
  no one paid any attention to the fact the label definition in the=20
  event</SPAN></FONT><o:p></o:p></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">message was =
different=20
  and not compatible.</SPAN></FONT><o:p></o:p></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">What =
current=20
  implementations do today is an important factor in this discussion, =
and I=20
  think</SPAN></FONT><o:p></o:p></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">it is time =
to come to=20
  realization that we might need a new version number for ANCP=20
  since</SPAN></FONT><o:p></o:p></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">it =
continues to look=20
  like there is big holes open for interpretation. So if I did a=20
  ANCP</SPAN></FONT><o:p></o:p></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">implementation there=20
  is bound to be interoperability issues with existing=20
  implementations</SPAN></FONT><o:p></o:p></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">runnig.</SPAN></FONT><o:p></o:p></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">cheers,</SPAN></FONT><o:p></o:p></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Peter</SPAN></FONT><o:p></o:p></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
  <BLOCKQUOTE=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: 5pt 0in 5pt =
3.75pt; BORDER-LEFT: blue 1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none">
    <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
    style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
    <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
    face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
    <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
    </SPAN></FONT></DIV>
    <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><B><FONT =
face=3DTahoma=20
    size=3D2><SPAN=20
    style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
    face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">=20
    Sanjay Wadhwa [mailto:swadhwa@juniper.net] <BR><B><SPAN=20
    style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> 30. april 2008 =
14:42<BR><B><SPAN=20
    style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Peter Arberg; Tina TSOU; =
Maglione=20
    Roberta; Wojciech Dec (wdec)<BR><B><SPAN=20
    style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B> ancp@ietf.org<BR><B><SPAN =

    style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [ANCP] question =
regarding=20
    Labels in ANCP port up messages</SPAN></FONT><o:p></o:p></P>
    <P><FONT face=3D"Times New Roman" size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt">Peter<BR>&nbsp; The ANCP draft as it =
currently=20
    stands is ba<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>d on RFC3292. It =
provides extensions=20
    and modifications to relevant constructs in RFC3292. There is no =
mention=20
    (implicit or explicit) of expired GSMP drafts in the ANCP draft. In =
order to=20
    implement the ANCP draft, I am not sure why one would look at the =
expired=20
    GSMP drafts. Do you <st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>e a reason to do this=20
    ba<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>d on anything that you =
read in the=20
    ANCP draft? Bringing up reference to expired gsmp draft in this=20
    thread&nbsp;just adds to the confusion. For GSMPv3 objects in the =
messages=20
    (such as Label Type), one has to look at RFC3292 (this is clearly =
stated in=20
    the ANCP draft - <st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>ction 2 and I am quoting =
it below)=20
    :</SPAN></FONT><o:p></o:p></P>
    <P><FONT face=3D"Times New Roman" color=3Dblue size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue">ANCP u<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>s a sub<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>t of GSMPv3 messages to =
implement=20
    currently defined u<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>-ca<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>s. The<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName> relevant GSMPv3 =
messages are=20
    identified in <st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>ction 5. GSMPv3 =
procedures with=20
    suitable extensions, as u<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>d by ANCP, are described =
in=20
    <st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>ctions 5.1, 5.2 and 5.3. =
GSMPv3=20
    general extensions and GSMPv3 message specific extensions required =
by ANCP=20
    are described in sub-<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>ctions of 5.4. In =
addition to=20
    specifying extensions and modifications to relevant GSMP messages =
applicable=20
    to ANCP, this draft also defines the usage of the<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName> messages by ANCP, and =
indicates the=20
    values that ANCP should <st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>t for relevant fields in =

    the<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName> GSMP messages. However, =
to=20
    understand the basic <st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>mantics of various =
fields in GSMP=20
    messages, the reader is referred to [4].&nbsp;=3D&gt; RFC=20
    3292.</SPAN></FONT><FONT size=3D2><SPAN style=3D"FONT-SIZE: =
10pt"><BR><BR>What=20
    existing implementations currently do is an important but =
<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>parate issue. =
The<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName> implementations for =
most part=20
    precede the current ANCP draft. It is fine to poll where =
the<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName> implementations diverge =
from the=20
    current draft. It is then upto the implementations (including the =
one that I=20
    am somewhat familiar with) to work towards compliance with the =
draft.=20
    </SPAN></FONT><o:p></o:p></P>
    <P><FONT face=3D"Times New Roman" size=3D2><SPAN style=3D"FONT-SIZE: =
10pt">On the=20
    following points&nbsp;from &nbsp;Woj:</SPAN></FONT><o:p></o:p></P>
    <P><FONT face=3D"Times New Roman" size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt">Woj&gt;2) The current version of the spec =
is not=20
    accurate, and does not reflect&nbsp;the fact that the known =
implementations=20
    follow the label field definition from =
draft-gsmpv3-ba<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 =
w:st=3D"on">se</st1:PersonName>-spec.</SPAN></FONT><o:p></o:p></P>
    <P><FONT face=3D"Times New Roman" size=3D2><SPAN style=3D"FONT-SIZE: =
10pt">It is=20
    not for the protocol draft to point out what current implementations =

    do.&nbsp;&nbsp;The best we can do is to further clarify in the draft =
that=20
    type and value fields of the Label object (defined in RFC3292) =
should be=20
    <st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>t to 0 in the port-up =
message (we=20
    already&nbsp;mention the lable object as a whole should be =
<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>t to all 0s).=20
    </SPAN></FONT><o:p></o:p></P>
    <P><FONT face=3D"Times New Roman" size=3D2><SPAN style=3D"FONT-SIZE: =
10pt">Woj&gt;=20
    This would be a good thing for the WG to discuss. There most =
evidently is a=20
    fair amount of&nbsp;"dead wood" in the current spec, ie stuff that =
nobody=20
    yet&nbsp;implements or cares about. &nbsp;In the former =
ca<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>, we could re-cast that =
material=20
    using the new notions/extensions, in the latter ca<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName> simply chop it=20
    out.</SPAN></FONT><o:p></o:p></P>
    <P><FONT face=3D"Times New Roman" size=3D2><SPAN style=3D"FONT-SIZE: =
10pt">I=20
    agree. We are ba<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>d on GSMPv3 (RFC3292)=20
    &nbsp;messages, and obviously not everything in the<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName> messages is leveraged =
by=20
    ANCP.&nbsp; However, the sync rate and OAM u<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>s-ca<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>s are implemented and in =

    u<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName> (ideally we should =
leave=20
    the<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName> alone...i.e. no change =
beyond=20
    adding more clarity if needed). For anything new (such as multicast) =
we are=20
    defining new messages&nbsp;(no legacy).&nbsp; =
</SPAN></FONT><o:p></o:p></P>
    <P><FONT face=3D"Times New Roman" size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt">-Sanjay<BR><BR>&gt;-----Original=20
    Message-----<BR>&gt;From: Peter Arberg [</SPAN></FONT><A=20
    href=3D"mailto:parberg@redback.com"><FONT size=3D2><SPAN=20
    style=3D"FONT-SIZE: =
10pt">mailto:parberg@redback.com</SPAN></FONT></A><FONT=20
    size=3D2><SPAN style=3D"FONT-SIZE: 10pt">]<BR>&gt;Sent: Wednesday, =
April 30,=20
    2008 3:56 PM<BR>&gt;To: Tina TSOU; Maglione Roberta; Sanjay Wadhwa; =
Wojciech=20
    Dec (wdec)<BR>&gt;Cc: ancp@ietf.org<BR>&gt;Subject: RE: [ANCP] =
question=20
    regarding Labels in ANCP port up=20
    messages<BR>&gt;<BR>&gt;<BR>&gt;Hi,<BR>&gt;<BR>&gt;some times I =
think it is=20
    amazing we ever got interoperability<BR>&gt;of ANCP=20
    :-)<BR>&gt;becau<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName> looking at the label =
discussion is=20
    a very good example that the<BR>&gt;whole GSMP - ANCP reference have =
not=20
    worked very well.<BR>&gt;<BR>&gt;In the ANCP draft, <st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>ction 5.4.2 the event =
message is=20
    shown like=20
    =
this:<BR>&gt;<BR>&gt;0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    3<BR>&gt;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=20
    =
1<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+<BR>&gt;|=20
    Vers&nbsp; |&nbsp; Sub&nbsp; | Message Type&nbsp; |=20
    Result|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Code&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
|<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+<BR>&gt;|=20
    Partition ID&nbsp;=20
    |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Transaction=20
    =
Identifier&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;=20
    =
|<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+<BR>&gt;|I|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    SubMessage Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;=20
    =
|<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+<BR>&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
Port&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
|<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+<BR>&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Port Session=20
    =
Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
|<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+<BR>&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Event Sequence=20
    =
Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
|<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+<BR>&gt;|x|S|x|x|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
|<BR>&gt;+-+-+-+-+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
Label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
|<BR>&gt;~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;=20
    =
~<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+<BR>&gt;|x|x|x|x|x|x|x|x|=20
    Message Type&nbsp; |&nbsp;&nbsp; Tech Type&nbsp;&nbsp; | Block =
Length&nbsp;=20
    =
|<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+<BR>&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;=20
    =
|<BR>&gt;~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;=20
    Extension=20
    =
Value&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
~<BR>&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;=20
    =
|<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+<BR>&gt;<BR>&gt;<BR>&gt;This=20
    is the exact same event message defined=20
    in<BR>&gt;draft-ietf-gsmp-v3-ba<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>-spec-08.txt&nbsp; =
<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>ction =
11.<BR>&gt;<BR>&gt;And in this=20
    gsmp-draft, <st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>ction 5.1.3 the label =
space is=20
    defined<BR>&gt;as minimum 8 bytes if the length=3D0 and as such no =
value, and=20
    this<BR>&gt;is becau<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName> the gsmp-draft has a =
new "label=20
    adaptaion" field.<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt;BUT in RFC3292 the =
event=20
    message is show in <st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>ction 9, like=20
    =
this:<BR>&gt;<BR>&gt;0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    3<BR>&gt;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=20
    =
1<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+<BR>&gt;|&nbsp;&nbsp;&nbsp;=20
    Version&nbsp;&nbsp;&nbsp; | Message Type&nbsp; |&nbsp;&nbsp;&nbsp;=20
    Result&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;=20
    Code&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
|<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+<BR>&gt;|=20
    Partition ID&nbsp;=20
    |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Transaction=20
    =
Identifier&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;=20
    =
|<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+<BR>&gt;|I|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    SubMessage Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;=20
    =
|<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+<BR>&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
Port&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
|<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+<BR>&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Port Session=20
    =
Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
|<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+<BR>&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Event Sequence=20
    =
Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
|<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+<BR>&gt;|x|S|x|x|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
|<BR>&gt;+-+-+-+-+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
Label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
|<BR>&gt;~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;=20
    =
~<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+<BR>&gt;<BR>&gt;<BR>&gt;So=20
    a different Event Message picture/definition than what is =
shown<BR>&gt;in=20
    the ANCP draft, and in RFC3292 <st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>ction 3.1.3 the label=20
    field<BR>&gt;is defined as 4 bytes if length=3D0 and as such no=20
    value.<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt;So I very much agree with Woj =
that we=20
    need this issue to be resolved,<BR>&gt;and proabably a show of hands =
what is=20
    actually done in different<BR>&gt;implementations, so we can nail =
down how=20
    the event message is<BR>&gt;suppo<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName> to look like in=20
    ANCP.<BR>&gt;<BR>&gt;<BR>&gt;I know at least 1 implementation which=20
    u<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>s 8 bytes for =
the<BR>&gt;label=20
    =
field.<BR>&gt;<BR>&gt;<BR>&gt;cheers,<BR>&gt;Peter<BR>&gt;<BR>&gt;<BR>&gt=
;<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt;________________________________<BR>&gt;=
<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    From: ancp-bounces@ietf.org<BR>&gt;[</SPAN></FONT><A=20
    href=3D"mailto:ancp-bounces@ietf.org"><FONT size=3D2><SPAN=20
    style=3D"FONT-SIZE: =
10pt">mailto:ancp-bounces@ietf.org</SPAN></FONT></A><FONT=20
    size=3D2><SPAN style=3D"FONT-SIZE: 10pt">] On Behalf Of Tina=20
    TSOU<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Sent: 30. =
april 2008=20
    00:19<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; To: Maglione =

    Roberta; Sanjay Wadhwa; Wojciech Dec=20
    (wdec)<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Cc:=20
    ancp@ietf.org<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Subject: Re:=20
    [ANCP] question regarding Labels in ANCP<BR>&gt;port up=20
    =
messages<BR>&gt;<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;=20
    Hi all,<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; It is =
clear to me=20
    that if Label Length is filled as 0,<BR>&gt;there is nothing to be =
filled=20
    into Label Value. The whole<BR>&gt;Label part is 4 bytes, not 8=20
    bytes.<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Cheers from=20
    the last working day before Labor's Day<BR>&gt;holidays in some=20
    =
countries:)<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
Tina<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    ----- Original Message=20
    =
-----<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    From: Wojciech Dec (wdec) &lt;</SPAN></FONT><A=20
    href=3D"mailto:wdec@cisco.com"><FONT size=3D2><SPAN=20
    style=3D"FONT-SIZE: =
10pt">mailto:wdec@cisco.com</SPAN></FONT></A><FONT=20
    size=3D2><SPAN=20
    style=3D"FONT-SIZE: =
10pt">&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    To: Sanjay Wadhwa &lt;</SPAN></FONT><A=20
    href=3D"mailto:swadhwa@juniper.net"><FONT size=3D2><SPAN=20
    style=3D"FONT-SIZE: =
10pt">mailto:swadhwa@juniper.net</SPAN></FONT></A><FONT=20
    size=3D2><SPAN style=3D"FONT-SIZE: 10pt">&gt;<BR>&gt; ; Maglione =
Roberta=20
    &lt;</SPAN></FONT><A =
href=3D"mailto:roberta.maglione@telecomitalia.it"><FONT=20
    size=3D2><SPAN=20
    style=3D"FONT-SIZE: =
10pt">mailto:roberta.maglione@telecomitalia.it</SPAN></FONT></A><FONT=20
    size=3D2><SPAN=20
    style=3D"FONT-SIZE: =
10pt">&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Cc:=20
    =
ancp@ietf.org<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Sent: Wednesday, April 30, 2008 1:12=20
    =
AM<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Subject: Re: [ANCP] question regarding Labels<BR>&gt;in ANCP port up =

    =
messages<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Sanjay,=20
    =
All,<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    What is stated below runs counter to at least<BR>&gt;a handful of=20
    =
ANCP<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    implementations, all of which are known to=20
    =
be<BR>&gt;interoperable.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    There are really two=20
    =
options:<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    1) The current version of the spec is correct,<BR>&gt;and the=20
    =
known<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    interoperable implementations do not follow=20
    =
it<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    2) The current version of the spec is not<BR>&gt;accurate, and does =
not=20
    =
reflect<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    the fact that the known implementations follow<BR>&gt;the label=20
    =
field<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    definition from draft-gsmpv3-ba<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0=20
    =
w:st=3D"on">se</st1:PersonName>-spec.<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    I would like to ask you, as the lead editor of<BR>&gt;the spec, to =
work=20
    =
with<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    the WG in resolving what the problem is, and<BR>&gt;clearing up what =
the=20
    =
WG<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    spec says about and if 1) holds to be true,<BR>&gt;then proposing=20
    =
an<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    interoperability=20
    =
fix.<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    In either ca<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>, the issue highlights =
the=20
    fact<BR>&gt;that there is=20
    =
still<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    lingering confusion as to the dependencies<BR>&gt;ANCP has on =
rfc3292,=20
    =
or<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    draft-gsmpv3-ba<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>-spec, or both. It =
<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>ems to<BR>&gt;be in the =
best=20
    interest=20
    =
of<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    all to address the<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0=20
    =
w:st=3D"on">se</st1:PersonName>.<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
Regards,<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
Woj.<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; -----Original=20
    =
Message-----<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; From: Sanjay Wadhwa [</SPAN></FONT><A=20
    href=3D"mailto:swadhwa@juniper.net"><FONT size=3D2><SPAN=20
    style=3D"FONT-SIZE: =
10pt">mailto:swadhwa@juniper.net</SPAN></FONT></A><FONT=20
    size=3D2><SPAN=20
    style=3D"FONT-SIZE: =
10pt">]<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; Sent: 29 April 2008=20
    =
17:29<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; To: Maglione=20
    =
Roberta<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; Cc: Wojciech Dec (wdec); ancp@ietf.org;<BR>&gt;Philippe =
Champagne=20
    =
(pchamp)<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; Subject: RE: question regarding Labels in<BR>&gt;ANCP port up=20
    =
messages<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; Hi=20
    =
Maglione<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;&nbsp;&nbsp; Yes, the label format is as defined in =
RFC<BR>&gt;3292. The=20
    ANCP draft=20
    =
is<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; ba<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>d on RFC 3292 and=20
    propo<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 =
w:st=3D"on">se</st1:PersonName>s<BR>&gt;extensions/modifications=20
    =
where<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
required.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; This is clearly stated upfront both in the<BR>&gt;abstract and=20
    =
in<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; <st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>ction 2.=20
    =
In<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; <st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>ction 5.4.2, it =
clearly&nbsp;=20
    specifies the<BR>&gt;format of "port up"=20
    =
message<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; (ba<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>d on RFC 3292), and =
explicitly=20
    states<BR>&gt;the label=20
    =
field<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; should be <st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0=20
    =
w:st=3D"on">se</st1:PersonName>t<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; to 0. Following is what the draft currently=20
    =
states:<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; 5.4.2 Topology Discovery=20
    =
Extensions<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; The GSMP Event message with PORT UP message<BR>&gt;type (80) is =

    u<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>d=20
    =
for<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; conveying DSL line attributes to the NAS.<BR>&gt;The version =
field=20
    should=20
    =
be<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; <st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>t to 3, and the sub =
field should be=20
    <st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>t to<BR>&gt;1. The I and =

    =
subMessage<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; fields SHOULD be <st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>t to 1 to signify=20
    no<BR>&gt;fragmentation. The Port=20
    =
and<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; Label fields should be <st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>t to=20
    =
0.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;&nbsp;=20
    =
0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
2&nbsp;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
3<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0 1 2 3 4 =
5 6 7 8=20
    9 0 1 2 3 4 5 6 7<BR>&gt;8 9 0 1 2 3 4=20
    =
5<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; 6 7 8 9 0=20
    =
1<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
&gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Vers&nbsp; =
|&nbsp;=20
    Sub&nbsp; | Message Type&nbsp;=20
    |<BR>&gt;Result|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
Code<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
&gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Partition =
ID&nbsp;=20
    =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&g=
t;Transaction=20
    =
Identifier<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
&gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    |I|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SubMessage=20
    Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    |&nbsp;&nbsp;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
Length<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
&gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;=20
    =
Port<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
&gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Port Session=20
    =
Number<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
&gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Event Sequence=20
    =
Number<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
&gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
|x|S|x|x|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
+-+-+-+-+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
Label<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
~<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
~<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
&gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|x|x|x|x|x|x|x|x|=20
    Message Type&nbsp; |&nbsp;&nbsp;<BR>&gt;Tech Type&nbsp;&nbsp; | =
Block=20
    =
Length<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
&gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =

    Extension=20
    =
Value<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
~<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
&gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; When we say the label field should be <st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>t to<BR>&gt;0, the=20
    =
intention<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; is for=20
    =
the<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; type and length fields in the label TLV to<BR>&gt;be =
<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>t to 0. We=20
    =
can<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; explicitly state this for=20
    =
clarity.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
-Sanjay<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;-----Original=20
    =
Message-----<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;From: Maglione Roberta<BR>&gt;[</SPAN></FONT><A=20
    href=3D"mailto:roberta.maglione@telecomitalia.it"><FONT =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: =
10pt">mailto:roberta.maglione@telecomitalia.it</SPAN></FONT></A><FONT=20
    size=3D2><SPAN=20
    style=3D"FONT-SIZE: =
10pt">]<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;Sent: Tuesday, April 29, 2008 8:06=20
    =
AM<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;To: Sanjay=20
    =
Wadhwa<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;Cc: Wojciech Dec (wdec);=20
    =
ancp@ietf.org;<BR>&gt;pchamp@cisco.com<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;Subject: RE: question regarding Labels in<BR>&gt;ANCP port =
up=20
    =
messages<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;Hi Sanjay and=20
    =
All,<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp; I was reading the current=20
    ancp<BR>&gt;protocol draft in order=20
    =
to<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt; understand which should be the correct<BR>&gt;format for =
the=20
    =
label<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;field in the ancp port Up=20
    =
message.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;Actually as it was already pointed out in<BR>&gt;the alias =
the=20
    =
draft<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;in <st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>ction 5.4.2 says "GSMP =
Event=20
    message<BR>&gt;with PORT UP=20
    =
message<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;type (80) is u<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>d"&nbsp; thus I am =
assuming=20
    that<BR>&gt;the label in=20
    =
the<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;port UP message should follow the message<BR>&gt;format =
defined=20
    =
in<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;RFC 3292, <st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>ction=20
    =
3.1.3:<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;=20
    =
0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt;2&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;=20
    =
3<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp; 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 =
9<BR>&gt;0=20
    1 2 3 4 5 6 7 8 9 0=20
    =
1<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
&gt;&nbsp;&nbsp;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp; |x|S|x|x|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Label=20
    Type&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt;&nbsp; Label=20
    Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
&gt;&nbsp;&nbsp;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;=20
    =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;=20
    =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;=20
    =
~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;=20
    Label=20
    =
Value&nbsp;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;=20
    =
~<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;=20
    =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;=20
    =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
&gt;&nbsp;&nbsp;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;but from what I have <st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>en =
different<BR>&gt;implementations=20
    u<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0=20
    =
w:st=3D"on">se</st1:PersonName><BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;different format for label field: in<BR>&gt;particular=20
    <st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0=20
    =
w:st=3D"on">se</st1:PersonName>veral<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;implementations u<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>&nbsp; a label format =
that=20
    is<BR>&gt;similar to the=20
    =
one<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;specified in the expired=20
    draft<BR>&gt;draft-ietf-gsmp-v3-ba<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0=20
    =
w:st=3D"on">se</st1:PersonName>-spec:<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt;=20
    =
2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
3<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0 1 2 3 4 5 6 7 8 9 0 =
1 2 3 4=20
    5 6 7<BR>&gt;8 9 0 1 2 3 4 5=20
    =
6<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; 7 8 9 0=20
    =
1<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
&gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
|x|S|x|x|x|x|x|x|x|x|x|x|x|x|x|x|&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
Label<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; Type&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
&gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp; Label=20
    =
Adaptation&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    |&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
Label<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
&gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;=20
    Label=20
    =
Value<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
~<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
&gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;Even if ancp does not care about the label<BR>&gt;field, =
having=20
    =
this<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;field somehow not clearly specified in the<BR>&gt;current =
ancp=20
    =
draft<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;can easily lead to interoperability issues,<BR>&gt;thus I =
think=20
    =
it<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;would be very helpful if you and/or the<BR>&gt;other =
editors=20
    =
can<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;clarify what should be the correct format<BR>&gt;for the =
label=20
    =
field<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;to be u<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>d in the ancp Port Up=20
    =
message.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;Thanks and best=20
    =
regards,<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
&gt;Roberta<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
&gt;________________________________________<BR>&gt;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;From: Philippe Champagne (pchamp)=20
    =
[pchamp@cisco.com]<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;Sent: Thursday, April 24, 2008 7:14=20
    =
PM<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;To: Sanjay=20
    =
Wadhwa<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;Cc: Maglione Roberta; Wojciech Dec=20
    =
(wdec);<BR>&gt;ancp@ietf.org<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;Subject: question regarding&nbsp; Labels in =
ANCP<BR>&gt;port up=20
    =
messages<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;Hi=20
    =
Sanjay<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;In <st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>ction 5.4.2 of the =
draft, we=20
    =
have:<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
2<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
3<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0 1 2 3 4 =
5 6 7 8=20
    9 0 1 2 3 4 5 6<BR>&gt;7 8 9 0 1 2 3 4 5=20
    =
6<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;7 8 9 0=20
    =
1<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
&gt;<BR>&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Vers&nbsp; =
|&nbsp;=20
    Sub&nbsp; | Message Type&nbsp;=20
    |<BR>&gt;Result|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
Code<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
&gt;<BR>&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Partition =
ID&nbsp;=20
    =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&g=
t;Transaction=20
    =
Identifier<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
&gt;<BR>&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    |I|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SubMessage=20
    Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    |&nbsp;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
Length<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
&gt;<BR>&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;=20
    =
Port<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
&gt;<BR>&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Port Session=20
    =
Number<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
&gt;<BR>&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Event Sequence=20
    =
Number<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
&gt;<BR>&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
|x|S|x|x|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
+-+-+-+-+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
Label<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
~<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
~<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
&gt;<BR>&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|x|x|x|x|x|x|x|x|=20
    Message Type&nbsp; |&nbsp;&nbsp;<BR>&gt;Tech Type&nbsp;&nbsp;=20
    =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;Block Length&nbsp;=20
    =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
&gt;<BR>&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =

    Extension=20
    =
Value<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
~<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
&gt;<BR>&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;Where Label I suppo<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName> is taken from the =
RFC<BR>&gt;3292,=20
    <st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0=20
    =
w:st=3D"on">se</st1:PersonName>ction<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;3.1.3: (well, I'm=20
    =
guessing)<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp; A summary of TLV labels supported =
in<BR>&gt;this=20
    version of=20
    =
the<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; protocol=20
    =
is<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp; listed=20
    =
below:<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; TLV=20
    Label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Type&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Section=20
    =
Title<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    ---------&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    ----&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
-------------<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ATM=20
    Label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
0x100&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ATM=20
    TLV=20
    =
Labels<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; FR=20
    Label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    0x101&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Frame Relay<BR>&gt;TLV=20
    =
Labels<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MPLS Gen Label=20
    0x102&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MPLS<BR>&gt;Generic TLV=20
    =
Labels<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; FEC=20
    Label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
0x103&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; FEC=20
    TLV=20
    =
Labels<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp; All Labels will be designated as=20
    =
follow:<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;=20
    =
0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt;2&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;=20
    =
3<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp; 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 =
9<BR>&gt;0=20
    1 2 3 4 5 6 7 8 9 0=20
    =
1<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
&gt;&nbsp;&nbsp;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp; |x|S|x|x|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Label=20
    Type&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt;&nbsp; Label=20
    Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
&gt;&nbsp;&nbsp;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;=20
    =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;=20
    =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;=20
    =
~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;=20
    Label=20
    =
Value&nbsp;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;=20
    =
~<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;=20
    =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;=20
    =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
&gt;&nbsp;&nbsp;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; x: Re<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>rved=20
    =
Flags.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
The<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName> are generally =
u<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>d by<BR>&gt;specific =
messages and=20
    will=20
    =
be<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; defined in =

    tho<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>=20
    =
messages.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; S: Stacked Label=20
    =
Indicator<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Label =
Stacking is=20
    discus<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>d below<BR>&gt;in =
<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>ction=20
    =
3.1.3.5<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Label=20
    =
Type<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A 12-bit =
field=20
    indicating the type<BR>&gt;of=20
    =
label.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Label=20
    =
Length<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A 16-bit =
field=20
    indicating the<BR>&gt;length of the=20
    =
Label<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; Value=20
    =
field<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; in=20
    =
bytes.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Label=20
    =
Value<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A variable =
length=20
    field that is an<BR>&gt;integer number of 32=20
    =
bit<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; words =
long.&nbsp;=20
    The Label Value field<BR>&gt;is=20
    =
interpreted<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; according=20
    =
to<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the Label =
Type as=20
    described in the<BR>&gt;following <st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0=20
    =
w:st=3D"on">se</st1:PersonName>ctions.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;The draft is a bit obscure about this and<BR>&gt;since it=20
    =
doesn't<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;specify much, it can lead to<BR>&gt;misinterpretation for =
the=20
    unu<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0=20
    =
w:st=3D"on">se</st1:PersonName>d<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;part. Moreover, it would appear that<BR>&gt;<st1:PersonName =

    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>veral=20
    =
implementations<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;currently u<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName> another format for the=20
    label<BR>&gt;field. Can=20
    =
you<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;explain?&nbsp; I mean, how come what's in =
the<BR>&gt;current draft=20
    =
doesn't<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;match what's known to be=20
    =
implemented?<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;I'm still wondering why we carried over<BR>&gt;pieces from =
GSMP=20
    =
that<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;we do not intend to u<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0=20
    =
w:st=3D"on">se</st1:PersonName>.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;I would recommend that if we are to keep<BR>&gt;them but =
not=20
    u<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0=20
    =
w:st=3D"on">se</st1:PersonName><BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;them, we should mention preci<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>ly how we<BR>&gt;intend =
not to=20
    u<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0=20
    =
w:st=3D"on">se</st1:PersonName><BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;them: that is how many 0 filled bytes this<BR>&gt;is =
expected to=20
    u<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0=20
    =
w:st=3D"on">se</st1:PersonName><BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;The rfc 3292 doesn't cover the ca<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName> where<BR>&gt;this field =
is not=20
    u<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0=20
    =
w:st=3D"on">se</st1:PersonName>d.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;Can you shed some ligths on=20
    =
this?<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
&gt;Thanks<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
&gt;Regards<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
&gt;Phil<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
&gt;<BR>&gt;&gt;---------------------------------------------------------=
-----------<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;CONFIDENTIALITY=20
    =
NOTICE<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;This message and its attachments =
are<BR>&gt;addres<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>d solely to=20
    =
the<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;persons above and may contain =
confidential<BR>&gt;information. If=20
    =
you<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;have received the message in error, be<BR>&gt;informed that =
any=20
    u<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0=20
    =
w:st=3D"on">se</st1:PersonName><BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;of the content hereof is prohibited. Plea<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName><BR>&gt;return=20
    =
it<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;immediately to the <st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>nder and delete =
the<BR>&gt;message.=20
    Should=20
    =
you<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;have any questions, plea<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName> contact us by replying=20
    =
to<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
&gt;webmaster@telecomitalia.it.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Thank=20
    =
you<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;<BR>&gt;www.telecomitalia.it<BR>&gt;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =

    &gt;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
&gt;<BR>&gt;&gt;---------------------------------------------------------=
-----------<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    &gt;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
_______________________________________________<BR>&gt;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =

    ANCP mailing=20
    =
list<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
ANCP@ietf.org<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    </SPAN></FONT><A href=3D"https://www.ietf.org/mailman/listinfo/ancp" =

    target=3D_blank><FONT size=3D2><SPAN=20
    style=3D"FONT-SIZE: =
10pt">https://www.ietf.org/mailman/listinfo/ancp</SPAN></FONT></A><BR><FO=
NT=20
    size=3D2><SPAN style=3D"FONT-SIZE: 10pt">&gt;<BR>&gt;</SPAN></FONT>=20
    <o:p></o:p></P></BLOCKQUOTE></DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C8AF71.41687A2C--

--===============0840661864==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============0840661864==--


From ancp-bounces@ietf.org  Tue May  6 09:34:00 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 33B7128C3E2;
	Tue,  6 May 2008 09:34:00 -0700 (PDT)
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 0081028C23E
	for <ancp@core3.amsl.com>; Tue,  6 May 2008 09:33:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.998
X-Spam-Level: 
X-Spam-Status: No, score=-3.998 tagged_above=-999 required=5
	tests=[BAYES_50=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 0mTiCtKVD9Ej for <ancp@core3.amsl.com>;
	Tue,  6 May 2008 09:33:52 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id 66B7F28C21B
	for <ancp@ietf.org>; Tue,  6 May 2008 09:33:49 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,444,1204498800"; d="scan'208,217";a="8174157"
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 06 May 2008 18:33:46 +0200
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m46GXkQx016135; 
	Tue, 6 May 2008 18:33:46 +0200
Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com
	[144.254.231.71])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m46GXkGl001471;
	Tue, 6 May 2008 16:33:46 GMT
Received: from xmb-ams-33b.cisco.com ([144.254.231.86]) by
	xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 6 May 2008 18:33:46 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 6 May 2008 18:33:28 +0200
Message-ID: <D9872168DBD43A41BD71FFC4713274D40504372B@xmb-ams-33b.emea.cisco.com>
In-Reply-To: <9BD5D7887235424FA97DFC223CAE3C28102EAC9B@proton.jnpr.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ANCP] Mandatory TLVs in draft-ietf-ancp-protocol proposal
thread-index: AcilQRMfK4kdawUKQOWs5fdBngS8QQAAr04QACRhApAAC0ujAADNHRywAADiEXAAAbhxoAAAWwcQACIOoKAAAXsqYAASvbCgAAE4sjAAASS6UAABRQpQABPWDgABARaTgA==
References: <1B6169C658325341A3B8066E23919E1C01230DC1@S4DE8PSAANK.mitte.t-com.de><1B6169C658325341A3B8066E23919E1CFBC5C4@S4DE8PSAANK.mitte.t-com.de><D9872168DBD43A41BD71FFC4713274D404FA6ACC@xmb-ams-33b.emea.cisco.com><7A6D4815C5E8F74988784FEBD50F2F1E01ABAA16@FRVELSMBS22.ad2.ad.alcatel.com><D9872168DBD43A41BD71FFC4713274D404FF10C1@xmb-ams-33b.emea.cisco.com><7A6D4815C5E8F74988784FEBD50F2F1E01ABAAA4@FRVELSMBS22.ad2.ad.alcatel.com><D9872168DBD43A41BD71FFC4713274D404FF1233@xmb-ams-33b.emea.cisco.com><7A6D4815C5E8F74988784FEBD50F2F1E01ABAC34@FRVELSMBS22.ad2.ad.alcatel.com><D9872168DBD43A41BD71FFC4713274D404FF13AD@xmb-ams-33b.emea.cisco.com><48C276B536524E478C659685995F6AA539DBB4F194@RBSJX.ad.redback.com><D9872168DBD43A41BD71FFC4713274D404FF172D@xmb-ams-33b.emea.cisco.com><48C276B536524E478C659685995F6AA539DBB4F25F@RBSJX.ad.redback.com>
	<D9872168DBD43A41BD71FFC4713274D404FF1751@xmb-ams-33b.emea.cisco.com>
	<9BD5D7887235424FA97DFC223CAE3C28102EAC9B@proton.jnpr.net>
From: "Wojciech Dec (wdec)" <wdec@cisco.com>
To: "Sanjay Wadhwa" <swadhwa@juniper.net>,
	"Peter Arberg" <parberg@redback.com>,
	"DE CNODDER Stefaan" <stefaan.de_cnodder@alcatel-lucent.be>,
	"Busser, M" <Michael.Busser@t-systems.com>, <ancp@ietf.org>
X-OriginalArrivalTime: 06 May 2008 16:33:46.0122 (UTC)
	FILETIME=[F4736EA0:01C8AF96]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=190171; t=1210091626;
	x=1210955626; c=relaxed/simple; s=amsdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=wdec@cisco.com;
	z=From:=20=22Wojciech=20Dec=20(wdec)=22=20<wdec@cisco.com>
	|Subject:=20RE=3A=20[ANCP]=20Mandatory=20TLVs=20in=20draft-
	ietf-ancp-protocol=20proposal |Sender:=20;
	bh=Fx4rqsZqw7L3TqPyr0Ctccy1iC7E5dW9uJ0ZtVuqCHI=;
	b=rUS4rDVX3TeDkMTiQGEZERGbe3zi1SEOHQEZ0/2s464abhtcObxpYV/rc3
	hfovJ/b04HoqzKCQ0VEV5/K23Y5I3pmK6cZ0fn5a2J+IypW+qJ06Y237vILY
	2x6eDJcC5X;
Authentication-Results: ams-dkim-2; header.From=wdec@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim2001 verified; ); 
Cc: "Haag, T" <Thomas.Haag@t-systems.com>
Subject: Re: [ANCP] Mandatory TLVs in draft-ietf-ancp-protocol proposal
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/pipermail/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>
Content-Type: multipart/mixed; boundary="===============1152964927=="
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1152964927==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8AF96.F40D1A81"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8AF96.F40D1A81
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Sanjay,
=20
Inline.... Woj#2


________________________________

	From: Sanjay Wadhwa [mailto:swadhwa@juniper.net]=20
	Sent: 30 April 2008 07:40
	To: Wojciech Dec (wdec); Peter Arberg; DE CNODDER Stefaan; Busser, M; =
ancp@ietf.org
	Cc: Haag, T
	Subject: RE: [ANCP] Mandatory TLVs in draft-ietf-ancp-protocol proposal
=09
=09

	Woj

	  I agree only on the following:

	=20

	1.	A TLV might be mandatory for one application or use-case, and =
optional for another application. We do need to clearly specify in the =
draft if a TLV is mandatory or optional for a given application (which =
boils down to specifying this per ANCP message and message type).=20

	=20
	Woj#2> I interpret this to mean that you've taken on the action to =
clarify the protocol spec text, and also prepare the table of TLVs =
indicating where each TLV is mandatory, and where optional. Please let =
me know if this is not so
	=20

	1.	We should clearly specify the behavior for handling missing =
mandatory TLVs in received messages.=20

	=20

	To me the utility of flagging a TLV as mandatory or optional via the =
protocol is at best debatable.  If a buggy implementation on the sender =
incorrectly sets a "known" TLV as mandatory (when it is not) or =
vice-versa, do we want the receiver to infer the handling of this TLV =
based on what the sender tells it? I don't think so. Ideally, we want =
the receiver and sender to have a common understanding of what is =
mandatory and what is optional based on what is in the spec, and handle =
the TLV based on that understanding. As Peter mentions, the spec clearly =
spells out TLVs that are mandatory and optional. Also, I don't see a =
major advantage of your proposal with respect to debuggability.=20

	=20

	=20

	Typical case where it does make sense for the sender to set some flag =
in the TLV to control the handling of the TLV on the receiver is for =
"unrecognized" TLV types...e.g.

	1.	Receiver is an intermediate node, which consumes the message but =
also needs to forward it along to other nodes. Here the sender can flag =
the handling of the TLV to the receiver (e.g. discard or forward if the =
TLV type is not recognized by the receiver). This doesn't quite apply to =
ANCP (messages are confined to be between two peers). =20

	=20
	Woj#2> It happens that an ANCP relay has already been proposed in the =
DSL Forum, and under in some situations it could be a viable entity. By =
NOT designing such flags now, we're likely making things more difficult =
in the future. Anyway, since there doesn't seem to be much enthusiasm =
for "Mandatory" flags, I'll put the subject to rest for now.

	=20

	2.	If handling of an unrecognized TLV on the receiver needs to be =
different for an optional TLV versus a mandatory TLV. Here the receiver =
doesn't understand the TLV type, but can infer the handling based on the =
flag in the TLV. However, do we want the treatment of "unrecognized" =
TLVs on the receiver to be different for optional and mandatory TLVs =
(e.g. silently discard an unrecognized optional TLV...but discard and =
also send an error back for an unrecognized mandatory TLV). I don't =
think this is necessary. However, if we do want to do this, then may be =
the flag in the TLV should explicitly indicate the handling for the TLV =
(e.g. "silently discard if un-recognized" versus "discard and send an =
error back")...as opposed to just flagging these as "mandatory" versus =
"optional". =20

	=20

	Woj> Of course it is, the whole spec is about this. The problem comes =
when people start to re-use well known TLVs for different applications, =
and then trying to make sense of it all >becomes non-trivial. Why do you =
think both BGP and Diamater, and a number of other protocols have =
definied "Mandatory" flags? Just for kicks? It's a well known protocol =
design tool, that >comes handy when re-using same data across multiple =
applications.

	=20

	We should look at why these protocols are doing this (as opposed to =
blindly following). For a counter example, please take a look at OSPF =
traffic engineering extensions (RFC 3630). =20

	=20

	Woj #2 >  The irony of the above statement in view of  the initiators =
of ANCP blindly following GSMP is hopefully not lost on you. On the =
Mandatory Flag aspect, there is one key reason why any protocol does; it =
is to offload the application from doing base data-element checking. =
Anyway, we can move on.

	=20

	-Woj.

	=20

	=20

	=20

	=20

	Cheers

	-Sanjay

	=20

=09
________________________________


	From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of =
Wojciech Dec (wdec)
	Sent: Tuesday, April 29, 2008 3:03 PM
	To: Peter Arberg; DE CNODDER Stefaan; Busser, M; ancp@ietf.org
	Cc: Haag, T
	Subject: Re: [ANCP] Mandatory TLVs in draft-ietf-ancp-protocol proposal

	=20

	Hi Peter,

	=20

	continued inline...

		=20

	=09
________________________________


		From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf =
Of Peter Arberg
		Sent: 29 April 2008 20:39
		To: Wojciech Dec (wdec); DE CNODDER Stefaan; Busser, M; ancp@ietf.org
		Cc: Haag, T
		Subject: Re: [ANCP] Mandatory TLVs in draft-ietf-ancp-protocol =
proposal

		Hi Woj,

		=20

		please see inline in your answers

		=20

			=20

		=09
________________________________


			From: Wojciech Dec (wdec) [mailto:wdec@cisco.com]=20
			Sent: 29. april 2008 11:07
			To: Peter Arberg; DE CNODDER Stefaan; Busser, M; ancp@ietf.org
			Cc: Haag, T
			Subject: RE: Re: [ANCP] Mandatory TLVs in draft-ietf-ancp-protocol =
proposal

			Hi Peter,

			=20

			=20

				=20

			=09
________________________________


				From: Peter Arberg [mailto:parberg@redback.com]=20
				Sent: 29 April 2008 19:34
				To: Wojciech Dec (wdec); DE CNODDER Stefaan; Busser, M; =
ancp@ietf.org
				Cc: Haag, T
				Subject: RE: Re: [ANCP] Mandatory TLVs in draft-ietf-ancp-protocol =
proposal

				Hi Woj,

				=20

				I agree with Michael and Stefan on this issue, I do not see a need =
to change the existing

				implementation with a mandatory/optional flag.=20

				=20

				Woj> Please indicate where in my proposal did you see anything about =
changing existing implementaions? =20

				=20

		PAR>  I might have misunderstood your email, but I read it as if you =
suggest a high bit

		value in existing TLV's to be interpreted as a mandatory flag.=20

		=20

		Woj#2> Yes, I suggested (in proposal 2) that *if* the WG found there =
to be a common set of TLVs currently in use, then the high-order bit set =
to "0" (ie as today) could be interpreted as "mandatory", and the rest =
of the TLV's redefined with a high order "1". To extsing =
implementations, the "new" TLVs would just look like a different TLV#, =
while anyone wishing to implement the more robust error cheking logic =
based on this bit, would be free to do so.=20

		=20

		If you are simply talking about new capability type definitions, then =
why do you not bring up

		the additional flag in a new internet-draft defining what capability =
type you have in mind ?=20

		=20

		Woj#2> No, a new capability was not intended, but could also be =
considered.

		=20

				=20

				I think I understand your arguments, but I do not agree with them. I =
think most places in

				the draft it is clear what is defined as mandatory and optional.=20

				=20

				I agree on the point we need to go through the draft and make =
clarifications to what TLV's

				in what capability types are mandatory and optional, and make more =
description what should

				happen if mandatory TLVs are not included.=20

				=20

				Woj> Exactly.=20

				=20

				I think the DSLF TR-101 document has a good example of such a =
description in it's=20

				"Table 3 - Access loop characteristics sub-options", and I think if =
we do the same for each

				capability types TLV's in the ANCP draft it will be a good help.

				=20

				Woj> Indeed, pre-ceeded by some rationalization. The appears to be =
no reason for some of the DSLF "mandatory" TLVs.=20

				=20

		PAR> I do not see a problem with re-visit in the draft if a TLV should =
be optional or mandatory, so if

		that is the intend, then I'm all for an email discussion on a TLV by =
TLV basis if we think it is a=20

		manfdatory or optional information inside the specific capability =
type.=20

		=20

		Woj#2> Great, because any change to the mandated set *will* affect =
existing implementation .

		=20

				=20

				=20

				I do not agree with your point that it is not listed if "rate" is =
mandatory or optional, it is clearly

				listed as a mandatory TLV, and as such it should be included in the =
port up message, I really

				do not understand what confusion you have with this.=20

				=20

				Woj> The text states:  =20

				=20

				5. Type (DSL Line Attributes =3D 0x04):=20

				Length : variable (up to 1024 bytes)=20

				Value : This consists of one or more Sub-TLVs corresponding to DSL=20

				line attributes. No sub-TLVs other than the "DSL type" and "DSL=20

				line state" SHOULD be included in a PORT DOWN message.=20

				The general format of the sub-TLVs is identical to the general TLV=20

				format. The value field in each sub-TLV is padded to a 4-octet=20

				alignment. The Length field in each sub-TLV contains the actual=20

				number of bytes in the TLV (not including the padding if present).=20

				Current defined sub-TLV types are start from 0x81. =20

				Maybe you can point me to where exatly it is stated clearly as being =
mandatory, or otherwise explain why you "not agree"? =20

				=20

		PAR> I think you forgot to read the most important part where the =
actual TLV is defined.=20

		=20

		Woj#2> I didn't. This part talks about the sub-TLV, not the main TLV =
0x04. Do you see my point now?

		=20

		=20

		Type (Actual-Net-Data-Upstream =3D 0x81): Actual upstream net data =
rate on a DSL line.=20

		This is a mandatory TLV. =20

		=20

		Length  :  (4 bytes)=20

		Value   : (Rate in Kb/sec)=20

		=20

		Type (Actual-Net-Data-Rate-Downstream =3D 0x82) : Actual downstream =
net data rate on a DSL line.=20

		This is a mandatory TLV.=20

		=20

		Length :  (4 bytes)=20

		Value  :  (Rate in Kb/sec)=20

		=20

				=20

				The fact you say "Port UP" and "OAM" is best considered as legacy =
applications, I have some

				trouble with this as well, since ANCP running in production networks =
use them, and as such

				it is a central part of the ANCP specifications we need to finish as =
soon as possible.=20

				=20

				Woj> I should have said legacy applications from a protocol =
messaging perspective, not usage, nor support. It's quite clear that =
GSMP derived messaging has baggage that is un called for in new =
applications.

				=20

				I think Stefaan's example is very valid, that we do not need to make =
mandatory requirements to=20

				what receivers of ANCP information use such info. for.  I don't =
think we should try and make the

				ANCP specifications "mandatory" for box behavior, I think it is much =
more important for the=20

				working group to make the protocol specifications easy to understand =
and get the first documentation

				finish and published, so the protocol can be used for different sets =
of applications, and make sure

				new applications can be added later.=20

				=20

				Woj> Indeed the aim of the WG to define a protocol that is =
relatively simple and easy to understand, not just to implementers but =
also to people using it, and across vendors. Currently, having anyone =
operating the device be familiar in what cases a TLV is mandatory and in =
what optional requires a thorough understanding of the spec, across =
applications. This is not easy, but I'll conceede that for the =
applications implemented so far we could live with it.=20

				=20

				I do think that by documenting if a TLV is mandatory or optional =
inside a specific capability type,

				it is easy to understand what must be sent to support the defined =
application/capability type.=20

				=20

				Woj> Of course it is, the whole spec is about this. The problem =
comes when people start to re-use well known TLVs for different =
applications, and then trying to make sense of it all becomes =
non-trivial. Why do you think both BGP and Diamater, and a number of =
other protocols have definied "Mandatory" flags? Just for kicks? It's a =
well known protocol design tool, that comes handy when re-using same =
data across multiple applications.=20

				=20

		PAR> I might be wrong, but I think I can find as many or more protocol =
examples who do not include

		a mandatory/optional flag, so examples can always be found which will =
support the point you are trying

		to make.

		=20

		I do not see a problem with a new internet-draft which defines new =
capability-types and where a TLV

		mandatory flag is included, I do see a problem if the intend is to try =
and adjust what already exist. =20

		=20

		Woj#2> Ok, so if adjusting is only scoped to what doesn't exist, as my =
proposal laid out conditionally, you're fine.

		=20

				=20

				=20

				Then if anybody want to include new capability types or sub-TLVs =
later to address specific applications,

				then I think changes can be discussed at that time instead of trying =
to change existing protocol

				implementations.=20

				=20

				Woj> Again I ask, where in the proposal did you see *anything* =
requiring a change to an existing implementation. Please be specific. I =
see that your main objection is on this issue, which means that you =
accept proposal 1 (have such a flag for new TLVs/apps).

				It would also be useful if you indicated whether the list of TLVs =
provided below is what you'd expect to be the minimum mandatory set.=20

				=20

		PAR> at the moment I read the draft as having defined the TLVs =
mandatory as you describe, except

		I also read it as the dsl-type =3D 0x91 must be part of the port down. =
If this is needed or not is a different

		discussion.

		=20

		=20

		Woj#2> Ok. Thanks. But please do come back to me if you see that the =
proposal impacts an exiting implementation. I conclude that there is no =
problem with doing changes to stuff that isn't currently used.

		Woj.

		=20

		cheers,

		Peter=20

				=20

				Cheers,

				Woj.

				=20

				cheers,

				Peter

				=20

				=20

				=20

					=20

				=09
________________________________


					From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On =
Behalf Of Wojciech Dec (wdec)
					Sent: 29. april 2008 02:28
					To: DE CNODDER Stefaan; Busser, M; ancp@ietf.org
					Cc: Haag, T
					Subject: Re: [ANCP] Mandatory TLVs in draft-ietf-ancp-protocol =
proposal

					Stefaan,

					=20

					a number of points:

					1. There currently is to my knowledge no implementation of ANCP =
there that doesn't send the DSL Line attributes info by default in =
Port-UP messages? The support of HS on the NAS is an orthogonal issue.

					2. The current ancp protocol draft (02) doesn't say whether the =
rate info is optional or mandatory, it only states that the sub-TLVs are =
mandatory. Based on this, an implementer can be justified to expect =
port-ups to *always* have the rate-info tlv (ie treat them as =
mandatory). Equally, she's justified in considering this  as optional.

					3. The port-up and OAM are best considered as legacy applications =
for ANCP. The re-use of any of the GSMP defined fields is already out of =
the question due to constrains put in place by the existing use-case =
messaging. Needless to say, this wasn't as thoroughly designed as it =
should have been, and with the OAM and port-up apps being coupled.

					4. It's up to the application to define what TLVs are mandatory and =
which aren't, as you also state. The AN does not need to know what the =
NAS will do with the info, BUT it needs to send the right TLVs for the =
application (eg if we had a hypothetical AN that only sends Port-up's =
with line-id, it would be next to useless for the dynamic shaping =
application).

					=20

					With all this in mind it's useful to re-read what I proposed =
originally below regarding the mandatory flag: 1. "have this TLV Flag be =
defined only for new applications" and 2. The notion of the mandatory =
flag applying to existing TLVs  being "conditional on deriving a =
suitable "commonly used" TLV set." The latter point would ensure that =
existing implementations do not need to change, but future ones can take =
advantage of the extra robustness.

					=20

					Hence, can the WG derive a set of commonly used, i.e. always used, =
TLVs for existing implementations?

					The list I came up is as follows (making them pretty much mandatory =
TLVs if it agrees with the views of others);

					=20

					Port-up message (0x80);

					    Extension-TLV (dsl tech type)

					    Access-Loop-circuit-id (0x01)

					    DSL Line Attribute (0x04) with the following sub TLVs;

					        DSL-Type =3D 0x91; Actual-Net-Data-Upstream =3D 0x81; =
Actual-Net-Data-Rate-Downstream =3D 0x82

					=20

					Port-down message (0x81);

					    Extension  TLV (dsl tech type)

					    Access-Loop-circuit-id (0x01)

					    DSL Line Attribute (0x04) with the following sub TLVs;

					        DSL line state =3D 0x8F

					=20

					All other TLVs are optional.

					=20

					Would appreciate confirmation from the WG regarding the above.

					=20

					Thanks,

					Woj.

					=20

					=20

				=09
________________________________


					From: DE CNODDER Stefaan =
[mailto:stefaan.de_cnodder@alcatel-lucent.be]=20
					Sent: 29 April 2008 09:52
					To: Wojciech Dec (wdec); Busser, M; ancp@ietf.org
					Cc: Haag, T
					Subject: RE: [ANCP] Mandatory TLVs in draft-ietf-ancp-protocol =
proposal

					=20

					Hi Woj,

					=20

					Take the following example: I have a network with 2 NASses, NAS-A =
is doing hierarchical shaping, NAS-B just wants to have the port =
information but is not doing hierarchical shaping (it is doing other =
things like OAM, ...).  This means NAS-A needs the bandwidth, while =
NAS-B does not need the bandwidth.  How should the flag be set in this =
case by the AN?  Set to 'Mandatory' for the port up messages to NAS-A, =
and set to 'Optional' for port up messages towards NAS-B? Or is it =
always set to 'Mandatory'?  From your answer below, I understand that it =
should be set to 'Optional' towards NAS-B.  Is that correct?

					=20

					NAS-B will simply ignore the bandwidth TLV.  If such a flag would =
exist, and the flag is set to 'Mandatory' by the AN to NAS-B, what =
should be the behavior of NAS-B?  Should it reject the whole message?  =
Maybe NAS-B is not supporting hierarchical shaping, so it might not =
support the bandwidth TLV.  Today, the bandwidht TLV is only mandatory =
to be put in the port up messages, but for the receiver there is nothing =
mandatory.

					=20

					I believe the original intend of ANCP was that the AN does not need =
to know what the NAS is doing with this information, the use of the =
bandwidth is also not specified by ANCP, only an example is given (which =
is shaping).  In the future there may be applications for which TLVs =
will be mandatory which are now optional.

					=20

					regards,

					Stefaan

					=20

					=20

					=20

					=20

				=09
________________________________


					From: Wojciech Dec (wdec) [mailto:wdec@cisco.com]=20
					Sent: maandag 28 april 2008 21:33
					To: DE CNODDER Stefaan; Busser, M; ancp@ietf.org
					Cc: Haag, T
					Subject: RE: [ANCP] Mandatory TLVs in draft-ietf-ancp-protocol =
proposal

					=20

					=20

				=09
________________________________


					From: DE CNODDER Stefaan =
[mailto:stefaan.de_cnodder@alcatel-lucent.be]=20
					Sent: 28 April 2008 17:15
					To: Wojciech Dec (wdec); Busser, M; ancp@ietf.org
					Cc: Haag, T
					Subject: RE: [ANCP] Mandatory TLVs in draft-ietf-ancp-protocol =
proposal

					=20

					Take the bandwidth sub-TLV in port up messages as example.  The =
current protocol spec says that it is mandatory to be sent in port up =
messages.  that's ok.  But it is not mandatory for the receiver to =
process the bandwidth sub-TLV.  What is done with this information by =
the NAS is not specified by ANCP, so you cannot make it mandatory for =
the receiver side.=20

					=20

					Woj> Is the information required by the application? It would =
appear for the dynamic shaping use-case to be most certainly so. Hence =
it is absolutely mandatory, otherwise the message makes no sense for the =
application. In any case, if=20

					=20

					So it looks to me that the flag can only indicate what the receiver =
should do.  Then the flag makes sense.=20

					=20

					Woj>  The flag tells the receiver what info the sender thinks is =
required to carry out the application. This in almost all cases has to =
match up to what the receiver thinks is required. The sender doesn't =
tell the receiver what to do with the info.

					=20

					If the receiver knows what is mandatory, then I do not see a reason =
why this has to be made explicit in the protocol.  It would only =
complicate the protocol.  As already said by Michael: if a mandatory TLV =
is not there, then it is just a bug.=20

					=20

					Woj> Can you specifically describe what aspect of the protocol does =
it complicate? It's just making explicitly clear what the protocol =
already has to implement anyway to be of any use.

					As to whether it is a bug, having such explicit marking makes it =
clear what/where the problem is when observing a messaging flow vs a lot =
of deduction work. In any case, the other point being made here is that =
today the protocol does NOT specify what should happen if a mandatory =
TLV is missing.

					=20

					-Woj.

					=20

					regards,

					Stefaan

					=20

					=20

					=20

				=09
________________________________


					From: Wojciech Dec (wdec) [mailto:wdec@cisco.com]=20
					Sent: maandag 28 april 2008 16:28
					To: DE CNODDER Stefaan; Busser, M; ancp@ietf.org
					Cc: Haag, T
					Subject: RE: [ANCP] Mandatory TLVs in draft-ietf-ancp-protocol =
proposal

					It's actually a mix of both. Inline...

					=20

				=09
________________________________


					From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On =
Behalf Of DE CNODDER Stefaan
					Sent: 28 April 2008 16:04
					To: Wojciech Dec (wdec); Busser, M; ancp@ietf.org
					Cc: Haag, T
					Subject: Re: [ANCP] Mandatory TLVs in draft-ietf-ancp-protocol =
proposal

					=20

					Hi,

					=20

					This new mandatory flag, what is exactly its meaning?

					=20

					(1) if flag set to "mandatory", then the *receiver* of this TLV =
MUST process it, and if unrecognized must drop the message=20

					=20

					If a received TLV is has the "mandatory" flag set then the receiver =
MUST drop the message and report an error to the sender if it doesn't =
recognize the TLV.=20

					If a the receiver expects a "mandatory" TLV but doesn't receive it, =
the message MUST be droped and an error report sent to the sender.=20

					=20

					OR

					=20

					(2) if flag is set to"mandatory", then the *sender* MUST include it =
in the message for which it is defined=20

					=20

					The sender MUST include mandatory TLVs as defined by the =
protocol-spec/applications.

					=20

					The current protocols draft says for certain TLVs that they are =
mandatory, but that applies to the sender of it (interpretation 2).  The =
flag would indicate interpretation 1 (like for Radius VSAs?)?

					=20

					If the higher order bit is set to "0" means that it is mandatory, =
then currently defined optional defined TLVs suddenly become mandatory =
which is not good.=20

					=20

					Woj> Only the currently used TLVs become mandatory. If they are not =
used/implemented we can re-define them as optional (set flag to 1) at no =
cost.=20

					=20

					But I would first to understand the exact meaning of this mandatory =
flag.  Defining such a flag indeed looks useful but then as =
interpretation 1, and I would say that if flag set to 1, then it is =
mandatory and actually, it is possible that a TLV is sent sometimes as =
optional and sometimes as mandatory.=20

					=20

					Woj> Precisely, that is possible on a per application basis. Having =
the flag would make troubleshooting of a message flow much more explicit =
(today, with any problem one has to browse the drafts to figure out what =
MUST be there vs what SHOULD be there all while looking what is actually =
there)

					=20

					Regards,

					Woj.

					=20

					regards,

					Stefaan

					=20

					=20

				=09
________________________________


					From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On =
Behalf Of Wojciech Dec (wdec)
					Sent: donderdag 24 april 2008 14:19
					To: Busser, M; ancp@ietf.org
					Cc: Haag, T
					Subject: Re: [ANCP] Mandatory TLVs in draft-ietf-ancp-protocol =
proposal

					Hi Michael,

					=20

					inline...

					=20

				=09
________________________________


					From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On =
Behalf Of Busser, M
					Sent: 24 April 2008 13:13
					To: ancp@ietf.org
					Cc: Haag, T
					Subject: Re: [ANCP] Mandatory TLVs in draft-ietf-ancp-protocol =
proposal

					Hi Woi, all

					=20

					I see the problem but i can not see, how an additional flag will =
help solving this problem.

					=20

					Lets assume your first proposal.

					If an implementation does not send the complete TLV, even it is =
defined to be mandatory, I would call this a bug and I can not see, how =
an additional flag can help here.=20

					=20

					Woj> The way it helps, and other protocols bear proof of this =
scheme, is that it is easier for implementations to reconcile errors =
resulting out of "Mandatory" and "Optional" TLV sets. The key to this =
lies on a per application basis. One application may mandate TLV A for =
operation, while another might not. Resolving such issues when =
implementing or troubleshooting multiple applications is not always =
trivial.=20

					=20

					Your second proposal seems obviously be required to keep existing =
things working, if we agree on your first proposal.=20

					But from my point of view it also assumes, that all existing =
implementations are using the same set of TLVs now.=20

					And I am not sure about that. =20

					=20

					Woj> This would be a good thing for the WG to discuss. There most =
evidently is a fair amount of "dead wood" in the current spec, ie stuff =
that nobody yet implements or cares about.  In the former case, we could =
re-cast that material using the new notions/extensions, in the latter =
case simply chop it out.

					=20

					Therefore I disagree with your first proposal. I recommend, the =
better way will be to be more precise in definitions.=20

					In my mind, it is a bug, if a mandatory TLV is missing. It is up to =
the robustness of the implementation to deal with this situation.

					Is it really neccesary to define the behavior of a network element =
in this case of failure in the ancp protocol itself? =20

					=20

					Woj> Other people have faced this problem before, and I would =
rather go with the lessons they learned, rather than clinging to hopes =
of perfect textual definitions and implementations. Other than backwards =
compatibility, I do not see in your statements a valid reason to object =
to the 1st proposal, particularly for new applications since it can only =
make things more robust. The counter argument of being precise in the =
definitions, as evidenced by the current spec, is admirable and needs to =
be there, with this proposal providing an extra level of robustness and =
visibility of any problems.=20

					=20

					Thanks,

					Woj.

					=20

					If optional TLVs are not present in a message, we should describe =
some kind of default behaviour, as you already stated.

					=20

					=20

					=20

					=20

					Comments on draft-ietf-ancp-protocol-02.txt:

					=20

					It is not clearly stated, if the TLV  "DSL Line Attributes " is =
mandatory or optional.=20

					In fact it is mandatory because some of its SubTLVs are mandatory.=20

					We should spent a sentence to make this clear.

					=20

					It is not clearly stated, if the TLV  "Service-Profile-Name" is =
mandatory or optional.

					I prefer mandatory because it is essetial for the use case Line =
Config.=20

					=20

					Section 5.4.3 Line Config, where the TLVs are mentioned (page 35):

					  ...defined in section 5.4.1....    must be corrected to    =
...defined in section 5.4.2........

					=20

					Section 5.4.4 OAM, where the TLVs are mentioned (page 36 and page =
38):

					  ...defined in section 5.4.1....    must be corrected to    =
...defined in section 5.4.2........

					=20

					=20

					=20

					=20

					Best Regards; Freundliche Gr=FC=DFe=20

					Michael Busser

					T-Systems Enterprise Services GmbH=20

					Production Line Network Centric Systems

					ICT-Systems Integration

					Network Integration Services

					=20

					Br=FCckes 2 -8, 55545 Bad Kreuznach
					Postfach 9100, 55541 Bad Kreuznach
					+49 671 8333 8911 (Phone)
					+49 521 9210 3859 (Fax)
					+49 151 1211 9689 (Mobile)
					E-Mail: michael.busser@t-systems.com

					Internet: http://www.t-systems.com <http://www.t-systems.com/> =20

					=20

					T-Systems Enterprise Services GmbH
					Aufsichtsrat: Ren=E9 Obermann (Vorsitzender)
					Executive Committee: Reinhard Clemens (Vorsitzender)*, Helmut =
Binder, Albert Henn, Olaf Heyden*, Katrin Horstmann, Ulrich Kemp, =
Wilfried Peters*,
					Dr. Herbert Schaaff*, Zvezdana Seeger*
					Handelsregister: Amtsgericht Frankfurt am Main HRB 55933
					Sitz der Gesellschaft: Frankfurt am Main
					WEEE-Reg.-Nr. DE87523644
					*Gesch=E4ftsf=FChrer gem. =A7 35 GmbHG

					=20

					Notice: This transmittal and/or attachments may be privileged or =
confidential. If you are not the intended recipient, you are hereby =
notified that you have received this transmittal in error; any review, =
dissemination, or copying is strictly prohibited. If you received this =
transmittal in error, please notify us immediately by reply and =
immediately delete this message and all its attachments. Thank you.=20
					T-Systems - Business flexibility=20

					=20

					=20

				=09
________________________________


					Von: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] Im =
Auftrag von Wojciech Dec (wdec)
					Gesendet: Mittwoch, 23. April 2008 14:54
					An: ancp@ietf.org
					Betreff: [ANCP] Mandatory TLVs in draft-ietf-ancp-protocol proposal

					=20

					Hi All,=20

					Continuing with the series of e-mails regarding basic protocol =
issues still to be addressed, I now would now like to ask your feedback =
regarding the distinction the protocol places on mandatory TLVs. Given =
the length of this mail I'll first cut to the proposal, and after it you =
can find the problem description.

					The proposal which I am putting in front of the WG is to define a =
new TLV format which contains at a minimum a Mandatory flag (much like =
Radius VSAs do). We could have this TLV Flag be defined only for new =
applications.

					A second proposal would be try to make this flag work with existing =
ones by for example defining the highest order bit of the TLV# field to =
mean "Mandatory" when set to "0". This would be invisible to exiting =
implementations, but newer ones may have problems in communicating with =
older ones when the latter do not send all TLVs. But that can also be =
addressed by simply forming the set of mandatory TLVs to be the ones =
that all implementations currently send by default.

					Without additional feedback, I will assume that the WG is fine with =
the first proposal, and also with the 2nd one conditional on deriving a =
suitable "commonly used" TLV set.

					The problem in more detail:=20

					Currently the situation is that Mandatory TLVs are only stated to =
be as such in the body of the protocol draft spec, with an implementer =
having to scour fairly attentively the text. Eg "Type =
(Access-Loop-Circuit-ID =3D 0x01): This is a mandatory TLV", etc.

					The behaviour of an implementation that receives a message with a =
missing mandatory TLV is not defined at all, and the opposite is handled =
but not very robustly, i.e. when receiving a TLV but not recognizing it, =
and implementation is free to discard it (even if it is mandatory!). =
This is a recipe for interoperability problems and an implementation =
mine field.

					This problem is complicated by different applications. For example =
the current OAM section states the following regarding TLVs that are to =
be carried in the request message (my italics):

					"=20
					Following TLVs can appear in this message:=20

					       o Type (Access-Loop-Circuit-ID =3D 0x01) : defined in =
section 5.4.1   =20

					       o Type (Access-Aggregation-Circuit-ID-Binary =3D 0x06): =
defined in=20
					         section 5.4.1.=20
					 =20
					       o Type (Access-Aggregation-Circuit-ID-ASCII =3D 0x03): =
defined in section=20
					         5.4.1. =20

					       o Type (OAM-Loopback-Test-Parameters =3D 0x07): Parameters =
related to =20
					         loopback test. This is an optional TLV. If this TLV is not =
present=20
					         in the request message, the DSLAM SHOULD use locally =
determined=20
					         default values for the test parameters. =20
					"=20
					(NOTE: The last "SHOULD" appears to be inappropriate. If the TLV is =
missing, the DSLAM MUST have some default parameters, or return an =
error)

					The "can" above indicates that they're all optional, while clearly =
the application cannot run its course without one or more of these =
fields. Here we have a case where one could have a perfectly compliant =
implementation that ignores all these TLVs...

					-Woj.=20

				=09
				=09
				=09
				=09
				=09
				=09
				=09
				=09
				=09
				=09


------_=_NextPart_001_01C8AF96.F40D1A81
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:p =3D=20
"urn:schemas-microsoft-com:office:powerpoint"><HEAD><TITLE>Nachricht</TIT=
LE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.3314" name=3DGENERATOR><!--[if !mso]>
<STYLE>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</STYLE>
<![endif]-->
<STYLE>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Arial-BoldMT;
	panose-1:0 0 0 0 0 0 0 0 0 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p
	{mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman";}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:Arial;
	color:navy;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:70.85pt 70.85pt 56.7pt 70.85pt;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:583926533;
	mso-list-type:hybrid;
	mso-list-template-ids:914754638 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1
	{mso-list-id:1760322391;
	mso-list-type:hybrid;
	mso-list-template-ids:916994444 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
	{mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</STYLE>
</HEAD>
<BODY lang=3DEN-US vLink=3Dpurple link=3Dblue>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D687430307-05052008><FONT =
face=3DArial=20
size=3D2>Sanjay,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D687430307-05052008><FONT =
face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D687430307-05052008><FONT =
face=3DArial=20
size=3D2>Inline.... Woj#2</FONT></SPAN></DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Sanjay Wadhwa=20
  [mailto:swadhwa@juniper.net] <BR><B>Sent:</B> 30 April 2008=20
  07:40<BR><B>To:</B> Wojciech Dec (wdec); Peter Arberg; DE CNODDER =
Stefaan;=20
  Busser, M; ancp@ietf.org<BR><B>Cc:</B> Haag, T<BR><B>Subject:</B> RE: =
[ANCP]=20
  Mandatory TLVs in draft-ietf-ancp-protocol =
proposal<BR></FONT><BR></DIV>
  <DIV></DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Woj<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">&nbsp; I =
agree only=20
  on the following:<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <OL style=3D"MARGIN-TOP: 0in" type=3D1>
    <LI class=3DMsoNormal style=3D"COLOR: blue; mso-list: l1 level1 =
lfo1"><FONT=20
    face=3DArial color=3Dblue size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">A TLV might be =
mandatory for one=20
    application or use-case, and optional for another application. We do =
need to=20
    clearly specify in the draft if a TLV is mandatory or optional for a =
given=20
    application (which boils down to specifying this per ANCP message =
and=20
    message type).<o:p></o:p></SPAN></FONT> </LI></OL>
  <DIV class=3DMsoNormal style=3D"COLOR: blue; mso-list: l1 level1 =
lfo1"><FONT=20
  face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV class=3DMsoNormal style=3D"COLOR: blue; mso-list: l1 level1 =
lfo1"><SPAN=20
  class=3D687430307-05052008><FONT face=3DArial color=3D#000000 =
size=3D2>Woj#2&gt;=20
  I&nbsp;interpret this to mean that you've taken on the action to =
clarify the=20
  protocol spec text, and also prepare the table of TLVs indicating =
where each=20
  TLV is mandatory, and where optional. Please let me know if this is =
not=20
  so</FONT></SPAN></DIV>
  <DIV class=3DMsoNormal style=3D"COLOR: blue; mso-list: l1 level1 =
lfo1"><SPAN=20
  class=3D687430307-05052008><FONT face=3DArial =
size=3D2></FONT></SPAN>&nbsp;</DIV>
  <OL style=3D"MARGIN-TOP: 0in" type=3D1>
    <LI class=3DMsoNormal style=3D"COLOR: blue; mso-list: l1 level1 =
lfo1"><FONT=20
    face=3DArial color=3Dblue size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">We should clearly =
specify the=20
    behavior for handling missing mandatory TLVs in received=20
    messages.<o:p></o:p></SPAN></FONT> </LI></OL>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT color=3Dblue><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">To me the =
utility of=20
  flagging a TLV as mandatory or optional via the protocol is at best =
debatable.=20
  &nbsp;If a buggy implementation on the sender incorrectly sets a =
=93known=94 TLV=20
  as mandatory (when it is not) or vice-versa, do we want the receiver =
to infer=20
  the handling of this TLV based on what the sender tells it? I don=92t =
think so.=20
  Ideally, we want the receiver and sender to have a common =
understanding of=20
  what is mandatory and what is optional based on what is in the spec, =
and=20
  handle the TLV based on that understanding. As Peter mentions, the =
spec=20
  clearly spells out TLVs that are mandatory and optional. Also, I =
don=92t see a=20
  major advantage of your proposal with respect to debuggability.<FONT=20
  color=3D#000000><SPAN=20
  class=3D687430307-05052008>&nbsp;</SPAN></FONT></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT color=3Dblue><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><FONT=20
  color=3D#000000><SPAN=20
  class=3D687430307-05052008></SPAN></FONT></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">Typical =
case where it=20
  does make sense for the sender to set some flag in the TLV to control =
the=20
  handling of the TLV on the receiver is for =93unrecognized=94 TLV=20
  types=85e.g.<o:p></o:p></SPAN></FONT></P>
  <OL style=3D"MARGIN-TOP: 0in" type=3D1>
    <LI class=3DMsoNormal style=3D"COLOR: blue; mso-list: l0 level1 =
lfo2"><FONT=20
    face=3DArial color=3Dblue size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Receiver is an =
intermediate=20
    node, which consumes the message but also needs to forward it along =
to other=20
    nodes. Here the sender can flag the handling of the TLV to the =
receiver=20
    (e.g. discard or forward if the TLV type is not recognized by the =
receiver).=20
    This doesn=92t quite apply to ANCP (messages are confined to be =
between two=20
    peers).<o:p></o:p></SPAN></FONT>&nbsp;<SPAN =
class=3D687430307-05052008><FONT=20
    face=3DArial color=3D#000000 size=3D2>&nbsp;</FONT></SPAN></LI></OL>
  <DIV class=3DMsoNormal style=3D"COLOR: blue; mso-list: l0 level1 =
lfo2"><SPAN=20
  class=3D687430307-05052008></SPAN>&nbsp;</DIV>
  <DIV class=3DMsoNormal style=3D"COLOR: blue; mso-list: l0 level1 =
lfo2"><SPAN=20
  class=3D687430307-05052008><FONT face=3DArial color=3D#000000 =
size=3D2>Woj#2&gt; It=20
  happens that an ANCP relay has already been proposed in the DSL Forum, =
and=20
  under&nbsp;in some situations it could be a viable entity. By NOT =
designing=20
  such flags now, we're likely making things&nbsp;more=20
  difficult</FONT>&nbsp;<FONT face=3DArial color=3D#000000 size=3D2>in =
the future.=20
  Anyway, since there doesn't seem to be much enthusiasm for "Mandatory" =
flags,=20
  I'll put the subject to rest for now.</FONT></SPAN></DIV>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.25in"><FONT face=3DArial =
color=3Dblue=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <OL style=3D"MARGIN-TOP: 0in" type=3D1 start=3D2>
    <LI class=3DMsoNormal style=3D"COLOR: blue; mso-list: l0 level1 =
lfo2"><FONT=20
    face=3DArial color=3Dblue size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">If handling of an =
unrecognized=20
    TLV on the receiver needs to be different for an optional TLV versus =
a=20
    mandatory TLV. Here the receiver doesn=92t understand the TLV type, =
but can=20
    infer the handling based on the flag in the TLV. However, do we want =
the=20
    treatment of =93unrecognized=94 TLVs on the receiver to be different =
for=20
    optional and mandatory TLVs (e.g. silently discard an unrecognized =
optional=20
    TLV=85but discard and also send an error back for an unrecognized =
mandatory=20
    TLV). I don=92t think this is necessary. However, if we do want to =
do this,=20
    then may be the flag in the TLV should explicitly indicate the =
handling for=20
    the TLV (e.g. =93silently discard if un-recognized=94 versus =
=93discard and send=20
    an error back=94)=85as opposed to just flagging these as =
=93mandatory=94 versus=20
    =93optional=94.<o:p></o:p></SPAN></FONT>&nbsp;<SPAN=20
    class=3D687430307-05052008><FONT face=3DArial color=3D#000000=20
    size=3D2>&nbsp;</FONT></SPAN></LI></OL>
  <DIV class=3DMsoNormal style=3D"COLOR: blue; mso-list: l0 level1 =
lfo2"><FONT=20
  face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></DIV>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Woj&gt; Of =
course it=20
  is,&nbsp;the whole spec is about this. The problem comes when people =
start to=20
  re-use&nbsp;well known TLVs for different applications, and then =
trying to=20
  make sense of it all &gt;becomes non-trivial. Why do you think both =
BGP and=20
  Diamater, and a number of other protocols have definied "Mandatory" =
flags?=20
  Just for kicks? It's a well known protocol design tool, that &gt;comes =
handy=20
  when re-using same data across multiple=20
  applications.<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT color=3Dblue><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">We should =
look at why=20
  these protocols are doing this (as opposed to blindly following). For =
a=20
  counter example, please take a look at OSPF traffic engineering =
extensions=20
  (RFC 3630).&nbsp;<FONT color=3D#000000><SPAN=20
  class=3D687430307-05052008>&nbsp;</SPAN></FONT></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT color=3Dblue><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><FONT=20
  color=3D#000000><SPAN=20
  class=3D687430307-05052008></SPAN></FONT></SPAN></FONT>&nbsp;</P><FONT =

  color=3Dblue><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><FONT =
size=3D+0><SPAN=20
  class=3D687430307-05052008>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><o:p><SPAN=20
  class=3D985581411-05052008><FONT color=3D#000000>Woj<SPAN=20
  class=3D687430307-05052008>&nbsp;#2&nbsp;</SPAN>&gt;&nbsp;<SPAN=20
  class=3D687430307-05052008>&nbsp;The irony of the above statement in =
view=20
  of&nbsp; the initiators of=20
  ANCP&nbsp;blindly&nbsp;following</SPAN>&nbsp;GSMP<SPAN=20
  class=3D687430307-05052008>&nbsp;is hopefully not lost on you.&nbsp;On =
the=20
  Mandatory Flag aspect, there is&nbsp;one key reason why any protocol =
does; it=20
  is&nbsp;to&nbsp;offload the application from doing base data-element =
checking.=20
  Anyway, we can move on.</SPAN></FONT></SPAN></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><o:p><SPAN=20
  class=3D985581411-05052008><FONT color=3D#000000><SPAN=20
  =
class=3D687430307-05052008></SPAN></FONT></SPAN></o:p></SPAN>&nbsp;</P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><o:p><SPAN=20
  class=3D985581411-05052008><FONT color=3D#000000><SPAN=20
  class=3D687430307-05052008>-Woj.</SPAN></FONT></SPAN></o:p></SPAN></P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><o:p><SPAN=20
  class=3D985581411-05052008><FONT color=3D#000000><SPAN=20
  =
class=3D687430307-05052008></SPAN></FONT></SPAN></o:p></SPAN>&nbsp;</P>
  <P class=3DMsoNormal><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><o:p><SPAN=20
  class=3D985581411-05052008><FONT color=3D#000000><SPAN=20
  =
class=3D687430307-05052008></SPAN></FONT></SPAN></o:p></SPAN>&nbsp;</P>
  <P class=3DMsoNormal><FONT=20
  =
color=3D#000000>&nbsp;</FONT></SPAN><o:p></o:p></FONT></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Cheers<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">-Sanjay<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <DIV>
  <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
  face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
  <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
  </SPAN></FONT></DIV>
  <P class=3DMsoNormal><B><FONT face=3DTahoma size=3D2><SPAN=20
  style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
  face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">=20
  ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] <B><SPAN=20
  style=3D"FONT-WEIGHT: bold">On Behalf Of </SPAN></B>Wojciech Dec=20
  (wdec)<BR><B><SPAN style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> =
Tuesday, April=20
  29, 2008 3:03 PM<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">To:</SPAN></B> Peter=20
  Arberg; DE CNODDER Stefaan; Busser, M; ancp@ietf.org<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B> Haag, T<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> Re: [ANCP] Mandatory =
TLVs in=20
  draft-ietf-ancp-protocol proposal</SPAN></FONT><o:p></o:p></P></DIV>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN lang=3DDE=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Hi =
Peter,</SPAN></FONT><SPAN=20
  lang=3DDE><o:p></o:p></SPAN></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DDE=20
  style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN lang=3DDE=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">continued=20
  inline...</SPAN></FONT><SPAN lang=3DDE><o:p></o:p></SPAN></P>
  <BLOCKQUOTE=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: 5pt 0in 5pt =
3.75pt; BORDER-LEFT: black 1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none">
    <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DDE=20
    style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
    <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
    face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
    <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
    </SPAN></FONT></DIV>
    <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><B><FONT =
face=3DTahoma=20
    size=3D2><SPAN=20
    style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
    face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">=20
    ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] <B><SPAN=20
    style=3D"FONT-WEIGHT: bold">On Behalf Of </SPAN></B>Peter =
Arberg<BR><B><SPAN=20
    style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> 29 April 2008 =
20:39<BR><B><SPAN=20
    style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Wojciech Dec (wdec); DE =
CNODDER=20
    Stefaan; Busser, M; ancp@ietf.org<BR><B><SPAN=20
    style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B> Haag, T<BR><B><SPAN=20
    style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> Re: [ANCP] Mandatory =
TLVs in=20
    draft-ietf-ancp-protocol proposal</SPAN></FONT><o:p></o:p></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DDE=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">Hi=20
    Woj,</SPAN></FONT><SPAN lang=3DDE><o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DDE=20
    style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DDE=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">please =
see inline=20
    in your answers</SPAN></FONT><SPAN lang=3DDE><o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DDE=20
    style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
    <BLOCKQUOTE=20
    style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: 5pt 0in 5pt =
3.75pt; BORDER-LEFT: blue 1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none">
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DDE=20
      style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
      <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
      face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
      <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
      </SPAN></FONT></DIV>
      <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><B><FONT =
face=3DTahoma=20
      size=3D2><SPAN=20
      style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
      face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Tahoma">=20
      Wojciech Dec (wdec) [mailto:wdec@cisco.com] <BR><B><SPAN=20
      style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> 29. april 2008=20
      11:07<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Peter =
Arberg;=20
      DE CNODDER Stefaan; Busser, M; ancp@ietf.org<BR><B><SPAN=20
      style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B> Haag, T<BR><B><SPAN=20
      style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: Re: [ANCP] =
Mandatory=20
      TLVs in draft-ietf-ancp-protocol =
proposal</SPAN></FONT><o:p></o:p></P>
      <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN lang=3DDE=20
      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Hi =
Peter,</SPAN></FONT><SPAN=20
      lang=3DDE><o:p></o:p></SPAN></P>
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DDE=20
      style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DDE=20
      style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
      <BLOCKQUOTE=20
      style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; =
BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: =
5pt 0in 5pt 3.75pt; BORDER-LEFT: black 1.5pt solid; PADDING-TOP: 0in; =
BORDER-BOTTOM: medium none">
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
        <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
        face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: =
12pt">
        <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
        </SPAN></FONT></DIV>
        <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><B><FONT =
face=3DTahoma=20
        size=3D2><SPAN=20
        style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
        face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Tahoma">=20
        Peter Arberg [mailto:parberg@redback.com] <BR><B><SPAN=20
        style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> 29 April 2008=20
        19:34<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> =
Wojciech Dec=20
        (wdec); DE CNODDER Stefaan; Busser, M; ancp@ietf.org<BR><B><SPAN =

        style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B> Haag, T<BR><B><SPAN=20
        style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: Re: [ANCP] =
Mandatory=20
        TLVs in draft-ietf-ancp-protocol =
proposal</SPAN></FONT><o:p></o:p></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">Hi=20
        Woj,</SPAN></FONT><SPAN lang=3DDE><o:p></o:p></SPAN></P>
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">I =
agree with=20
        Michael and Stefan on this issue, I do not see a need to change =
the=20
        existing</SPAN></FONT><SPAN lang=3DDE><o:p></o:p></SPAN></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">implementation=20
        with a mandatory/optional flag.</SPAN></FONT><FONT face=3DArial=20
        color=3Dblack size=3D2><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><SPAN=20
        lang=3DDE><o:p></o:p></SPAN></P>
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Woj&gt; Please=20
        indicate where in my proposal did you see anything=20
        about</SPAN></FONT><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><FONT=20
        face=3DArial color=3Dblack size=3D2><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">changing=20
        existing implementaions?&nbsp;</SPAN></FONT><FONT face=3DArial =
color=3Dblue=20
        size=3D2><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><SPAN=20
        lang=3DDE><o:p></o:p></SPAN></P>
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></BLOCKQUOTE></BLOCKQUOTE>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DDE=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">PAR&gt;&nbsp;&nbsp;I=20
    might have misunderstood your email, but I read it as if you suggest =
a high=20
    bit</SPAN></FONT><SPAN lang=3DDE><o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DDE=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">value in =
existing=20
    TLV's to be interpreted as a mandatory flag.</SPAN></FONT><FONT =
face=3DArial=20
    color=3Dblack size=3D2><SPAN lang=3DDE=20
    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><SPAN=20
    lang=3DDE><o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DDE=20
    style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DDE=20
    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Woj#2&gt; Yes, I=20
    suggested (in proposal 2) that *if* the WG found there to be a =
common set of=20
    TLVs currently in use, then the high-order bit set to "0" (ie as =
today)=20
    could be interpreted as "mandatory", and the rest of the TLV's =
redefined=20
    with a high order "1". To extsing implementations, the "new" TLVs =
would just=20
    look like a different TLV#, while&nbsp;anyone wishing to implement =
the more=20
    robust error cheking logic based on this bit,&nbsp;would be free to =
do=20
    so.</SPAN></FONT><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DDE=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><SPAN=20
    lang=3DDE><o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DDE=20
    style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DDE=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">If you =
are simply=20
    talking about new capability type definitions, then why do you not =
bring=20
    up</SPAN></FONT><SPAN lang=3DDE><o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DDE=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">the =
additional flag=20
    in a new internet-draft defining what capability type you have in =
mind=20
    ?</SPAN></FONT><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DDE=20
    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><SPAN=20
    lang=3DDE><o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DDE=20
    style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DDE=20
    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Woj#2&gt; No, a=20
    new capability was not intended, but could also be=20
    considered.</SPAN></FONT><SPAN lang=3DDE><o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DDE=20
    style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
    <BLOCKQUOTE=20
    style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: 5pt 0in 5pt =
3.75pt; BORDER-LEFT: blue 1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none">
      <BLOCKQUOTE=20
      style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; =
BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: =
5pt 0in 5pt 3.75pt; BORDER-LEFT: black 1.5pt solid; PADDING-TOP: 0in; =
BORDER-BOTTOM: medium none">
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">I =
think I=20
        understand your arguments, but I do not agree with them. I think =
most=20
        places in</SPAN></FONT><SPAN lang=3DDE><o:p></o:p></SPAN></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">the =
draft it is=20
        clear what is defined as mandatory and =
optional.</SPAN></FONT><FONT=20
        face=3DArial color=3Dblack size=3D2><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><SPAN=20
        lang=3DDE><o:p></o:p></SPAN></P>
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">I =
agree on the=20
        point we need to go through the draft and make clarifications to =
what=20
        TLV's</SPAN></FONT><SPAN lang=3DDE><o:p></o:p></SPAN></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">in =
what=20
        capability types are mandatory and optional, and make more =
description=20
        what should</SPAN></FONT><SPAN lang=3DDE><o:p></o:p></SPAN></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">happen if=20
        mandatory TLVs are not included.</SPAN></FONT><FONT face=3DArial =

        color=3Dblack size=3D2><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><SPAN=20
        lang=3DDE><o:p></o:p></SPAN></P>
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Woj&gt;=20
        Exactly.</SPAN></FONT><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><SPAN=20
        lang=3DDE><o:p></o:p></SPAN></P>
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">I =
think the=20
        DSLF TR-101 document has a good example of such a description in =
it's=20
        </SPAN></FONT><SPAN lang=3DDE><o:p></o:p></SPAN></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">"</SPAN></FONT><FONT=20
        face=3DArial-BoldMT color=3Dblue size=3D2><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial-BoldMT">Table 3=20
        - Access loop characteristics sub-options", and I think if we do =
the=20
        same for each</SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P>
        <P class=3DMsoNormal><FONT face=3DArial-BoldMT color=3Dblue =
size=3D2><SPAN=20
        lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial-BoldMT">capability=20
        types TLV's in the ANCP draft it will be a good =
help.</SPAN></FONT><FONT=20
        face=3DArial-BoldMT size=3D2><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial-BoldMT"><o:p></o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Woj&gt;</SPAN></FONT><FONT=20
        face=3DArial color=3Dblue size=3D2><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">=20
        </SPAN></FONT><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Indeed,=20
        pre-ceeded by some rationalization. The appears to be no reason =
for some=20
        of the DSLF "mandatory" TLVs.</SPAN></FONT><FONT face=3DArial =
color=3Dblue=20
        size=3D2><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><SPAN=20
        lang=3DDE><o:p></o:p></SPAN></P>
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></BLOCKQUOTE></BLOCKQUOTE>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DDE=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">PAR&gt; I =
do not=20
    see a problem with re-visit in the draft if a TLV should be optional =
or=20
    mandatory, so if</SPAN></FONT><SPAN lang=3DDE><o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DDE=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">that is =
the intend,=20
    then I'm all for an email discussion on a TLV by TLV basis if we =
think it is=20
    a </SPAN></FONT><SPAN lang=3DDE><o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DDE=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">manfdatory or=20
    optional information inside the specific capability =
type.</SPAN></FONT><FONT=20
    face=3DArial color=3Dblack size=3D2><SPAN lang=3DDE=20
    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><SPAN=20
    lang=3DDE><o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DDE=20
    style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DDE=20
    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Woj#2&gt; Great,=20
    because any change to the mandated set&nbsp;*will* affect existing=20
    implementation</SPAN></FONT><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><FONT=20
    face=3DArial color=3Dblack size=3D2><SPAN lang=3DDE=20
    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">.</SPAN></FONT><SPAN=20
    lang=3DDE><o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DDE=20
    style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
    <BLOCKQUOTE=20
    style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: 5pt 0in 5pt =
3.75pt; BORDER-LEFT: blue 1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none">
      <BLOCKQUOTE=20
      style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; =
BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: =
5pt 0in 5pt 3.75pt; BORDER-LEFT: black 1.5pt solid; PADDING-TOP: 0in; =
BORDER-BOTTOM: medium none">
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">I do =
not agree=20
        with your point that it is not listed if "rate" is mandatory or=20
        optional, it is clearly</SPAN></FONT><SPAN=20
lang=3DDE><o:p></o:p></SPAN></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">listed as a=20
        mandatory TLV, and as such it should be included in the port up =
message,=20
        I really</SPAN></FONT><SPAN lang=3DDE><o:p></o:p></SPAN></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">do =
not=20
        understand what confusion you have with this.</SPAN></FONT><FONT =

        face=3DArial color=3Dblack size=3D2><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><SPAN=20
        lang=3DDE><o:p></o:p></SPAN></P>
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Woj&gt; The=20
        text states:&nbsp;&nbsp;</SPAN></FONT><FONT face=3DArial =
color=3Dblue=20
        size=3D2><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><SPAN=20
        lang=3DDE><o:p></o:p></SPAN></P>
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><FONT face=3D"Courier New" color=3Dblack =
size=3D2><SPAN=20
        lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: 'Courier =
New'">5.=20
        Type (DSL Line Attributes =3D 0x04): </SPAN></FONT><FONT =
face=3DArial=20
        color=3Dblue size=3D1><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 7.5pt; COLOR: blue; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></P>
        <P><FONT face=3D"Courier New" color=3Dblack size=3D2><SPAN =
lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: 'Courier =
New'">Length=20
        : variable (up to 1024 bytes) </SPAN></FONT><FONT =
color=3Dblue><SPAN=20
        lang=3DDE style=3D"COLOR: blue"><o:p></o:p></SPAN></FONT></P>
        <P><FONT face=3D"Courier New" color=3Dblack size=3D2><SPAN =
lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: 'Courier =
New'">Value=20
        : This consists of one or more Sub-TLVs corresponding to DSL=20
        </SPAN></FONT><FONT color=3Dblue><SPAN lang=3DDE=20
        style=3D"COLOR: blue"><o:p></o:p></SPAN></FONT></P>
        <P><FONT face=3D"Courier New" color=3Dblack size=3D2><SPAN =
lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: 'Courier =
New'">line=20
        attributes. No sub-TLVs other than the "DSL type" and "DSL=20
        </SPAN></FONT><FONT color=3Dblue><SPAN lang=3DDE=20
        style=3D"COLOR: blue"><o:p></o:p></SPAN></FONT></P>
        <P><FONT face=3D"Courier New" color=3Dblack size=3D2><SPAN =
lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: 'Courier =
New'">line=20
        state" SHOULD be included in a PORT DOWN message. =
</SPAN></FONT><FONT=20
        color=3Dblue><SPAN lang=3DDE=20
        style=3D"COLOR: blue"><o:p></o:p></SPAN></FONT></P>
        <P><FONT face=3D"Courier New" color=3Dblack size=3D2><SPAN =
lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: 'Courier =
New'">The=20
        general format of the sub-TLVs is identical to the general TLV=20
        </SPAN></FONT><FONT color=3Dblue><SPAN lang=3DDE=20
        style=3D"COLOR: blue"><o:p></o:p></SPAN></FONT></P>
        <P><FONT face=3D"Courier New" color=3Dblack size=3D2><SPAN =
lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: 'Courier =
New'">format.=20
        The value field in each sub-TLV is padded to a 4-octet=20
        </SPAN></FONT><FONT color=3Dblue><SPAN lang=3DDE=20
        style=3D"COLOR: blue"><o:p></o:p></SPAN></FONT></P>
        <P><FONT face=3D"Courier New" color=3Dblack size=3D2><SPAN =
lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: 'Courier =
New'">alignment.=20
        The Length field in each sub-TLV contains the actual =
</SPAN></FONT><FONT=20
        color=3Dblue><SPAN lang=3DDE=20
        style=3D"COLOR: blue"><o:p></o:p></SPAN></FONT></P>
        <P><FONT face=3D"Courier New" color=3Dblack size=3D2><SPAN =
lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: 'Courier =
New'">number=20
        of bytes in the TLV (not including the padding if present).=20
        </SPAN></FONT><FONT color=3Dblue><SPAN lang=3DDE=20
        style=3D"COLOR: blue"><o:p></o:p></SPAN></FONT></P>
        <P><FONT face=3D"Courier New" color=3Dblack size=3D2><SPAN =
lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: 'Courier =
New'">Current=20
        defined sub-TLV types are start from 0x81.</SPAN></FONT><FONT=20
        color=3Dblack><SPAN lang=3DDE style=3D"COLOR: =
black">&nbsp;</SPAN></FONT><FONT=20
        face=3DArial color=3Dblack size=3D2><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><FONT=20
        color=3Dblue><SPAN lang=3DDE=20
        style=3D"COLOR: blue"><o:p></o:p></SPAN></FONT></P>
        <P><FONT face=3DArial color=3Dblack size=3D2><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Maybe you can=20
        point me to where exatly it is stated clearly as being =
mandatory, or=20
        otherwise explain why you "not agree"?</SPAN></FONT><FONT=20
        color=3Dblack><SPAN lang=3DDE style=3D"COLOR: =
black">&nbsp;</SPAN></FONT><FONT=20
        face=3DArial color=3Dblue size=3D2><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><FONT=20
        color=3Dblue><SPAN lang=3DDE=20
        style=3D"COLOR: blue"><o:p></o:p></SPAN></FONT></P>
        <P><FONT face=3D"Times New Roman" color=3Dblue size=3D3><SPAN =
lang=3DDE=20
        style=3D"FONT-SIZE: 12pt; COLOR: =
blue">&nbsp;<o:p></o:p></SPAN></FONT></P></BLOCKQUOTE></BLOCKQUOTE>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DDE=20
    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">PAR&gt; =
I think=20
    you forgot to read the most important part where the actual TLV is=20
    defined.&nbsp;</SPAN></FONT><FONT face=3DArial color=3Dblue =
size=3D1><SPAN lang=3DDE=20
    style=3D"FONT-SIZE: 7.5pt; COLOR: blue; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D1><SPAN =
lang=3DDE=20
    style=3D"FONT-SIZE: 7.5pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;<o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DDE=20
    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Woj#2&gt;&nbsp;I=20
    didn't. This part talks about the sub-TLV, not the main TLV 0x04. Do =
you see=20
    my point now?</SPAN></FONT><FONT face=3DArial color=3Dblue =
size=3D1><SPAN lang=3DDE=20
    style=3D"FONT-SIZE: 7.5pt; COLOR: blue; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D1><SPAN =
lang=3DDE=20
    style=3D"FONT-SIZE: 7.5pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;<o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D1><SPAN =
lang=3DDE=20
    style=3D"FONT-SIZE: 7.5pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;<o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DDE=20
    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Type=20
    (Actual-Net-Data-Upstream =3D 0x81): Actual upstream net =
data&nbsp;rate on a=20
    DSL line. </SPAN></FONT><FONT face=3DArial color=3Dblue =
size=3D1><SPAN lang=3DDE=20
    style=3D"FONT-SIZE: 7.5pt; COLOR: blue; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DDE=20
    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">This is =
a=20
    mandatory TLV.&nbsp; </SPAN></FONT><FONT face=3DArial color=3Dblue =
size=3D1><SPAN=20
    lang=3DDE=20
    style=3D"FONT-SIZE: 7.5pt; COLOR: blue; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></P>
    <DIV>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D1><SPAN =
lang=3DDE=20
    style=3D"FONT-SIZE: 7.5pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DDE=20
    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Length&nbsp;=20
    :&nbsp; (4 bytes) </SPAN></FONT><FONT face=3DArial color=3Dblue =
size=3D1><SPAN=20
    lang=3DDE=20
    style=3D"FONT-SIZE: 7.5pt; COLOR: blue; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></P>
    <DIV>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DDE=20
    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Value&nbsp;&nbsp;=20
    : (Rate in Kb/sec) </SPAN></FONT><FONT face=3DArial color=3Dblue =
size=3D1><SPAN=20
    lang=3DDE=20
    style=3D"FONT-SIZE: 7.5pt; COLOR: blue; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></P></DIV>
    <DIV>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D1><SPAN =
lang=3DDE=20
    style=3D"FONT-SIZE: 7.5pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DDE=20
    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Type=20
    (Actual-Net-Data-Rate-Downstream =3D 0x82) : Actual downstream net =
data rate=20
    on a DSL line. </SPAN></FONT><FONT face=3DArial color=3Dblue =
size=3D1><SPAN=20
    lang=3DDE=20
    style=3D"FONT-SIZE: 7.5pt; COLOR: blue; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DDE=20
    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">This is =
a=20
    mandatory TLV. </SPAN></FONT><FONT face=3DArial color=3Dblue =
size=3D1><SPAN=20
    lang=3DDE=20
    style=3D"FONT-SIZE: 7.5pt; COLOR: blue; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></P>
    <DIV>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D1><SPAN =
lang=3DDE=20
    style=3D"FONT-SIZE: 7.5pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DDE=20
    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Length =
:&nbsp; (4=20
    bytes) </SPAN></FONT><FONT face=3DArial color=3Dblue size=3D1><SPAN =
lang=3DDE=20
    style=3D"FONT-SIZE: 7.5pt; COLOR: blue; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></P>
    <DIV>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DDE=20
    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Value&nbsp;=20
    :&nbsp; (Rate in Kb/sec) </SPAN></FONT><FONT face=3DArial =
color=3Dblue=20
    size=3D1><SPAN lang=3DDE=20
    style=3D"FONT-SIZE: 7.5pt; COLOR: blue; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></P></DIV>
    <DIV>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D1><SPAN =
lang=3DDE=20
    style=3D"FONT-SIZE: 7.5pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
    <BLOCKQUOTE=20
    style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: 5pt 0in 5pt =
3.75pt; BORDER-LEFT: blue 1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none">
      <BLOCKQUOTE=20
      style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; =
BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: =
5pt 0in 5pt 3.75pt; BORDER-LEFT: black 1.5pt solid; PADDING-TOP: 0in; =
BORDER-BOTTOM: medium none">
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">The =
fact you=20
        say "Port UP" and "OAM" is best considered as legacy =
applications, I=20
        have some</SPAN></FONT><SPAN lang=3DDE><o:p></o:p></SPAN></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">trouble with=20
        this as well, since ANCP running in production networks use =
them, and as=20
        such</SPAN></FONT><SPAN lang=3DDE><o:p></o:p></SPAN></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">it is =
a central=20
        part of the ANCP specifications we need to finish as soon as=20
        possible.</SPAN></FONT><FONT face=3DArial color=3Dblack =
size=3D2><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><SPAN=20
        lang=3DDE><o:p></o:p></SPAN></P>
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Woj&gt; I=20
        should have said legacy applications from a protocol messaging=20
        perspective, not usage, nor support. It's quite clear that GSMP =
derived=20
        messaging has baggage that is un called for in new=20
        applications.</SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P>
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">I =
think=20
        Stefaan's example is very valid, that we do not need to make =
mandatory=20
        requirements to </SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">what =
receivers=20
        of ANCP information use such info. for.&nbsp; I don't think we =
should=20
        try and make the</SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">ANCP=20
        specifications "mandatory" for box behavior, I think it is much =
more=20
        important for the </SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">working group=20
        to make the protocol specifications easy to understand and get =
the first=20
        documentation</SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">finish and=20
        published, so the protocol can be used for different sets of=20
        applications, and make sure</SPAN></FONT><SPAN=20
        lang=3DDE><o:p></o:p></SPAN></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">new=20
        applications can be added later.</SPAN></FONT><FONT face=3DArial =

        color=3Dblack size=3D2><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><SPAN=20
        lang=3DDE><o:p></o:p></SPAN></P>
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Woj&gt; Indeed=20
        the aim of the WG to define a protocol that is relatively simple =
and=20
        easy to understand, not just to implementers but also to people =
using=20
        it, and across vendors. Currently, having anyone operating the =
device be=20
        familiar in what cases a TLV is mandatory and in what optional =
requires=20
        a thorough understanding of the spec, across applications. This =
is not=20
        easy, but I'll conceede that for the applications implemented so =
far we=20
        could live with it. </SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P>
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">I do =
think that=20
        by documenting if a TLV is mandatory or optional inside a =
specific=20
        capability type,</SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">it is =
easy to=20
        understand what must be sent to support the defined=20
        application/capability type.</SPAN></FONT><FONT face=3DArial =
color=3Dblack=20
        size=3D2><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><SPAN=20
        lang=3DDE><o:p></o:p></SPAN></P>
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Woj&gt; Of=20
        course it is,&nbsp;the whole spec is about this. The problem =
comes when=20
        people start to re-use&nbsp;well known TLVs for different =
applications,=20
        and then trying to make sense of it all becomes non-trivial. Why =
do you=20
        think both BGP and Diamater, and a number of other protocols =
have=20
        definied "Mandatory" flags? Just for kicks? It's a well known =
protocol=20
        design tool, that comes handy when re-using same data across =
multiple=20
        applications.</SPAN></FONT><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
        lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><SPAN=20
        lang=3DDE><o:p></o:p></SPAN></P>
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></BLOCKQUOTE></BLOCKQUOTE>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DDE=20
    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">PAR&gt; =
I might be=20
    wrong, but I think I can find as many or more protocol examples who =
do not=20
    include</SPAN></FONT><SPAN lang=3DDE><o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DDE=20
    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">a=20
    mandatory/optional flag, so examples can always be found which will =
support=20
    the point you are trying</SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DDE=20
    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">to=20
    make.</SPAN></FONT><SPAN lang=3DDE><o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DDE=20
    style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DDE=20
    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">I do not =
see a=20
    problem with a new internet-draft which defines new capability-types =
and=20
    where a TLV</SPAN></FONT><SPAN lang=3DDE><o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN lang=3DDE=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">mandatory flag is =
included, I do=20
    see a problem if the intend is to try and&nbsp;adjust what already=20
    exist.&nbsp;&nbsp;</SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DDE=20
    style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN lang=3DDE=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Woj#2&gt; Ok, so if =
adjusting is=20
    only scoped to what doesn't exist, as my proposal laid=20
    out&nbsp;conditionally, you're fine.</SPAN></FONT><SPAN=20
    lang=3DDE><o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DDE=20
    style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
    <BLOCKQUOTE=20
    style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: 5pt 0in 5pt =
3.75pt; BORDER-LEFT: blue 1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none">
      <BLOCKQUOTE=20
      style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; =
BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: =
5pt 0in 5pt 3.75pt; BORDER-LEFT: black 1.5pt solid; PADDING-TOP: 0in; =
BORDER-BOTTOM: medium none">
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">Then =
if anybody=20
        want to include new capability types or sub-TLVs later to =
address=20
        specific applications,</SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">then =
I think=20
        changes can be discussed at that time instead of trying to =
change=20
        existing protocol</SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">implementations.</SPAN></FONT><FONT=20
        face=3DArial color=3Dblack size=3D2><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><SPAN=20
        lang=3DDE><o:p></o:p></SPAN></P>
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Woj&gt; Again=20
        I ask, where in the proposal did you see =
*anything*&nbsp;requiring a=20
        change to an existing implementation. Please be=20
        specific.</SPAN></FONT><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><FONT=20
        face=3DArial color=3Dblack size=3D2><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">I =
see that=20
        your main objection is on this issue, which means that you =
accept=20
        proposal 1 (have such a flag for new =
TLVs/apps).</SPAN></FONT><SPAN=20
        lang=3DDE><o:p></o:p></SPAN></P>
        <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN lang=3DDE =

        style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">It would also be =
useful if=20
        you indicated whether the list of TLVs provided below is what =
you'd=20
        expect to be the minimum mandatory set.<FONT color=3Dblue><SPAN=20
        style=3D"COLOR: blue">&nbsp;</SPAN></FONT></SPAN></FONT><SPAN=20
        lang=3DDE><o:p></o:p></SPAN></P>
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></BLOCKQUOTE></BLOCKQUOTE>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DDE=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">PAR&gt; =
at the=20
    moment I read the draft as having&nbsp;defined the TLVs mandatory as =
you=20
    describe, except</SPAN></FONT><SPAN lang=3DDE><o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DDE=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">I =
also&nbsp;read it=20
    as the dsl-type =3D 0x91 must be part of the port down. If this is =
needed or=20
    not is a different</SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DDE=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">discussion.</SPAN></FONT><SPAN=20
    lang=3DDE><o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DDE=20
    style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DDE=20
    style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DDE=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">Woj#2&gt; =
Ok.=20
    Thanks. But please do come back to me if you see that the proposal =
impacts=20
    an exiting implementation. I conclude that there is no problem with =
doing=20
    changes to stuff that isn't currently used.</SPAN></FONT><SPAN=20
    lang=3DDE><o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DDE=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Woj.</SPAN></FONT><SPAN=20
    lang=3DDE><o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DDE=20
    style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DDE=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">cheers,</SPAN></FONT><SPAN=20
    lang=3DDE><o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN =
lang=3DDE=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Peter&nbsp;</SPAN></FONT><SPAN=20
    lang=3DDE><o:p></o:p></SPAN></P>
    <BLOCKQUOTE=20
    style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: 5pt 0in 5pt =
3.75pt; BORDER-LEFT: blue 1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none">
      <BLOCKQUOTE=20
      style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; =
BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: =
5pt 0in 5pt 3.75pt; BORDER-LEFT: black 1.5pt solid; PADDING-TOP: 0in; =
BORDER-BOTTOM: medium none">
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN lang=3DDE =

        style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Cheers,</SPAN></FONT><SPAN=20
        lang=3DDE><o:p></o:p></SPAN></P>
        <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN lang=3DDE =

        style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Woj.</SPAN></FONT><SPAN=20
        lang=3DDE><o:p></o:p></SPAN></P>
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">cheers,</SPAN></FONT><SPAN=20
        lang=3DDE><o:p></o:p></SPAN></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Peter</SPAN></FONT><SPAN=20
        lang=3DDE><o:p></o:p></SPAN></P>
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
        <BLOCKQUOTE=20
        style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; =
BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: =
5pt 0in 5pt 3.75pt; BORDER-LEFT: blue 1.5pt solid; PADDING-TOP: 0in; =
BORDER-BOTTOM: medium none">
          <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
          <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
          face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: =
12pt">
          <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
          </SPAN></FONT></DIV>
          <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><B><FONT =
face=3DTahoma=20
          size=3D2><SPAN=20
          style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
          face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Tahoma">=20
          ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] <B><SPAN=20
          style=3D"FONT-WEIGHT: bold">On Behalf Of </SPAN></B>Wojciech =
Dec=20
          (wdec)<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">Sent:</SPAN></B> 29.=20
          april 2008 02:28<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">To:</SPAN></B>=20
          DE CNODDER Stefaan; Busser, M; ancp@ietf.org<BR><B><SPAN=20
          style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B> Haag, T<BR><B><SPAN =

          style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> Re: [ANCP] =
Mandatory=20
          TLVs in draft-ietf-ancp-protocol =
proposal</SPAN></FONT><o:p></o:p></P>
          <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Stefaan,</SPAN></FONT><SPAN=20
          lang=3DDE><o:p></o:p></SPAN></P>
          <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
          <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">a number of=20
          points:</SPAN></FONT><SPAN lang=3DDE><o:p></o:p></SPAN></P>
          <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">1. There =
currently is to=20
          my knowledge&nbsp;no implementation of ANCP there that doesn't =
send=20
          the DSL Line attributes info by default in Port-UP messages? =
The=20
          support of HS on the NAS is an orthogonal =
issue.</SPAN></FONT><SPAN=20
          lang=3DDE><o:p></o:p></SPAN></P>
          <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">2. The current =
ancp=20
          protocol draft (02) doesn't say whether the rate info is =
optional or=20
          mandatory, it only states that the sub-TLVs are mandatory. =
Based on=20
          this, an implementer can be&nbsp;justified to expect port-ups =
to=20
          *always* have the rate-info tlv (ie treat them as mandatory). =
Equally,=20
          she's justified&nbsp;in considering this&nbsp; as=20
          optional.</SPAN></FONT><SPAN lang=3DDE><o:p></o:p></SPAN></P>
          <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">3.<EM><I><FONT=20
          face=3DArial><SPAN=20
          style=3D"FONT-FAMILY: Arial">&nbsp;</SPAN></FONT></I></EM>The =
port-up=20
          and OAM are&nbsp;best considered as legacy applications for =
ANCP. The=20
          re-use of any of the GSMP defined fields is already out of the =

          question due to constrains put in place by the existing =
use-case=20
          messaging. Needless to say, this wasn't as thoroughly designed =
as it=20
          should have been, and with the OAM and port-up apps being=20
          coupled.</SPAN></FONT><SPAN lang=3DDE><o:p></o:p></SPAN></P>
          <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">4. It's up to =
the=20
          application to define what TLVs are mandatory and which =
aren't, as you=20
          also state.&nbsp;The AN does not need to know what the NAS =
will do=20
          with the info, BUT it needs to send the right TLVs for the =
application=20
          (eg if we had a hypothetical&nbsp;AN that only sends Port-up's =
with=20
          line-id, it would be next to useless for the dynamic shaping=20
          application).</SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P>
          <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
          <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">With all this in =
mind it's=20
          useful to re-read what I proposed originally below regarding =
the=20
          mandatory flag:&nbsp;1. "<EM><I><FONT face=3DArial><SPAN=20
          style=3D"FONT-FAMILY: Arial">have this TLV Flag be defined =
only for new=20
          applications" </SPAN></FONT></I></EM>and 2. The notion of the=20
          mandatory flag applying to existing TLVs&nbsp; being =
"<EM><I><FONT=20
          face=3DArial><SPAN style=3D"FONT-FAMILY: Arial">conditional on =
deriving a=20
          suitable "commonly used" TLV set." </SPAN></FONT></I></EM>The =
latter=20
          point would ensure that existing implementations do not need =
to=20
          change, but future ones can take advantage of the extra=20
          robustness.</SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P>
          <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
          <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Hence, can the =
WG derive a=20
          set of commonly used, i.e. always used, TLVs for existing=20
          implementations?</SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P>
          <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">The list I came =
up is as=20
          follows (making them pretty much mandatory TLVs if it agrees =
with the=20
          views of others);</SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P>
          <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
          <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Port-up message=20
          (0x80);</SPAN></FONT><SPAN lang=3DDE><o:p></o:p></SPAN></P>
          <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;=20
          Extension-TLV (dsl tech type)</SPAN></FONT><SPAN=20
          lang=3DDE><o:p></o:p></SPAN></P>
          <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;=20
          Access-Loop-circuit-id (0x01)</SPAN></FONT><SPAN=20
          lang=3DDE><o:p></o:p></SPAN></P>
          <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp; DSL=20
          Line Attribute (0x04) with the following sub =
TLVs;</SPAN></FONT><SPAN=20
          lang=3DDE><o:p></o:p></SPAN></P>
          <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 12pt">&nbsp;</SPAN></FONT><FONT =
size=3D2><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 10pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
DSL-Type=20
          =3D 0x91; Actual-Net-Data-Upstream =3D 0x81;=20
          Actual-Net-Data-Rate-Downstream =3D 0x82</SPAN></FONT><SPAN=20
          lang=3DDE><o:p></o:p></SPAN></P>
          <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
          <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Port-down =
message=20
          (0x81);</SPAN></FONT><SPAN lang=3DDE><o:p></o:p></SPAN></P>
          <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 12pt">&nbsp;&nbsp;&nbsp; =
</SPAN></FONT><FONT=20
          face=3DArial size=3D2><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Extension&nbsp; =
TLV (dsl=20
          tech type)</SPAN></FONT><SPAN lang=3DDE><o:p></o:p></SPAN></P>
          <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 12pt">&nbsp;&nbsp;&nbsp; =
</SPAN></FONT><FONT=20
          face=3DArial size=3D2><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Access-Loop-circuit-id=20
          (0x01)</SPAN></FONT><SPAN lang=3DDE><o:p></o:p></SPAN></P>
          <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 12pt">&nbsp;&nbsp;&nbsp; =
</SPAN></FONT><FONT=20
          face=3DArial size=3D2><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">DSL Line =
Attribute (0x04)=20
          with the following sub TLVs;</SPAN></FONT><SPAN=20
          lang=3DDE><o:p></o:p></SPAN></P>
          <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: =
12pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</SPAN></FONT><FONT=20
          size=3D2><SPAN lang=3DDE style=3D"FONT-SIZE: 10pt"> DSL line =
state =3D=20
          0x8F</SPAN></FONT><SPAN lang=3DDE><o:p></o:p></SPAN></P>
          <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
          <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">All other TLVs =
are=20
          optional.</SPAN></FONT><SPAN lang=3DDE><o:p></o:p></SPAN></P>
          <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
          <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Would appreciate =

          confirmation from the WG regarding the =
above.</SPAN></FONT><SPAN=20
          lang=3DDE><o:p></o:p></SPAN></P>
          <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
          <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Thanks,</SPAN></FONT><SPAN=20
          lang=3DDE><o:p></o:p></SPAN></P>
          <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Woj.</SPAN></FONT><SPAN=20
          lang=3DDE><o:p></o:p></SPAN></P>
          <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
          <BLOCKQUOTE=20
          style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; =
BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: =
5pt 0in 5pt 3.75pt; BORDER-LEFT: black 1.5pt solid; PADDING-TOP: 0in; =
BORDER-BOTTOM: medium none">
            <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
            style=3D"FONT-SIZE: =
12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
            <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
            face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: =
12pt">
            <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
            </SPAN></FONT></DIV>
            <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><B><FONT =
face=3DTahoma=20
            size=3D2><SPAN=20
            style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
            face=3DTahoma size=3D2><SPAN=20
            style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma"> DE CNODDER =
Stefaan=20
            [mailto:stefaan.de_cnodder@alcatel-lucent.be] <BR><B><SPAN=20
            style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> 29 April 2008=20
            09:52<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> =
Wojciech=20
            Dec (wdec); Busser, M; ancp@ietf.org<BR><B><SPAN=20
            style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B> Haag, =
T<BR><B><SPAN=20
            style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [ANCP] =
Mandatory=20
            TLVs in draft-ietf-ancp-protocol=20
            proposal</SPAN></FONT><o:p></o:p></P>
            <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
            style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
            <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
            style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Hi=20
            Woj,</SPAN></FONT><SPAN lang=3DDE><o:p></o:p></SPAN></P>
            <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
            style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
            <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
            style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Take the=20
            following example: I have a network with 2 NASses, NAS-A is =
doing=20
            hierarchical shaping, NAS-B just wants to have the port =
information=20
            but is not doing hierarchical shaping (it is doing other =
things like=20
            OAM, ...).&nbsp; This means NAS-A needs the bandwidth, while =
NAS-B=20
            does not need the bandwidth.&nbsp; How should the flag be =
set in=20
            this case by the AN?&nbsp; Set to 'Mandatory' for the port =
up=20
            messages to NAS-A, and set to 'Optional' for port up =
messages=20
            towards NAS-B? Or is it always set to 'Mandatory'?&nbsp; =
From your=20
            answer below, I understand that it should be set to =
'Optional'=20
            towards NAS-B.&nbsp; Is that correct?</SPAN></FONT><SPAN=20
            lang=3DDE><o:p></o:p></SPAN></P>
            <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
            style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
            <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
            style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">NAS-B will=20
            simply ignore the bandwidth TLV.&nbsp; If such a flag would =
exist,=20
            and the flag is set to 'Mandatory' by the AN to NAS-B, what =
should=20
            be the behavior of NAS-B?&nbsp; Should it reject the whole=20
            message?&nbsp; Maybe NAS-B is not supporting hierarchical =
shaping,=20
            so it might not support the bandwidth TLV.&nbsp; Today, the=20
            bandwidht TLV is only mandatory to be put in the port up =
messages,=20
            but for the receiver there is nothing =
mandatory.</SPAN></FONT><SPAN=20
            lang=3DDE><o:p></o:p></SPAN></P>
            <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
            style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
            <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
            style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">I =
believe=20
            the original intend of ANCP was that the AN does not need to =
know=20
            what the NAS is doing with this information, the use of the=20
            bandwidth is also not specified by ANCP, only an example is =
given=20
            (which is shaping).&nbsp; In the future there may be =
applications=20
            for which TLVs will be mandatory which are now=20
            optional.</SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P>
            <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
            style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
            <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
            style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">regards,</SPAN></FONT><SPAN=20
            lang=3DDE><o:p></o:p></SPAN></P>
            <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
            style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Stefaan</SPAN></FONT><SPAN=20
            lang=3DDE><o:p></o:p></SPAN></P>
            <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
            style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
            <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
            style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
            <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
            style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
            <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
            style=3D"FONT-SIZE: =
12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
            <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
            face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: =
12pt">
            <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
            </SPAN></FONT></DIV>
            <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><B><FONT =
face=3DTahoma=20
            size=3D2><SPAN=20
            style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
            face=3DTahoma size=3D2><SPAN=20
            style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma"> Wojciech Dec =
(wdec)=20
            [mailto:wdec@cisco.com] <BR><B><SPAN=20
            style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> maandag 28 =
april 2008=20
            21:33<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> =
DE=20
            CNODDER Stefaan; Busser, M; ancp@ietf.org<BR><B><SPAN=20
            style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B> Haag, =
T<BR><B><SPAN=20
            style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [ANCP] =
Mandatory=20
            TLVs in draft-ietf-ancp-protocol=20
            proposal</SPAN></FONT><o:p></o:p></P>
            <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
            style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
            <BLOCKQUOTE=20
            style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; =
BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: =
5pt 0in 5pt 3.75pt; BORDER-LEFT: black 1.5pt solid; PADDING-TOP: 0in; =
BORDER-BOTTOM: medium none">
              <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
              lang=3DDE=20
style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
              <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
              face=3D"Times New Roman" size=3D3><SPAN =
style=3D"FONT-SIZE: 12pt">
              <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
              </SPAN></FONT></DIV>
              <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: =
12pt"><B><FONT=20
              face=3DTahoma size=3D2><SPAN=20
              style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
              face=3DTahoma size=3D2><SPAN=20
              style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma"> DE CNODDER =
Stefaan=20
              [mailto:stefaan.de_cnodder@alcatel-lucent.be] <BR><B><SPAN =

              style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> 28 April 2008 =

              17:15<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">To:</SPAN></B>=20
              Wojciech Dec (wdec); Busser, M; ancp@ietf.org<BR><B><SPAN=20
              style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B> Haag, =
T<BR><B><SPAN=20
              style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [ANCP] =
Mandatory=20
              TLVs in draft-ietf-ancp-protocol=20
              proposal</SPAN></FONT><o:p></o:p></P>
              <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
              lang=3DDE=20
style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
              <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
              lang=3DDE=20
              style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Take the=20
              bandwidth sub-TLV in port up messages as example.&nbsp; =
The=20
              current protocol spec says that it is mandatory&nbsp;to be =
sent in=20
              port up messages.&nbsp; that's ok.&nbsp; But it is not =
mandatory=20
              for the receiver to process the bandwidth sub-TLV.&nbsp; =
What is=20
              done with this information by the NAS is not specified by =
ANCP, so=20
              you cannot make it mandatory for the receiver=20
              side.</SPAN></FONT><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
              lang=3DDE=20
              style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><SPAN=20
              lang=3DDE><o:p></o:p></SPAN></P>
              <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
              lang=3DDE=20
style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
              <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
              lang=3DDE=20
              style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Woj&gt;=20
              Is the information required by the application? It would =
appear=20
              for the dynamic shaping use-case to be most certainly so. =
Hence it=20
              is absolutely mandatory, otherwise the message makes no =
sense for=20
              the application.</SPAN></FONT><FONT face=3DArial =
color=3Dblue=20
              size=3D2><SPAN lang=3DDE=20
              style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><FONT=20
              face=3DArial color=3Dblack size=3D2><SPAN lang=3DDE=20
              style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">In any=20
              case, if </SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P>
              <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
              lang=3DDE=20
style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
              <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
              lang=3DDE=20
              style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">So it=20
              looks to me that the flag can only indicate what the =
receiver=20
              should do.&nbsp; Then the flag makes =
sense.</SPAN></FONT><FONT=20
              face=3DArial color=3Dblack size=3D2><SPAN lang=3DDE=20
              style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><SPAN=20
              lang=3DDE><o:p></o:p></SPAN></P>
              <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
              lang=3DDE=20
style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
              <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
              lang=3DDE=20
              style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Woj&gt;=20
              </SPAN></FONT><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
              style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><FONT=20
              face=3DArial color=3Dblack size=3D2><SPAN lang=3DDE=20
              style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">The flag=20
              tells the receiver what info the sender thinks is required =
to=20
              carry out the application. This in almost all cases has to =
match=20
              up to what the receiver thinks is required. The=20
              sender&nbsp;doesn't tell the receiver what to do with the=20
              info.</SPAN></FONT><SPAN lang=3DDE><o:p></o:p></SPAN></P>
              <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
              lang=3DDE=20
style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
              <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
              lang=3DDE=20
              style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">If the=20
              receiver knows what is mandatory, then I do not see a =
reason why=20
              this has to be made explicit in the protocol.&nbsp; It =
would only=20
              complicate the protocol.&nbsp; As already said by Michael: =
if a=20
              mandatory TLV is not there, then it is just a=20
              bug.</SPAN></FONT><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
              lang=3DDE=20
              style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><SPAN=20
              lang=3DDE><o:p></o:p></SPAN></P>
              <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
              lang=3DDE=20
style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
              <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
              lang=3DDE=20
              style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Woj&gt;=20
              Can you specifically describe what aspect of the protocol =
does it=20
              complicate?</SPAN></FONT><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
              lang=3DDE=20
              style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><FONT=20
              face=3DArial color=3Dblack size=3D2><SPAN lang=3DDE=20
              style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">It's=20
              just making explicitly clear what the protocol already has =
to=20
              implement anyway to be of any use.</SPAN></FONT><SPAN=20
              lang=3DDE><o:p></o:p></SPAN></P>
              <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
              style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">As to =
whether it is a=20
              bug, having such explicit marking makes it clear =
what/where the=20
              problem is when observing a messaging flow&nbsp;vs a lot =
of=20
              deduction work. In any case, the other point being made=20
              here&nbsp;is that today the protocol does NOT specify what =
should=20
              happen if a mandatory TLV is missing.</SPAN></FONT><SPAN=20
              lang=3DDE><o:p></o:p></SPAN></P>
              <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
              lang=3DDE=20
style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
              <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
              style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">-Woj.</SPAN></FONT><SPAN=20
              lang=3DDE><o:p></o:p></SPAN></P>
              <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
              lang=3DDE=20
style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
              <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
              lang=3DDE=20
              style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">regards,</SPAN></FONT><SPAN=20
              lang=3DDE><o:p></o:p></SPAN></P>
              <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
              lang=3DDE=20
              style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Stefaan</SPAN></FONT><SPAN=20
              lang=3DDE><o:p></o:p></SPAN></P>
              <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
              lang=3DDE=20
style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
              <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
              lang=3DDE=20
style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
              <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
              lang=3DDE=20
style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
              <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
              face=3D"Times New Roman" size=3D3><SPAN =
style=3D"FONT-SIZE: 12pt">
              <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
              </SPAN></FONT></DIV>
              <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: =
12pt"><B><FONT=20
              face=3DTahoma size=3D2><SPAN=20
              style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
              face=3DTahoma size=3D2><SPAN=20
              style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma"> Wojciech =
Dec (wdec)=20
              [mailto:wdec@cisco.com] <BR><B><SPAN=20
              style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> maandag 28 =
april 2008=20
              16:28<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">To:</SPAN></B> DE=20
              CNODDER Stefaan; Busser, M; ancp@ietf.org<BR><B><SPAN=20
              style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B> Haag, =
T<BR><B><SPAN=20
              style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [ANCP] =
Mandatory=20
              TLVs in draft-ietf-ancp-protocol=20
              proposal</SPAN></FONT><o:p></o:p></P>
              <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
              style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">It's =
actually a mix of=20
              both. Inline...</SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P>
              <BLOCKQUOTE=20
              style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; =
BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: =
5pt 0in 5pt 3.75pt; BORDER-LEFT: black 1.5pt solid; PADDING-TOP: 0in; =
BORDER-BOTTOM: medium none">
                <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                lang=3DDE=20
                style=3D"FONT-SIZE: =
12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
                <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center"=20
                align=3Dcenter><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                style=3D"FONT-SIZE: 12pt">
                <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" =
SIZE=3D2>
                </SPAN></FONT></DIV>
                <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: =
12pt"><B><FONT=20
                face=3DTahoma size=3D2><SPAN=20
                style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; =
FONT-FAMILY: Tahoma">From:</SPAN></FONT></B><FONT=20
                face=3DTahoma size=3D2><SPAN=20
                style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">=20
                ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] =
<B><SPAN=20
                style=3D"FONT-WEIGHT: bold">On Behalf Of </SPAN></B>DE =
CNODDER=20
                Stefaan<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">Sent:</SPAN></B>=20
                28 April 2008 16:04<BR><B><SPAN=20
                style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Wojciech Dec =
(wdec);=20
                Busser, M; ancp@ietf.org<BR><B><SPAN=20
                style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B> Haag, =
T<BR><B><SPAN=20
                style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> Re: =
[ANCP]=20
                Mandatory TLVs in draft-ietf-ancp-protocol=20
                proposal</SPAN></FONT><o:p></o:p></P>
                <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                lang=3DDE=20
                style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
                <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
                lang=3DDE=20
                style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Hi,</SPAN></FONT><SPAN=20
                lang=3DDE><o:p></o:p></SPAN></P>
                <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                lang=3DDE=20
                style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
                <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
                lang=3DDE=20
                style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">This=20
                new mandatory flag, what is exactly its=20
                meaning?</SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P>
                <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                lang=3DDE=20
                style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
                <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
                lang=3DDE=20
                style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">(1)&nbsp;if=20
                flag set to "mandatory", then the *receiver* of this TLV =
MUST=20
                process it, and if unrecognized must drop the=20
                message</SPAN></FONT><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
                lang=3DDE=20
                style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><SPAN=20
                lang=3DDE><o:p></o:p></SPAN></P>
                <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                lang=3DDE=20
                style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
                <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
                lang=3DDE=20
                style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">If a=20
                received TLV is has the&nbsp;"mandatory" flag =
set&nbsp;then the=20
                receiver MUST drop the message and report an error to =
the=20
                sender&nbsp;if it doesn't recognize the =
TLV.</SPAN></FONT><FONT=20
                face=3DArial color=3Dblue size=3D2><SPAN lang=3DDE=20
                style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><SPAN=20
                lang=3DDE><o:p></o:p></SPAN></P>
                <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
                lang=3DDE=20
                style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">If a=20
                the receiver expects a&nbsp;"mandatory" TLV but doesn't =
receive=20
                it,&nbsp;the message MUST be&nbsp;droped&nbsp;and =
an&nbsp;error=20
                report&nbsp;sent to the&nbsp;sender.</SPAN></FONT><FONT=20
                face=3DArial color=3Dblue size=3D2><SPAN lang=3DDE=20
                style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><SPAN=20
                lang=3DDE><o:p></o:p></SPAN></P>
                <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                lang=3DDE=20
                style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
                <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
                lang=3DDE=20
                style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">OR</SPAN></FONT><SPAN=20
                lang=3DDE><o:p></o:p></SPAN></P>
                <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                lang=3DDE=20
                style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
                <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
                lang=3DDE=20
                style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">(2)&nbsp;if=20
                flag is set to"mandatory", then the *sender* MUST =
include it in=20
                the message for which it is defined</SPAN></FONT><FONT=20
                face=3DArial color=3Dblack size=3D2><SPAN lang=3DDE=20
                style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><SPAN=20
                lang=3DDE><o:p></o:p></SPAN></P>
                <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                lang=3DDE=20
                style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
                <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
                lang=3DDE=20
                style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">The=20
                sender MUST include mandatory TLVs as defined by the=20
                protocol-spec/applications.</SPAN></FONT><SPAN=20
                lang=3DDE><o:p></o:p></SPAN></P>
                <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                lang=3DDE=20
                style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
                <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
                lang=3DDE=20
                style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">The=20
                current protocols draft says for certain TLVs that they =
are=20
                mandatory, but that applies to the sender of it =
(interpretation=20
                2).&nbsp; The flag would indicate interpretation 1 (like =
for=20
                Radius VSAs?)?</SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P>
                <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                lang=3DDE=20
                style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
                <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
                lang=3DDE=20
                style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">If the=20
                higher order bit is set to "0" means that it is =
mandatory, then=20
                currently defined optional defined TLVs suddenly become=20
                mandatory which is not good.</SPAN></FONT><FONT =
face=3DArial=20
                color=3Dblack size=3D2><SPAN lang=3DDE=20
                style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><SPAN=20
                lang=3DDE><o:p></o:p></SPAN></P>
                <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                lang=3DDE=20
                style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
                <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
                lang=3DDE=20
                style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Woj&gt;=20
                Only the currently used TLVs&nbsp;become mandatory. If =
they are=20
                not used/implemented we can re-define them as optional =
(set flag=20
                to 1) at no cost. </SPAN></FONT><SPAN=20
                lang=3DDE><o:p></o:p></SPAN></P>
                <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                lang=3DDE=20
                style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
                <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
                lang=3DDE=20
                style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">But I=20
                would first to understand the exact meaning of this =
mandatory=20
                flag.&nbsp; Defining such a flag indeed looks useful but =
then as=20
                interpretation 1, and I would say that if flag set to 1, =
then it=20
                is mandatory and actually, it is possible that a TLV is =
sent=20
                sometimes as optional and sometimes as=20
                mandatory.</SPAN></FONT><FONT face=3DArial color=3Dblack =

                size=3D2><SPAN lang=3DDE=20
                style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><SPAN=20
                lang=3DDE><o:p></o:p></SPAN></P>
                <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                lang=3DDE=20
                style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
                <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
                lang=3DDE=20
                style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Woj&gt;=20
                Precisely, that is possible on a per application=20
                basis.</SPAN></FONT><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
                lang=3DDE=20
                style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><FONT=20
                face=3DArial color=3Dblack size=3D2><SPAN lang=3DDE=20
                style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Having=20
                the flag would make troubleshooting of a message =
flow&nbsp;much=20
                more explicit (today, with any problem&nbsp;one has to =
browse=20
                the drafts to figure out what MUST be there vs what =
SHOULD be=20
                there&nbsp;all while looking&nbsp;what is actually=20
                there)</SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P>
                <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                lang=3DDE=20
                style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
                <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
                lang=3DDE=20
                style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Regards,</SPAN></FONT><SPAN=20
                lang=3DDE><o:p></o:p></SPAN></P>
                <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
                lang=3DDE=20
                style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Woj.</SPAN></FONT><SPAN=20
                lang=3DDE><o:p></o:p></SPAN></P>
                <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                lang=3DDE=20
                style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
                <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
                lang=3DDE=20
                style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">regards,</SPAN></FONT><SPAN=20
                lang=3DDE><o:p></o:p></SPAN></P>
                <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
                lang=3DDE=20
                style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Stefaan</SPAN></FONT><SPAN=20
                lang=3DDE><o:p></o:p></SPAN></P>
                <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                lang=3DDE=20
                style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
                <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                lang=3DDE=20
                style=3D"FONT-SIZE: =
12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
                <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center"=20
                align=3Dcenter><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                style=3D"FONT-SIZE: 12pt">
                <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" =
SIZE=3D2>
                </SPAN></FONT></DIV>
                <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: =
12pt"><B><FONT=20
                face=3DTahoma size=3D2><SPAN=20
                style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; =
FONT-FAMILY: Tahoma">From:</SPAN></FONT></B><FONT=20
                face=3DTahoma size=3D2><SPAN=20
                style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">=20
                ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] =
<B><SPAN=20
                style=3D"FONT-WEIGHT: bold">On Behalf Of =
</SPAN></B>Wojciech Dec=20
                (wdec)<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">Sent:</SPAN></B>=20
                donderdag 24 april 2008 14:19<BR><B><SPAN=20
                style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Busser, M;=20
                ancp@ietf.org<BR><B><SPAN=20
                style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B> Haag, =
T<BR><B><SPAN=20
                style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> Re: =
[ANCP]=20
                Mandatory TLVs in draft-ietf-ancp-protocol=20
                proposal</SPAN></FONT><o:p></o:p></P>
                <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
                style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Hi=20
                Michael,</SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P>
                <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                lang=3DDE=20
                style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
                <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
                style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">inline...</SPAN></FONT><SPAN=20
                lang=3DDE><o:p></o:p></SPAN></P>
                <BLOCKQUOTE=20
                style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; =
BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: =
5pt 0in 5pt 3.75pt; BORDER-LEFT: black 1.5pt solid; PADDING-TOP: 0in; =
BORDER-BOTTOM: medium none">
                  <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-SIZE: =
12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
                  <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center"=20
                  align=3Dcenter><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                  style=3D"FONT-SIZE: 12pt">
                  <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" =
SIZE=3D2>
                  </SPAN></FONT></DIV>
                  <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: =
12pt"><B><FONT=20
                  face=3DTahoma size=3D2><SPAN=20
                  style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; =
FONT-FAMILY: Tahoma">From:</SPAN></FONT></B><FONT=20
                  face=3DTahoma size=3D2><SPAN=20
                  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">=20
                  ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] =
<B><SPAN=20
                  style=3D"FONT-WEIGHT: bold">On Behalf Of =
</SPAN></B>Busser,=20
                  M<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">Sent:</SPAN></B> 24=20
                  April 2008 13:13<BR><B><SPAN=20
                  style=3D"FONT-WEIGHT: bold">To:</SPAN></B>=20
                  ancp@ietf.org<BR><B><SPAN=20
                  style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B> Haag, =
T<BR><B><SPAN=20
                  style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> Re: =
[ANCP]=20
                  Mandatory TLVs in draft-ietf-ancp-protocol=20
                  proposal</SPAN></FONT><o:p></o:p></P>
                  <DIV>
                  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
                  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Hi Woi,=20
                  all</SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P></DIV>
                  <DIV>
                  <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
                  <DIV>
                  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
                  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">I see =
the problem=20
                  but i can not see, how an additional flag will help =
solving=20
                  this problem.</SPAN></FONT><SPAN=20
                  lang=3DDE><o:p></o:p></SPAN></P></DIV>
                  <DIV>
                  <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
                  <DIV>
                  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
                  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Lets =
assume your=20
                  first&nbsp;proposal.</SPAN></FONT><SPAN=20
                  lang=3DDE><o:p></o:p></SPAN></P></DIV>
                  <DIV>
                  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
                  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">If&nbsp;an=20
                  implementation does not send the complete&nbsp;TLV, =
even it is=20
                  defined&nbsp;to be&nbsp;mandatory,&nbsp;I would call =
this a=20
                  bug and&nbsp;I can not see, how an additional flag can =
help=20
                  here.&nbsp;</SPAN></FONT><SPAN=20
                  lang=3DDE><o:p></o:p></SPAN></P></DIV>
                  <DIV>
                  <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
                  <DIV>
                  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
                  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Woj&gt; =
The way it=20
                  helps, and other protocols bear proof of this scheme, =
is that=20
                  it is easier for implementations to reconcile errors =
resulting=20
                  out of "Mandatory" and "Optional"&nbsp;TLV sets. The =
key to=20
                  this lies on a per application basis. One application =
may=20
                  mandate TLV A for operation, while another might not.=20
                  Resolving such issues when implementing or =
troubleshooting=20
                  multiple applications is not always trivial.=20
                  </SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P></DIV>
                  <DIV>
                  <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
                  <DIV>
                  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
                  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Your =
second=20
                  proposal seems obviously&nbsp;be required to keep =
existing=20
                  things working, if we&nbsp;agree on&nbsp;your first =
proposal.=20
                  </SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P></DIV>
                  <DIV>
                  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
                  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">But from =
my point=20
                  of view&nbsp;it also assumes, that all existing=20
                  implementations are using the same set of TLVs now.=20
                  </SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P></DIV>
                  <DIV>
                  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
                  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">And&nbsp;I am not=20
                  sure about&nbsp;that.&nbsp;&nbsp;</SPAN></FONT><SPAN=20
                  lang=3DDE><o:p></o:p></SPAN></P></DIV>
                  <DIV>
                  <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
                  <DIV>
                  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
                  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Woj&gt; =
This would=20
                  be a good thing for the WG to discuss. There most =
evidently is=20
                  a fair amount of&nbsp;"dead wood" in the current spec, =
ie=20
                  stuff that nobody yet&nbsp;implements or cares about. =
&nbsp;In=20
                  the former case, we could re-cast that material using =
the new=20
                  notions/extensions, in the latter case simply chop it=20
                  out.</SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P></DIV>
                  <DIV>
                  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
                  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
                  <DIV>
                  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
                  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Therefore I=20
                  disagree with your first proposal. I recommend, the =
better=20
                  way&nbsp;will be to be more precise in=20
                  definitions.&nbsp;</SPAN></FONT><SPAN=20
                  lang=3DDE><o:p></o:p></SPAN></P></DIV>
                  <DIV>
                  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
                  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">In my =
mind, it is=20
                  a bug, if a mandatory TLV is missing. It is up to the=20
                  robustness of the implementation&nbsp;to deal with =
this=20
                  situation.</SPAN></FONT><SPAN=20
                  lang=3DDE><o:p></o:p></SPAN></P></DIV>
                  <DIV>
                  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
                  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Is it =
really=20
                  neccesary to define the behavior of a network element =
in this=20
                  case of failure in the ancp protocol=20
                  itself?&nbsp;&nbsp;</SPAN></FONT><SPAN=20
                  lang=3DDE><o:p></o:p></SPAN></P></DIV>
                  <DIV>
                  <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
                  <DIV>
                  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
                  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Woj&gt; =
Other=20
                  people have faced this problem before, and I would =
rather go=20
                  with the lessons they learned, rather than clinging to =
hopes=20
                  of perfect textual definitions and implementations. =
Other than=20
                  backwards compatibility, I do not see in your =
statements a=20
                  valid reason&nbsp;to object to the 1st&nbsp;proposal,=20
                  particularly for new applications since it can only =
make=20
                  things more robust. The counter argument of being =
precise in=20
                  the definitions, as evidenced by the current spec, is=20
                  admirable and needs to be there, with this proposal =
providing=20
                  an extra level of robustness and visibility of any =
problems.=20
                  </SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P></DIV>
                  <DIV>
                  <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
                  <DIV>
                  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
                  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Thanks,</SPAN></FONT><SPAN=20
                  lang=3DDE><o:p></o:p></SPAN></P></DIV>
                  <DIV>
                  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
                  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Woj.</SPAN></FONT><SPAN=20
                  lang=3DDE><o:p></o:p></SPAN></P></DIV>
                  <DIV>
                  <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
                  <DIV>
                  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
                  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">If =
optional TLVs=20
                  are not present in a message, we should describe some =
kind of=20
                  default behaviour, as you already =
stated.</SPAN></FONT><SPAN=20
                  lang=3DDE><o:p></o:p></SPAN></P></DIV>
                  <DIV>
                  <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
                  <DIV>
                  <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
                  <DIV>
                  <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
                  <DIV>
                  <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
                  <DIV>
                  <DIV>
                  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
                  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Comments =
on=20
                  =
draft-ietf-ancp-protocol-02.txt:<o:p></o:p></SPAN></FONT></P></DIV></DIV>=

                  <DIV>
                  <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
                  <DIV>
                  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
                  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">It is =
not clearly=20
                  stated,&nbsp;if the TLV &nbsp;"</SPAN></FONT><FONT=20
                  size=3D2><SPAN lang=3DEN-GB style=3D"FONT-SIZE: =
10pt">DSL Line=20
                  Attributes "</SPAN></FONT><FONT face=3DArial =
size=3D2><SPAN=20
                  lang=3DEN-GB style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"> is=20
                  mandatory or optional. </SPAN></FONT><SPAN=20
                  lang=3DDE><o:p></o:p></SPAN></P></DIV>
                  <DIV>
                  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DEN-GB=20
                  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">In fact =
it is=20
                  mandatory because some of its SubTLVs are mandatory.=20
                  </SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P></DIV>
                  <DIV>
                  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DEN-GB=20
                  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">We =
should spent a=20
                  sentence to make this clear.</SPAN></FONT><SPAN=20
                  lang=3DDE><o:p></o:p></SPAN></P></DIV>
                  <DIV>
                  <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
                  <DIV>
                  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
                  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">It is =
not clearly=20
                  stated,&nbsp;if the TLV &nbsp;"</SPAN></FONT><FONT=20
                  size=3D2><SPAN lang=3DEN-GB=20
                  style=3D"FONT-SIZE: =
10pt">Service-Profile-Name"</SPAN></FONT><FONT=20
                  face=3DArial size=3D2><SPAN lang=3DEN-GB=20
                  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"> is =
mandatory or=20
                  optional.</SPAN></FONT><SPAN=20
                  lang=3DDE><o:p></o:p></SPAN></P></DIV>
                  <DIV>
                  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DEN-GB=20
                  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">I prefer =
mandatory=20
                  because it is essetial for the use case Line=20
                  Config.&nbsp;</SPAN></FONT><FONT face=3DArial =
size=3D2><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></P></DIV>
                  <DIV>
                  <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
                  <DIV>
                  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
                  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Section =
5.4.3 Line=20
                  Config, where the TLVs are mentioned (page=20
                  35):</SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P></DIV>
                  <DIV>
                  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
                  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp; =
...defined=20
                  in section 5.4.1....&nbsp;&nbsp;&nbsp; must be =
corrected=20
                  to&nbsp;&nbsp;&nbsp; ...defined in section=20
                  5.4.2........</SPAN></FONT><SPAN=20
                  lang=3DDE><o:p></o:p></SPAN></P></DIV>
                  <DIV>
                  <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
                  <DIV>
                  <DIV>
                  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
                  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Section=20
                  5.4.4&nbsp;OAM, where the TLVs are mentioned (page 36 =
and page=20
                  38):</SPAN></FONT><FONT size=3D2><SPAN lang=3DDE=20
                  style=3D"FONT-SIZE: =
10pt"><o:p></o:p></SPAN></FONT></P></DIV>
                  <DIV>
                  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
                  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp; =
...defined=20
                  in section 5.4.1....&nbsp;&nbsp;&nbsp; must be =
corrected=20
                  to&nbsp;&nbsp;&nbsp; ...defined in section=20
                  5.4.2........</SPAN></FONT><FONT size=3D2><SPAN =
lang=3DDE=20
                  style=3D"FONT-SIZE: =
10pt"><o:p></o:p></SPAN></FONT></P></DIV>
                  <DIV>
                  <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D2><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-SIZE: =
10pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
                  <DIV>
                  <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV></DIV>
                  <DIV>
                  <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
                  <DIV>
                  <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
                  <P><FONT face=3D"Times New Roman" color=3Dnavy =
size=3D3><SPAN=20
                  lang=3DDE style=3D"FONT-SIZE: 12pt; COLOR: navy">Best =
Regards;=20
                  Freundliche Gr=FC=DFe <o:p></o:p></SPAN></FONT></P>
                  <P><B><FONT face=3D"Times New Roman" color=3Dnavy =
size=3D3><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-WEIGHT: bold; FONT-SIZE: 12pt; COLOR: =
navy">Michael=20
                  Busser<o:p></o:p></SPAN></FONT></B></P>
                  <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D1><SPAN=20
                  lang=3DDE style=3D"FONT-SIZE: 8pt">T-Systems =
Enterprise Services=20
                  GmbH </SPAN></FONT><FONT size=3D1><SPAN lang=3DDE=20
                  style=3D"FONT-SIZE: =
7.5pt"><o:p></o:p></SPAN></FONT></P>
                  <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D1><SPAN=20
                  lang=3DDE style=3D"FONT-SIZE: 7.5pt">Production Line =
Network=20
                  Centric Systems<o:p></o:p></SPAN></FONT></P>
                  <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D1><SPAN=20
                  lang=3DDE style=3D"FONT-SIZE: 7.5pt">ICT-Systems=20
                  Integration<o:p></o:p></SPAN></FONT></P>
                  <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D1><SPAN=20
                  lang=3DDE style=3D"FONT-SIZE: 7.5pt">Network =
Integration=20
                  Services<o:p></o:p></SPAN></FONT></P>
                  <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D1><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-SIZE: =
7.5pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
                  <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
color=3Dblack=20
                  size=3D1><SPAN lang=3DDE=20
                  style=3D"FONT-SIZE: 7.5pt; COLOR: black">Br=FCckes 2 =
-8, 55545 Bad=20
                  Kreuznach<BR>Postfach 9100, 55541 Bad Kreuznach<BR>+49 =
671=20
                  8333 8911 (Phone)<BR>+49 521&nbsp;9210&nbsp;3859 =
(Fax)<BR>+49=20
                  151 1211&nbsp;9689 (Mobile)<BR>E-Mail: <A=20
                  =
href=3D"mailto:michael.busser@t-systems.com">michael.busser@t-systems.com=
</A></SPAN></FONT><FONT=20
                  size=3D1><SPAN lang=3DDE=20
                  style=3D"FONT-SIZE: 8pt"><o:p></o:p></SPAN></FONT></P>
                  <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D1><SPAN=20
                  lang=3DDE style=3D"FONT-SIZE: 8pt">Internet: <A=20
                  href=3D"http://www.t-systems.com/"=20
                  target=3D_parent><p:onmouseclick=20
                  href=3D"http://www.t-systems.com/"=20
                  hyperlinktype=3D"url"></p:onmouseclick><FONT =
color=3D#6699ff><SPAN=20
                  style=3D"COLOR: =
#6699ff">http://www.t-systems.com</SPAN></FONT></A>=20
                  </SPAN></FONT><FONT size=3D1><SPAN lang=3DDE=20
                  style=3D"FONT-SIZE: =
7.5pt"><o:p></o:p></SPAN></FONT></P>
                  <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D1><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-SIZE: =
7.5pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
                  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D1><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-SIZE: 7.5pt; COLOR: black; FONT-FAMILY: =
Arial">T-Systems=20
                  Enterprise Services GmbH<BR>Aufsichtsrat: Ren=E9 =
Obermann=20
                  (Vorsitzender)<BR>Executive Committee: Reinhard =
Clemens=20
                  (Vorsitzender)*, Helmut Binder, Albert Henn, Olaf =
Heyden*,=20
                  Katrin Horstmann, Ulrich Kemp, Wilfried =
Peters*,<BR>Dr.=20
                  Herbert Schaaff*, Zvezdana Seeger*<BR>Handelsregister: =

                  Amtsgericht Frankfurt am Main HRB 55933<BR>Sitz der=20
                  Gesellschaft: Frankfurt am Main<BR>WEEE-Reg.-Nr.=20
                  DE87523644<BR>*Gesch=E4ftsf=FChrer gem. =A7 35=20
                  GmbHG</SPAN></FONT><FONT size=3D1><SPAN lang=3DDE=20
                  style=3D"FONT-SIZE: =
7.5pt"><o:p></o:p></SPAN></FONT></P>
                  <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D1><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-SIZE: =
7.5pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
                  <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D1><SPAN=20
                  lang=3DDE style=3D"FONT-SIZE: 7.5pt">Notice: This =
transmittal=20
                  and/or attachments may be privileged or confidential. =
If you=20
                  are not the intended recipient, you are hereby =
notified that=20
                  you have received this transmittal in error; any =
review,=20
                  dissemination, or copying is strictly prohibited. If =
you=20
                  received this transmittal in error, please notify us=20
                  immediately by reply and immediately delete this =
message and=20
                  all its attachments. Thank you. <BR>T-Systems =96 =
Business=20
                  flexibility </SPAN></FONT><FONT size=3D1><SPAN =
lang=3DDE=20
                  style=3D"FONT-SIZE: 8pt"><o:p></o:p></SPAN></FONT></P>
                  <DIV>
                  <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D1><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-SIZE: =
7.5pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
                  <BLOCKQUOTE=20
                  style=3D"MARGIN-TOP: 5pt; MARGIN-BOTTOM: 5pt; =
MARGIN-RIGHT: 0in">
                    <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
                    lang=3DDE=20
                    style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
                    <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center"=20
                    align=3Dcenter><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                    lang=3DDE style=3D"FONT-SIZE: 12pt">
                    <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" =
SIZE=3D2>
                    </SPAN></FONT></DIV>
                    <DIV>
                    <P class=3DMsoNormal><B><FONT face=3DTahoma =
size=3D2><SPAN lang=3DDE=20
                    style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; =
FONT-FAMILY: Tahoma">Von:</SPAN></FONT></B><FONT=20
                    face=3DTahoma size=3D2><SPAN lang=3DDE=20
                    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">=20
                    ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] =

                    <B><SPAN style=3D"FONT-WEIGHT: bold">Im Auftrag von=20
                    </SPAN></B>Wojciech Dec (wdec)<BR><B><SPAN=20
                    style=3D"FONT-WEIGHT: bold">Gesendet:</SPAN></B> =
Mittwoch, 23.=20
                    April 2008 14:54<BR><B><SPAN=20
                    style=3D"FONT-WEIGHT: bold">An:</SPAN></B>=20
                    ancp@ietf.org<BR><B><SPAN=20
                    style=3D"FONT-WEIGHT: bold">Betreff:</SPAN></B> =
[ANCP]=20
                    Mandatory TLVs in draft-ietf-ancp-protocol=20
                    proposal</SPAN></FONT><SPAN=20
                    lang=3DDE><o:p></o:p></SPAN></P></DIV>
                    <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                    lang=3DDE=20
                    style=3D"FONT-SIZE: =
12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
                    <P><FONT face=3DArial size=3D2><SPAN lang=3DEN-GB=20
                    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Hi=20
                    All,</SPAN></FONT><SPAN lang=3DEN-GB> </SPAN><SPAN=20
                    lang=3DDE><o:p></o:p></SPAN></P>
                    <P><FONT face=3DArial size=3D2><SPAN lang=3DEN-GB=20
                    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Continuing with=20
                    the series of e-mails regarding basic protocol =
issues still=20
                    to be addressed, I now would now like to ask your =
feedback=20
                    regarding the distinction the protocol places on =
mandatory=20
                    TLVs. Given the length of this mail I'll first cut =
to the=20
                    proposal, and after it you can find the problem=20
                    description.</SPAN></FONT><SPAN=20
                    lang=3DDE><o:p></o:p></SPAN></P>
                    <P><FONT face=3DArial size=3D2><SPAN lang=3DEN-GB=20
                    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">The =
proposal=20
                    which I am putting in front of the WG is to define a =
new TLV=20
                    format which contains at a minimum a Mandatory flag =
(much=20
                    like Radius VSAs do). We could have this TLV Flag be =
defined=20
                    only for new applications.</SPAN></FONT><SPAN=20
                    lang=3DDE><o:p></o:p></SPAN></P>
                    <P><FONT face=3DArial size=3D2><SPAN lang=3DEN-GB=20
                    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">A =
second=20
                    proposal would be try to make this flag work with =
existing=20
                    ones by for example defining the highest order bit =
of the=20
                    TLV# field to mean "Mandatory" when set to "0". This =
would=20
                    be invisible to exiting implementations, but newer =
ones may=20
                    have problems in communicating with older ones when =
the=20
                    latter do not send all TLVs. But that can also be =
addressed=20
                    by simply forming the set of mandatory TLVs to be =
the ones=20
                    that all implementations currently send by=20
                    default.</SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P>
                    <P><FONT face=3DArial size=3D2><SPAN lang=3DEN-GB=20
                    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Without=20
                    additional feedback, I will assume that the WG is =
fine with=20
                    the first proposal, and also with the 2nd one =
conditional on=20
                    deriving a suitable "commonly used" TLV=20
                    set.</SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P>
                    <P><FONT face=3DArial size=3D2><SPAN lang=3DEN-GB=20
                    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">The =
problem in=20
                    more detail: </SPAN></FONT><SPAN=20
                    lang=3DDE><o:p></o:p></SPAN></P>
                    <P><FONT face=3DArial size=3D2><SPAN lang=3DEN-GB=20
                    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Currently the=20
                    situation is that Mandatory TLVs are only stated to =
be as=20
                    such in the body of the protocol draft spec, with an =

                    implementer having to scour fairly attentively the =
text. Eg=20
                    "Type (Access-Loop-Circuit-ID =3D 0x01): This is a =
mandatory=20
                    TLV", etc.</SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P>
                    <P><FONT face=3DArial size=3D2><SPAN lang=3DEN-GB=20
                    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">The =
behaviour of=20
                    an implementation that receives a message with a =
missing=20
                    mandatory TLV is not defined at all, and the =
opposite is=20
                    handled but not very robustly, i.e. when receiving a =
TLV but=20
                    not recognizing it, and implementation is free to =
discard it=20
                    (even if it is mandatory!). This is a recipe for=20
                    interoperability problems and an implementation mine =

                    field.</SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P>
                    <P><FONT face=3DArial size=3D2><SPAN lang=3DEN-GB=20
                    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">This =
problem is=20
                    complicated by different applications. For example =
the=20
                    current OAM section states the following regarding =
TLVs that=20
                    are to be carried in the request message (my=20
                    italics):</SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P>
                    <P><FONT face=3DArial size=3D2><SPAN lang=3DEN-GB=20
                    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">"</SPAN></FONT><SPAN=20
                    lang=3DDE> <BR></SPAN><FONT face=3D"Courier New" =
color=3Dblack=20
                    size=3D2><SPAN=20
                    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
'Courier New'">Following=20
                    TLVs<B><I><SPAN=20
                    style=3D"FONT-WEIGHT: bold; FONT-STYLE: italic">=20
                    can</SPAN></I></B> appear in this message:=20
                    </SPAN></FONT><SPAN lang=3DDE><o:p></o:p></SPAN></P>
                    <P><FONT face=3D"Courier New" color=3Dblack =
size=3D2><SPAN=20
                    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
'Courier New'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
                    o Type (Access-Loop-Circuit-ID =3D 0x01) : defined =
in section=20
                    5.4.1&nbsp;&nbsp;&nbsp; </SPAN></FONT><SPAN=20
                    lang=3DDE><o:p></o:p></SPAN></P>
                    <P><FONT face=3D"Courier New" color=3Dblack =
size=3D2><SPAN=20
                    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
'Courier New'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
                    o Type (Access-Aggregation-Circuit-ID-Binary =3D =
0x06):=20
                    defined in </SPAN></FONT><SPAN =
lang=3DDE><BR></SPAN><FONT=20
                    face=3D"Courier New" color=3Dblack size=3D2><SPAN=20
                    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
'Courier New'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
                    section 5.4.1. </SPAN></FONT><SPAN =
lang=3DDE><BR></SPAN><FONT=20
                    face=3D"Courier New" color=3Dblack size=3D2><SPAN=20
                    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
'Courier New'">&nbsp;</SPAN></FONT><SPAN=20
                    lang=3DDE> <BR></SPAN><FONT face=3D"Courier New" =
color=3Dblack=20
                    size=3D2><SPAN=20
                    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
'Courier New'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
                    o Type (Access-Aggregation-Circuit-ID-ASCII =3D =
0x03): defined=20
                    in section </SPAN></FONT><SPAN =
lang=3DDE><BR></SPAN><FONT=20
                    face=3D"Courier New" color=3Dblack size=3D2><SPAN=20
                    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
'Courier New'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
                    5.4.1.&nbsp; </SPAN></FONT><SPAN=20
                    lang=3DDE><o:p></o:p></SPAN></P>
                    <P><FONT face=3D"Courier New" color=3Dblack =
size=3D2><SPAN=20
                    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
'Courier New'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
                    o Type (OAM-Loopback-Test-Parameters =3D 0x07): =
Parameters=20
                    related to&nbsp; </SPAN></FONT><SPAN=20
                    lang=3DDE><BR></SPAN><FONT face=3D"Courier New" =
color=3Dblack=20
                    size=3D2><SPAN=20
                    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
'Courier New'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
                    loopback test. This is an optional TLV. If this TLV =
is not=20
                    present </SPAN></FONT><SPAN =
lang=3DDE><BR></SPAN><FONT=20
                    face=3D"Courier New" color=3Dblack size=3D2><SPAN=20
                    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
'Courier New'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
                    in the request message, the DSLAM SHOULD use locally =

                    determined </SPAN></FONT><SPAN =
lang=3DDE><BR></SPAN><FONT=20
                    face=3D"Courier New" color=3Dblack size=3D2><SPAN=20
                    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
'Courier New'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
                    default values for the test parameters.&nbsp;=20
                    </SPAN></FONT><SPAN lang=3DDE><BR></SPAN><FONT=20
                    face=3D"Courier New" color=3Dblack size=3D2><SPAN=20
                    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
'Courier New'">"</SPAN></FONT><SPAN=20
                    lang=3DDE> <BR></SPAN><FONT face=3DArial =
color=3Dblack=20
                    size=3D2><SPAN=20
                    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">(NOTE:=20
                    The last "SHOULD" appears to be inappropriate. If =
the TLV is=20
                    missing, the DSLAM MUST have some default =
parameters, or=20
                    return an error)</SPAN></FONT><SPAN=20
                    lang=3DDE><o:p></o:p></SPAN></P>
                    <P><FONT face=3DArial color=3Dblack size=3D2><SPAN=20
                    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">The=20
                    "can" above indicates that they're all optional, =
while=20
                    clearly the application cannot run its course =
without one or=20
                    more of these fields. Here we have a case where one =
could=20
                    have a perfectly compliant implementation that =
ignores all=20
                    these TLVs=85</SPAN></FONT><SPAN=20
lang=3DDE><o:p></o:p></SPAN></P>
                    <P><FONT face=3DArial color=3Dblack size=3D2><SPAN=20
                    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">-Woj.</SPAN></FONT>=20
                    <SPAN lang=3DDE><o:p></o:p></SPAN></P>
                    <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: =
12pt"><FONT=20
                    face=3D"Times New Roman" size=3D3><SPAN lang=3DDE=20
                    style=3D"FONT-SIZE: =
12pt"><BR><BR><BR><BR><BR><BR><BR><BR><BR><o:p></o:p></SPAN></FONT></P></=
BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUO=
TE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C8AF96.F40D1A81--

--===============1152964927==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1152964927==--


From ancp-bounces@ietf.org  Tue May  6 09:43:35 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 194D93A6890;
	Tue,  6 May 2008 09:43:35 -0700 (PDT)
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 3F0F93A67A3
	for <ancp@core3.amsl.com>; Tue,  6 May 2008 09:43:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.298
X-Spam-Level: 
X-Spam-Status: No, score=-5.298 tagged_above=-999 required=5 tests=[AWL=1.300, 
	BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 W2skzPK5xnGi for <ancp@core3.amsl.com>;
	Tue,  6 May 2008 09:43:29 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id 45F3B3A6B71
	for <ancp@ietf.org>; Tue,  6 May 2008 09:43:28 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,444,1204498800"; d="scan'208,217";a="8174958"
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 06 May 2008 18:43:25 +0200
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m46GhPlt018519; 
	Tue, 6 May 2008 18:43:25 +0200
Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com
	[144.254.231.71])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m46GhPXZ004464;
	Tue, 6 May 2008 16:43:25 GMT
Received: from xmb-ams-33b.cisco.com ([144.254.231.86]) by
	xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 6 May 2008 18:43:25 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 6 May 2008 18:42:25 +0200
Message-ID: <D9872168DBD43A41BD71FFC4713274D405043733@xmb-ams-33b.emea.cisco.com>
In-Reply-To: <D9872168DBD43A41BD71FFC4713274D404F12512@xmb-ams-33b.emea.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ANCP] Bulk Transaction Message
thread-index: AcihZWeDZVeOVtxMS1uttRBEffcNEwAVDjfgAEod1tAAAWRvoAMsB4yQ
References: <D9872168DBD43A41BD71FFC4713274D404F12299@xmb-ams-33b.emea.cisco.com><48C276B536524E478C659685995F6AA539DBA2CA93@RBSJX.ad.redback.com><D9872168DBD43A41BD71FFC4713274D404F12507@xmb-ams-33b.emea.cisco.com>
	<D9872168DBD43A41BD71FFC4713274D404F12512@xmb-ams-33b.emea.cisco.com>
From: "Wojciech Dec (wdec)" <wdec@cisco.com>
To: "Peter Arberg" <parberg@redback.com>, <ancp@ietf.org>
X-OriginalArrivalTime: 06 May 2008 16:43:25.0493 (UTC)
	FILETIME=[4DC86E50:01C8AF98]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=9773; t=1210092205;
	x=1210956205; c=relaxed/simple; s=amsdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=wdec@cisco.com;
	z=From:=20=22Wojciech=20Dec=20(wdec)=22=20<wdec@cisco.com>
	|Subject:=20RE=3A=20[ANCP]=20Bulk=20Transaction=20Message
	|Sender:=20; bh=L2zrPnhNOlQH4SJCHX6Q4o3P8hPjI/T5Di7+BtVqFhg=;
	b=HEBz5btThZS5dJ0tMEYmsrLbvTu/CQ2v/CWaxAjdKBHYvFyZk5Y0uvz0Ad
	GDRZBI89TNzpCoOruvsvxZPleSFrdT+AzWWF3lGyfIN8csmT2abEoosx093J
	r/BrMTX8W5;
Authentication-Results: ams-dkim-2; header.From=wdec@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim2001 verified; ); 
Subject: Re: [ANCP] Bulk Transaction Message
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/pipermail/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>
Content-Type: multipart/mixed; boundary="===============1915971896=="
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1915971896==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8AF98.4D6BCDE2"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8AF98.4D6BCDE2
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Folks,
=20
given that no discernable use of Bulk messaging has been identified, nor
there being a good reason for it given the fact that ANCP is bound to
the TCP transport (or equivalent), I would like to propose to remove all
of the text relating to this capability and associated message from the
protocol spec draft.
=20
Regards,
Woj.


________________________________

	From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On
Behalf Of Wojciech Dec (wdec)
	Sent: 20 April 2008 15:18
	To: Peter Arberg; ancp@ietf.org
	Subject: Re: [ANCP] Bulk Transaction Message
=09
=09
	Should also have added: Given that currently the bulk message
does not appear to have had any practical adoption, having the DTeam
adopt it/modify it, or possibly have it removed from the spec all
together are all valid options.
	=20
	-Woj.


________________________________

		From: ancp-bounces@ietf.org
[mailto:ancp-bounces@ietf.org] On Behalf Of Wojciech Dec (wdec)
		Sent: 20 April 2008 14:39
		To: Peter Arberg; ancp@ietf.org
		Subject: Re: [ANCP] Bulk Transaction Message
	=09
	=09
		It's all simple:
		- the Design Team is looking at the possibility of using
this message
		- the message in its current form does not appear to be
terribly useful, and could be removed from the spec.
		=20
		-Woj.
		=20


________________________________

			From: ancp-bounces@ietf.org
[mailto:ancp-bounces@ietf.org] On Behalf Of Peter Arberg
			Sent: 19 April 2008 03:07
			To: Wojciech Dec (wdec); ancp@ietf.org
			Subject: Re: [ANCP] Bulk Transaction Message
		=09
		=09
			Hi Woj,
			=20
			can you give a little background to why you are
looking for vendor
			implementation support for this specific
capability & message ?
			=20
			thanks,
			Peter


________________________________

				From: ancp-bounces@ietf.org
[mailto:ancp-bounces@ietf.org] On Behalf Of Wojciech Dec (wdec)
				Sent: 18. april 2008 08:04
				To: ancp@ietf.org
				Subject: [ANCP] Bulk Transaction Message
			=09
			=09

				Hi Folks,=20

				Could you please let me/us know if you
currently have an implementation of ANCP that supports the Bulk
Transaction Capability and Message?

				Thanks,=20
				Woj.=20


------_=_NextPart_001_01C8AF98.4D6BCDE2
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Bulk Transaction Message</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3314" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
class=3D811403916-06052008>Hi Folks,</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
class=3D811403916-06052008></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
class=3D811403916-06052008>given that no discernable use of Bulk =
messaging has=20
been identified, nor&nbsp;there being a good reason for it given the =
fact that=20
ANCP is bound to the TCP transport (or equivalent),&nbsp;I would like to =
propose=20
to remove all of the text relating to this capability and associated =
message=20
from the protocol spec draft.</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
class=3D811403916-06052008></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
class=3D811403916-06052008>Regards,</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
class=3D811403916-06052008>Woj.</SPAN></FONT></DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> ancp-bounces@ietf.org=20
  [mailto:ancp-bounces@ietf.org] <B>On Behalf Of </B>Wojciech Dec=20
  (wdec)<BR><B>Sent:</B> 20 April 2008 15:18<BR><B>To:</B> Peter Arberg; =

  ancp@ietf.org<BR><B>Subject:</B> Re: [ANCP] Bulk Transaction=20
  Message<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D490440813-20042008><FONT =
face=3DArial=20
  size=3D2>Should also have added: Given that currently&nbsp;the bulk =
message does=20
  not appear to have had any practical&nbsp;adoption, having the DTeam =
adopt=20
  it/modify it, or possibly have it removed from the spec all =
together&nbsp;are=20
  all valid options.</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D490440813-20042008><FONT =
face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D490440813-20042008><FONT =
face=3DArial=20
  size=3D2>-Woj.</FONT></SPAN></DIV><BR>
  <BLOCKQUOTE dir=3Dltr=20
  style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px =
solid; MARGIN-RIGHT: 0px">
    <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
    <HR tabIndex=3D-1>
    <FONT face=3DTahoma size=3D2><B>From:</B> ancp-bounces@ietf.org=20
    [mailto:ancp-bounces@ietf.org] <B>On Behalf Of </B>Wojciech Dec=20
    (wdec)<BR><B>Sent:</B> 20 April 2008 14:39<BR><B>To:</B> Peter =
Arberg;=20
    ancp@ietf.org<BR><B>Subject:</B> Re: [ANCP] Bulk Transaction=20
    Message<BR></FONT><BR></DIV>
    <DIV></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D668522812-20042008><FONT =
face=3DArial=20
    size=3D2>It's all simple:</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D668522812-20042008><FONT =
face=3DArial=20
    size=3D2>-&nbsp;the Design Team is looking at the possibility of =
using this=20
    message</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D668522812-20042008><FONT =
face=3DArial=20
    size=3D2>- the message in its current form does not appear to be =
terribly=20
    useful, and could be&nbsp;removed from the spec.</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D668522812-20042008><FONT =
face=3DArial=20
    size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D668522812-20042008><FONT =
face=3DArial=20
    size=3D2>-Woj.</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D668522812-20042008><FONT =
face=3DArial=20
    size=3D2></FONT></SPAN>&nbsp;</DIV><BR>
    <BLOCKQUOTE dir=3Dltr=20
    style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 =
2px solid; MARGIN-RIGHT: 0px">
      <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
      <HR tabIndex=3D-1>
      <FONT face=3DTahoma size=3D2><B>From:</B> ancp-bounces@ietf.org=20
      [mailto:ancp-bounces@ietf.org] <B>On Behalf Of </B>Peter=20
      Arberg<BR><B>Sent:</B> 19 April 2008 03:07<BR><B>To:</B> Wojciech =
Dec=20
      (wdec); ancp@ietf.org<BR><B>Subject:</B> Re: [ANCP] Bulk =
Transaction=20
      Message<BR></FONT><BR></DIV>
      <DIV></DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D197410601-19042008><FONT =
face=3DArial=20
      color=3D#0000ff size=3D2>Hi Woj,</FONT></SPAN></DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D197410601-19042008><FONT =
face=3DArial=20
      color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D197410601-19042008><FONT =
face=3DArial=20
      color=3D#0000ff size=3D2>can you give a little background to why =
you are=20
      looking for vendor</FONT></SPAN></DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D197410601-19042008><FONT =
face=3DArial=20
      color=3D#0000ff size=3D2>implementation support for this specific =
capability=20
      &amp; message ?</FONT></SPAN></DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D197410601-19042008><FONT =
face=3DArial=20
      color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D197410601-19042008><FONT =
face=3DArial=20
      color=3D#0000ff size=3D2>thanks,</FONT></SPAN></DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D197410601-19042008><FONT =
face=3DArial=20
      color=3D#0000ff size=3D2>Peter</FONT></SPAN></DIV><BR>
      <BLOCKQUOTE dir=3Dltr=20
      style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff =
2px solid; MARGIN-RIGHT: 0px">
        <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
        <HR tabIndex=3D-1>
        <FONT face=3DTahoma size=3D2><B>From:</B> ancp-bounces@ietf.org=20
        [mailto:ancp-bounces@ietf.org] <B>On Behalf Of </B>Wojciech Dec=20
        (wdec)<BR><B>Sent:</B> 18. april 2008 08:04<BR><B>To:</B>=20
        ancp@ietf.org<BR><B>Subject:</B> [ANCP] Bulk Transaction=20
        Message<BR></FONT><BR></DIV>
        <DIV></DIV><!-- Converted from text/rtf format -->
        <P><SPAN lang=3Den-gb><FONT face=3DArial size=3D2>Hi =
Folks,</FONT></SPAN> </P>
        <P><SPAN lang=3Den-gb><FONT face=3DArial size=3D2>Could you =
please let me/us=20
        know if you currently have an implementation of ANCP that =
supports the=20
        Bulk Transaction Capability and Message?</FONT></SPAN></P>
        <P><SPAN lang=3Den-gb><FONT face=3DArial =
size=3D2>Thanks,</FONT></SPAN>=20
        <BR><SPAN lang=3Den-gb><FONT face=3DArial =
size=3D2>Woj.</FONT></SPAN><SPAN=20
        lang=3Den-us></SPAN>=20
</P></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C8AF98.4D6BCDE2--

--===============1915971896==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1915971896==--


From ancp-bounces@ietf.org  Tue May  6 10:08:35 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id ED5F03A69AF;
	Tue,  6 May 2008 10:08:34 -0700 (PDT)
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 A4A953A69AF
	for <ancp@core3.amsl.com>; Tue,  6 May 2008 10:08:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 qoL1b93pZNzS for <ancp@core3.amsl.com>;
	Tue,  6 May 2008 10:08:31 -0700 (PDT)
Received: from chip3og59.obsmtp.com (chip3og59.obsmtp.com [64.18.14.183])
	by core3.amsl.com (Postfix) with ESMTP id 9F3803A68DA
	for <ancp@ietf.org>; Tue,  6 May 2008 10:08:30 -0700 (PDT)
Received: from source ([66.129.224.36]) by chip3ob59.postini.com
	([64.18.6.12]) with SMTP; Tue, 06 May 2008 10:08:22 PDT
Received: from proton.jnpr.net ([10.10.2.37]) by emailsmtp55.jnpr.net with
	Microsoft SMTPSVC(6.0.3790.1830); Tue, 6 May 2008 10:08:17 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 6 May 2008 13:08:15 -0400
Message-ID: <9BD5D7887235424FA97DFC223CAE3C280AB43A56@proton.jnpr.net>
In-Reply-To: <D9872168DBD43A41BD71FFC4713274D405043733@xmb-ams-33b.emea.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ANCP] Bulk Transaction Message
Thread-Index: AcihZWeDZVeOVtxMS1uttRBEffcNEwAVDjfgAEod1tAAAWRvoAMsB4yQAADCZxA=
From: "Sanjay Wadhwa" <swadhwa@juniper.net>
To: "Wojciech Dec (wdec)" <wdec@cisco.com>,
	"Peter Arberg" <parberg@redback.com>, <ancp@ietf.org>
X-OriginalArrivalTime: 06 May 2008 17:08:17.0336 (UTC)
	FILETIME=[C6FD9B80:01C8AF9B]
Subject: Re: [ANCP] Bulk Transaction Message
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/pipermail/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>
Content-Type: multipart/mixed; boundary="===============1355129709=="
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1355129709==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8AF9B.C5A4F99B"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8AF9B.C5A4F99B
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Woj
  It is a bad idea to remove bulk-transaction capability from the draft.
On one hand you are trying to add "marginally useful" extensions (with
TLVs), and on the other hand you are arguing for removing useful
abstractions which can help with scaling. If bulk-transaction capability
needs to be augmented or modified, then we should consider augmenting
it, rather than removing it from the draft.
=20
Cheers
-Sanjay

-----Original Message-----
From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org]On Behalf Of
Wojciech Dec (wdec)
Sent: Tuesday, May 06, 2008 12:42 PM
To: Peter Arberg; ancp@ietf.org
Subject: Re: [ANCP] Bulk Transaction Message


Hi Folks,
=20
given that no discernable use of Bulk messaging has been identified, nor
there being a good reason for it given the fact that ANCP is bound to
the TCP transport (or equivalent), I would like to propose to remove all
of the text relating to this capability and associated message from the
protocol spec draft.
=20
Regards,
Woj.


  _____ =20

From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of
Wojciech Dec (wdec)
Sent: 20 April 2008 15:18
To: Peter Arberg; ancp@ietf.org
Subject: Re: [ANCP] Bulk Transaction Message


Should also have added: Given that currently the bulk message does not
appear to have had any practical adoption, having the DTeam adopt
it/modify it, or possibly have it removed from the spec all together are
all valid options.
=20
-Woj.


  _____ =20

From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of
Wojciech Dec (wdec)
Sent: 20 April 2008 14:39
To: Peter Arberg; ancp@ietf.org
Subject: Re: [ANCP] Bulk Transaction Message


It's all simple:
- the Design Team is looking at the possibility of using this message
- the message in its current form does not appear to be terribly useful,
and could be removed from the spec.
=20
-Woj.
=20


  _____ =20

From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of
Peter Arberg
Sent: 19 April 2008 03:07
To: Wojciech Dec (wdec); ancp@ietf.org
Subject: Re: [ANCP] Bulk Transaction Message


Hi Woj,
=20
can you give a little background to why you are looking for vendor
implementation support for this specific capability & message ?
=20
thanks,
Peter


  _____ =20

From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of
Wojciech Dec (wdec)
Sent: 18. april 2008 08:04
To: ancp@ietf.org
Subject: [ANCP] Bulk Transaction Message



Hi Folks,=20

Could you please let me/us know if you currently have an implementation
of ANCP that supports the Bulk Transaction Capability and Message?

Thanks,=20
Woj.=20


------_=_NextPart_001_01C8AF9B.C5A4F99B
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<TITLE>Bulk Transaction Message</TITLE>

<META content=3D"MSHTML 6.00.2800.1609" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D093250117-06052008>Woj</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D093250117-06052008>&nbsp;=20
It is a bad idea to remove bulk-transaction capability from the draft. =
On one=20
hand you are trying to add "marginally useful" extensions (with TLVs), =
and on=20
the other hand you are arguing for removing useful abstractions which =
can help=20
with scaling. </SPAN></FONT><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D093250117-06052008>If bulk-transaction capability needs to be =
augmented or=20
modified, then we should consider augmenting it, rather than removing it =
from=20
the draft.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D093250117-06052008></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D093250117-06052008>Cheers</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D093250117-06052008>-Sanjay</SPAN></FONT></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> =
ancp-bounces@ietf.org=20
  [mailto:ancp-bounces@ietf.org]<B>On Behalf Of </B>Wojciech Dec=20
  (wdec)<BR><B>Sent:</B> Tuesday, May 06, 2008 12:42 PM<BR><B>To:</B> =
Peter=20
  Arberg; ancp@ietf.org<BR><B>Subject:</B> Re: [ANCP] Bulk Transaction=20
  Message<BR><BR></FONT></DIV>
  <DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
  class=3D811403916-06052008>Hi Folks,</SPAN></FONT></DIV>
  <DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
  class=3D811403916-06052008></SPAN></FONT>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
  class=3D811403916-06052008>given that no discernable use of Bulk =
messaging has=20
  been identified, nor&nbsp;there being a good reason for it given the =
fact that=20
  ANCP is bound to the TCP transport (or equivalent),&nbsp;I would like =
to=20
  propose to remove all of the text relating to this capability and =
associated=20
  message from the protocol spec draft.</SPAN></FONT></DIV>
  <DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
  class=3D811403916-06052008></SPAN></FONT>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
  class=3D811403916-06052008>Regards,</SPAN></FONT></DIV>
  <DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
  class=3D811403916-06052008>Woj.</SPAN></FONT></DIV><BR>
  <BLOCKQUOTE dir=3Dltr=20
  style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px =
solid; MARGIN-RIGHT: 0px">
    <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
    <HR tabIndex=3D-1>
    <FONT face=3DTahoma size=3D2><B>From:</B> ancp-bounces@ietf.org=20
    [mailto:ancp-bounces@ietf.org] <B>On Behalf Of </B>Wojciech Dec=20
    (wdec)<BR><B>Sent:</B> 20 April 2008 15:18<BR><B>To:</B> Peter =
Arberg;=20
    ancp@ietf.org<BR><B>Subject:</B> Re: [ANCP] Bulk Transaction=20
    Message<BR></FONT><BR></DIV>
    <DIV></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D490440813-20042008><FONT =
face=3DArial=20
    size=3D2>Should also have added: Given that currently&nbsp;the bulk =
message=20
    does not appear to have had any practical&nbsp;adoption, having the =
DTeam=20
    adopt it/modify it, or possibly have it removed from the spec all=20
    together&nbsp;are all valid options.</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D490440813-20042008><FONT =
face=3DArial=20
    size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D490440813-20042008><FONT =
face=3DArial=20
    size=3D2>-Woj.</FONT></SPAN></DIV><BR>
    <BLOCKQUOTE dir=3Dltr=20
    style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 =
2px solid; MARGIN-RIGHT: 0px">
      <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
      <HR tabIndex=3D-1>
      <FONT face=3DTahoma size=3D2><B>From:</B> ancp-bounces@ietf.org=20
      [mailto:ancp-bounces@ietf.org] <B>On Behalf Of </B>Wojciech Dec=20
      (wdec)<BR><B>Sent:</B> 20 April 2008 14:39<BR><B>To:</B> Peter =
Arberg;=20
      ancp@ietf.org<BR><B>Subject:</B> Re: [ANCP] Bulk Transaction=20
      Message<BR></FONT><BR></DIV>
      <DIV></DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D668522812-20042008><FONT =
face=3DArial=20
      size=3D2>It's all simple:</FONT></SPAN></DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D668522812-20042008><FONT =
face=3DArial=20
      size=3D2>-&nbsp;the Design Team is looking at the possibility of =
using this=20
      message</FONT></SPAN></DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D668522812-20042008><FONT =
face=3DArial=20
      size=3D2>- the message in its current form does not appear to be =
terribly=20
      useful, and could be&nbsp;removed from the =
spec.</FONT></SPAN></DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D668522812-20042008><FONT =
face=3DArial=20
      size=3D2></FONT></SPAN>&nbsp;</DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D668522812-20042008><FONT =
face=3DArial=20
      size=3D2>-Woj.</FONT></SPAN></DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D668522812-20042008><FONT =
face=3DArial=20
      size=3D2></FONT></SPAN>&nbsp;</DIV><BR>
      <BLOCKQUOTE dir=3Dltr=20
      style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 =
2px solid; MARGIN-RIGHT: 0px">
        <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
        <HR tabIndex=3D-1>
        <FONT face=3DTahoma size=3D2><B>From:</B> ancp-bounces@ietf.org=20
        [mailto:ancp-bounces@ietf.org] <B>On Behalf Of </B>Peter=20
        Arberg<BR><B>Sent:</B> 19 April 2008 03:07<BR><B>To:</B> =
Wojciech Dec=20
        (wdec); ancp@ietf.org<BR><B>Subject:</B> Re: [ANCP] Bulk =
Transaction=20
        Message<BR></FONT><BR></DIV>
        <DIV></DIV>
        <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D197410601-19042008><FONT face=3DArial=20
        color=3D#0000ff size=3D2>Hi Woj,</FONT></SPAN></DIV>
        <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D197410601-19042008><FONT face=3DArial=20
        color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
        <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D197410601-19042008><FONT face=3DArial=20
        color=3D#0000ff size=3D2>can you give a little background to why =
you are=20
        looking for vendor</FONT></SPAN></DIV>
        <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D197410601-19042008><FONT face=3DArial=20
        color=3D#0000ff size=3D2>implementation support for this =
specific capability=20
        &amp; message ?</FONT></SPAN></DIV>
        <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D197410601-19042008><FONT face=3DArial=20
        color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
        <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D197410601-19042008><FONT face=3DArial=20
        color=3D#0000ff size=3D2>thanks,</FONT></SPAN></DIV>
        <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D197410601-19042008><FONT face=3DArial=20
        color=3D#0000ff size=3D2>Peter</FONT></SPAN></DIV><BR>
        <BLOCKQUOTE dir=3Dltr=20
        style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: =
#0000ff 2px solid; MARGIN-RIGHT: 0px">
          <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
          <HR tabIndex=3D-1>
          <FONT face=3DTahoma size=3D2><B>From:</B> =
ancp-bounces@ietf.org=20
          [mailto:ancp-bounces@ietf.org] <B>On Behalf Of </B>Wojciech =
Dec=20
          (wdec)<BR><B>Sent:</B> 18. april 2008 08:04<BR><B>To:</B>=20
          ancp@ietf.org<BR><B>Subject:</B> [ANCP] Bulk Transaction=20
          Message<BR></FONT><BR></DIV>
          <DIV></DIV><!-- Converted from text/rtf format -->
          <P><SPAN lang=3Den-gb><FONT face=3DArial size=3D2>Hi =
Folks,</FONT></SPAN>=20
          </P>
          <P><SPAN lang=3Den-gb><FONT face=3DArial size=3D2>Could you =
please let me/us=20
          know if you currently have an implementation of ANCP that =
supports the=20
          Bulk Transaction Capability and Message?</FONT></SPAN></P>
          <P><SPAN lang=3Den-gb><FONT face=3DArial =
size=3D2>Thanks,</FONT></SPAN>=20
          <BR><SPAN lang=3Den-gb><FONT face=3DArial =
size=3D2>Woj.</FONT></SPAN><SPAN=20
          lang=3Den-us></SPAN>=20
</P></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BO=
DY></HTML>

------_=_NextPart_001_01C8AF9B.C5A4F99B--

--===============1355129709==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1355129709==--


From ancp-bounces@ietf.org  Tue May  6 10:23:44 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 48FEB3A6A40;
	Tue,  6 May 2008 10:23:44 -0700 (PDT)
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 66BD73A68DA
	for <ancp@core3.amsl.com>; Tue,  6 May 2008 10:23:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 UTf7j8hZoJHP for <ancp@core3.amsl.com>;
	Tue,  6 May 2008 10:23:41 -0700 (PDT)
Received: from prattle.redback.com (prattle.redback.com [155.53.12.9])
	by core3.amsl.com (Postfix) with ESMTP id 43F643A6839
	for <ancp@ietf.org>; Tue,  6 May 2008 10:23:41 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by prattle.redback.com (Postfix) with ESMTP id A7B336C642B;
	Tue,  6 May 2008 10:23:39 -0700 (PDT)
Received: from prattle.redback.com ([127.0.0.1])
	by localhost (prattle [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
	id 23469-05; Tue,  6 May 2008 10:23:39 -0700 (PDT)
Received: from rbsjx.ad.redback.com (rbsjxh1.redback.com [155.53.14.105])
	by prattle.redback.com (Postfix) with ESMTP id 1F52A6C642D;
	Tue,  6 May 2008 10:23:39 -0700 (PDT)
Received: from RBSJX.ad.redback.com ([155.53.14.103]) by
	rbsjxh1.ad.redback.com ([155.53.14.105]) with mapi;
	Tue, 6 May 2008 10:23:39 -0700
From: Peter Arberg <parberg@redback.com>
To: "Wojciech Dec (wdec)" <wdec@cisco.com>,
	"ancp@ietf.org" <ancp@ietf.org>
Date: Tue, 6 May 2008 10:23:38 -0700
Thread-Topic: [ANCP] Bulk Transaction Message
Thread-Index: AcihZWeDZVeOVtxMS1uttRBEffcNEwAVDjfgAEod1tAAAWRvoAMsB4yQAAEiyiA=
Message-ID: <48C276B536524E478C659685995F6AA53B59592B52@RBSJX.ad.redback.com>
References: <D9872168DBD43A41BD71FFC4713274D404F12299@xmb-ams-33b.emea.cisco.com><48C276B536524E478C659685995F6AA539DBA2CA93@RBSJX.ad.redback.com><D9872168DBD43A41BD71FFC4713274D404F12507@xmb-ams-33b.emea.cisco.com>
	<D9872168DBD43A41BD71FFC4713274D404F12512@xmb-ams-33b.emea.cisco.com>
	<D9872168DBD43A41BD71FFC4713274D405043733@xmb-ams-33b.emea.cisco.com>
In-Reply-To: <D9872168DBD43A41BD71FFC4713274D405043733@xmb-ams-33b.emea.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-Virus-Scanned: by amavisd-new at redback.com
Subject: Re: [ANCP] Bulk Transaction Message
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/pipermail/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>
Content-Type: multipart/mixed; boundary="===============1055105922=="
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org

--===============1055105922==
Content-Language: en-US
Content-Type: multipart/alternative;
	boundary="_000_48C276B536524E478C659685995F6AA53B59592B52RBSJXadredbac_"

--_000_48C276B536524E478C659685995F6AA53B59592B52RBSJXadredbac_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

I agree with this proposal.

cheers,
Peter

________________________________
From: Wojciech Dec (wdec) [mailto:wdec@cisco.com]
Sent: 6. maj 2008 09:42
To: Peter Arberg; ancp@ietf.org
Subject: RE: [ANCP] Bulk Transaction Message

Hi Folks,

given that no discernable use of Bulk messaging has been identified, nor th=
ere being a good reason for it given the fact that ANCP is bound to the TCP=
 transport (or equivalent), I would like to propose to remove all of the te=
xt relating to this capability and associated message from the protocol spe=
c draft.

Regards,
Woj.

________________________________
From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of Woj=
ciech Dec (wdec)
Sent: 20 April 2008 15:18
To: Peter Arberg; ancp@ietf.org
Subject: Re: [ANCP] Bulk Transaction Message

Should also have added: Given that currently the bulk message does not appe=
ar to have had any practical adoption, having the DTeam adopt it/modify it,=
 or possibly have it removed from the spec all together are all valid optio=
ns.

-Woj.

________________________________
From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of Woj=
ciech Dec (wdec)
Sent: 20 April 2008 14:39
To: Peter Arberg; ancp@ietf.org
Subject: Re: [ANCP] Bulk Transaction Message

It's all simple:
- the Design Team is looking at the possibility of using this message
- the message in its current form does not appear to be terribly useful, an=
d could be removed from the spec.

-Woj.


________________________________
From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of Pet=
er Arberg
Sent: 19 April 2008 03:07
To: Wojciech Dec (wdec); ancp@ietf.org
Subject: Re: [ANCP] Bulk Transaction Message

Hi Woj,

can you give a little background to why you are looking for vendor
implementation support for this specific capability & message ?

thanks,
Peter

________________________________
From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of Woj=
ciech Dec (wdec)
Sent: 18. april 2008 08:04
To: ancp@ietf.org
Subject: [ANCP] Bulk Transaction Message


Hi Folks,

Could you please let me/us know if you currently have an implementation of =
ANCP that supports the Bulk Transaction Capability and Message?

Thanks,
Woj.

--_000_48C276B536524E478C659685995F6AA53B59592B52RBSJXadredbac_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Bulk Transaction Message</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.6000.16640" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D917111217-06052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Hi,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D917111217-06052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D917111217-06052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>I agree with this proposal.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D917111217-06052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D917111217-06052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>cheers,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D917111217-06052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Peter</FONT></SPAN></DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px soli=
d; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Wojciech Dec (wdec)=20
  [mailto:wdec@cisco.com] <BR><B>Sent:</B> 6. maj 2008 09:42<BR><B>To:</B> =
Peter=20
  Arberg; ancp@ietf.org<BR><B>Subject:</B> RE: [ANCP] Bulk Transaction=20
  Message<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
  class=3D811403916-06052008>Hi Folks,</SPAN></FONT></DIV>
  <DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
  class=3D811403916-06052008></SPAN></FONT>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
  class=3D811403916-06052008>given that no discernable use of Bulk messagin=
g has=20
  been identified, nor&nbsp;there being a good reason for it given the fact=
 that=20
  ANCP is bound to the TCP transport (or equivalent),&nbsp;I would like to=
=20
  propose to remove all of the text relating to this capability and associa=
ted=20
  message from the protocol spec draft.</SPAN></FONT></DIV>
  <DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
  class=3D811403916-06052008></SPAN></FONT>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
  class=3D811403916-06052008>Regards,</SPAN></FONT></DIV>
  <DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
  class=3D811403916-06052008>Woj.</SPAN></FONT></DIV><BR>
  <BLOCKQUOTE dir=3Dltr=20
  style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px so=
lid; MARGIN-RIGHT: 0px">
    <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
    <HR tabIndex=3D-1>
    <FONT face=3DTahoma size=3D2><B>From:</B> ancp-bounces@ietf.org=20
    [mailto:ancp-bounces@ietf.org] <B>On Behalf Of </B>Wojciech Dec=20
    (wdec)<BR><B>Sent:</B> 20 April 2008 15:18<BR><B>To:</B> Peter Arberg;=
=20
    ancp@ietf.org<BR><B>Subject:</B> Re: [ANCP] Bulk Transaction=20
    Message<BR></FONT><BR></DIV>
    <DIV></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D490440813-20042008><FONT face=
=3DArial=20
    size=3D2>Should also have added: Given that currently&nbsp;the bulk mes=
sage=20
    does not appear to have had any practical&nbsp;adoption, having the DTe=
am=20
    adopt it/modify it, or possibly have it removed from the spec all=20
    together&nbsp;are all valid options.</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D490440813-20042008><FONT face=
=3DArial=20
    size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D490440813-20042008><FONT face=
=3DArial=20
    size=3D2>-Woj.</FONT></SPAN></DIV><BR>
    <BLOCKQUOTE dir=3Dltr=20
    style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px =
solid; MARGIN-RIGHT: 0px">
      <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft=
>
      <HR tabIndex=3D-1>
      <FONT face=3DTahoma size=3D2><B>From:</B> ancp-bounces@ietf.org=20
      [mailto:ancp-bounces@ietf.org] <B>On Behalf Of </B>Wojciech Dec=20
      (wdec)<BR><B>Sent:</B> 20 April 2008 14:39<BR><B>To:</B> Peter Arberg=
;=20
      ancp@ietf.org<BR><B>Subject:</B> Re: [ANCP] Bulk Transaction=20
      Message<BR></FONT><BR></DIV>
      <DIV></DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D668522812-20042008><FONT fa=
ce=3DArial=20
      size=3D2>It's all simple:</FONT></SPAN></DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D668522812-20042008><FONT fa=
ce=3DArial=20
      size=3D2>-&nbsp;the Design Team is looking at the possibility of usin=
g this=20
      message</FONT></SPAN></DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D668522812-20042008><FONT fa=
ce=3DArial=20
      size=3D2>- the message in its current form does not appear to be terr=
ibly=20
      useful, and could be&nbsp;removed from the spec.</FONT></SPAN></DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D668522812-20042008><FONT fa=
ce=3DArial=20
      size=3D2></FONT></SPAN>&nbsp;</DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D668522812-20042008><FONT fa=
ce=3DArial=20
      size=3D2>-Woj.</FONT></SPAN></DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D668522812-20042008><FONT fa=
ce=3DArial=20
      size=3D2></FONT></SPAN>&nbsp;</DIV><BR>
      <BLOCKQUOTE dir=3Dltr=20
      style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2p=
x solid; MARGIN-RIGHT: 0px">
        <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dle=
ft>
        <HR tabIndex=3D-1>
        <FONT face=3DTahoma size=3D2><B>From:</B> ancp-bounces@ietf.org=20
        [mailto:ancp-bounces@ietf.org] <B>On Behalf Of </B>Peter=20
        Arberg<BR><B>Sent:</B> 19 April 2008 03:07<BR><B>To:</B> Wojciech D=
ec=20
        (wdec); ancp@ietf.org<BR><B>Subject:</B> Re: [ANCP] Bulk Transactio=
n=20
        Message<BR></FONT><BR></DIV>
        <DIV></DIV>
        <DIV dir=3Dltr align=3Dleft><SPAN class=3D197410601-19042008><FONT =
face=3DArial=20
        color=3D#0000ff size=3D2>Hi Woj,</FONT></SPAN></DIV>
        <DIV dir=3Dltr align=3Dleft><SPAN class=3D197410601-19042008><FONT =
face=3DArial=20
        color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
        <DIV dir=3Dltr align=3Dleft><SPAN class=3D197410601-19042008><FONT =
face=3DArial=20
        color=3D#0000ff size=3D2>can you give a little background to why yo=
u are=20
        looking for vendor</FONT></SPAN></DIV>
        <DIV dir=3Dltr align=3Dleft><SPAN class=3D197410601-19042008><FONT =
face=3DArial=20
        color=3D#0000ff size=3D2>implementation support for this specific c=
apability=20
        &amp; message ?</FONT></SPAN></DIV>
        <DIV dir=3Dltr align=3Dleft><SPAN class=3D197410601-19042008><FONT =
face=3DArial=20
        color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
        <DIV dir=3Dltr align=3Dleft><SPAN class=3D197410601-19042008><FONT =
face=3DArial=20
        color=3D#0000ff size=3D2>thanks,</FONT></SPAN></DIV>
        <DIV dir=3Dltr align=3Dleft><SPAN class=3D197410601-19042008><FONT =
face=3DArial=20
        color=3D#0000ff size=3D2>Peter</FONT></SPAN></DIV><BR>
        <BLOCKQUOTE dir=3Dltr=20
        style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff =
2px solid; MARGIN-RIGHT: 0px">
          <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3D=
left>
          <HR tabIndex=3D-1>
          <FONT face=3DTahoma size=3D2><B>From:</B> ancp-bounces@ietf.org=20
          [mailto:ancp-bounces@ietf.org] <B>On Behalf Of </B>Wojciech Dec=20
          (wdec)<BR><B>Sent:</B> 18. april 2008 08:04<BR><B>To:</B>=20
          ancp@ietf.org<BR><B>Subject:</B> [ANCP] Bulk Transaction=20
          Message<BR></FONT><BR></DIV>
          <DIV></DIV><!-- Converted from text/rtf format -->
          <P><SPAN lang=3Den-gb><FONT face=3DArial size=3D2>Hi Folks,</FONT=
></SPAN>=20
          </P>
          <P><SPAN lang=3Den-gb><FONT face=3DArial size=3D2>Could you pleas=
e let me/us=20
          know if you currently have an implementation of ANCP that support=
s the=20
          Bulk Transaction Capability and Message?</FONT></SPAN></P>
          <P><SPAN lang=3Den-gb><FONT face=3DArial size=3D2>Thanks,</FONT><=
/SPAN>=20
          <BR><SPAN lang=3Den-gb><FONT face=3DArial size=3D2>Woj.</FONT></S=
PAN><SPAN=20
          lang=3Den-us></SPAN>=20
</P></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BODY=
></HTML>

--_000_48C276B536524E478C659685995F6AA53B59592B52RBSJXadredbac_--

--===============1055105922==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1055105922==--


From ancp-bounces@ietf.org  Tue May  6 10:24:40 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8096C3A683D;
	Tue,  6 May 2008 10:24:40 -0700 (PDT)
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 017F73A683D
	for <ancp@core3.amsl.com>; Tue,  6 May 2008 10:24:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.948
X-Spam-Level: 
X-Spam-Status: No, score=-5.948 tagged_above=-999 required=5 tests=[AWL=0.650, 
	BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 3sYobCdyJX60 for <ancp@core3.amsl.com>;
	Tue,  6 May 2008 10:24:38 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id E792B3A6839
	for <ancp@ietf.org>; Tue,  6 May 2008 10:24:37 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,444,1204498800"; d="scan'208,217";a="8178050"
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 06 May 2008 19:24:34 +0200
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m46HOYMj022880; 
	Tue, 6 May 2008 19:24:34 +0200
Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com
	[144.254.231.71])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m46HOYVa016383;
	Tue, 6 May 2008 17:24:34 GMT
Received: from xmb-ams-33b.cisco.com ([144.254.231.86]) by
	xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 6 May 2008 19:24:34 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 6 May 2008 19:24:18 +0200
Message-ID: <D9872168DBD43A41BD71FFC4713274D405043771@xmb-ams-33b.emea.cisco.com>
In-Reply-To: <9BD5D7887235424FA97DFC223CAE3C280AB43A56@proton.jnpr.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ANCP] Bulk Transaction Message
thread-index: AcihZWeDZVeOVtxMS1uttRBEffcNEwAVDjfgAEod1tAAAWRvoAMsB4yQAADCZxAAAKZHUA==
References: <D9872168DBD43A41BD71FFC4713274D405043733@xmb-ams-33b.emea.cisco.com>
	<9BD5D7887235424FA97DFC223CAE3C280AB43A56@proton.jnpr.net>
From: "Wojciech Dec (wdec)" <wdec@cisco.com>
To: "Sanjay Wadhwa" <swadhwa@juniper.net>,
	"Peter Arberg" <parberg@redback.com>, <ancp@ietf.org>
X-OriginalArrivalTime: 06 May 2008 17:24:34.0818 (UTC)
	FILETIME=[0D9D8620:01C8AF9E]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=14832; t=1210094674;
	x=1210958674; c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=wdec@cisco.com;
	z=From:=20=22Wojciech=20Dec=20(wdec)=22=20<wdec@cisco.com>
	|Subject:=20RE=3A=20[ANCP]=20Bulk=20Transaction=20Message
	|Sender:=20; bh=BZ43KTvK4NS2ZvT8Pu70PVq5sshHOuLcjFuDhojJEcE=;
	b=ubS/TAORNfvBoXERmyue7lW/M894jiFkIPSz31HQmCELjQX4P2WL1ebl+N
	XSZeqOu8N+lCU2enXF7x9tDC4S/UkL2tTu9+wKtEalG2ZXBOFYt5dJtdsWmC
	0BYAzMNwF3;
Authentication-Results: ams-dkim-1; header.From=wdec@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
Subject: Re: [ANCP] Bulk Transaction Message
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/pipermail/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>
Content-Type: multipart/mixed; boundary="===============1635149171=="
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1635149171==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8AF9E.0D544F6C"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8AF9E.0D544F6C
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Sanjay,
=20
can you please present to the WG and myself how bulk transaction
capability is useful in any way in terms of scaling for example? And by
the way, please treat this discussion is orthogonal to any other.
=20
Cheers,
Woj.
=20


________________________________

	From: Sanjay Wadhwa [mailto:swadhwa@juniper.net]=20
	Sent: 06 May 2008 19:08
	To: Wojciech Dec (wdec); Peter Arberg; ancp@ietf.org
	Subject: RE: [ANCP] Bulk Transaction Message
=09
=09
	Woj
	  It is a bad idea to remove bulk-transaction capability from
the draft. On one hand you are trying to add "marginally useful"
extensions (with TLVs), and on the other hand you are arguing for
removing useful abstractions which can help with scaling. If
bulk-transaction capability needs to be augmented or modified, then we
should consider augmenting it, rather than removing it from the draft.
	=20
	Cheers
	-Sanjay

		-----Original Message-----
		From: ancp-bounces@ietf.org
[mailto:ancp-bounces@ietf.org]On Behalf Of Wojciech Dec (wdec)
		Sent: Tuesday, May 06, 2008 12:42 PM
		To: Peter Arberg; ancp@ietf.org
		Subject: Re: [ANCP] Bulk Transaction Message
	=09
	=09
		Hi Folks,
		=20
		given that no discernable use of Bulk messaging has been
identified, nor there being a good reason for it given the fact that
ANCP is bound to the TCP transport (or equivalent), I would like to
propose to remove all of the text relating to this capability and
associated message from the protocol spec draft.
		=20
		Regards,
		Woj.


________________________________

			From: ancp-bounces@ietf.org
[mailto:ancp-bounces@ietf.org] On Behalf Of Wojciech Dec (wdec)
			Sent: 20 April 2008 15:18
			To: Peter Arberg; ancp@ietf.org
			Subject: Re: [ANCP] Bulk Transaction Message
		=09
		=09
			Should also have added: Given that currently the
bulk message does not appear to have had any practical adoption, having
the DTeam adopt it/modify it, or possibly have it removed from the spec
all together are all valid options.
			=20
			-Woj.


________________________________

				From: ancp-bounces@ietf.org
[mailto:ancp-bounces@ietf.org] On Behalf Of Wojciech Dec (wdec)
				Sent: 20 April 2008 14:39
				To: Peter Arberg; ancp@ietf.org
				Subject: Re: [ANCP] Bulk Transaction
Message
			=09
			=09
				It's all simple:
				- the Design Team is looking at the
possibility of using this message
				- the message in its current form does
not appear to be terribly useful, and could be removed from the spec.
				=20
				-Woj.
				=20


________________________________

				From: ancp-bounces@ietf.org
[mailto:ancp-bounces@ietf.org] On Behalf Of Peter Arberg
				Sent: 19 April 2008 03:07
				To: Wojciech Dec (wdec); ancp@ietf.org
				Subject: Re: [ANCP] Bulk Transaction
Message
			=09
			=09
				Hi Woj,
				=20
				can you give a little background to why
you are looking for vendor
				implementation support for this specific
capability & message ?
				=20
				thanks,
				Peter


________________________________

				From: ancp-bounces@ietf.org
[mailto:ancp-bounces@ietf.org] On Behalf Of Wojciech Dec (wdec)
				Sent: 18. april 2008 08:04
				To: ancp@ietf.org
				Subject: [ANCP] Bulk Transaction Message
			=09
			=09

				Hi Folks,=20

				Could you please let me/us know if you
currently have an implementation of ANCP that supports the Bulk
Transaction Capability and Message?

				Thanks,=20
				Woj.=20


------_=_NextPart_001_01C8AF9E.0D544F6C
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Bulk Transaction Message</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3314" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D967002017-06052008><FONT =
face=3DArial=20
size=3D2>Sanjay,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D967002017-06052008><FONT =
face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D967002017-06052008><FONT =
face=3DArial=20
size=3D2>can you please present to the WG and myself how bulk =
transaction=20
capability is useful in any way in terms of scaling for example? And by =
the way,=20
please treat this discussion is orthogonal to any =
other.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D967002017-06052008><FONT =
face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D967002017-06052008><FONT =
face=3DArial=20
size=3D2>Cheers,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D967002017-06052008><FONT =
face=3DArial=20
size=3D2>Woj.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D967002017-06052008><FONT =
face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Sanjay Wadhwa=20
  [mailto:swadhwa@juniper.net] <BR><B>Sent:</B> 06 May 2008 =
19:08<BR><B>To:</B>=20
  Wojciech Dec (wdec); Peter Arberg; ancp@ietf.org<BR><B>Subject:</B> =
RE: [ANCP]=20
  Bulk Transaction Message<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D093250117-06052008>Woj</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D093250117-06052008>&nbsp; It is a bad idea to remove =
bulk-transaction=20
  capability from the draft. On one hand you are trying to add =
"marginally=20
  useful" extensions (with TLVs), and on the other hand you are arguing =
for=20
  removing useful abstractions which can help with scaling. =
</SPAN></FONT><FONT=20
  face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D093250117-06052008>If=20
  bulk-transaction capability needs to be augmented or modified, then we =
should=20
  consider augmenting it, rather than removing it from the=20
  draft.</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D093250117-06052008></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D093250117-06052008>Cheers</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D093250117-06052008>-Sanjay</SPAN></FONT></DIV>
  <BLOCKQUOTE dir=3Dltr=20
  style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
    <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
    size=3D2>-----Original Message-----<BR><B>From:</B> =
ancp-bounces@ietf.org=20
    [mailto:ancp-bounces@ietf.org]<B>On Behalf Of </B>Wojciech Dec=20
    (wdec)<BR><B>Sent:</B> Tuesday, May 06, 2008 12:42 PM<BR><B>To:</B> =
Peter=20
    Arberg; ancp@ietf.org<BR><B>Subject:</B> Re: [ANCP] Bulk Transaction =

    Message<BR><BR></FONT></DIV>
    <DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
    class=3D811403916-06052008>Hi Folks,</SPAN></FONT></DIV>
    <DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
    class=3D811403916-06052008></SPAN></FONT>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
    class=3D811403916-06052008>given that no discernable use of Bulk =
messaging has=20
    been identified, nor&nbsp;there being a good reason for it given the =
fact=20
    that ANCP is bound to the TCP transport (or equivalent),&nbsp;I =
would like=20
    to propose to remove all of the text relating to this capability and =

    associated message from the protocol spec draft.</SPAN></FONT></DIV>
    <DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
    class=3D811403916-06052008></SPAN></FONT>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
    class=3D811403916-06052008>Regards,</SPAN></FONT></DIV>
    <DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
    class=3D811403916-06052008>Woj.</SPAN></FONT></DIV><BR>
    <BLOCKQUOTE dir=3Dltr=20
    style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 =
2px solid; MARGIN-RIGHT: 0px">
      <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
      <HR tabIndex=3D-1>
      <FONT face=3DTahoma size=3D2><B>From:</B> ancp-bounces@ietf.org=20
      [mailto:ancp-bounces@ietf.org] <B>On Behalf Of </B>Wojciech Dec=20
      (wdec)<BR><B>Sent:</B> 20 April 2008 15:18<BR><B>To:</B> Peter =
Arberg;=20
      ancp@ietf.org<BR><B>Subject:</B> Re: [ANCP] Bulk Transaction=20
      Message<BR></FONT><BR></DIV>
      <DIV></DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D490440813-20042008><FONT =
face=3DArial=20
      size=3D2>Should also have added: Given that currently&nbsp;the =
bulk message=20
      does not appear to have had any practical&nbsp;adoption, having =
the DTeam=20
      adopt it/modify it, or possibly have it removed from the spec all=20
      together&nbsp;are all valid options.</FONT></SPAN></DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D490440813-20042008><FONT =
face=3DArial=20
      size=3D2></FONT></SPAN>&nbsp;</DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D490440813-20042008><FONT =
face=3DArial=20
      size=3D2>-Woj.</FONT></SPAN></DIV><BR>
      <BLOCKQUOTE dir=3Dltr=20
      style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 =
2px solid; MARGIN-RIGHT: 0px">
        <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
        <HR tabIndex=3D-1>
        <FONT face=3DTahoma size=3D2><B>From:</B> ancp-bounces@ietf.org=20
        [mailto:ancp-bounces@ietf.org] <B>On Behalf Of </B>Wojciech Dec=20
        (wdec)<BR><B>Sent:</B> 20 April 2008 14:39<BR><B>To:</B> Peter =
Arberg;=20
        ancp@ietf.org<BR><B>Subject:</B> Re: [ANCP] Bulk Transaction=20
        Message<BR></FONT><BR></DIV>
        <DIV></DIV>
        <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D668522812-20042008><FONT face=3DArial=20
        size=3D2>It's all simple:</FONT></SPAN></DIV>
        <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D668522812-20042008><FONT face=3DArial=20
        size=3D2>-&nbsp;the Design Team is looking at the possibility of =
using=20
        this message</FONT></SPAN></DIV>
        <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D668522812-20042008><FONT face=3DArial=20
        size=3D2>- the message in its current form does not appear to be =
terribly=20
        useful, and could be&nbsp;removed from the =
spec.</FONT></SPAN></DIV>
        <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D668522812-20042008><FONT face=3DArial=20
        size=3D2></FONT></SPAN>&nbsp;</DIV>
        <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D668522812-20042008><FONT face=3DArial=20
        size=3D2>-Woj.</FONT></SPAN></DIV>
        <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D668522812-20042008><FONT face=3DArial=20
        size=3D2></FONT></SPAN>&nbsp;</DIV><BR>
        <BLOCKQUOTE dir=3Dltr=20
        style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: =
#000000 2px solid; MARGIN-RIGHT: 0px">
          <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
          <HR tabIndex=3D-1>
          <FONT face=3DTahoma size=3D2><B>From:</B> =
ancp-bounces@ietf.org=20
          [mailto:ancp-bounces@ietf.org] <B>On Behalf Of </B>Peter=20
          Arberg<BR><B>Sent:</B> 19 April 2008 03:07<BR><B>To:</B> =
Wojciech Dec=20
          (wdec); ancp@ietf.org<BR><B>Subject:</B> Re: [ANCP] Bulk =
Transaction=20
          Message<BR></FONT><BR></DIV>
          <DIV></DIV>
          <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D197410601-19042008><FONT=20
          face=3DArial color=3D#0000ff size=3D2>Hi =
Woj,</FONT></SPAN></DIV>
          <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D197410601-19042008><FONT=20
          face=3DArial color=3D#0000ff =
size=3D2></FONT></SPAN>&nbsp;</DIV>
          <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D197410601-19042008><FONT=20
          face=3DArial color=3D#0000ff size=3D2>can you give a little =
background to=20
          why you are looking for vendor</FONT></SPAN></DIV>
          <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D197410601-19042008><FONT=20
          face=3DArial color=3D#0000ff size=3D2>implementation support =
for this=20
          specific capability &amp; message ?</FONT></SPAN></DIV>
          <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D197410601-19042008><FONT=20
          face=3DArial color=3D#0000ff =
size=3D2></FONT></SPAN>&nbsp;</DIV>
          <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D197410601-19042008><FONT=20
          face=3DArial color=3D#0000ff =
size=3D2>thanks,</FONT></SPAN></DIV>
          <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D197410601-19042008><FONT=20
          face=3DArial color=3D#0000ff =
size=3D2>Peter</FONT></SPAN></DIV><BR>
          <BLOCKQUOTE dir=3Dltr=20
          style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: =
#0000ff 2px solid; MARGIN-RIGHT: 0px">
            <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
            <HR tabIndex=3D-1>
            <FONT face=3DTahoma size=3D2><B>From:</B> =
ancp-bounces@ietf.org=20
            [mailto:ancp-bounces@ietf.org] <B>On Behalf Of </B>Wojciech =
Dec=20
            (wdec)<BR><B>Sent:</B> 18. april 2008 08:04<BR><B>To:</B>=20
            ancp@ietf.org<BR><B>Subject:</B> [ANCP] Bulk Transaction=20
            Message<BR></FONT><BR></DIV>
            <DIV></DIV><!-- Converted from text/rtf format -->
            <P><SPAN lang=3Den-gb><FONT face=3DArial size=3D2>Hi =
Folks,</FONT></SPAN>=20
            </P>
            <P><SPAN lang=3Den-gb><FONT face=3DArial size=3D2>Could you =
please let=20
            me/us know if you currently have an implementation of ANCP =
that=20
            supports the Bulk Transaction Capability and=20
            Message?</FONT></SPAN></P>
            <P><SPAN lang=3Den-gb><FONT face=3DArial =
size=3D2>Thanks,</FONT></SPAN>=20
            <BR><SPAN lang=3Den-gb><FONT face=3DArial =
size=3D2>Woj.</FONT></SPAN><SPAN=20
            lang=3Den-us></SPAN>=20
  =
</P></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BL=
OCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C8AF9E.0D544F6C--

--===============1635149171==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1635149171==--


From ancp-bounces@ietf.org  Tue May  6 10:33:39 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3CA263A6A40;
	Tue,  6 May 2008 10:33:39 -0700 (PDT)
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 ED1B13A6CA3
	for <ancp@core3.amsl.com>; Tue,  6 May 2008 10:33:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.248
X-Spam-Level: 
X-Spam-Status: No, score=-2.248 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001]
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 iQEu09u84ZzA for <ancp@core3.amsl.com>;
	Tue,  6 May 2008 10:33:37 -0700 (PDT)
Received: from smail6.alcatel.fr (gc-na5.alcatel.fr [64.208.49.5])
	by core3.amsl.com (Postfix) with ESMTP id 60A503A6A40
	for <ancp@ietf.org>; Tue,  6 May 2008 10:33:36 -0700 (PDT)
Received: from FRVELSBHS05.ad2.ad.alcatel.com (frvelsbhs05.ad2.ad.alcatel.com
	[155.132.6.77])
	by smail6.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id m46HWkNS022819; 
	Tue, 6 May 2008 19:32:46 +0200
Received: from FRVELSMBS22.ad2.ad.alcatel.com ([155.132.6.52]) by
	FRVELSBHS05.ad2.ad.alcatel.com with Microsoft
	SMTPSVC(6.0.3790.2499); Tue, 6 May 2008 19:32:46 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 6 May 2008 19:32:44 +0200
Message-ID: <7A6D4815C5E8F74988784FEBD50F2F1E01B8A6B9@FRVELSMBS22.ad2.ad.alcatel.com>
In-Reply-To: <D9872168DBD43A41BD71FFC4713274D405043733@xmb-ams-33b.emea.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ANCP] Bulk Transaction Message
Thread-Index: AcihZWeDZVeOVtxMS1uttRBEffcNEwAVDjfgAEod1tAAAWRvoAMsB4yQAAGmQCA=
References: <D9872168DBD43A41BD71FFC4713274D404F12299@xmb-ams-33b.emea.cisco.com><48C276B536524E478C659685995F6AA539DBA2CA93@RBSJX.ad.redback.com><D9872168DBD43A41BD71FFC4713274D404F12507@xmb-ams-33b.emea.cisco.com><D9872168DBD43A41BD71FFC4713274D404F12512@xmb-ams-33b.emea.cisco.com>
	<D9872168DBD43A41BD71FFC4713274D405043733@xmb-ams-33b.emea.cisco.com>
From: "DE CNODDER Stefaan" <stefaan.de_cnodder@alcatel-lucent.be>
To: "Wojciech Dec (wdec)" <wdec@cisco.com>, <ancp@ietf.org>
X-OriginalArrivalTime: 06 May 2008 17:32:46.0246 (UTC)
	FILETIME=[32877C60:01C8AF9F]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.84
Subject: Re: [ANCP] Bulk Transaction Message
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/pipermail/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>
Content-Type: multipart/mixed; boundary="===============0075374826=="
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0075374826==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8AF9F.320199DA"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8AF9F.320199DA
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

=20
I agree with Woj's proposal under 1 condition: if bulk messages are
removed, it does not mean that other optimization methods are now Ok
which were previously not Ok because there was already bulk messages.
If someone in the future proposes to optimize ANCP in some way (e.g., by
defining new TLVs) then at that time bulk messaging should be considered
again as possible candidate for optimization the protocol.  I like bulk
messages but I can understand that at this stage, no optimizations are
needed and that making the protocol more scalable is a topic for the
future.
=20
regards,
Stefaan

________________________________

From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of
Wojciech Dec (wdec)
Sent: dinsdag 6 mei 2008 18:42
To: Peter Arberg; ancp@ietf.org
Subject: Re: [ANCP] Bulk Transaction Message


Hi Folks,
=20
given that no discernable use of Bulk messaging has been identified, nor
there being a good reason for it given the fact that ANCP is bound to
the TCP transport (or equivalent), I would like to propose to remove all
of the text relating to this capability and associated message from the
protocol spec draft.
=20
Regards,
Woj.


________________________________

	From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On
Behalf Of Wojciech Dec (wdec)
	Sent: 20 April 2008 15:18
	To: Peter Arberg; ancp@ietf.org
	Subject: Re: [ANCP] Bulk Transaction Message
=09
=09
	Should also have added: Given that currently the bulk message
does not appear to have had any practical adoption, having the DTeam
adopt it/modify it, or possibly have it removed from the spec all
together are all valid options.
	=20
	-Woj.


________________________________

		From: ancp-bounces@ietf.org
[mailto:ancp-bounces@ietf.org] On Behalf Of Wojciech Dec (wdec)
		Sent: 20 April 2008 14:39
		To: Peter Arberg; ancp@ietf.org
		Subject: Re: [ANCP] Bulk Transaction Message
	=09
	=09
		It's all simple:
		- the Design Team is looking at the possibility of using
this message
		- the message in its current form does not appear to be
terribly useful, and could be removed from the spec.
		=20
		-Woj.
		=20


________________________________

			From: ancp-bounces@ietf.org
[mailto:ancp-bounces@ietf.org] On Behalf Of Peter Arberg
			Sent: 19 April 2008 03:07
			To: Wojciech Dec (wdec); ancp@ietf.org
			Subject: Re: [ANCP] Bulk Transaction Message
		=09
		=09
			Hi Woj,
			=20
			can you give a little background to why you are
looking for vendor
			implementation support for this specific
capability & message ?
			=20
			thanks,
			Peter


________________________________

				From: ancp-bounces@ietf.org
[mailto:ancp-bounces@ietf.org] On Behalf Of Wojciech Dec (wdec)
				Sent: 18. april 2008 08:04
				To: ancp@ietf.org
				Subject: [ANCP] Bulk Transaction Message
			=09
			=09

				Hi Folks,=20

				Could you please let me/us know if you
currently have an implementation of ANCP that supports the Bulk
Transaction Capability and Message?

				Thanks,=20
				Woj.=20


------_=_NextPart_001_01C8AF9F.320199DA
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Bulk Transaction Message</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3314" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D433542617-06052008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>I agree with Woj's proposal under 1 condition: =
if bulk=20
messages are removed, it does not mean that other optimization methods =
are now=20
Ok which were previously not Ok because there was already bulk =
messages.&nbsp;=20
If someone in the future proposes to optimize ANCP in some way (e.g., by =

defining new TLVs) then at that time bulk messaging should be considered =
again=20
as possible candidate for optimization the protocol.&nbsp; I like bulk =
messages=20
but I can understand that at this stage, no optimizations are needed and =
that=20
making the protocol more scalable is a topic for the =
future.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D433542617-06052008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D433542617-06052008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>regards,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D433542617-06052008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Stefaan</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> ancp-bounces@ietf.org=20
[mailto:ancp-bounces@ietf.org] <B>On Behalf Of </B>Wojciech Dec=20
(wdec)<BR><B>Sent:</B> dinsdag 6 mei 2008 18:42<BR><B>To:</B> Peter =
Arberg;=20
ancp@ietf.org<BR><B>Subject:</B> Re: [ANCP] Bulk Transaction=20
Message<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
class=3D811403916-06052008>Hi Folks,</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
class=3D811403916-06052008></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
class=3D811403916-06052008>given that no discernable use of Bulk =
messaging has=20
been identified, nor&nbsp;there being a good reason for it given the =
fact that=20
ANCP is bound to the TCP transport (or equivalent),&nbsp;I would like to =
propose=20
to remove all of the text relating to this capability and associated =
message=20
from the protocol spec draft.</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
class=3D811403916-06052008></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
class=3D811403916-06052008>Regards,</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
class=3D811403916-06052008>Woj.</SPAN></FONT></DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> ancp-bounces@ietf.org=20
  [mailto:ancp-bounces@ietf.org] <B>On Behalf Of </B>Wojciech Dec=20
  (wdec)<BR><B>Sent:</B> 20 April 2008 15:18<BR><B>To:</B> Peter Arberg; =

  ancp@ietf.org<BR><B>Subject:</B> Re: [ANCP] Bulk Transaction=20
  Message<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D490440813-20042008><FONT =
face=3DArial=20
  size=3D2>Should also have added: Given that currently&nbsp;the bulk =
message does=20
  not appear to have had any practical&nbsp;adoption, having the DTeam =
adopt=20
  it/modify it, or possibly have it removed from the spec all =
together&nbsp;are=20
  all valid options.</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D490440813-20042008><FONT =
face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D490440813-20042008><FONT =
face=3DArial=20
  size=3D2>-Woj.</FONT></SPAN></DIV><BR>
  <BLOCKQUOTE dir=3Dltr=20
  style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px =
solid; MARGIN-RIGHT: 0px">
    <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
    <HR tabIndex=3D-1>
    <FONT face=3DTahoma size=3D2><B>From:</B> ancp-bounces@ietf.org=20
    [mailto:ancp-bounces@ietf.org] <B>On Behalf Of </B>Wojciech Dec=20
    (wdec)<BR><B>Sent:</B> 20 April 2008 14:39<BR><B>To:</B> Peter =
Arberg;=20
    ancp@ietf.org<BR><B>Subject:</B> Re: [ANCP] Bulk Transaction=20
    Message<BR></FONT><BR></DIV>
    <DIV></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D668522812-20042008><FONT =
face=3DArial=20
    size=3D2>It's all simple:</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D668522812-20042008><FONT =
face=3DArial=20
    size=3D2>-&nbsp;the Design Team is looking at the possibility of =
using this=20
    message</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D668522812-20042008><FONT =
face=3DArial=20
    size=3D2>- the message in its current form does not appear to be =
terribly=20
    useful, and could be&nbsp;removed from the spec.</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D668522812-20042008><FONT =
face=3DArial=20
    size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D668522812-20042008><FONT =
face=3DArial=20
    size=3D2>-Woj.</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D668522812-20042008><FONT =
face=3DArial=20
    size=3D2></FONT></SPAN>&nbsp;</DIV><BR>
    <BLOCKQUOTE dir=3Dltr=20
    style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 =
2px solid; MARGIN-RIGHT: 0px">
      <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
      <HR tabIndex=3D-1>
      <FONT face=3DTahoma size=3D2><B>From:</B> ancp-bounces@ietf.org=20
      [mailto:ancp-bounces@ietf.org] <B>On Behalf Of </B>Peter=20
      Arberg<BR><B>Sent:</B> 19 April 2008 03:07<BR><B>To:</B> Wojciech =
Dec=20
      (wdec); ancp@ietf.org<BR><B>Subject:</B> Re: [ANCP] Bulk =
Transaction=20
      Message<BR></FONT><BR></DIV>
      <DIV></DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D197410601-19042008><FONT =
face=3DArial=20
      color=3D#0000ff size=3D2>Hi Woj,</FONT></SPAN></DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D197410601-19042008><FONT =
face=3DArial=20
      color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D197410601-19042008><FONT =
face=3DArial=20
      color=3D#0000ff size=3D2>can you give a little background to why =
you are=20
      looking for vendor</FONT></SPAN></DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D197410601-19042008><FONT =
face=3DArial=20
      color=3D#0000ff size=3D2>implementation support for this specific =
capability=20
      &amp; message ?</FONT></SPAN></DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D197410601-19042008><FONT =
face=3DArial=20
      color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D197410601-19042008><FONT =
face=3DArial=20
      color=3D#0000ff size=3D2>thanks,</FONT></SPAN></DIV>
      <DIV dir=3Dltr align=3Dleft><SPAN class=3D197410601-19042008><FONT =
face=3DArial=20
      color=3D#0000ff size=3D2>Peter</FONT></SPAN></DIV><BR>
      <BLOCKQUOTE dir=3Dltr=20
      style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff =
2px solid; MARGIN-RIGHT: 0px">
        <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
        <HR tabIndex=3D-1>
        <FONT face=3DTahoma size=3D2><B>From:</B> ancp-bounces@ietf.org=20
        [mailto:ancp-bounces@ietf.org] <B>On Behalf Of </B>Wojciech Dec=20
        (wdec)<BR><B>Sent:</B> 18. april 2008 08:04<BR><B>To:</B>=20
        ancp@ietf.org<BR><B>Subject:</B> [ANCP] Bulk Transaction=20
        Message<BR></FONT><BR></DIV>
        <DIV></DIV><!-- Converted from text/rtf format -->
        <P><SPAN lang=3Den-gb><FONT face=3DArial size=3D2>Hi =
Folks,</FONT></SPAN> </P>
        <P><SPAN lang=3Den-gb><FONT face=3DArial size=3D2>Could you =
please let me/us=20
        know if you currently have an implementation of ANCP that =
supports the=20
        Bulk Transaction Capability and Message?</FONT></SPAN></P>
        <P><SPAN lang=3Den-gb><FONT face=3DArial =
size=3D2>Thanks,</FONT></SPAN>=20
        <BR><SPAN lang=3Den-gb><FONT face=3DArial =
size=3D2>Woj.</FONT></SPAN><SPAN=20
        lang=3Den-us></SPAN>=20
</P></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C8AF9F.320199DA--

--===============0075374826==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============0075374826==--


From ancp-bounces@ietf.org  Tue May  6 17:04:36 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6BCAD3A6D32;
	Tue,  6 May 2008 17:04:36 -0700 (PDT)
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 C22023A6913
	for <ancp@core3.amsl.com>; Tue,  6 May 2008 17:04:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 m0tNVAQkDA9o for <ancp@core3.amsl.com>;
	Tue,  6 May 2008 17:04:20 -0700 (PDT)
Received: from exprod7og105.obsmtp.com (exprod7og105.obsmtp.com [64.18.2.163])
	by core3.amsl.com (Postfix) with ESMTP id 481A828C52B
	for <ancp@ietf.org>; Tue,  6 May 2008 17:04:04 -0700 (PDT)
Received: from source ([66.129.224.36]) by exprod7ob105.postini.com
	([64.18.6.12]) with SMTP; Tue, 06 May 2008 17:04:01 PDT
Received: from proton.jnpr.net ([10.10.2.37]) by gamma.jnpr.net with Microsoft
	SMTPSVC(6.0.3790.1830); Tue, 6 May 2008 17:03:11 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 6 May 2008 20:03:10 -0400
Message-ID: <9BD5D7887235424FA97DFC223CAE3C280AB43A61@proton.jnpr.net>
In-Reply-To: <D9872168DBD43A41BD71FFC4713274D405043771@xmb-ams-33b.emea.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ANCP] Bulk Transaction Message
Thread-Index: AcihZWeDZVeOVtxMS1uttRBEffcNEwAVDjfgAEod1tAAAWRvoAMsB4yQAADCZxAAAKZHUAAJVuxQ
From: "Sanjay Wadhwa" <swadhwa@juniper.net>
To: "Wojciech Dec (wdec)" <wdec@cisco.com>,
	"Peter Arberg" <parberg@redback.com>, <ancp@ietf.org>
X-OriginalArrivalTime: 07 May 2008 00:03:11.0806 (UTC)
	FILETIME=[BD4045E0:01C8AFD5]
Subject: Re: [ANCP] Bulk Transaction Message
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/pipermail/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>
Content-Type: multipart/mixed; boundary="===============1082363773=="
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1082363773==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8AFD5.BC4D6B44"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8AFD5.BC4D6B44
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Even with transport being TCP, I see atleast a couple of benefits:
=20
1. If a sender knows it has a bunch of messages to send (e.g. ANCP
adjacency flaps, and all the port-up messages need to re-played), then
bulking by definition allows the application to invoke TCP fewer times
to transmit everything that it needs to transmit, which in a lot of
systems can translate to significant compute and memory efficiency
(specially, if we are considering a large amount of state). This is not
to say one can't realize this in an implementation specific way.=20
However, if neeeded, bulking also has the benefit of affording optimized
acking (e.g. if no error is encountered in proccessing all the
sub-messages in the bundled message, it is possible for the receiver to
send a cummulative ack to the sender rather than individual acks).
=20
2. Bulking also provides a nice solution if one ever needed to
atomically receive and process *distinct* ANCP message types.=20
=20
What is the downside of having it? It is negotiable as an optional
capability.
=20
Cheers
-Sanjay

-----Original Message-----
From: Wojciech Dec (wdec) [mailto:wdec@cisco.com]
Sent: Tuesday, May 06, 2008 1:24 PM
To: Sanjay Wadhwa; Peter Arberg; ancp@ietf.org
Subject: RE: [ANCP] Bulk Transaction Message


Sanjay,
=20
can you please present to the WG and myself how bulk transaction
capability is useful in any way in terms of scaling for example? And by
the way, please treat this discussion is orthogonal to any other.
=20
Cheers,
Woj.
=20


  _____ =20

From: Sanjay Wadhwa [mailto:swadhwa@juniper.net]=20
Sent: 06 May 2008 19:08
To: Wojciech Dec (wdec); Peter Arberg; ancp@ietf.org
Subject: RE: [ANCP] Bulk Transaction Message


Woj
  It is a bad idea to remove bulk-transaction capability from the draft.
On one hand you are trying to add "marginally useful" extensions (with
TLVs), and on the other hand you are arguing for removing useful
abstractions which can help with scaling. If bulk-transaction capability
needs to be augmented or modified, then we should consider augmenting
it, rather than removing it from the draft.
=20
Cheers
-Sanjay

-----Original Message-----
From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org]On Behalf Of
Wojciech Dec (wdec)
Sent: Tuesday, May 06, 2008 12:42 PM
To: Peter Arberg; ancp@ietf.org
Subject: Re: [ANCP] Bulk Transaction Message


Hi Folks,
=20
given that no discernable use of Bulk messaging has been identified, nor
there being a good reason for it given the fact that ANCP is bound to
the TCP transport (or equivalent), I would like to propose to remove all
of the text relating to this capability and associated message from the
protocol spec draft.
=20
Regards,
Woj.


  _____ =20

From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of
Wojciech Dec (wdec)
Sent: 20 April 2008 15:18
To: Peter Arberg; ancp@ietf.org
Subject: Re: [ANCP] Bulk Transaction Message


Should also have added: Given that currently the bulk message does not
appear to have had any practical adoption, having the DTeam adopt
it/modify it, or possibly have it removed from the spec all together are
all valid options.
=20
-Woj.


  _____ =20

From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of
Wojciech Dec (wdec)
Sent: 20 April 2008 14:39
To: Peter Arberg; ancp@ietf.org
Subject: Re: [ANCP] Bulk Transaction Message


It's all simple:
- the Design Team is looking at the possibility of using this message
- the message in its current form does not appear to be terribly useful,
and could be removed from the spec.
=20
-Woj.
=20


  _____ =20

From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of
Peter Arberg
Sent: 19 April 2008 03:07
To: Wojciech Dec (wdec); ancp@ietf.org
Subject: Re: [ANCP] Bulk Transaction Message


Hi Woj,
=20
can you give a little background to why you are looking for vendor
implementation support for this specific capability & message ?
=20
thanks,
Peter


  _____ =20

From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of
Wojciech Dec (wdec)
Sent: 18. april 2008 08:04
To: ancp@ietf.org
Subject: [ANCP] Bulk Transaction Message



Hi Folks,=20

Could you please let me/us know if you currently have an implementation
of ANCP that supports the Bulk Transaction Capability and Message?

Thanks,=20
Woj.=20


------_=_NextPart_001_01C8AFD5.BC4D6B44
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<TITLE>Bulk Transaction Message</TITLE>

<META content=3D"MSHTML 6.00.2800.1609" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D155264721-06052008>Even=20
with transport being TCP, I see atleast a couple of=20
benefits:</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D155264721-06052008></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D155264721-06052008>1. If=20
a&nbsp;sender knows it has a bunch of messages to send (e.g. ANCP =
adjacency=20
flaps, and all the port-up messages need to re-played), then bulking by=20
definition&nbsp;allows the application to invoke TCP fewer times to=20
transmit&nbsp;everything that it needs to transmit, which&nbsp;in a lot =
of=20
systems can translate to significant&nbsp;compute and memory efficiency=20
(specially, if we are considering a large amount of state). This&nbsp;is =
not to=20
say one can't&nbsp;realize this&nbsp;in an implementation specific=20
way.&nbsp;</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D155264721-06052008>However,&nbsp;if neeeded, bulking =
also&nbsp;has the=20
benefit of affording optimized acking (e.g. if no error is encountered =
in=20
proccessing all the sub-messages in the bundled message, it&nbsp;is=20
possible&nbsp;for the receiver to send a cummulative ack to the sender =
rather=20
than individual acks).</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D155264721-06052008></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D155264721-06052008>2.=20
Bulking also provides a nice solution if one&nbsp;ever needed to =
atomically=20
receive and process *distinct* ANCP message types. </SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D155264721-06052008></SPAN></FONT><FONT face=3DArial =
color=3D#0000ff=20
size=3D2><SPAN class=3D155264721-06052008></SPAN></FONT><FONT =
face=3DArial=20
color=3D#0000ff size=3D2><SPAN =
class=3D155264721-06052008></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D155264721-06052008>What=20
is the downside of having it? It is&nbsp;negotiable as an optional=20
capability.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D155264721-06052008></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D155264721-06052008>Cheers</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D155264721-06052008>-Sanjay</SPAN></FONT></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> Wojciech Dec =
(wdec)=20
  [mailto:wdec@cisco.com]<BR><B>Sent:</B> Tuesday, May 06, 2008 1:24=20
  PM<BR><B>To:</B> Sanjay Wadhwa; Peter Arberg; =
ancp@ietf.org<BR><B>Subject:</B>=20
  RE: [ANCP] Bulk Transaction Message<BR><BR></FONT></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D967002017-06052008><FONT =
face=3DArial=20
  size=3D2>Sanjay,</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D967002017-06052008><FONT =
face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D967002017-06052008><FONT =
face=3DArial=20
  size=3D2>can you please present to the WG and myself how bulk =
transaction=20
  capability is useful in any way in terms of scaling for example? And =
by the=20
  way, please treat this discussion is orthogonal to any=20
  other.</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D967002017-06052008><FONT =
face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D967002017-06052008><FONT =
face=3DArial=20
  size=3D2>Cheers,</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D967002017-06052008><FONT =
face=3DArial=20
  size=3D2>Woj.</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D967002017-06052008><FONT =
face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV><BR>
  <BLOCKQUOTE dir=3Dltr=20
  style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px =
solid; MARGIN-RIGHT: 0px">
    <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
    <HR tabIndex=3D-1>
    <FONT face=3DTahoma size=3D2><B>From:</B> Sanjay Wadhwa=20
    [mailto:swadhwa@juniper.net] <BR><B>Sent:</B> 06 May 2008=20
    19:08<BR><B>To:</B> Wojciech Dec (wdec); Peter Arberg;=20
    ancp@ietf.org<BR><B>Subject:</B> RE: [ANCP] Bulk Transaction=20
    Message<BR></FONT><BR></DIV>
    <DIV></DIV>
    <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
    class=3D093250117-06052008>Woj</SPAN></FONT></DIV>
    <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
    class=3D093250117-06052008>&nbsp; It is a bad idea to remove =
bulk-transaction=20
    capability from the draft. On one hand you are trying to add =
"marginally=20
    useful" extensions (with TLVs), and on the other hand you are =
arguing for=20
    removing useful abstractions which can help with scaling.=20
    </SPAN></FONT><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
    class=3D093250117-06052008>If bulk-transaction capability needs to =
be=20
    augmented or modified, then we should consider augmenting it, rather =
than=20
    removing it from the draft.</SPAN></FONT></DIV>
    <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
    class=3D093250117-06052008></SPAN></FONT>&nbsp;</DIV>
    <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
    class=3D093250117-06052008>Cheers</SPAN></FONT></DIV>
    <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
    class=3D093250117-06052008>-Sanjay</SPAN></FONT></DIV>
    <BLOCKQUOTE dir=3Dltr=20
    style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff =
2px solid; MARGIN-RIGHT: 0px">
      <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
      size=3D2>-----Original Message-----<BR><B>From:</B> =
ancp-bounces@ietf.org=20
      [mailto:ancp-bounces@ietf.org]<B>On Behalf Of </B>Wojciech Dec=20
      (wdec)<BR><B>Sent:</B> Tuesday, May 06, 2008 12:42 =
PM<BR><B>To:</B> Peter=20
      Arberg; ancp@ietf.org<BR><B>Subject:</B> Re: [ANCP] Bulk =
Transaction=20
      Message<BR><BR></FONT></DIV>
      <DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
      class=3D811403916-06052008>Hi Folks,</SPAN></FONT></DIV>
      <DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
      class=3D811403916-06052008></SPAN></FONT>&nbsp;</DIV>
      <DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
      class=3D811403916-06052008>given that no discernable use of Bulk =
messaging=20
      has been identified, nor&nbsp;there being a good reason for it =
given the=20
      fact that ANCP is bound to the TCP transport (or =
equivalent),&nbsp;I would=20
      like to propose to remove all of the text relating to this =
capability and=20
      associated message from the protocol spec =
draft.</SPAN></FONT></DIV>
      <DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
      class=3D811403916-06052008></SPAN></FONT>&nbsp;</DIV>
      <DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
      class=3D811403916-06052008>Regards,</SPAN></FONT></DIV>
      <DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
      class=3D811403916-06052008>Woj.</SPAN></FONT></DIV><BR>
      <BLOCKQUOTE dir=3Dltr=20
      style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 =
2px solid; MARGIN-RIGHT: 0px">
        <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
        <HR tabIndex=3D-1>
        <FONT face=3DTahoma size=3D2><B>From:</B> ancp-bounces@ietf.org=20
        [mailto:ancp-bounces@ietf.org] <B>On Behalf Of </B>Wojciech Dec=20
        (wdec)<BR><B>Sent:</B> 20 April 2008 15:18<BR><B>To:</B> Peter =
Arberg;=20
        ancp@ietf.org<BR><B>Subject:</B> Re: [ANCP] Bulk Transaction=20
        Message<BR></FONT><BR></DIV>
        <DIV></DIV>
        <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D490440813-20042008><FONT face=3DArial=20
        size=3D2>Should also have added: Given that currently&nbsp;the =
bulk=20
        message does not appear to have had any practical&nbsp;adoption, =
having=20
        the DTeam adopt it/modify it, or possibly have it removed from =
the spec=20
        all together&nbsp;are all valid options.</FONT></SPAN></DIV>
        <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D490440813-20042008><FONT face=3DArial=20
        size=3D2></FONT></SPAN>&nbsp;</DIV>
        <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D490440813-20042008><FONT face=3DArial=20
        size=3D2>-Woj.</FONT></SPAN></DIV><BR>
        <BLOCKQUOTE dir=3Dltr=20
        style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: =
#000000 2px solid; MARGIN-RIGHT: 0px">
          <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
          <HR tabIndex=3D-1>
          <FONT face=3DTahoma size=3D2><B>From:</B> =
ancp-bounces@ietf.org=20
          [mailto:ancp-bounces@ietf.org] <B>On Behalf Of </B>Wojciech =
Dec=20
          (wdec)<BR><B>Sent:</B> 20 April 2008 14:39<BR><B>To:</B> Peter =
Arberg;=20
          ancp@ietf.org<BR><B>Subject:</B> Re: [ANCP] Bulk Transaction=20
          Message<BR></FONT><BR></DIV>
          <DIV></DIV>
          <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D668522812-20042008><FONT=20
          face=3DArial size=3D2>It's all simple:</FONT></SPAN></DIV>
          <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D668522812-20042008><FONT=20
          face=3DArial size=3D2>-&nbsp;the Design Team is looking at the =
possibility=20
          of using this message</FONT></SPAN></DIV>
          <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D668522812-20042008><FONT=20
          face=3DArial size=3D2>- the message in its current form does =
not appear to=20
          be terribly useful, and could be&nbsp;removed from the=20
          spec.</FONT></SPAN></DIV>
          <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D668522812-20042008><FONT=20
          face=3DArial size=3D2></FONT></SPAN>&nbsp;</DIV>
          <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D668522812-20042008><FONT=20
          face=3DArial size=3D2>-Woj.</FONT></SPAN></DIV>
          <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D668522812-20042008><FONT=20
          face=3DArial size=3D2></FONT></SPAN>&nbsp;</DIV><BR>
          <BLOCKQUOTE dir=3Dltr=20
          style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: =
#000000 2px solid; MARGIN-RIGHT: 0px">
            <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
            <HR tabIndex=3D-1>
            <FONT face=3DTahoma size=3D2><B>From:</B> =
ancp-bounces@ietf.org=20
            [mailto:ancp-bounces@ietf.org] <B>On Behalf Of </B>Peter=20
            Arberg<BR><B>Sent:</B> 19 April 2008 03:07<BR><B>To:</B> =
Wojciech=20
            Dec (wdec); ancp@ietf.org<BR><B>Subject:</B> Re: [ANCP] Bulk =

            Transaction Message<BR></FONT><BR></DIV>
            <DIV></DIV>
            <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D197410601-19042008><FONT=20
            face=3DArial color=3D#0000ff size=3D2>Hi =
Woj,</FONT></SPAN></DIV>
            <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D197410601-19042008><FONT=20
            face=3DArial color=3D#0000ff =
size=3D2></FONT></SPAN>&nbsp;</DIV>
            <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D197410601-19042008><FONT=20
            face=3DArial color=3D#0000ff size=3D2>can you give a little =
background to=20
            why you are looking for vendor</FONT></SPAN></DIV>
            <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D197410601-19042008><FONT=20
            face=3DArial color=3D#0000ff size=3D2>implementation support =
for this=20
            specific capability &amp; message ?</FONT></SPAN></DIV>
            <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D197410601-19042008><FONT=20
            face=3DArial color=3D#0000ff =
size=3D2></FONT></SPAN>&nbsp;</DIV>
            <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D197410601-19042008><FONT=20
            face=3DArial color=3D#0000ff =
size=3D2>thanks,</FONT></SPAN></DIV>
            <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D197410601-19042008><FONT=20
            face=3DArial color=3D#0000ff =
size=3D2>Peter</FONT></SPAN></DIV><BR>
            <BLOCKQUOTE dir=3Dltr=20
            style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: =
#0000ff 2px solid; MARGIN-RIGHT: 0px">
              <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
              <HR tabIndex=3D-1>
              <FONT face=3DTahoma size=3D2><B>From:</B> =
ancp-bounces@ietf.org=20
              [mailto:ancp-bounces@ietf.org] <B>On Behalf Of =
</B>Wojciech Dec=20
              (wdec)<BR><B>Sent:</B> 18. april 2008 08:04<BR><B>To:</B>=20
              ancp@ietf.org<BR><B>Subject:</B> [ANCP] Bulk Transaction=20
              Message<BR></FONT><BR></DIV>
              <DIV></DIV><!-- Converted from text/rtf format -->
              <P><SPAN lang=3Den-gb><FONT face=3DArial size=3D2>Hi=20
              Folks,</FONT></SPAN> </P>
              <P><SPAN lang=3Den-gb><FONT face=3DArial size=3D2>Could =
you please let=20
              me/us know if you currently have an implementation of ANCP =
that=20
              supports the Bulk Transaction Capability and=20
              Message?</FONT></SPAN></P>
              <P><SPAN lang=3Den-gb><FONT face=3DArial =
size=3D2>Thanks,</FONT></SPAN>=20
              <BR><SPAN lang=3Den-gb><FONT face=3DArial=20
              size=3D2>Woj.</FONT></SPAN><SPAN lang=3Den-us></SPAN>=20
          =
</P></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BL=
OCKQUOTE></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C8AFD5.BC4D6B44--

--===============1082363773==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1082363773==--


From ancp-bounces@ietf.org  Tue May  6 17:18:49 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 5B7AB3A682F;
	Tue,  6 May 2008 17:18:49 -0700 (PDT)
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 9E0DB3A682F
	for <ancp@core3.amsl.com>; Tue,  6 May 2008 17:18:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 Ul+EFqJ-sZus for <ancp@core3.amsl.com>;
	Tue,  6 May 2008 17:18:12 -0700 (PDT)
Received: from exprod7og104.obsmtp.com (exprod7og104.obsmtp.com [64.18.2.161])
	by core3.amsl.com (Postfix) with ESMTP id 3A6323A6DB4
	for <ancp@ietf.org>; Tue,  6 May 2008 17:16:09 -0700 (PDT)
Received: from source ([66.129.224.36]) by exprod7ob104.postini.com
	([64.18.6.12]) with SMTP; Tue, 06 May 2008 17:16:04 PDT
Received: from proton.jnpr.net ([10.10.2.37]) by emailsmtp56.jnpr.net with
	Microsoft SMTPSVC(6.0.3790.3959); Tue, 6 May 2008 17:15:47 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 6 May 2008 20:15:45 -0400
Message-ID: <9BD5D7887235424FA97DFC223CAE3C280AB43A62@proton.jnpr.net>
In-Reply-To: <D9872168DBD43A41BD71FFC4713274D40504372B@xmb-ams-33b.emea.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ANCP] Mandatory TLVs in draft-ietf-ancp-protocol proposal
Thread-Index: AcilQRMfK4kdawUKQOWs5fdBngS8QQAAr04QACRhApAAC0ujAADNHRywAADiEXAAAbhxoAAAWwcQACIOoKAAAXsqYAASvbCgAAE4sjAAASS6UAABRQpQABPWDgABARaTgABWLaoQ
From: "Sanjay Wadhwa" <swadhwa@juniper.net>
To: "Wojciech Dec (wdec)" <wdec@cisco.com>,
	"Peter Arberg" <parberg@redback.com>,
	"DE CNODDER Stefaan" <stefaan.de_cnodder@alcatel-lucent.be>,
	"Busser, M" <Michael.Busser@t-systems.com>, <ancp@ietf.org>
X-OriginalArrivalTime: 07 May 2008 00:15:47.0018 (UTC)
	FILETIME=[7F647AA0:01C8AFD7]
Cc: "Haag, T" <Thomas.Haag@t-systems.com>
Subject: Re: [ANCP] Mandatory TLVs in draft-ietf-ancp-protocol proposal
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/pipermail/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>
Content-Type: multipart/mixed; boundary="===============1172968506=="
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1172968506==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8AFD7.7E33EDD8"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8AFD7.7E33EDD8
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

>On the Mandatory Flag aspect, there is one key reason why any protocol =
does; it is to offload the application from doing base data-element =
checking.
=20
How and why ? Sounds dangerous to me.
=20
-Sanjay

-----Original Message-----
From: Wojciech Dec (wdec) [mailto:wdec@cisco.com]
Sent: Tuesday, May 06, 2008 12:33 PM
To: Sanjay Wadhwa; Peter Arberg; DE CNODDER Stefaan; Busser, M; =
ancp@ietf.org
Cc: Haag, T
Subject: RE: [ANCP] Mandatory TLVs in draft-ietf-ancp-protocol proposal


Sanjay,
=20
Inline.... Woj#2


  _____ =20

From: Sanjay Wadhwa [mailto:swadhwa@juniper.net]=20
Sent: 30 April 2008 07:40
To: Wojciech Dec (wdec); Peter Arberg; DE CNODDER Stefaan; Busser, M; =
ancp@ietf.org
Cc: Haag, T
Subject: RE: [ANCP] Mandatory TLVs in draft-ietf-ancp-protocol proposal



Woj

  I agree only on the following:

=20

1.	A TLV might be mandatory for one application or use-case, and =
optional for another application. We do need to clearly specify in the =
draft if a TLV is mandatory or optional for a given application (which =
boils down to specifying this per ANCP message and message type).=20

=20
Woj#2> I interpret this to mean that you've taken on the action to =
clarify the protocol spec text, and also prepare the table of TLVs =
indicating where each TLV is mandatory, and where optional. Please let =
me know if this is not so
=20

1.	We should clearly specify the behavior for handling missing mandatory =
TLVs in received messages.=20

=20

To me the utility of flagging a TLV as mandatory or optional via the =
protocol is at best debatable.  If a buggy implementation on the sender =
incorrectly sets a "known" TLV as mandatory (when it is not) or =
vice-versa, do we want the receiver to infer the handling of this TLV =
based on what the sender tells it? I don't think so. Ideally, we want =
the receiver and sender to have a common understanding of what is =
mandatory and what is optional based on what is in the spec, and handle =
the TLV based on that understanding. As Peter mentions, the spec clearly =
spells out TLVs that are mandatory and optional. Also, I don't see a =
major advantage of your proposal with respect to debuggability.=20

=20

=20

Typical case where it does make sense for the sender to set some flag in =
the TLV to control the handling of the TLV on the receiver is for =
"unrecognized" TLV types...e.g.

1.	Receiver is an intermediate node, which consumes the message but also =
needs to forward it along to other nodes. Here the sender can flag the =
handling of the TLV to the receiver (e.g. discard or forward if the TLV =
type is not recognized by the receiver). This doesn't quite apply to =
ANCP (messages are confined to be between two peers). =20

=20
Woj#2> It happens that an ANCP relay has already been proposed in the =
DSL Forum, and under in some situations it could be a viable entity. By =
NOT designing such flags now, we're likely making things more difficult =
in the future. Anyway, since there doesn't seem to be much enthusiasm =
for "Mandatory" flags, I'll put the subject to rest for now.

=20

2.	If handling of an unrecognized TLV on the receiver needs to be =
different for an optional TLV versus a mandatory TLV. Here the receiver =
doesn't understand the TLV type, but can infer the handling based on the =
flag in the TLV. However, do we want the treatment of "unrecognized" =
TLVs on the receiver to be different for optional and mandatory TLVs =
(e.g. silently discard an unrecognized optional TLV...but discard and =
also send an error back for an unrecognized mandatory TLV). I don't =
think this is necessary. However, if we do want to do this, then may be =
the flag in the TLV should explicitly indicate the handling for the TLV =
(e.g. "silently discard if un-recognized" versus "discard and send an =
error back")...as opposed to just flagging these as "mandatory" versus =
"optional". =20

=20

Woj> Of course it is, the whole spec is about this. The problem comes =
when people start to re-use well known TLVs for different applications, =
and then trying to make sense of it all >becomes non-trivial. Why do you =
think both BGP and Diamater, and a number of other protocols have =
definied "Mandatory" flags? Just for kicks? It's a well known protocol =
design tool, that >comes handy when re-using same data across multiple =
applications.

=20

We should look at why these protocols are doing this (as opposed to =
blindly following). For a counter example, please take a look at OSPF =
traffic engineering extensions (RFC 3630). =20

=20

Woj #2 >  The irony of the above statement in view of  the initiators of =
ANCP blindly following GSMP is hopefully not lost on you. On the =
Mandatory Flag aspect, there is one key reason why any protocol does; it =
is to offload the application from doing base data-element checking. =
Anyway, we can move on.

=20

-Woj.

=20

=20

=20

=20

Cheers

-Sanjay

=20


  _____ =20


From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of =
Wojciech Dec (wdec)
Sent: Tuesday, April 29, 2008 3:03 PM
To: Peter Arberg; DE CNODDER Stefaan; Busser, M; ancp@ietf.org
Cc: Haag, T
Subject: Re: [ANCP] Mandatory TLVs in draft-ietf-ancp-protocol proposal

=20

Hi Peter,

=20

continued inline...

=20


  _____ =20


From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of =
Peter Arberg
Sent: 29 April 2008 20:39
To: Wojciech Dec (wdec); DE CNODDER Stefaan; Busser, M; ancp@ietf.org
Cc: Haag, T
Subject: Re: [ANCP] Mandatory TLVs in draft-ietf-ancp-protocol proposal

Hi Woj,

=20

please see inline in your answers

=20

=20


  _____ =20


From: Wojciech Dec (wdec) [mailto:wdec@cisco.com]=20
Sent: 29. april 2008 11:07
To: Peter Arberg; DE CNODDER Stefaan; Busser, M; ancp@ietf.org
Cc: Haag, T
Subject: RE: Re: [ANCP] Mandatory TLVs in draft-ietf-ancp-protocol =
proposal

Hi Peter,

=20

=20

=20


  _____ =20


From: Peter Arberg [mailto:parberg@redback.com]=20
Sent: 29 April 2008 19:34
To: Wojciech Dec (wdec); DE CNODDER Stefaan; Busser, M; ancp@ietf.org
Cc: Haag, T
Subject: RE: Re: [ANCP] Mandatory TLVs in draft-ietf-ancp-protocol =
proposal

Hi Woj,

=20

I agree with Michael and Stefan on this issue, I do not see a need to =
change the existing

implementation with a mandatory/optional flag.=20

=20

Woj> Please indicate where in my proposal did you see anything about =
changing existing implementaions? =20

=20

PAR>  I might have misunderstood your email, but I read it as if you =
suggest a high bit

value in existing TLV's to be interpreted as a mandatory flag.=20

=20

Woj#2> Yes, I suggested (in proposal 2) that *if* the WG found there to =
be a common set of TLVs currently in use, then the high-order bit set to =
"0" (ie as today) could be interpreted as "mandatory", and the rest of =
the TLV's redefined with a high order "1". To extsing implementations, =
the "new" TLVs would just look like a different TLV#, while anyone =
wishing to implement the more robust error cheking logic based on this =
bit, would be free to do so.=20

=20

If you are simply talking about new capability type definitions, then =
why do you not bring up

the additional flag in a new internet-draft defining what capability =
type you have in mind ?=20

=20

Woj#2> No, a new capability was not intended, but could also be =
considered.

=20

=20

I think I understand your arguments, but I do not agree with them. I =
think most places in

the draft it is clear what is defined as mandatory and optional.=20

=20

I agree on the point we need to go through the draft and make =
clarifications to what TLV's

in what capability types are mandatory and optional, and make more =
description what should

happen if mandatory TLVs are not included.=20

=20

Woj> Exactly.=20

=20

I think the DSLF TR-101 document has a good example of such a =
description in it's=20

"Table 3 - Access loop characteristics sub-options", and I think if we =
do the same for each

capability types TLV's in the ANCP draft it will be a good help.

=20

Woj> Indeed, pre-ceeded by some rationalization. The appears to be no =
reason for some of the DSLF "mandatory" TLVs.=20

=20

PAR> I do not see a problem with re-visit in the draft if a TLV should =
be optional or mandatory, so if

that is the intend, then I'm all for an email discussion on a TLV by TLV =
basis if we think it is a=20

manfdatory or optional information inside the specific capability type.=20

=20

Woj#2> Great, because any change to the mandated set *will* affect =
existing implementation .

=20

=20

=20

I do not agree with your point that it is not listed if "rate" is =
mandatory or optional, it is clearly

listed as a mandatory TLV, and as such it should be included in the port =
up message, I really

do not understand what confusion you have with this.=20

=20

Woj> The text states:  =20

=20

5. Type (DSL Line Attributes =3D 0x04):=20

Length : variable (up to 1024 bytes)=20

Value : This consists of one or more Sub-TLVs corresponding to DSL=20

line attributes. No sub-TLVs other than the "DSL type" and "DSL=20

line state" SHOULD be included in a PORT DOWN message.=20

The general format of the sub-TLVs is identical to the general TLV=20

format. The value field in each sub-TLV is padded to a 4-octet=20

alignment. The Length field in each sub-TLV contains the actual=20

number of bytes in the TLV (not including the padding if present).=20

Current defined sub-TLV types are start from 0x81. =20

Maybe you can point me to where exatly it is stated clearly as being =
mandatory, or otherwise explain why you "not agree"? =20

=20

PAR> I think you forgot to read the most important part where the actual =
TLV is defined.=20

=20

Woj#2> I didn't. This part talks about the sub-TLV, not the main TLV =
0x04. Do you see my point now?

=20

=20

Type (Actual-Net-Data-Upstream =3D 0x81): Actual upstream net data rate =
on a DSL line.=20

This is a mandatory TLV. =20

=20

Length  :  (4 bytes)=20

Value   : (Rate in Kb/sec)=20

=20

Type (Actual-Net-Data-Rate-Downstream =3D 0x82) : Actual downstream net =
data rate on a DSL line.=20

This is a mandatory TLV.=20

=20

Length :  (4 bytes)=20

Value  :  (Rate in Kb/sec)=20

=20

=20

The fact you say "Port UP" and "OAM" is best considered as legacy =
applications, I have some

trouble with this as well, since ANCP running in production networks use =
them, and as such

it is a central part of the ANCP specifications we need to finish as =
soon as possible.=20

=20

Woj> I should have said legacy applications from a protocol messaging =
perspective, not usage, nor support. It's quite clear that GSMP derived =
messaging has baggage that is un called for in new applications.

=20

I think Stefaan's example is very valid, that we do not need to make =
mandatory requirements to=20

what receivers of ANCP information use such info. for.  I don't think we =
should try and make the

ANCP specifications "mandatory" for box behavior, I think it is much =
more important for the=20

working group to make the protocol specifications easy to understand and =
get the first documentation

finish and published, so the protocol can be used for different sets of =
applications, and make sure

new applications can be added later.=20

=20

Woj> Indeed the aim of the WG to define a protocol that is relatively =
simple and easy to understand, not just to implementers but also to =
people using it, and across vendors. Currently, having anyone operating =
the device be familiar in what cases a TLV is mandatory and in what =
optional requires a thorough understanding of the spec, across =
applications. This is not easy, but I'll conceede that for the =
applications implemented so far we could live with it.=20

=20

I do think that by documenting if a TLV is mandatory or optional inside =
a specific capability type,

it is easy to understand what must be sent to support the defined =
application/capability type.=20

=20

Woj> Of course it is, the whole spec is about this. The problem comes =
when people start to re-use well known TLVs for different applications, =
and then trying to make sense of it all becomes non-trivial. Why do you =
think both BGP and Diamater, and a number of other protocols have =
definied "Mandatory" flags? Just for kicks? It's a well known protocol =
design tool, that comes handy when re-using same data across multiple =
applications.=20

=20

PAR> I might be wrong, but I think I can find as many or more protocol =
examples who do not include

a mandatory/optional flag, so examples can always be found which will =
support the point you are trying

to make.

=20

I do not see a problem with a new internet-draft which defines new =
capability-types and where a TLV

mandatory flag is included, I do see a problem if the intend is to try =
and adjust what already exist. =20

=20

Woj#2> Ok, so if adjusting is only scoped to what doesn't exist, as my =
proposal laid out conditionally, you're fine.

=20

=20

=20

Then if anybody want to include new capability types or sub-TLVs later =
to address specific applications,

then I think changes can be discussed at that time instead of trying to =
change existing protocol

implementations.=20

=20

Woj> Again I ask, where in the proposal did you see *anything* requiring =
a change to an existing implementation. Please be specific. I see that =
your main objection is on this issue, which means that you accept =
proposal 1 (have such a flag for new TLVs/apps).

It would also be useful if you indicated whether the list of TLVs =
provided below is what you'd expect to be the minimum mandatory set.=20

=20

PAR> at the moment I read the draft as having defined the TLVs mandatory =
as you describe, except

I also read it as the dsl-type =3D 0x91 must be part of the port down. =
If this is needed or not is a different

discussion.

=20

=20

Woj#2> Ok. Thanks. But please do come back to me if you see that the =
proposal impacts an exiting implementation. I conclude that there is no =
problem with doing changes to stuff that isn't currently used.

Woj.

=20

cheers,

Peter=20

=20

Cheers,

Woj.

=20

cheers,

Peter

=20

=20

=20

=20


  _____ =20


From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of =
Wojciech Dec (wdec)
Sent: 29. april 2008 02:28
To: DE CNODDER Stefaan; Busser, M; ancp@ietf.org
Cc: Haag, T
Subject: Re: [ANCP] Mandatory TLVs in draft-ietf-ancp-protocol proposal

Stefaan,

=20

a number of points:

1. There currently is to my knowledge no implementation of ANCP there =
that doesn't send the DSL Line attributes info by default in Port-UP =
messages? The support of HS on the NAS is an orthogonal issue.

2. The current ancp protocol draft (02) doesn't say whether the rate =
info is optional or mandatory, it only states that the sub-TLVs are =
mandatory. Based on this, an implementer can be justified to expect =
port-ups to *always* have the rate-info tlv (ie treat them as =
mandatory). Equally, she's justified in considering this  as optional.

3. The port-up and OAM are best considered as legacy applications for =
ANCP. The re-use of any of the GSMP defined fields is already out of the =
question due to constrains put in place by the existing use-case =
messaging. Needless to say, this wasn't as thoroughly designed as it =
should have been, and with the OAM and port-up apps being coupled.

4. It's up to the application to define what TLVs are mandatory and =
which aren't, as you also state. The AN does not need to know what the =
NAS will do with the info, BUT it needs to send the right TLVs for the =
application (eg if we had a hypothetical AN that only sends Port-up's =
with line-id, it would be next to useless for the dynamic shaping =
application).

=20

With all this in mind it's useful to re-read what I proposed originally =
below regarding the mandatory flag: 1. "have this TLV Flag be defined =
only for new applications" and 2. The notion of the mandatory flag =
applying to existing TLVs  being "conditional on deriving a suitable =
"commonly used" TLV set." The latter point would ensure that existing =
implementations do not need to change, but future ones can take =
advantage of the extra robustness.

=20

Hence, can the WG derive a set of commonly used, i.e. always used, TLVs =
for existing implementations?

The list I came up is as follows (making them pretty much mandatory TLVs =
if it agrees with the views of others);

=20

Port-up message (0x80);

    Extension-TLV (dsl tech type)

    Access-Loop-circuit-id (0x01)

    DSL Line Attribute (0x04) with the following sub TLVs;

        DSL-Type =3D 0x91; Actual-Net-Data-Upstream =3D 0x81; =
Actual-Net-Data-Rate-Downstream =3D 0x82

=20

Port-down message (0x81);

    Extension  TLV (dsl tech type)

    Access-Loop-circuit-id (0x01)

    DSL Line Attribute (0x04) with the following sub TLVs;

        DSL line state =3D 0x8F

=20

All other TLVs are optional.

=20

Would appreciate confirmation from the WG regarding the above.

=20

Thanks,

Woj.

=20

=20


  _____ =20


From: DE CNODDER Stefaan [mailto:stefaan.de_cnodder@alcatel-lucent.be]=20
Sent: 29 April 2008 09:52
To: Wojciech Dec (wdec); Busser, M; ancp@ietf.org
Cc: Haag, T
Subject: RE: [ANCP] Mandatory TLVs in draft-ietf-ancp-protocol proposal

=20

Hi Woj,

=20

Take the following example: I have a network with 2 NASses, NAS-A is =
doing hierarchical shaping, NAS-B just wants to have the port =
information but is not doing hierarchical shaping (it is doing other =
things like OAM, ...).  This means NAS-A needs the bandwidth, while =
NAS-B does not need the bandwidth.  How should the flag be set in this =
case by the AN?  Set to 'Mandatory' for the port up messages to NAS-A, =
and set to 'Optional' for port up messages towards NAS-B? Or is it =
always set to 'Mandatory'?  From your answer below, I understand that it =
should be set to 'Optional' towards NAS-B.  Is that correct?

=20

NAS-B will simply ignore the bandwidth TLV.  If such a flag would exist, =
and the flag is set to 'Mandatory' by the AN to NAS-B, what should be =
the behavior of NAS-B?  Should it reject the whole message?  Maybe NAS-B =
is not supporting hierarchical shaping, so it might not support the =
bandwidth TLV.  Today, the bandwidht TLV is only mandatory to be put in =
the port up messages, but for the receiver there is nothing mandatory.

=20

I believe the original intend of ANCP was that the AN does not need to =
know what the NAS is doing with this information, the use of the =
bandwidth is also not specified by ANCP, only an example is given (which =
is shaping).  In the future there may be applications for which TLVs =
will be mandatory which are now optional.

=20

regards,

Stefaan

=20

=20

=20

=20


  _____ =20


From: Wojciech Dec (wdec) [mailto:wdec@cisco.com]=20
Sent: maandag 28 april 2008 21:33
To: DE CNODDER Stefaan; Busser, M; ancp@ietf.org
Cc: Haag, T
Subject: RE: [ANCP] Mandatory TLVs in draft-ietf-ancp-protocol proposal

=20

=20


  _____ =20


From: DE CNODDER Stefaan [mailto:stefaan.de_cnodder@alcatel-lucent.be]=20
Sent: 28 April 2008 17:15
To: Wojciech Dec (wdec); Busser, M; ancp@ietf.org
Cc: Haag, T
Subject: RE: [ANCP] Mandatory TLVs in draft-ietf-ancp-protocol proposal

=20

Take the bandwidth sub-TLV in port up messages as example.  The current =
protocol spec says that it is mandatory to be sent in port up messages.  =
that's ok.  But it is not mandatory for the receiver to process the =
bandwidth sub-TLV.  What is done with this information by the NAS is not =
specified by ANCP, so you cannot make it mandatory for the receiver =
side.=20

=20

Woj> Is the information required by the application? It would appear for =
the dynamic shaping use-case to be most certainly so. Hence it is =
absolutely mandatory, otherwise the message makes no sense for the =
application. In any case, if=20

=20

So it looks to me that the flag can only indicate what the receiver =
should do.  Then the flag makes sense.=20

=20

Woj>  The flag tells the receiver what info the sender thinks is =
required to carry out the application. This in almost all cases has to =
match up to what the receiver thinks is required. The sender doesn't =
tell the receiver what to do with the info.

=20

If the receiver knows what is mandatory, then I do not see a reason why =
this has to be made explicit in the protocol.  It would only complicate =
the protocol.  As already said by Michael: if a mandatory TLV is not =
there, then it is just a bug.=20

=20

Woj> Can you specifically describe what aspect of the protocol does it =
complicate? It's just making explicitly clear what the protocol already =
has to implement anyway to be of any use.

As to whether it is a bug, having such explicit marking makes it clear =
what/where the problem is when observing a messaging flow vs a lot of =
deduction work. In any case, the other point being made here is that =
today the protocol does NOT specify what should happen if a mandatory =
TLV is missing.

=20

-Woj.

=20

regards,

Stefaan

=20

=20

=20


  _____ =20


From: Wojciech Dec (wdec) [mailto:wdec@cisco.com]=20
Sent: maandag 28 april 2008 16:28
To: DE CNODDER Stefaan; Busser, M; ancp@ietf.org
Cc: Haag, T
Subject: RE: [ANCP] Mandatory TLVs in draft-ietf-ancp-protocol proposal

It's actually a mix of both. Inline...

=20


  _____ =20


From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of =
DE CNODDER Stefaan
Sent: 28 April 2008 16:04
To: Wojciech Dec (wdec); Busser, M; ancp@ietf.org
Cc: Haag, T
Subject: Re: [ANCP] Mandatory TLVs in draft-ietf-ancp-protocol proposal

=20

Hi,

=20

This new mandatory flag, what is exactly its meaning?

=20

(1) if flag set to "mandatory", then the *receiver* of this TLV MUST =
process it, and if unrecognized must drop the message=20

=20

If a received TLV is has the "mandatory" flag set then the receiver MUST =
drop the message and report an error to the sender if it doesn't =
recognize the TLV.=20

If a the receiver expects a "mandatory" TLV but doesn't receive it, the =
message MUST be droped and an error report sent to the sender.=20

=20

OR

=20

(2) if flag is set to"mandatory", then the *sender* MUST include it in =
the message for which it is defined=20

=20

The sender MUST include mandatory TLVs as defined by the =
protocol-spec/applications.

=20

The current protocols draft says for certain TLVs that they are =
mandatory, but that applies to the sender of it (interpretation 2).  The =
flag would indicate interpretation 1 (like for Radius VSAs?)?

=20

If the higher order bit is set to "0" means that it is mandatory, then =
currently defined optional defined TLVs suddenly become mandatory which =
is not good.=20

=20

Woj> Only the currently used TLVs become mandatory. If they are not =
used/implemented we can re-define them as optional (set flag to 1) at no =
cost.=20

=20

But I would first to understand the exact meaning of this mandatory =
flag.  Defining such a flag indeed looks useful but then as =
interpretation 1, and I would say that if flag set to 1, then it is =
mandatory and actually, it is possible that a TLV is sent sometimes as =
optional and sometimes as mandatory.=20

=20

Woj> Precisely, that is possible on a per application basis. Having the =
flag would make troubleshooting of a message flow much more explicit =
(today, with any problem one has to browse the drafts to figure out what =
MUST be there vs what SHOULD be there all while looking what is actually =
there)

=20

Regards,

Woj.

=20

regards,

Stefaan

=20

=20


  _____ =20


From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of =
Wojciech Dec (wdec)
Sent: donderdag 24 april 2008 14:19
To: Busser, M; ancp@ietf.org
Cc: Haag, T
Subject: Re: [ANCP] Mandatory TLVs in draft-ietf-ancp-protocol proposal

Hi Michael,

=20

inline...

=20


  _____ =20


From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of =
Busser, M
Sent: 24 April 2008 13:13
To: ancp@ietf.org
Cc: Haag, T
Subject: Re: [ANCP] Mandatory TLVs in draft-ietf-ancp-protocol proposal

Hi Woi, all

=20

I see the problem but i can not see, how an additional flag will help =
solving this problem.

=20

Lets assume your first proposal.

If an implementation does not send the complete TLV, even it is defined =
to be mandatory, I would call this a bug and I can not see, how an =
additional flag can help here.=20

=20

Woj> The way it helps, and other protocols bear proof of this scheme, is =
that it is easier for implementations to reconcile errors resulting out =
of "Mandatory" and "Optional" TLV sets. The key to this lies on a per =
application basis. One application may mandate TLV A for operation, =
while another might not. Resolving such issues when implementing or =
troubleshooting multiple applications is not always trivial.=20

=20

Your second proposal seems obviously be required to keep existing things =
working, if we agree on your first proposal.=20

But from my point of view it also assumes, that all existing =
implementations are using the same set of TLVs now.=20

And I am not sure about that. =20

=20

Woj> This would be a good thing for the WG to discuss. There most =
evidently is a fair amount of "dead wood" in the current spec, ie stuff =
that nobody yet implements or cares about.  In the former case, we could =
re-cast that material using the new notions/extensions, in the latter =
case simply chop it out.

=20

Therefore I disagree with your first proposal. I recommend, the better =
way will be to be more precise in definitions.=20

In my mind, it is a bug, if a mandatory TLV is missing. It is up to the =
robustness of the implementation to deal with this situation.

Is it really neccesary to define the behavior of a network element in =
this case of failure in the ancp protocol itself? =20

=20

Woj> Other people have faced this problem before, and I would rather go =
with the lessons they learned, rather than clinging to hopes of perfect =
textual definitions and implementations. Other than backwards =
compatibility, I do not see in your statements a valid reason to object =
to the 1st proposal, particularly for new applications since it can only =
make things more robust. The counter argument of being precise in the =
definitions, as evidenced by the current spec, is admirable and needs to =
be there, with this proposal providing an extra level of robustness and =
visibility of any problems.=20

=20

Thanks,

Woj.

=20

If optional TLVs are not present in a message, we should describe some =
kind of default behaviour, as you already stated.

=20

=20

=20

=20

Comments on draft-ietf-ancp-protocol-02.txt:

=20

It is not clearly stated, if the TLV  "DSL Line Attributes " is =
mandatory or optional.=20

In fact it is mandatory because some of its SubTLVs are mandatory.=20

We should spent a sentence to make this clear.

=20

It is not clearly stated, if the TLV  "Service-Profile-Name" is =
mandatory or optional.

I prefer mandatory because it is essetial for the use case Line Config.=20

=20

Section 5.4.3 Line Config, where the TLVs are mentioned (page 35):

  ...defined in section 5.4.1....    must be corrected to    ...defined =
in section 5.4.2........

=20

Section 5.4.4 OAM, where the TLVs are mentioned (page 36 and page 38):

  ...defined in section 5.4.1....    must be corrected to    ...defined =
in section 5.4.2........

=20

=20

=20

=20

Best Regards; Freundliche Gr=FC=DFe=20

Michael Busser

T-Systems Enterprise Services GmbH=20

Production Line Network Centric Systems

ICT-Systems Integration

Network Integration Services

=20

Br=FCckes 2 -8, 55545 Bad Kreuznach
Postfach 9100, 55541 Bad Kreuznach
+49 671 8333 8911 (Phone)
+49 521 9210 3859 (Fax)
+49 151 1211 9689 (Mobile)
E-Mail: michael.busser@t-systems.com

Internet:  <http://www.t-systems.com/> http://www.t-systems.com=20

=20

T-Systems Enterprise Services GmbH
Aufsichtsrat: Ren=E9 Obermann (Vorsitzender)
Executive Committee: Reinhard Clemens (Vorsitzender)*, Helmut Binder, =
Albert Henn, Olaf Heyden*, Katrin Horstmann, Ulrich Kemp, Wilfried =
Peters*,
Dr. Herbert Schaaff*, Zvezdana Seeger*
Handelsregister: Amtsgericht Frankfurt am Main HRB 55933
Sitz der Gesellschaft: Frankfurt am Main
WEEE-Reg.-Nr. DE87523644
*Gesch=E4ftsf=FChrer gem. =A7 35 GmbHG

=20

Notice: This transmittal and/or attachments may be privileged or =
confidential. If you are not the intended recipient, you are hereby =
notified that you have received this transmittal in error; any review, =
dissemination, or copying is strictly prohibited. If you received this =
transmittal in error, please notify us immediately by reply and =
immediately delete this message and all its attachments. Thank you.=20
T-Systems - Business flexibility=20

=20

=20


  _____ =20


Von: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] Im Auftrag von =
Wojciech Dec (wdec)
Gesendet: Mittwoch, 23. April 2008 14:54
An: ancp@ietf.org
Betreff: [ANCP] Mandatory TLVs in draft-ietf-ancp-protocol proposal

=20

Hi All,=20

Continuing with the series of e-mails regarding basic protocol issues =
still to be addressed, I now would now like to ask your feedback =
regarding the distinction the protocol places on mandatory TLVs. Given =
the length of this mail I'll first cut to the proposal, and after it you =
can find the problem description.

The proposal which I am putting in front of the WG is to define a new =
TLV format which contains at a minimum a Mandatory flag (much like =
Radius VSAs do). We could have this TLV Flag be defined only for new =
applications.

A second proposal would be try to make this flag work with existing ones =
by for example defining the highest order bit of the TLV# field to mean =
"Mandatory" when set to "0". This would be invisible to exiting =
implementations, but newer ones may have problems in communicating with =
older ones when the latter do not send all TLVs. But that can also be =
addressed by simply forming the set of mandatory TLVs to be the ones =
that all implementations currently send by default.

Without additional feedback, I will assume that the WG is fine with the =
first proposal, and also with the 2nd one conditional on deriving a =
suitable "commonly used" TLV set.

The problem in more detail:=20

Currently the situation is that Mandatory TLVs are only stated to be as =
such in the body of the protocol draft spec, with an implementer having =
to scour fairly attentively the text. Eg "Type (Access-Loop-Circuit-ID =
=3D 0x01): This is a mandatory TLV", etc.

The behaviour of an implementation that receives a message with a =
missing mandatory TLV is not defined at all, and the opposite is handled =
but not very robustly, i.e. when receiving a TLV but not recognizing it, =
and implementation is free to discard it (even if it is mandatory!). =
This is a recipe for interoperability problems and an implementation =
mine field.

This problem is complicated by different applications. For example the =
current OAM section states the following regarding TLVs that are to be =
carried in the request message (my italics):

"=20
Following TLVs can appear in this message:=20

       o Type (Access-Loop-Circuit-ID =3D 0x01) : defined in section =
5.4.1   =20

       o Type (Access-Aggregation-Circuit-ID-Binary =3D 0x06): defined =
in=20
         section 5.4.1.=20
 =20
       o Type (Access-Aggregation-Circuit-ID-ASCII =3D 0x03): defined in =
section=20
         5.4.1. =20

       o Type (OAM-Loopback-Test-Parameters =3D 0x07): Parameters =
related to =20
         loopback test. This is an optional TLV. If this TLV is not =
present=20
         in the request message, the DSLAM SHOULD use locally determined =

         default values for the test parameters. =20
"=20
(NOTE: The last "SHOULD" appears to be inappropriate. If the TLV is =
missing, the DSLAM MUST have some default parameters, or return an =
error)

The "can" above indicates that they're all optional, while clearly the =
application cannot run its course without one or more of these fields. =
Here we have a case where one could have a perfectly compliant =
implementation that ignores all these TLVs...

-Woj.=20













------_=_NextPart_001_01C8AFD7.7E33EDD8
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:p =3D=20
"urn:schemas-microsoft-com:office:powerpoint"><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<TITLE>Nachricht</TITLE>

<META content=3D"MSHTML 6.00.2800.1609" name=3DGENERATOR><!--[if !mso]>
<STYLE>v\:* {
	BEHAVIOR: url(#default#VML)
}
o\:* {
	BEHAVIOR: url(#default#VML)
}
w\:* {
	BEHAVIOR: url(#default#VML)
}
.shape {
	BEHAVIOR: url(#default#VML)
}
</STYLE>
<![endif]-->
<STYLE>@font-face {
	font-family: Tahoma;
}
@font-face {
	font-family: Arial-BoldMT;
}
@page Section1 {size: 595.3pt 841.9pt; margin: 70.85pt 70.85pt 56.7pt =
70.85pt; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline
}
P {
	FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: =
"Times New Roman"; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto
}
SPAN.EmailStyle18 {
	COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal
}
SPAN.EmailStyle20 {
	COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal-reply
}
DIV.Section1 {
	page: Section1
}
OL {
	MARGIN-BOTTOM: 0in
}
UL {
	MARGIN-BOTTOM: 0in
}
</STYLE>
</HEAD>
<BODY lang=3DEN-US vLink=3Dpurple link=3Dblue>
<DIV><FONT face=3DArial><FONT size=3D2><SPAN =
class=3D960161100-07052008>&gt;</SPAN>On=20
the Mandatory Flag aspect, there is&nbsp;one key reason why any protocol =
does;=20
it is&nbsp;to&nbsp;offload the application from doing base data-element=20
checking.</FONT></FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><SPAN class=3D960161100-07052008><FONT face=3DArial size=3D2>How =
and why ? Sounds=20
dangerous to me.</FONT></SPAN></DIV>
<DIV><SPAN class=3D960161100-07052008><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D960161100-07052008><FONT face=3DArial=20
size=3D2>-Sanjay</FONT></SPAN></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> Wojciech Dec =
(wdec)=20
  [mailto:wdec@cisco.com]<BR><B>Sent:</B> Tuesday, May 06, 2008 12:33=20
  PM<BR><B>To:</B> Sanjay Wadhwa; Peter Arberg; DE CNODDER Stefaan; =
Busser, M;=20
  ancp@ietf.org<BR><B>Cc:</B> Haag, T<BR><B>Subject:</B> RE: [ANCP] =
Mandatory=20
  TLVs in draft-ietf-ancp-protocol proposal<BR><BR></FONT></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D687430307-05052008><FONT =
face=3DArial=20
  size=3D2>Sanjay,</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D687430307-05052008><FONT =
face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D687430307-05052008><FONT =
face=3DArial=20
  size=3D2>Inline.... Woj#2</FONT></SPAN></DIV><BR>
  <BLOCKQUOTE dir=3Dltr=20
  style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px =
solid; MARGIN-RIGHT: 0px">
    <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
    <HR tabIndex=3D-1>
    <FONT face=3DTahoma size=3D2><B>From:</B> Sanjay Wadhwa=20
    [mailto:swadhwa@juniper.net] <BR><B>Sent:</B> 30 April 2008=20
    07:40<BR><B>To:</B> Wojciech Dec (wdec); Peter Arberg; DE CNODDER =
Stefaan;=20
    Busser, M; ancp@ietf.org<BR><B>Cc:</B> Haag, T<BR><B>Subject:</B> =
RE: [ANCP]=20
    Mandatory TLVs in draft-ietf-ancp-protocol =
proposal<BR></FONT><BR></DIV>
    <DIV></DIV>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Woj<o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">&nbsp; I =
agree only=20
    on the following:<o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
    <OL style=3D"MARGIN-TOP: 0in" type=3D1>
      <LI class=3DMsoNormal style=3D"COLOR: blue; mso-list: l1 level1 =
lfo1"><FONT=20
      face=3DArial color=3Dblue size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">A TLV might be =
mandatory for=20
      one application or use-case, and optional for another application. =
We do=20
      need to clearly specify in the draft if a TLV is mandatory or =
optional for=20
      a given application (which boils down to specifying this per ANCP =
message=20
      and message type).<o:p></o:p></SPAN></FONT> </LI></OL>
    <DIV class=3DMsoNormal style=3D"COLOR: blue; mso-list: l1 level1 =
lfo1"><FONT=20
    face=3DArial size=3D2></FONT>&nbsp;</DIV>
    <DIV class=3DMsoNormal style=3D"COLOR: blue; mso-list: l1 level1 =
lfo1"><SPAN=20
    class=3D687430307-05052008><FONT face=3DArial color=3D#000000 =
size=3D2>Woj#2&gt;=20
    I&nbsp;interpret this to mean that you've taken on the action to =
clarify the=20
    protocol spec text, and also prepare the table of TLVs indicating =
where each=20
    TLV is mandatory, and where optional. Please let me know if this is =
not=20
    so</FONT></SPAN></DIV>
    <DIV class=3DMsoNormal style=3D"COLOR: blue; mso-list: l1 level1 =
lfo1"><SPAN=20
    class=3D687430307-05052008><FONT face=3DArial =
size=3D2></FONT></SPAN>&nbsp;</DIV>
    <OL style=3D"MARGIN-TOP: 0in" type=3D1>
      <LI class=3DMsoNormal style=3D"COLOR: blue; mso-list: l1 level1 =
lfo1"><FONT=20
      face=3DArial color=3Dblue size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">We should clearly =
specify the=20
      behavior for handling missing mandatory TLVs in received=20
      messages.<o:p></o:p></SPAN></FONT> </LI></OL>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT color=3Dblue><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">To me the =
utility=20
    of flagging a TLV as mandatory or optional via the protocol is at =
best=20
    debatable. &nbsp;If a buggy implementation on the sender incorrectly =
sets a=20
    &#8220;known&#8221; TLV as mandatory (when it is not) or vice-versa, =
do we want the=20
    receiver to infer the handling of this TLV based on what the sender =
tells=20
    it? I don&#8217;t think so. Ideally, we want the receiver and sender =
to have a=20
    common understanding of what is mandatory and what is optional based =
on what=20
    is in the spec, and handle the TLV based on that understanding. As =
Peter=20
    mentions, the spec clearly spells out TLVs that are mandatory and =
optional.=20
    Also, I don&#8217;t see a major advantage of your proposal with =
respect to=20
    debuggability.<FONT color=3D#000000><SPAN=20
    class=3D687430307-05052008>&nbsp;</SPAN></FONT></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT color=3Dblue><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><FONT=20
    color=3D#000000><SPAN=20
    class=3D687430307-05052008></SPAN></FONT></SPAN></FONT>&nbsp;</P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">Typical =
case where=20
    it does make sense for the sender to set some flag in the TLV to =
control the=20
    handling of the TLV on the receiver is for =
&#8220;unrecognized&#8221; TLV=20
    types&#8230;e.g.<o:p></o:p></SPAN></FONT></P>
    <OL style=3D"MARGIN-TOP: 0in" type=3D1>
      <LI class=3DMsoNormal style=3D"COLOR: blue; mso-list: l0 level1 =
lfo2"><FONT=20
      face=3DArial color=3Dblue size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Receiver is an =
intermediate=20
      node, which consumes the message but also needs to forward it =
along to=20
      other nodes. Here the sender can flag the handling of the TLV to =
the=20
      receiver (e.g. discard or forward if the TLV type is not =
recognized by the=20
      receiver). This doesn&#8217;t quite apply to ANCP (messages are =
confined to be=20
      between two peers).<o:p></o:p></SPAN></FONT>&nbsp;<SPAN=20
      class=3D687430307-05052008><FONT face=3DArial color=3D#000000=20
      size=3D2>&nbsp;</FONT></SPAN></LI></OL>
    <DIV class=3DMsoNormal style=3D"COLOR: blue; mso-list: l0 level1 =
lfo2"><SPAN=20
    class=3D687430307-05052008></SPAN>&nbsp;</DIV>
    <DIV class=3DMsoNormal style=3D"COLOR: blue; mso-list: l0 level1 =
lfo2"><SPAN=20
    class=3D687430307-05052008><FONT face=3DArial color=3D#000000 =
size=3D2>Woj#2&gt; It=20
    happens that an ANCP relay has already been proposed in the DSL =
Forum, and=20
    under&nbsp;in some situations it could be a viable entity. By NOT =
designing=20
    such flags now, we're likely making things&nbsp;more=20
    difficult</FONT>&nbsp;<FONT face=3DArial color=3D#000000 size=3D2>in =
the future.=20
    Anyway, since there doesn't seem to be much enthusiasm for =
"Mandatory"=20
    flags, I'll put the subject to rest for now.</FONT></SPAN></DIV>
    <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.25in"><FONT =
face=3DArial color=3Dblue=20
    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
    <OL style=3D"MARGIN-TOP: 0in" type=3D1 start=3D2>
      <LI class=3DMsoNormal style=3D"COLOR: blue; mso-list: l0 level1 =
lfo2"><FONT=20
      face=3DArial color=3Dblue size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">If handling of an =
unrecognized=20
      TLV on the receiver needs to be different for an optional TLV =
versus a=20
      mandatory TLV. Here the receiver doesn&#8217;t understand the TLV =
type, but can=20
      infer the handling based on the flag in the TLV. However, do we =
want the=20
      treatment of &#8220;unrecognized&#8221; TLVs on the receiver to be =
different for=20
      optional and mandatory TLVs (e.g. silently discard an unrecognized =

      optional TLV&#8230;but discard and also send an error back for an =
unrecognized=20
      mandatory TLV). I don&#8217;t think this is necessary. However, if =
we do want to=20
      do this, then may be the flag in the TLV should explicitly =
indicate the=20
      handling for the TLV (e.g. &#8220;silently discard if =
un-recognized&#8221; versus=20
      &#8220;discard and send an error back&#8221;)&#8230;as opposed to =
just flagging these as=20
      &#8220;mandatory&#8221; versus =
&#8220;optional&#8221;.<o:p></o:p></SPAN></FONT>&nbsp;<SPAN=20
      class=3D687430307-05052008><FONT face=3DArial color=3D#000000=20
      size=3D2>&nbsp;</FONT></SPAN></LI></OL>
    <DIV class=3DMsoNormal style=3D"COLOR: blue; mso-list: l0 level1 =
lfo2"><FONT=20
    face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></DIV>
    <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Woj&gt; =
Of course=20
    it is,&nbsp;the whole spec is about this. The problem comes when =
people=20
    start to re-use&nbsp;well known TLVs for different applications, and =
then=20
    trying to make sense of it all &gt;becomes non-trivial. Why do you =
think=20
    both BGP and Diamater, and a number of other protocols have definied =

    "Mandatory" flags? Just for kicks? It's a well known protocol design =
tool,=20
    that &gt;comes handy when re-using same data across multiple=20
    applications.<o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT color=3Dblue><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">We should =
look at=20
    why these protocols are doing this (as opposed to blindly =
following). For a=20
    counter example, please take a look at OSPF traffic engineering =
extensions=20
    (RFC 3630).&nbsp;<FONT color=3D#000000><SPAN=20
    class=3D687430307-05052008>&nbsp;</SPAN></FONT></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT color=3Dblue><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><FONT=20
    color=3D#000000><SPAN=20
    =
class=3D687430307-05052008></SPAN></FONT></SPAN></FONT>&nbsp;</P><FONT=20
    color=3Dblue><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><FONT =
size=3D+0><SPAN=20
    class=3D687430307-05052008>
    <P class=3DMsoNormal><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial"><o:p><SPAN=20
    class=3D985581411-05052008><FONT color=3D#000000>Woj<SPAN=20
    class=3D687430307-05052008>&nbsp;#2&nbsp;</SPAN>&gt;&nbsp;<SPAN=20
    class=3D687430307-05052008>&nbsp;The irony of the above statement in =
view=20
    of&nbsp; the initiators of=20
    ANCP&nbsp;blindly&nbsp;following</SPAN>&nbsp;GSMP<SPAN=20
    class=3D687430307-05052008>&nbsp;is hopefully not lost on =
you.&nbsp;On the=20
    Mandatory Flag aspect, there is&nbsp;one key reason why any protocol =
does;=20
    it is&nbsp;to&nbsp;offload the application from doing base =
data-element=20
    checking. Anyway, we can move =
on.</SPAN></FONT></SPAN></o:p></SPAN></P>
    <P class=3DMsoNormal><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial"><o:p><SPAN=20
    class=3D985581411-05052008><FONT color=3D#000000><SPAN=20
    =
class=3D687430307-05052008></SPAN></FONT></SPAN></o:p></SPAN>&nbsp;</P>
    <P class=3DMsoNormal><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial"><o:p><SPAN=20
    class=3D985581411-05052008><FONT color=3D#000000><SPAN=20
    =
class=3D687430307-05052008>-Woj.</SPAN></FONT></SPAN></o:p></SPAN></P>
    <P class=3DMsoNormal><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial"><o:p><SPAN=20
    class=3D985581411-05052008><FONT color=3D#000000><SPAN=20
    =
class=3D687430307-05052008></SPAN></FONT></SPAN></o:p></SPAN>&nbsp;</P>
    <P class=3DMsoNormal><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial"><o:p><SPAN=20
    class=3D985581411-05052008><FONT color=3D#000000><SPAN=20
    =
class=3D687430307-05052008></SPAN></FONT></SPAN></o:p></SPAN>&nbsp;</P>
    <P class=3DMsoNormal><FONT=20
    =
color=3D#000000>&nbsp;</FONT></SPAN><o:p></o:p></FONT></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Cheers<o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">-Sanjay<o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
    <DIV>
    <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
    face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
    <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
    </SPAN></FONT></DIV>
    <P class=3DMsoNormal><B><FONT face=3DTahoma size=3D2><SPAN=20
    style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
    face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">=20
    ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] <B><SPAN=20
    style=3D"FONT-WEIGHT: bold">On Behalf Of </SPAN></B>Wojciech Dec=20
    (wdec)<BR><B><SPAN style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> =
Tuesday, April=20
    29, 2008 3:03 PM<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">To:</SPAN></B> Peter=20
    Arberg; DE CNODDER Stefaan; Busser, M; ancp@ietf.org<BR><B><SPAN=20
    style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B> Haag, T<BR><B><SPAN=20
    style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> Re: [ANCP] Mandatory =
TLVs in=20
    draft-ietf-ancp-protocol proposal</SPAN></FONT><o:p></o:p></P></DIV>
    <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
    style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN lang=3DDE=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Hi =
Peter,</SPAN></FONT><SPAN=20
    lang=3DDE><o:p></o:p></SPAN></P>
    <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DDE=20
    style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN lang=3DDE=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">continued=20
    inline...</SPAN></FONT><SPAN lang=3DDE><o:p></o:p></SPAN></P>
    <BLOCKQUOTE=20
    style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: 5pt 0in 5pt =
3.75pt; BORDER-LEFT: black 1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none">
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DDE=20
      style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
      <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
      face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
      <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
      </SPAN></FONT></DIV>
      <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><B><FONT =
face=3DTahoma=20
      size=3D2><SPAN=20
      style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
      face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Tahoma">=20
      ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] <B><SPAN=20
      style=3D"FONT-WEIGHT: bold">On Behalf Of </SPAN></B>Peter =
Arberg<BR><B><SPAN=20
      style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> 29 April 2008 =
20:39<BR><B><SPAN=20
      style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Wojciech Dec (wdec); DE =
CNODDER=20
      Stefaan; Busser, M; ancp@ietf.org<BR><B><SPAN=20
      style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B> Haag, T<BR><B><SPAN=20
      style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> Re: [ANCP] =
Mandatory TLVs in=20
      draft-ietf-ancp-protocol proposal</SPAN></FONT><o:p></o:p></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
      style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">Hi=20
      Woj,</SPAN></FONT><SPAN lang=3DDE><o:p></o:p></SPAN></P>
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DDE=20
      style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
      style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">please =
see inline=20
      in your answers</SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P>
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DDE=20
      style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
      <BLOCKQUOTE=20
      style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; =
BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: =
5pt 0in 5pt 3.75pt; BORDER-LEFT: blue 1.5pt solid; PADDING-TOP: 0in; =
BORDER-BOTTOM: medium none">
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
        <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
        face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: =
12pt">
        <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
        </SPAN></FONT></DIV>
        <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><B><FONT =
face=3DTahoma=20
        size=3D2><SPAN=20
        style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
        face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Tahoma">=20
        Wojciech Dec (wdec) [mailto:wdec@cisco.com] <BR><B><SPAN=20
        style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> 29. april 2008=20
        11:07<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> =
Peter Arberg;=20
        DE CNODDER Stefaan; Busser, M; ancp@ietf.org<BR><B><SPAN=20
        style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B> Haag, T<BR><B><SPAN=20
        style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: Re: [ANCP] =
Mandatory=20
        TLVs in draft-ietf-ancp-protocol =
proposal</SPAN></FONT><o:p></o:p></P>
        <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN lang=3DDE =

        style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Hi =
Peter,</SPAN></FONT><SPAN=20
        lang=3DDE><o:p></o:p></SPAN></P>
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
        style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
        <BLOCKQUOTE=20
        style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; =
BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: =
5pt 0in 5pt 3.75pt; BORDER-LEFT: black 1.5pt solid; PADDING-TOP: 0in; =
BORDER-BOTTOM: medium none">
          <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
          <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
          face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: =
12pt">
          <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
          </SPAN></FONT></DIV>
          <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><B><FONT =
face=3DTahoma=20
          size=3D2><SPAN=20
          style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
          face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Tahoma">=20
          Peter Arberg [mailto:parberg@redback.com] <BR><B><SPAN=20
          style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> 29 April 2008=20
          19:34<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> =
Wojciech=20
          Dec (wdec); DE CNODDER Stefaan; Busser, M; =
ancp@ietf.org<BR><B><SPAN=20
          style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B> Haag, T<BR><B><SPAN =

          style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: Re: [ANCP] =
Mandatory=20
          TLVs in draft-ietf-ancp-protocol =
proposal</SPAN></FONT><o:p></o:p></P>
          <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">Hi=20
          Woj,</SPAN></FONT><SPAN lang=3DDE><o:p></o:p></SPAN></P>
          <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
          <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">I =
agree with=20
          Michael and Stefan on this issue, I do not see a need to =
change the=20
          existing</SPAN></FONT><SPAN lang=3DDE><o:p></o:p></SPAN></P>
          <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">implementation=20
          with a mandatory/optional flag.</SPAN></FONT><FONT =
face=3DArial=20
          color=3Dblack size=3D2><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><SPAN=20
          lang=3DDE><o:p></o:p></SPAN></P>
          <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
          <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Woj&gt;=20
          Please indicate where in my proposal did you see anything=20
          about</SPAN></FONT><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><FONT=20
          face=3DArial color=3Dblack size=3D2><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">changing=20
          existing implementaions?&nbsp;</SPAN></FONT><FONT face=3DArial =

          color=3Dblue size=3D2><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><SPAN=20
          lang=3DDE><o:p></o:p></SPAN></P>
          <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></BLOCKQUOTE></BLOCKQUOTE>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
      style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">PAR&gt;&nbsp;&nbsp;I=20
      might have misunderstood your email, but I read it as if you =
suggest a=20
      high bit</SPAN></FONT><SPAN lang=3DDE><o:p></o:p></SPAN></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
      style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">value =
in existing=20
      TLV's to be interpreted as a mandatory flag.</SPAN></FONT><FONT =
face=3DArial=20
      color=3Dblack size=3D2><SPAN lang=3DDE=20
      style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><SPAN=20
      lang=3DDE><o:p></o:p></SPAN></P>
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DDE=20
      style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN lang=3DDE=20
      style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Woj#2&gt; Yes, I=20
      suggested (in proposal 2) that *if* the WG found there to be a =
common set=20
      of TLVs currently in use, then the high-order bit set to "0" (ie =
as today)=20
      could be interpreted as "mandatory", and the rest of the TLV's =
redefined=20
      with a high order "1". To extsing implementations, the "new" TLVs =
would=20
      just look like a different TLV#, while&nbsp;anyone wishing to =
implement=20
      the more robust error cheking logic based on this bit,&nbsp;would =
be free=20
      to do so.</SPAN></FONT><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
      style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><SPAN=20
      lang=3DDE><o:p></o:p></SPAN></P>
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DDE=20
      style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
      style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">If you =
are simply=20
      talking about new capability type definitions, then why do you not =
bring=20
      up</SPAN></FONT><SPAN lang=3DDE><o:p></o:p></SPAN></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
      style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">the =
additional=20
      flag in a new internet-draft defining what capability type you =
have in=20
      mind ?</SPAN></FONT><FONT face=3DArial color=3Dblack =
size=3D2><SPAN lang=3DDE=20
      style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><SPAN=20
      lang=3DDE><o:p></o:p></SPAN></P>
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DDE=20
      style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN lang=3DDE=20
      style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Woj#2&gt; No, a=20
      new capability was not intended, but could also be=20
      considered.</SPAN></FONT><SPAN lang=3DDE><o:p></o:p></SPAN></P>
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DDE=20
      style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
      <BLOCKQUOTE=20
      style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; =
BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: =
5pt 0in 5pt 3.75pt; BORDER-LEFT: blue 1.5pt solid; PADDING-TOP: 0in; =
BORDER-BOTTOM: medium none">
        <BLOCKQUOTE=20
        style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; =
BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: =
5pt 0in 5pt 3.75pt; BORDER-LEFT: black 1.5pt solid; PADDING-TOP: 0in; =
BORDER-BOTTOM: medium none">
          <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
          <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">I =
think I=20
          understand your arguments, but I do not agree with them. I =
think most=20
          places in</SPAN></FONT><SPAN lang=3DDE><o:p></o:p></SPAN></P>
          <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">the =
draft it=20
          is clear what is defined as mandatory and =
optional.</SPAN></FONT><FONT=20
          face=3DArial color=3Dblack size=3D2><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><SPAN=20
          lang=3DDE><o:p></o:p></SPAN></P>
          <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
          <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">I =
agree on=20
          the point we need to go through the draft and make =
clarifications to=20
          what TLV's</SPAN></FONT><SPAN lang=3DDE><o:p></o:p></SPAN></P>
          <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">in =
what=20
          capability types are mandatory and optional, and make more =
description=20
          what should</SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P>
          <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">happen if=20
          mandatory TLVs are not included.</SPAN></FONT><FONT =
face=3DArial=20
          color=3Dblack size=3D2><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><SPAN=20
          lang=3DDE><o:p></o:p></SPAN></P>
          <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
          <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Woj&gt;=20
          Exactly.</SPAN></FONT><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><SPAN=20
          lang=3DDE><o:p></o:p></SPAN></P>
          <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
          <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">I =
think the=20
          DSLF TR-101 document has a good example of such a description =
in it's=20
          </SPAN></FONT><SPAN lang=3DDE><o:p></o:p></SPAN></P>
          <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">"</SPAN></FONT><FONT=20
          face=3DArial-BoldMT color=3Dblue size=3D2><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial-BoldMT">Table=20
          3 - Access loop characteristics sub-options", and I think if =
we do the=20
          same for each</SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P>
          <P class=3DMsoNormal><FONT face=3DArial-BoldMT color=3Dblue =
size=3D2><SPAN=20
          lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial-BoldMT">capability=20
          types TLV's in the ANCP draft it will be a good=20
          help.</SPAN></FONT><FONT face=3DArial-BoldMT size=3D2><SPAN =
lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial-BoldMT"><o:p></o:p></SPAN></FONT></P>
          <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
          <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Woj&gt;</SPAN></FONT><FONT=20
          face=3DArial color=3Dblue size=3D2><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">=20
          </SPAN></FONT><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Indeed,=20
          pre-ceeded by some rationalization. The appears to be no =
reason for=20
          some of the DSLF "mandatory" TLVs.</SPAN></FONT><FONT =
face=3DArial=20
          color=3Dblue size=3D2><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><SPAN=20
          lang=3DDE><o:p></o:p></SPAN></P>
          <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></BLOCKQUOTE></BLOCKQUOTE>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
      style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">PAR&gt; =
I do not=20
      see a problem with re-visit in the draft if a TLV should be =
optional or=20
      mandatory, so if</SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
      style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">that is =
the=20
      intend, then I'm all for an email discussion on a TLV by TLV basis =
if we=20
      think it is a </SPAN></FONT><SPAN lang=3DDE><o:p></o:p></SPAN></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
      style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">manfdatory or=20
      optional information inside the specific capability=20
      type.</SPAN></FONT><FONT face=3DArial color=3Dblack size=3D2><SPAN =
lang=3DDE=20
      style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><SPAN=20
      lang=3DDE><o:p></o:p></SPAN></P>
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DDE=20
      style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN lang=3DDE=20
      style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Woj#2&gt; Great,=20
      because any change to the mandated set&nbsp;*will* affect existing =

      implementation</SPAN></FONT><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
      lang=3DDE=20
      style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><FONT=20
      face=3DArial color=3Dblack size=3D2><SPAN lang=3DDE=20
      style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">.</SPAN></FONT><SPAN=20
      lang=3DDE><o:p></o:p></SPAN></P>
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DDE=20
      style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
      <BLOCKQUOTE=20
      style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; =
BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: =
5pt 0in 5pt 3.75pt; BORDER-LEFT: blue 1.5pt solid; PADDING-TOP: 0in; =
BORDER-BOTTOM: medium none">
        <BLOCKQUOTE=20
        style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; =
BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: =
5pt 0in 5pt 3.75pt; BORDER-LEFT: black 1.5pt solid; PADDING-TOP: 0in; =
BORDER-BOTTOM: medium none">
          <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
          <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
          <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">I =
do not=20
          agree with your point that it is not listed if "rate" is =
mandatory or=20
          optional, it is clearly</SPAN></FONT><SPAN=20
          lang=3DDE><o:p></o:p></SPAN></P>
          <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">listed as a=20
          mandatory TLV, and as such it should be included in the port =
up=20
          message, I really</SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P>
          <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">do =
not=20
          understand what confusion you have with =
this.</SPAN></FONT><FONT=20
          face=3DArial color=3Dblack size=3D2><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><SPAN=20
          lang=3DDE><o:p></o:p></SPAN></P>
          <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
          <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Woj&gt; The=20
          text states:&nbsp;&nbsp;</SPAN></FONT><FONT face=3DArial =
color=3Dblue=20
          size=3D2><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><SPAN=20
          lang=3DDE><o:p></o:p></SPAN></P>
          <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
          <P class=3DMsoNormal><FONT face=3D"Courier New" color=3Dblack =
size=3D2><SPAN=20
          lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: 'Courier =
New'">5.=20
          Type (DSL Line Attributes =3D 0x04): </SPAN></FONT><FONT =
face=3DArial=20
          color=3Dblue size=3D1><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 7.5pt; COLOR: blue; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></P>
          <P><FONT face=3D"Courier New" color=3Dblack size=3D2><SPAN =
lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: 'Courier =
New'">Length=20
          : variable (up to 1024 bytes) </SPAN></FONT><FONT =
color=3Dblue><SPAN=20
          lang=3DDE style=3D"COLOR: blue"><o:p></o:p></SPAN></FONT></P>
          <P><FONT face=3D"Courier New" color=3Dblack size=3D2><SPAN =
lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: 'Courier =
New'">Value=20
          : This consists of one or more Sub-TLVs corresponding to DSL=20
          </SPAN></FONT><FONT color=3Dblue><SPAN lang=3DDE=20
          style=3D"COLOR: blue"><o:p></o:p></SPAN></FONT></P>
          <P><FONT face=3D"Courier New" color=3Dblack size=3D2><SPAN =
lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: 'Courier =
New'">line=20
          attributes. No sub-TLVs other than the "DSL type" and "DSL=20
          </SPAN></FONT><FONT color=3Dblue><SPAN lang=3DDE=20
          style=3D"COLOR: blue"><o:p></o:p></SPAN></FONT></P>
          <P><FONT face=3D"Courier New" color=3Dblack size=3D2><SPAN =
lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: 'Courier =
New'">line=20
          state" SHOULD be included in a PORT DOWN message. =
</SPAN></FONT><FONT=20
          color=3Dblue><SPAN lang=3DDE=20
          style=3D"COLOR: blue"><o:p></o:p></SPAN></FONT></P>
          <P><FONT face=3D"Courier New" color=3Dblack size=3D2><SPAN =
lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: 'Courier =
New'">The=20
          general format of the sub-TLVs is identical to the general TLV =

          </SPAN></FONT><FONT color=3Dblue><SPAN lang=3DDE=20
          style=3D"COLOR: blue"><o:p></o:p></SPAN></FONT></P>
          <P><FONT face=3D"Courier New" color=3Dblack size=3D2><SPAN =
lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: 'Courier =
New'">format.=20
          The value field in each sub-TLV is padded to a 4-octet=20
          </SPAN></FONT><FONT color=3Dblue><SPAN lang=3DDE=20
          style=3D"COLOR: blue"><o:p></o:p></SPAN></FONT></P>
          <P><FONT face=3D"Courier New" color=3Dblack size=3D2><SPAN =
lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: 'Courier =
New'">alignment.=20
          The Length field in each sub-TLV contains the actual=20
          </SPAN></FONT><FONT color=3Dblue><SPAN lang=3DDE=20
          style=3D"COLOR: blue"><o:p></o:p></SPAN></FONT></P>
          <P><FONT face=3D"Courier New" color=3Dblack size=3D2><SPAN =
lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: 'Courier =
New'">number=20
          of bytes in the TLV (not including the padding if present).=20
          </SPAN></FONT><FONT color=3Dblue><SPAN lang=3DDE=20
          style=3D"COLOR: blue"><o:p></o:p></SPAN></FONT></P>
          <P><FONT face=3D"Courier New" color=3Dblack size=3D2><SPAN =
lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: 'Courier =
New'">Current=20
          defined sub-TLV types are start from 0x81.</SPAN></FONT><FONT=20
          color=3Dblack><SPAN lang=3DDE=20
          style=3D"COLOR: black">&nbsp;</SPAN></FONT><FONT face=3DArial =
color=3Dblack=20
          size=3D2><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><FONT=20
          color=3Dblue><SPAN lang=3DDE=20
          style=3D"COLOR: blue"><o:p></o:p></SPAN></FONT></P>
          <P><FONT face=3DArial color=3Dblack size=3D2><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Maybe you=20
          can point me to where exatly it is stated clearly as being =
mandatory,=20
          or otherwise explain why you "not agree"?</SPAN></FONT><FONT=20
          color=3Dblack><SPAN lang=3DDE=20
          style=3D"COLOR: black">&nbsp;</SPAN></FONT><FONT face=3DArial =
color=3Dblue=20
          size=3D2><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><FONT=20
          color=3Dblue><SPAN lang=3DDE=20
          style=3D"COLOR: blue"><o:p></o:p></SPAN></FONT></P>
          <P><FONT face=3D"Times New Roman" color=3Dblue size=3D3><SPAN =
lang=3DDE=20
          style=3D"FONT-SIZE: 12pt; COLOR: =
blue">&nbsp;<o:p></o:p></SPAN></FONT></P></BLOCKQUOTE></BLOCKQUOTE>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN lang=3DDE=20
      style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">PAR&gt; I think=20
      you forgot to read the most important part where the actual TLV is =

      defined.&nbsp;</SPAN></FONT><FONT face=3DArial color=3Dblue =
size=3D1><SPAN=20
      lang=3DDE=20
      style=3D"FONT-SIZE: 7.5pt; COLOR: blue; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D1><SPAN lang=3DDE=20
      style=3D"FONT-SIZE: 7.5pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;<o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN lang=3DDE=20
      style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Woj#2&gt;&nbsp;I=20
      didn't. This part talks about the sub-TLV, not the main TLV 0x04. =
Do you=20
      see my point now?</SPAN></FONT><FONT face=3DArial color=3Dblue =
size=3D1><SPAN=20
      lang=3DDE=20
      style=3D"FONT-SIZE: 7.5pt; COLOR: blue; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D1><SPAN lang=3DDE=20
      style=3D"FONT-SIZE: 7.5pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;<o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D1><SPAN lang=3DDE=20
      style=3D"FONT-SIZE: 7.5pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;<o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN lang=3DDE=20
      style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Type=20
      (Actual-Net-Data-Upstream =3D 0x81): Actual upstream net =
data&nbsp;rate on a=20
      DSL line. </SPAN></FONT><FONT face=3DArial color=3Dblue =
size=3D1><SPAN lang=3DDE=20
      style=3D"FONT-SIZE: 7.5pt; COLOR: blue; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN lang=3DDE=20
      style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">This =
is a=20
      mandatory TLV.&nbsp; </SPAN></FONT><FONT face=3DArial color=3Dblue =

      size=3D1><SPAN lang=3DDE=20
      style=3D"FONT-SIZE: 7.5pt; COLOR: blue; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></P>
      <DIV>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D1><SPAN lang=3DDE=20
      style=3D"FONT-SIZE: 7.5pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN lang=3DDE=20
      style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Length&nbsp;=20
      :&nbsp; (4 bytes) </SPAN></FONT><FONT face=3DArial color=3Dblue =
size=3D1><SPAN=20
      lang=3DDE=20
      style=3D"FONT-SIZE: 7.5pt; COLOR: blue; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></P>
      <DIV>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN lang=3DDE=20
      style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Value&nbsp;&nbsp;=20
      : (Rate in Kb/sec) </SPAN></FONT><FONT face=3DArial color=3Dblue =
size=3D1><SPAN=20
      lang=3DDE=20
      style=3D"FONT-SIZE: 7.5pt; COLOR: blue; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></P></DIV>
      <DIV>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D1><SPAN lang=3DDE=20
      style=3D"FONT-SIZE: 7.5pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN lang=3DDE=20
      style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Type=20
      (Actual-Net-Data-Rate-Downstream =3D 0x82) : Actual downstream net =
data rate=20
      on a DSL line. </SPAN></FONT><FONT face=3DArial color=3Dblue =
size=3D1><SPAN=20
      lang=3DDE=20
      style=3D"FONT-SIZE: 7.5pt; COLOR: blue; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN lang=3DDE=20
      style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">This =
is a=20
      mandatory TLV. </SPAN></FONT><FONT face=3DArial color=3Dblue =
size=3D1><SPAN=20
      lang=3DDE=20
      style=3D"FONT-SIZE: 7.5pt; COLOR: blue; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></P>
      <DIV>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D1><SPAN lang=3DDE=20
      style=3D"FONT-SIZE: 7.5pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN lang=3DDE=20
      style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Length =
:&nbsp;=20
      (4 bytes) </SPAN></FONT><FONT face=3DArial color=3Dblue =
size=3D1><SPAN lang=3DDE=20
      style=3D"FONT-SIZE: 7.5pt; COLOR: blue; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></P>
      <DIV>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN lang=3DDE=20
      style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Value&nbsp;=20
      :&nbsp; (Rate in Kb/sec) </SPAN></FONT><FONT face=3DArial =
color=3Dblue=20
      size=3D1><SPAN lang=3DDE=20
      style=3D"FONT-SIZE: 7.5pt; COLOR: blue; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></P></DIV>
      <DIV>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D1><SPAN lang=3DDE=20
      style=3D"FONT-SIZE: 7.5pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
      <BLOCKQUOTE=20
      style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; =
BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: =
5pt 0in 5pt 3.75pt; BORDER-LEFT: blue 1.5pt solid; PADDING-TOP: 0in; =
BORDER-BOTTOM: medium none">
        <BLOCKQUOTE=20
        style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; =
BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: =
5pt 0in 5pt 3.75pt; BORDER-LEFT: black 1.5pt solid; PADDING-TOP: 0in; =
BORDER-BOTTOM: medium none">
          <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
          <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">The =
fact you=20
          say "Port UP" and "OAM" is best considered as legacy =
applications, I=20
          have some</SPAN></FONT><SPAN lang=3DDE><o:p></o:p></SPAN></P>
          <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">trouble with=20
          this as well, since ANCP running in production networks use =
them, and=20
          as such</SPAN></FONT><SPAN lang=3DDE><o:p></o:p></SPAN></P>
          <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">it =
is a=20
          central part of the ANCP specifications we need to finish as =
soon as=20
          possible.</SPAN></FONT><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
          lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><SPAN=20
          lang=3DDE><o:p></o:p></SPAN></P>
          <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
          <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Woj&gt; I=20
          should have said legacy applications from a protocol messaging =

          perspective, not usage, nor support. It's quite clear that =
GSMP=20
          derived messaging has baggage that is un called for in new=20
          applications.</SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P>
          <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
          <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">I =
think=20
          Stefaan's example is very valid, that we do not need to make =
mandatory=20
          requirements to </SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P>
          <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">what=20
          receivers of ANCP information use such info. for.&nbsp; I =
don't think=20
          we should try and make the</SPAN></FONT><SPAN=20
          lang=3DDE><o:p></o:p></SPAN></P>
          <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">ANCP=20
          specifications "mandatory" for box behavior, I think it is =
much more=20
          important for the </SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P>
          <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">working group=20
          to make the protocol specifications easy to understand and get =
the=20
          first documentation</SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P>
          <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">finish and=20
          published, so the protocol can be used for different sets of=20
          applications, and make sure</SPAN></FONT><SPAN=20
          lang=3DDE><o:p></o:p></SPAN></P>
          <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">new =

          applications can be added later.</SPAN></FONT><FONT =
face=3DArial=20
          color=3Dblack size=3D2><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><SPAN=20
          lang=3DDE><o:p></o:p></SPAN></P>
          <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
          <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Woj&gt;=20
          Indeed the aim of the WG to define a protocol that is =
relatively=20
          simple and easy to understand, not just to implementers but =
also to=20
          people using it, and across vendors. Currently, having anyone=20
          operating the device be familiar in what cases a TLV is =
mandatory and=20
          in what optional requires a thorough understanding of the =
spec, across=20
          applications. This is not easy, but I'll conceede that for the =

          applications implemented so far we could live with it.=20
          </SPAN></FONT><SPAN lang=3DDE><o:p></o:p></SPAN></P>
          <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
          <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">I =
do think=20
          that by documenting if a TLV is mandatory or optional inside a =

          specific capability type,</SPAN></FONT><SPAN=20
          lang=3DDE><o:p></o:p></SPAN></P>
          <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">it =
is easy to=20
          understand what must be sent to support the defined=20
          application/capability type.</SPAN></FONT><FONT face=3DArial =
color=3Dblack=20
          size=3D2><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><SPAN=20
          lang=3DDE><o:p></o:p></SPAN></P>
          <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
          <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Woj&gt; Of=20
          course it is,&nbsp;the whole spec is about this. The problem =
comes=20
          when people start to re-use&nbsp;well known TLVs for different =

          applications, and then trying to make sense of it all becomes=20
          non-trivial. Why do you think both BGP and Diamater, and a =
number of=20
          other protocols have definied "Mandatory" flags? Just for =
kicks? It's=20
          a well known protocol design tool, that comes handy when =
re-using same=20
          data across multiple applications.</SPAN></FONT><FONT =
face=3DArial=20
          color=3Dblue size=3D2><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><SPAN=20
          lang=3DDE><o:p></o:p></SPAN></P>
          <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></BLOCKQUOTE></BLOCKQUOTE>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN lang=3DDE=20
      style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">PAR&gt; I might=20
      be wrong, but I think I can find as many or more protocol examples =
who do=20
      not include</SPAN></FONT><SPAN lang=3DDE><o:p></o:p></SPAN></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN lang=3DDE=20
      style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">a=20
      mandatory/optional flag, so examples can always be found which =
will=20
      support the point you are trying</SPAN></FONT><SPAN=20
      lang=3DDE><o:p></o:p></SPAN></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN lang=3DDE=20
      style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">to=20
      make.</SPAN></FONT><SPAN lang=3DDE><o:p></o:p></SPAN></P>
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DDE=20
      style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN lang=3DDE=20
      style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">I do =
not see a=20
      problem with a new internet-draft which defines new =
capability-types and=20
      where a TLV</SPAN></FONT><SPAN lang=3DDE><o:p></o:p></SPAN></P>
      <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN lang=3DDE=20
      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">mandatory flag is =
included, I=20
      do see a problem if the intend is to try and&nbsp;adjust what =
already=20
      exist.&nbsp;&nbsp;</SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P>
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DDE=20
      style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN lang=3DDE=20
      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Woj#2&gt; Ok, so if =
adjusting=20
      is only scoped to what doesn't exist, as my proposal laid=20
      out&nbsp;conditionally, you're fine.</SPAN></FONT><SPAN=20
      lang=3DDE><o:p></o:p></SPAN></P>
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DDE=20
      style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
      <BLOCKQUOTE=20
      style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; =
BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: =
5pt 0in 5pt 3.75pt; BORDER-LEFT: blue 1.5pt solid; PADDING-TOP: 0in; =
BORDER-BOTTOM: medium none">
        <BLOCKQUOTE=20
        style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; =
BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: =
5pt 0in 5pt 3.75pt; BORDER-LEFT: black 1.5pt solid; PADDING-TOP: 0in; =
BORDER-BOTTOM: medium none">
          <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
          <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
          <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Then if=20
          anybody want to include new capability types or sub-TLVs later =
to=20
          address specific applications,</SPAN></FONT><SPAN=20
          lang=3DDE><o:p></o:p></SPAN></P>
          <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">then I think=20
          changes can be discussed at that time instead of trying to =
change=20
          existing protocol</SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P>
          <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">implementations.</SPAN></FONT><FONT=20
          face=3DArial color=3Dblack size=3D2><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><SPAN=20
          lang=3DDE><o:p></o:p></SPAN></P>
          <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
          <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Woj&gt;=20
          Again I ask, where in the proposal did you see=20
          *anything*&nbsp;requiring a change to an existing =
implementation.=20
          Please be specific.</SPAN></FONT><FONT face=3DArial =
color=3Dblue=20
          size=3D2><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><FONT=20
          face=3DArial color=3Dblack size=3D2><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">I =
see that=20
          your main objection is on this issue, which means that you =
accept=20
          proposal 1 (have such a flag for new =
TLVs/apps).</SPAN></FONT><SPAN=20
          lang=3DDE><o:p></o:p></SPAN></P>
          <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">It would also be =
useful if=20
          you indicated whether the list of TLVs provided below is what =
you'd=20
          expect to be the minimum mandatory set.<FONT =
color=3Dblue><SPAN=20
          style=3D"COLOR: blue">&nbsp;</SPAN></FONT></SPAN></FONT><SPAN=20
          lang=3DDE><o:p></o:p></SPAN></P>
          <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></BLOCKQUOTE></BLOCKQUOTE>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
      style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">PAR&gt; =
at the=20
      moment I read the draft as having&nbsp;defined the TLVs mandatory =
as you=20
      describe, except</SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
      style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">I =
also&nbsp;read=20
      it as the dsl-type =3D 0x91 must be part of the port down. If this =
is needed=20
      or not is a different</SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
      style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">discussion.</SPAN></FONT><SPAN=20
      lang=3DDE><o:p></o:p></SPAN></P>
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DDE=20
      style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DDE=20
      style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
      style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Woj#2&gt; Ok.=20
      Thanks. But please do come back to me if you see that the proposal =
impacts=20
      an exiting implementation. I conclude that there is no problem =
with doing=20
      changes to stuff that isn't currently used.</SPAN></FONT><SPAN=20
      lang=3DDE><o:p></o:p></SPAN></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
      style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Woj.</SPAN></FONT><SPAN=20
      lang=3DDE><o:p></o:p></SPAN></P>
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =
lang=3DDE=20
      style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
      style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">cheers,</SPAN></FONT><SPAN=20
      lang=3DDE><o:p></o:p></SPAN></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
      style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Peter&nbsp;</SPAN></FONT><SPAN=20
      lang=3DDE><o:p></o:p></SPAN></P>
      <BLOCKQUOTE=20
      style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; =
BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: =
5pt 0in 5pt 3.75pt; BORDER-LEFT: blue 1.5pt solid; PADDING-TOP: 0in; =
BORDER-BOTTOM: medium none">
        <BLOCKQUOTE=20
        style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; =
BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: =
5pt 0in 5pt 3.75pt; BORDER-LEFT: black 1.5pt solid; PADDING-TOP: 0in; =
BORDER-BOTTOM: medium none">
          <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
          <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Cheers,</SPAN></FONT><SPAN=20
          lang=3DDE><o:p></o:p></SPAN></P>
          <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Woj.</SPAN></FONT><SPAN=20
          lang=3DDE><o:p></o:p></SPAN></P>
          <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
          <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">cheers,</SPAN></FONT><SPAN=20
          lang=3DDE><o:p></o:p></SPAN></P>
          <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Peter</SPAN></FONT><SPAN=20
          lang=3DDE><o:p></o:p></SPAN></P>
          <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
          <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
          <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
          style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
          <BLOCKQUOTE=20
          style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; =
BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: =
5pt 0in 5pt 3.75pt; BORDER-LEFT: blue 1.5pt solid; PADDING-TOP: 0in; =
BORDER-BOTTOM: medium none">
            <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
            style=3D"FONT-SIZE: =
12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
            <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
            face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: =
12pt">
            <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
            </SPAN></FONT></DIV>
            <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><B><FONT =
face=3DTahoma=20
            size=3D2><SPAN=20
            style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
            face=3DTahoma size=3D2><SPAN=20
            style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma"> =
ancp-bounces@ietf.org=20
            [mailto:ancp-bounces@ietf.org] <B><SPAN =
style=3D"FONT-WEIGHT: bold">On=20
            Behalf Of </SPAN></B>Wojciech Dec (wdec)<BR><B><SPAN=20
            style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> 29. april 2008=20
            02:28<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> =
DE=20
            CNODDER Stefaan; Busser, M; ancp@ietf.org<BR><B><SPAN=20
            style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B> Haag, =
T<BR><B><SPAN=20
            style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> Re: [ANCP] =
Mandatory=20
            TLVs in draft-ietf-ancp-protocol=20
            proposal</SPAN></FONT><o:p></o:p></P>
            <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
            style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Stefaan,</SPAN></FONT><SPAN=20
            lang=3DDE><o:p></o:p></SPAN></P>
            <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
            style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
            <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
            style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">a number of=20
            points:</SPAN></FONT><SPAN lang=3DDE><o:p></o:p></SPAN></P>
            <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
            style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">1. There =
currently is to=20
            my knowledge&nbsp;no implementation of ANCP there that =
doesn't send=20
            the DSL Line attributes info by default in Port-UP messages? =
The=20
            support of HS on the NAS is an orthogonal =
issue.</SPAN></FONT><SPAN=20
            lang=3DDE><o:p></o:p></SPAN></P>
            <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
            style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">2. The current =
ancp=20
            protocol draft (02) doesn't say whether the rate info is =
optional or=20
            mandatory, it only states that the sub-TLVs are mandatory. =
Based on=20
            this, an implementer can be&nbsp;justified to expect =
port-ups to=20
            *always* have the rate-info tlv (ie treat them as =
mandatory).=20
            Equally, she's justified&nbsp;in considering this&nbsp; as=20
            optional.</SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P>
            <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
            style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">3.<EM><I><FONT =

            face=3DArial><SPAN=20
            style=3D"FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT></I></EM>The port-up=20
            and OAM are&nbsp;best considered as legacy applications for =
ANCP.=20
            The re-use of any of the GSMP defined fields is already out =
of the=20
            question due to constrains put in place by the existing =
use-case=20
            messaging. Needless to say, this wasn't as thoroughly =
designed as it=20
            should have been, and with the OAM and port-up apps being=20
            coupled.</SPAN></FONT><SPAN lang=3DDE><o:p></o:p></SPAN></P>
            <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
            style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">4. It's up to =
the=20
            application to define what TLVs are mandatory and which =
aren't, as=20
            you also state.&nbsp;The AN does not need to know what the =
NAS will=20
            do with the info, BUT it needs to send the right TLVs for =
the=20
            application (eg if we had a hypothetical&nbsp;AN that only =
sends=20
            Port-up's with line-id, it would be next to useless for the =
dynamic=20
            shaping application).</SPAN></FONT><SPAN=20
            lang=3DDE><o:p></o:p></SPAN></P>
            <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
            style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
            <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
            style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">With all this =
in mind=20
            it's useful to re-read what I proposed originally below =
regarding=20
            the mandatory flag:&nbsp;1. "<EM><I><FONT face=3DArial><SPAN =

            style=3D"FONT-FAMILY: Arial">have this TLV Flag be defined =
only for=20
            new applications" </SPAN></FONT></I></EM>and 2. The notion =
of the=20
            mandatory flag applying to existing TLVs&nbsp; being =
"<EM><I><FONT=20
            face=3DArial><SPAN style=3D"FONT-FAMILY: Arial">conditional =
on deriving=20
            a suitable "commonly used" TLV set." =
</SPAN></FONT></I></EM>The=20
            latter point would ensure that existing implementations do =
not need=20
            to change, but future ones can take advantage of the extra=20
            robustness.</SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P>
            <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
            style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
            <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
            style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Hence, can the =
WG derive=20
            a set of commonly used, i.e. always used, TLVs for existing=20
            implementations?</SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P>
            <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
            style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">The list I =
came up is as=20
            follows (making them pretty much mandatory TLVs if it agrees =
with=20
            the views of others);</SPAN></FONT><SPAN=20
            lang=3DDE><o:p></o:p></SPAN></P>
            <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
            style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
            <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
            style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Port-up =
message=20
            (0x80);</SPAN></FONT><SPAN lang=3DDE><o:p></o:p></SPAN></P>
            <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
            style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;=20
            Extension-TLV (dsl tech type)</SPAN></FONT><SPAN=20
            lang=3DDE><o:p></o:p></SPAN></P>
            <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
            style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp;=20
            Access-Loop-circuit-id (0x01)</SPAN></FONT><SPAN=20
            lang=3DDE><o:p></o:p></SPAN></P>
            <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
            style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;&nbsp;&nbsp; DSL=20
            Line Attribute (0x04) with the following sub=20
            TLVs;</SPAN></FONT><SPAN lang=3DDE><o:p></o:p></SPAN></P>
            <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
            style=3D"FONT-SIZE: 12pt">&nbsp;</SPAN></FONT><FONT =
size=3D2><SPAN=20
            lang=3DDE style=3D"FONT-SIZE: =
10pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
            DSL-Type =3D 0x91; Actual-Net-Data-Upstream =3D 0x81;=20
            Actual-Net-Data-Rate-Downstream =3D 0x82</SPAN></FONT><SPAN=20
            lang=3DDE><o:p></o:p></SPAN></P>
            <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
            style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
            <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
            style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Port-down =
message=20
            (0x81);</SPAN></FONT><SPAN lang=3DDE><o:p></o:p></SPAN></P>
            <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
            style=3D"FONT-SIZE: 12pt">&nbsp;&nbsp;&nbsp; =
</SPAN></FONT><FONT=20
            face=3DArial size=3D2><SPAN lang=3DDE=20
            style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Extension&nbsp; TLV (dsl=20
            tech type)</SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P>
            <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
            style=3D"FONT-SIZE: 12pt">&nbsp;&nbsp;&nbsp; =
</SPAN></FONT><FONT=20
            face=3DArial size=3D2><SPAN lang=3DDE=20
            style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Access-Loop-circuit-id=20
            (0x01)</SPAN></FONT><SPAN lang=3DDE><o:p></o:p></SPAN></P>
            <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
            style=3D"FONT-SIZE: 12pt">&nbsp;&nbsp;&nbsp; =
</SPAN></FONT><FONT=20
            face=3DArial size=3D2><SPAN lang=3DDE=20
            style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">DSL Line =
Attribute=20
            (0x04) with the following sub TLVs;</SPAN></FONT><SPAN=20
            lang=3DDE><o:p></o:p></SPAN></P>
            <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
            style=3D"FONT-SIZE: =
12pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</SPAN></FONT><FONT=20
            size=3D2><SPAN lang=3DDE style=3D"FONT-SIZE: 10pt"> DSL line =
state =3D=20
            0x8F</SPAN></FONT><SPAN lang=3DDE><o:p></o:p></SPAN></P>
            <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
            style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
            <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
            style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">All other TLVs =
are=20
            optional.</SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P>
            <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
            style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
            <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
            style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Would =
appreciate=20
            confirmation from the WG regarding the =
above.</SPAN></FONT><SPAN=20
            lang=3DDE><o:p></o:p></SPAN></P>
            <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
            style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
            <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
            style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Thanks,</SPAN></FONT><SPAN=20
            lang=3DDE><o:p></o:p></SPAN></P>
            <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
            style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Woj.</SPAN></FONT><SPAN=20
            lang=3DDE><o:p></o:p></SPAN></P>
            <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN lang=3DDE=20
            style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
            <BLOCKQUOTE=20
            style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; =
BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: =
5pt 0in 5pt 3.75pt; BORDER-LEFT: black 1.5pt solid; PADDING-TOP: 0in; =
BORDER-BOTTOM: medium none">
              <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
              lang=3DDE=20
style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
              <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
              face=3D"Times New Roman" size=3D3><SPAN =
style=3D"FONT-SIZE: 12pt">
              <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
              </SPAN></FONT></DIV>
              <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: =
12pt"><B><FONT=20
              face=3DTahoma size=3D2><SPAN=20
              style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
              face=3DTahoma size=3D2><SPAN=20
              style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma"> DE CNODDER =
Stefaan=20
              [mailto:stefaan.de_cnodder@alcatel-lucent.be] <BR><B><SPAN =

              style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> 29 April 2008 =

              09:52<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">To:</SPAN></B>=20
              Wojciech Dec (wdec); Busser, M; ancp@ietf.org<BR><B><SPAN=20
              style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B> Haag, =
T<BR><B><SPAN=20
              style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [ANCP] =
Mandatory=20
              TLVs in draft-ietf-ancp-protocol=20
              proposal</SPAN></FONT><o:p></o:p></P>
              <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
              lang=3DDE=20
style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
              <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
              lang=3DDE=20
              style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Hi=20
              Woj,</SPAN></FONT><SPAN lang=3DDE><o:p></o:p></SPAN></P>
              <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
              lang=3DDE=20
style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
              <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
              lang=3DDE=20
              style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Take the=20
              following example: I have a network with 2 NASses, NAS-A =
is doing=20
              hierarchical shaping, NAS-B just wants to have the port=20
              information but is not doing hierarchical shaping (it is =
doing=20
              other things like OAM, ...).&nbsp; This means NAS-A needs =
the=20
              bandwidth, while NAS-B does not need the bandwidth.&nbsp; =
How=20
              should the flag be set in this case by the AN?&nbsp; Set =
to=20
              'Mandatory' for the port up messages to NAS-A, and set to=20
              'Optional' for port up messages towards NAS-B? Or is it =
always set=20
              to 'Mandatory'?&nbsp; From your answer below, I understand =
that it=20
              should be set to 'Optional' towards NAS-B.&nbsp; Is that=20
              correct?</SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P>
              <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
              lang=3DDE=20
style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
              <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
              lang=3DDE=20
              style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">NAS-B=20
              will simply ignore the bandwidth TLV.&nbsp; If such a flag =
would=20
              exist, and the flag is set to 'Mandatory' by the AN to =
NAS-B, what=20
              should be the behavior of NAS-B?&nbsp; Should it reject =
the whole=20
              message?&nbsp; Maybe NAS-B is not supporting hierarchical =
shaping,=20
              so it might not support the bandwidth TLV.&nbsp; Today, =
the=20
              bandwidht TLV is only mandatory to be put in the port up =
messages,=20
              but for the receiver there is nothing=20
              mandatory.</SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P>
              <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
              lang=3DDE=20
style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
              <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
              lang=3DDE style=3D"FONT-SIZE: 10pt; COLOR: blue; =
FONT-FAMILY: Arial">I=20
              believe the original intend of ANCP was that the AN does =
not need=20
              to know what the NAS is doing with this information, the =
use of=20
              the bandwidth is also not specified by ANCP, only an =
example is=20
              given (which is shaping).&nbsp; In the future there may be =

              applications for which TLVs will be mandatory which are =
now=20
              optional.</SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P>
              <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
              lang=3DDE=20
style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
              <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
              lang=3DDE=20
              style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">regards,</SPAN></FONT><SPAN=20
              lang=3DDE><o:p></o:p></SPAN></P>
              <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
              lang=3DDE=20
              style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Stefaan</SPAN></FONT><SPAN=20
              lang=3DDE><o:p></o:p></SPAN></P>
              <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
              lang=3DDE=20
style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
              <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
              lang=3DDE=20
style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
              <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
              lang=3DDE=20
style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
              <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
              lang=3DDE=20
style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
              <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
              face=3D"Times New Roman" size=3D3><SPAN =
style=3D"FONT-SIZE: 12pt">
              <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
              </SPAN></FONT></DIV>
              <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: =
12pt"><B><FONT=20
              face=3DTahoma size=3D2><SPAN=20
              style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
              face=3DTahoma size=3D2><SPAN=20
              style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma"> Wojciech =
Dec (wdec)=20
              [mailto:wdec@cisco.com] <BR><B><SPAN=20
              style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> maandag 28 =
april 2008=20
              21:33<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">To:</SPAN></B> DE=20
              CNODDER Stefaan; Busser, M; ancp@ietf.org<BR><B><SPAN=20
              style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B> Haag, =
T<BR><B><SPAN=20
              style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [ANCP] =
Mandatory=20
              TLVs in draft-ietf-ancp-protocol=20
              proposal</SPAN></FONT><o:p></o:p></P>
              <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
              lang=3DDE=20
style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
              <BLOCKQUOTE=20
              style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; =
BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: =
5pt 0in 5pt 3.75pt; BORDER-LEFT: black 1.5pt solid; PADDING-TOP: 0in; =
BORDER-BOTTOM: medium none">
                <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                lang=3DDE=20
                style=3D"FONT-SIZE: =
12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
                <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center"=20
                align=3Dcenter><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                style=3D"FONT-SIZE: 12pt">
                <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" =
SIZE=3D2>
                </SPAN></FONT></DIV>
                <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: =
12pt"><B><FONT=20
                face=3DTahoma size=3D2><SPAN=20
                style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; =
FONT-FAMILY: Tahoma">From:</SPAN></FONT></B><FONT=20
                face=3DTahoma size=3D2><SPAN=20
                style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma"> DE =
CNODDER Stefaan=20
                [mailto:stefaan.de_cnodder@alcatel-lucent.be] =
<BR><B><SPAN=20
                style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> 28 April =
2008=20
                17:15<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">To:</SPAN></B>=20
                Wojciech Dec (wdec); Busser, M; =
ancp@ietf.org<BR><B><SPAN=20
                style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B> Haag, =
T<BR><B><SPAN=20
                style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: =
[ANCP]=20
                Mandatory TLVs in draft-ietf-ancp-protocol=20
                proposal</SPAN></FONT><o:p></o:p></P>
                <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                lang=3DDE=20
                style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
                <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
                lang=3DDE=20
                style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Take=20
                the bandwidth sub-TLV in port up messages as =
example.&nbsp; The=20
                current protocol spec says that it is mandatory&nbsp;to =
be sent=20
                in port up messages.&nbsp; that's ok.&nbsp; But it is =
not=20
                mandatory for the receiver to process the bandwidth=20
                sub-TLV.&nbsp; What is done with this information by the =
NAS is=20
                not specified by ANCP, so you cannot make it mandatory =
for the=20
                receiver side.</SPAN></FONT><FONT face=3DArial =
color=3Dblack=20
                size=3D2><SPAN lang=3DDE=20
                style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><SPAN=20
                lang=3DDE><o:p></o:p></SPAN></P>
                <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                lang=3DDE=20
                style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
                <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
                lang=3DDE=20
                style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Woj&gt;=20
                Is the information required by the application? It would =
appear=20
                for the dynamic shaping use-case to be most certainly =
so. Hence=20
                it is absolutely mandatory, otherwise the message makes =
no sense=20
                for the application.</SPAN></FONT><FONT face=3DArial =
color=3Dblue=20
                size=3D2><SPAN lang=3DDE=20
                style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><FONT=20
                face=3DArial color=3Dblack size=3D2><SPAN lang=3DDE=20
                style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">In any=20
                case, if </SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P>
                <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                lang=3DDE=20
                style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
                <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
                lang=3DDE=20
                style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">So it=20
                looks to me that the flag can only indicate what the =
receiver=20
                should do.&nbsp; Then the flag makes =
sense.</SPAN></FONT><FONT=20
                face=3DArial color=3Dblack size=3D2><SPAN lang=3DDE=20
                style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><SPAN=20
                lang=3DDE><o:p></o:p></SPAN></P>
                <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                lang=3DDE=20
                style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
                <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
                lang=3DDE=20
                style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Woj&gt;=20
                </SPAN></FONT><FONT face=3DArial color=3Dblue =
size=3D2><SPAN lang=3DDE=20
                style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><FONT=20
                face=3DArial color=3Dblack size=3D2><SPAN lang=3DDE=20
                style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">The=20
                flag tells the receiver what info the sender thinks is =
required=20
                to carry out the application. This in almost all cases =
has to=20
                match up to what the receiver thinks is required. The=20
                sender&nbsp;doesn't tell the receiver what to do with =
the=20
                info.</SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P>
                <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                lang=3DDE=20
                style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
                <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
                lang=3DDE=20
                style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">If the=20
                receiver knows what is mandatory, then I do not see a =
reason why=20
                this has to be made explicit in the protocol.&nbsp; It =
would=20
                only complicate the protocol.&nbsp; As already said by =
Michael:=20
                if a mandatory TLV is not there, then it is just a=20
                bug.</SPAN></FONT><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
                lang=3DDE=20
                style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><SPAN=20
                lang=3DDE><o:p></o:p></SPAN></P>
                <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                lang=3DDE=20
                style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
                <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
                lang=3DDE=20
                style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Woj&gt;=20
                Can you specifically describe what aspect of the =
protocol does=20
                it complicate?</SPAN></FONT><FONT face=3DArial =
color=3Dblue=20
                size=3D2><SPAN lang=3DDE=20
                style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><FONT=20
                face=3DArial color=3Dblack size=3D2><SPAN lang=3DDE=20
                style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">It's=20
                just making explicitly clear what the protocol already =
has to=20
                implement anyway to be of any use.</SPAN></FONT><SPAN=20
                lang=3DDE><o:p></o:p></SPAN></P>
                <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
                style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">As to =
whether it is=20
                a bug, having such explicit marking makes it clear =
what/where=20
                the problem is when observing a messaging flow&nbsp;vs a =
lot of=20
                deduction work. In any case, the other point being made=20
                here&nbsp;is that today the protocol does NOT specify =
what=20
                should happen if a mandatory TLV is =
missing.</SPAN></FONT><SPAN=20
                lang=3DDE><o:p></o:p></SPAN></P>
                <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                lang=3DDE=20
                style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
                <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
                style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">-Woj.</SPAN></FONT><SPAN=20
                lang=3DDE><o:p></o:p></SPAN></P>
                <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                lang=3DDE=20
                style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
                <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
                lang=3DDE=20
                style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">regards,</SPAN></FONT><SPAN=20
                lang=3DDE><o:p></o:p></SPAN></P>
                <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
                lang=3DDE=20
                style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Stefaan</SPAN></FONT><SPAN=20
                lang=3DDE><o:p></o:p></SPAN></P>
                <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                lang=3DDE=20
                style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
                <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                lang=3DDE=20
                style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
                <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                lang=3DDE=20
                style=3D"FONT-SIZE: =
12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
                <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center"=20
                align=3Dcenter><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                style=3D"FONT-SIZE: 12pt">
                <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" =
SIZE=3D2>
                </SPAN></FONT></DIV>
                <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: =
12pt"><B><FONT=20
                face=3DTahoma size=3D2><SPAN=20
                style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; =
FONT-FAMILY: Tahoma">From:</SPAN></FONT></B><FONT=20
                face=3DTahoma size=3D2><SPAN=20
                style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma"> Wojciech =
Dec=20
                (wdec) [mailto:wdec@cisco.com] <BR><B><SPAN=20
                style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> maandag 28 =
april 2008=20
                16:28<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">To:</SPAN></B> DE=20
                CNODDER Stefaan; Busser, M; ancp@ietf.org<BR><B><SPAN=20
                style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B> Haag, =
T<BR><B><SPAN=20
                style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: =
[ANCP]=20
                Mandatory TLVs in draft-ietf-ancp-protocol=20
                proposal</SPAN></FONT><o:p></o:p></P>
                <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
                style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">It's =
actually a mix=20
                of both. Inline...</SPAN></FONT><SPAN=20
                lang=3DDE><o:p></o:p></SPAN></P>
                <BLOCKQUOTE=20
                style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; =
BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: =
5pt 0in 5pt 3.75pt; BORDER-LEFT: black 1.5pt solid; PADDING-TOP: 0in; =
BORDER-BOTTOM: medium none">
                  <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-SIZE: =
12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
                  <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center"=20
                  align=3Dcenter><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                  style=3D"FONT-SIZE: 12pt">
                  <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" =
SIZE=3D2>
                  </SPAN></FONT></DIV>
                  <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: =
12pt"><B><FONT=20
                  face=3DTahoma size=3D2><SPAN=20
                  style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; =
FONT-FAMILY: Tahoma">From:</SPAN></FONT></B><FONT=20
                  face=3DTahoma size=3D2><SPAN=20
                  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">=20
                  ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] =
<B><SPAN=20
                  style=3D"FONT-WEIGHT: bold">On Behalf Of </SPAN></B>DE =
CNODDER=20
                  Stefaan<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">Sent:</SPAN></B>=20
                  28 April 2008 16:04<BR><B><SPAN=20
                  style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Wojciech =
Dec (wdec);=20
                  Busser, M; ancp@ietf.org<BR><B><SPAN=20
                  style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B> Haag, =
T<BR><B><SPAN=20
                  style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> Re: =
[ANCP]=20
                  Mandatory TLVs in draft-ietf-ancp-protocol=20
                  proposal</SPAN></FONT><o:p></o:p></P>
                  <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
                  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Hi,</SPAN></FONT><SPAN=20
                  lang=3DDE><o:p></o:p></SPAN></P>
                  <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
                  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">This=20
                  new mandatory flag, what is exactly its=20
                  meaning?</SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P>
                  <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
                  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">(1)&nbsp;if=20
                  flag set to "mandatory", then the *receiver* of this =
TLV MUST=20
                  process it, and if unrecognized must drop the=20
                  message</SPAN></FONT><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><SPAN=20
                  lang=3DDE><o:p></o:p></SPAN></P>
                  <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
                  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">If a=20
                  received TLV is has the&nbsp;"mandatory" flag =
set&nbsp;then=20
                  the receiver MUST drop the message and report an error =
to the=20
                  sender&nbsp;if it doesn't recognize the=20
                  TLV.</SPAN></FONT><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><SPAN=20
                  lang=3DDE><o:p></o:p></SPAN></P>
                  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">If a=20
                  the receiver expects a&nbsp;"mandatory" TLV but =
doesn't=20
                  receive it,&nbsp;the message MUST =
be&nbsp;droped&nbsp;and=20
                  an&nbsp;error report&nbsp;sent to=20
                  the&nbsp;sender.</SPAN></FONT><FONT face=3DArial =
color=3Dblue=20
                  size=3D2><SPAN lang=3DDE=20
                  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><SPAN=20
                  lang=3DDE><o:p></o:p></SPAN></P>
                  <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
                  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">OR</SPAN></FONT><SPAN=20
                  lang=3DDE><o:p></o:p></SPAN></P>
                  <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
                  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">(2)&nbsp;if=20
                  flag is set to"mandatory", then the *sender* MUST =
include it=20
                  in the message for which it is =
defined</SPAN></FONT><FONT=20
                  face=3DArial color=3Dblack size=3D2><SPAN lang=3DDE=20
                  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><SPAN=20
                  lang=3DDE><o:p></o:p></SPAN></P>
                  <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
                  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">The=20
                  sender MUST include mandatory TLVs as defined by the=20
                  protocol-spec/applications.</SPAN></FONT><SPAN=20
                  lang=3DDE><o:p></o:p></SPAN></P>
                  <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
                  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">The=20
                  current protocols draft says for certain TLVs that =
they are=20
                  mandatory, but that applies to the sender of it=20
                  (interpretation 2).&nbsp; The flag would indicate=20
                  interpretation 1 (like for Radius =
VSAs?)?</SPAN></FONT><SPAN=20
                  lang=3DDE><o:p></o:p></SPAN></P>
                  <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
                  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">If=20
                  the higher order bit is set to "0" means that it is =
mandatory,=20
                  then currently defined optional defined TLVs suddenly =
become=20
                  mandatory which is not good.</SPAN></FONT><FONT =
face=3DArial=20
                  color=3Dblack size=3D2><SPAN lang=3DDE=20
                  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><SPAN=20
                  lang=3DDE><o:p></o:p></SPAN></P>
                  <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
                  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Woj&gt;=20
                  Only the currently used TLVs&nbsp;become mandatory. If =
they=20
                  are not used/implemented we can re-define them as =
optional=20
                  (set flag to 1) at no cost. </SPAN></FONT><SPAN=20
                  lang=3DDE><o:p></o:p></SPAN></P>
                  <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
                  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">But I=20
                  would first to understand the exact meaning of this =
mandatory=20
                  flag.&nbsp; Defining such a flag indeed looks useful =
but then=20
                  as interpretation 1, and I would say that if flag set =
to 1,=20
                  then it is mandatory and actually, it is possible that =
a TLV=20
                  is sent sometimes as optional and sometimes as=20
                  mandatory.</SPAN></FONT><FONT face=3DArial =
color=3Dblack=20
                  size=3D2><SPAN lang=3DDE=20
                  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><SPAN=20
                  lang=3DDE><o:p></o:p></SPAN></P>
                  <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
                  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Woj&gt;=20
                  Precisely, that is possible on a per application=20
                  basis.</SPAN></FONT><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><FONT=20
                  face=3DArial color=3Dblack size=3D2><SPAN lang=3DDE=20
                  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Having=20
                  the flag would make troubleshooting of a message=20
                  flow&nbsp;much more explicit (today, with any =
problem&nbsp;one=20
                  has to browse the drafts to figure out what MUST be =
there vs=20
                  what SHOULD be there&nbsp;all while looking&nbsp;what =
is=20
                  actually there)</SPAN></FONT><SPAN=20
                  lang=3DDE><o:p></o:p></SPAN></P>
                  <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
                  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Regards,</SPAN></FONT><SPAN=20
                  lang=3DDE><o:p></o:p></SPAN></P>
                  <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Woj.</SPAN></FONT><SPAN=20
                  lang=3DDE><o:p></o:p></SPAN></P>
                  <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
                  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">regards,</SPAN></FONT><SPAN=20
                  lang=3DDE><o:p></o:p></SPAN></P>
                  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Stefaan</SPAN></FONT><SPAN=20
                  lang=3DDE><o:p></o:p></SPAN></P>
                  <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
                  <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-SIZE: =
12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
                  <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center"=20
                  align=3Dcenter><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                  style=3D"FONT-SIZE: 12pt">
                  <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" =
SIZE=3D2>
                  </SPAN></FONT></DIV>
                  <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: =
12pt"><B><FONT=20
                  face=3DTahoma size=3D2><SPAN=20
                  style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; =
FONT-FAMILY: Tahoma">From:</SPAN></FONT></B><FONT=20
                  face=3DTahoma size=3D2><SPAN=20
                  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">=20
                  ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] =
<B><SPAN=20
                  style=3D"FONT-WEIGHT: bold">On Behalf Of =
</SPAN></B>Wojciech Dec=20
                  (wdec)<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">Sent:</SPAN></B>=20
                  donderdag 24 april 2008 14:19<BR><B><SPAN=20
                  style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Busser, M;=20
                  ancp@ietf.org<BR><B><SPAN=20
                  style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B> Haag, =
T<BR><B><SPAN=20
                  style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> Re: =
[ANCP]=20
                  Mandatory TLVs in draft-ietf-ancp-protocol=20
                  proposal</SPAN></FONT><o:p></o:p></P>
                  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
                  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Hi=20
                  Michael,</SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P>
                  <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                  lang=3DDE=20
                  style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
                  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =
lang=3DDE=20
                  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">inline...</SPAN></FONT><SPAN=20
                  lang=3DDE><o:p></o:p></SPAN></P>
                  <BLOCKQUOTE=20
                  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: =
0in; BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; =
MARGIN: 5pt 0in 5pt 3.75pt; BORDER-LEFT: black 1.5pt solid; PADDING-TOP: =
0in; BORDER-BOTTOM: medium none">
                    <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                    lang=3DDE=20
                    style=3D"FONT-SIZE: =
12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
                    <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center"=20
                    align=3Dcenter><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                    style=3D"FONT-SIZE: 12pt">
                    <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" =
SIZE=3D2>
                    </SPAN></FONT></DIV>
                    <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: =
12pt"><B><FONT=20
                    face=3DTahoma size=3D2><SPAN=20
                    style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; =
FONT-FAMILY: Tahoma">From:</SPAN></FONT></B><FONT=20
                    face=3DTahoma size=3D2><SPAN=20
                    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">=20
                    ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] =

                    <B><SPAN style=3D"FONT-WEIGHT: bold">On Behalf Of=20
                    </SPAN></B>Busser, M<BR><B><SPAN=20
                    style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> 24 =
April 2008=20
                    13:13<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">To:</SPAN></B>=20
                    ancp@ietf.org<BR><B><SPAN=20
                    style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B> Haag, =
T<BR><B><SPAN=20
                    style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> Re: =
[ANCP]=20
                    Mandatory TLVs in draft-ietf-ancp-protocol=20
                    proposal</SPAN></FONT><o:p></o:p></P>
                    <DIV>
                    <P class=3DMsoNormal><FONT face=3DArial =
size=3D2><SPAN lang=3DDE=20
                    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Hi =
Woi,=20
                    all</SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P></DIV>
                    <DIV>
                    <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                    lang=3DDE=20
                    style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
                    <DIV>
                    <P class=3DMsoNormal><FONT face=3DArial =
size=3D2><SPAN lang=3DDE=20
                    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">I see =
the=20
                    problem but i can not see, how an additional flag =
will help=20
                    solving this problem.</SPAN></FONT><SPAN=20
                    lang=3DDE><o:p></o:p></SPAN></P></DIV>
                    <DIV>
                    <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                    lang=3DDE=20
                    style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
                    <DIV>
                    <P class=3DMsoNormal><FONT face=3DArial =
size=3D2><SPAN lang=3DDE=20
                    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Lets =
assume your=20
                    first&nbsp;proposal.</SPAN></FONT><SPAN=20
                    lang=3DDE><o:p></o:p></SPAN></P></DIV>
                    <DIV>
                    <P class=3DMsoNormal><FONT face=3DArial =
size=3D2><SPAN lang=3DDE=20
                    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">If&nbsp;an=20
                    implementation does not send the complete&nbsp;TLV, =
even it=20
                    is defined&nbsp;to be&nbsp;mandatory,&nbsp;I would =
call this=20
                    a bug and&nbsp;I can not see, how an additional flag =
can=20
                    help here.&nbsp;</SPAN></FONT><SPAN=20
                    lang=3DDE><o:p></o:p></SPAN></P></DIV>
                    <DIV>
                    <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                    lang=3DDE=20
                    style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
                    <DIV>
                    <P class=3DMsoNormal><FONT face=3DArial =
size=3D2><SPAN lang=3DDE=20
                    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Woj&gt; The way=20
                    it helps, and other protocols bear proof of this =
scheme, is=20
                    that it is easier for implementations to reconcile =
errors=20
                    resulting out of "Mandatory" and "Optional"&nbsp;TLV =
sets.=20
                    The key to this lies on a per application basis. One =

                    application may mandate TLV A for operation, while =
another=20
                    might not. Resolving such issues when implementing =
or=20
                    troubleshooting multiple applications is not always =
trivial.=20
                    </SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P></DIV>
                    <DIV>
                    <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                    lang=3DDE=20
                    style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
                    <DIV>
                    <P class=3DMsoNormal><FONT face=3DArial =
size=3D2><SPAN lang=3DDE=20
                    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Your =
second=20
                    proposal seems obviously&nbsp;be required to keep =
existing=20
                    things working, if we&nbsp;agree on&nbsp;your first=20
                    proposal. </SPAN></FONT><SPAN=20
                    lang=3DDE><o:p></o:p></SPAN></P></DIV>
                    <DIV>
                    <P class=3DMsoNormal><FONT face=3DArial =
size=3D2><SPAN lang=3DDE=20
                    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">But =
from my=20
                    point of view&nbsp;it also assumes, that all =
existing=20
                    implementations are using the same set of TLVs now.=20
                    </SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P></DIV>
                    <DIV>
                    <P class=3DMsoNormal><FONT face=3DArial =
size=3D2><SPAN lang=3DDE=20
                    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">And&nbsp;I am=20
                    not sure =
about&nbsp;that.&nbsp;&nbsp;</SPAN></FONT><SPAN=20
                    lang=3DDE><o:p></o:p></SPAN></P></DIV>
                    <DIV>
                    <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                    lang=3DDE=20
                    style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
                    <DIV>
                    <P class=3DMsoNormal><FONT face=3DArial =
size=3D2><SPAN lang=3DDE=20
                    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Woj&gt; This=20
                    would be a good thing for the WG to discuss. There =
most=20
                    evidently is a fair amount of&nbsp;"dead wood" in =
the=20
                    current spec, ie stuff that nobody =
yet&nbsp;implements or=20
                    cares about. &nbsp;In the former case, we could =
re-cast that=20
                    material using the new notions/extensions, in the =
latter=20
                    case simply chop it out.</SPAN></FONT><SPAN=20
                    lang=3DDE><o:p></o:p></SPAN></P></DIV>
                    <DIV>
                    <P class=3DMsoNormal><FONT face=3DArial =
size=3D2><SPAN lang=3DDE=20
                    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
                    <DIV>
                    <P class=3DMsoNormal><FONT face=3DArial =
size=3D2><SPAN lang=3DDE=20
                    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Therefore I=20
                    disagree with your first proposal. I recommend, the =
better=20
                    way&nbsp;will be to be more precise in=20
                    definitions.&nbsp;</SPAN></FONT><SPAN=20
                    lang=3DDE><o:p></o:p></SPAN></P></DIV>
                    <DIV>
                    <P class=3DMsoNormal><FONT face=3DArial =
size=3D2><SPAN lang=3DDE=20
                    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">In my =
mind, it=20
                    is a bug, if a mandatory TLV is missing. It is up to =
the=20
                    robustness of the implementation&nbsp;to deal with =
this=20
                    situation.</SPAN></FONT><SPAN=20
                    lang=3DDE><o:p></o:p></SPAN></P></DIV>
                    <DIV>
                    <P class=3DMsoNormal><FONT face=3DArial =
size=3D2><SPAN lang=3DDE=20
                    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Is it =
really=20
                    neccesary to define the behavior of a network =
element in=20
                    this case of failure in the ancp protocol=20
                    itself?&nbsp;&nbsp;</SPAN></FONT><SPAN=20
                    lang=3DDE><o:p></o:p></SPAN></P></DIV>
                    <DIV>
                    <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                    lang=3DDE=20
                    style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
                    <DIV>
                    <P class=3DMsoNormal><FONT face=3DArial =
size=3D2><SPAN lang=3DDE=20
                    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Woj&gt; Other=20
                    people have faced this problem before, and I would =
rather go=20
                    with the lessons they learned, rather than clinging =
to hopes=20
                    of perfect textual definitions and implementations. =
Other=20
                    than backwards compatibility, I do not see in your=20
                    statements a valid reason&nbsp;to object to the=20
                    1st&nbsp;proposal, particularly for new applications =
since=20
                    it can only make things more robust. The counter =
argument of=20
                    being precise in the definitions, as evidenced by =
the=20
                    current spec, is admirable and needs to be there, =
with this=20
                    proposal providing an extra level of robustness and=20
                    visibility of any problems. </SPAN></FONT><SPAN=20
                    lang=3DDE><o:p></o:p></SPAN></P></DIV>
                    <DIV>
                    <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                    lang=3DDE=20
                    style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
                    <DIV>
                    <P class=3DMsoNormal><FONT face=3DArial =
size=3D2><SPAN lang=3DDE=20
                    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Thanks,</SPAN></FONT><SPAN=20
                    lang=3DDE><o:p></o:p></SPAN></P></DIV>
                    <DIV>
                    <P class=3DMsoNormal><FONT face=3DArial =
size=3D2><SPAN lang=3DDE=20
                    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Woj.</SPAN></FONT><SPAN=20
                    lang=3DDE><o:p></o:p></SPAN></P></DIV>
                    <DIV>
                    <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                    lang=3DDE=20
                    style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
                    <DIV>
                    <P class=3DMsoNormal><FONT face=3DArial =
size=3D2><SPAN lang=3DDE=20
                    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">If =
optional TLVs=20
                    are not present in a message, we should describe =
some kind=20
                    of default behaviour, as you already=20
                    stated.</SPAN></FONT><SPAN=20
                    lang=3DDE><o:p></o:p></SPAN></P></DIV>
                    <DIV>
                    <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                    lang=3DDE=20
                    style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
                    <DIV>
                    <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                    lang=3DDE=20
                    style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
                    <DIV>
                    <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                    lang=3DDE=20
                    style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
                    <DIV>
                    <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                    lang=3DDE=20
                    style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
                    <DIV>
                    <DIV>
                    <P class=3DMsoNormal><FONT face=3DArial =
size=3D2><SPAN lang=3DDE=20
                    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Comments on=20
                    =
draft-ietf-ancp-protocol-02.txt:<o:p></o:p></SPAN></FONT></P></DIV></DIV>=

                    <DIV>
                    <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                    lang=3DDE=20
                    style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
                    <DIV>
                    <P class=3DMsoNormal><FONT face=3DArial =
size=3D2><SPAN lang=3DDE=20
                    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">It is =
not=20
                    clearly stated,&nbsp;if the TLV =
&nbsp;"</SPAN></FONT><FONT=20
                    size=3D2><SPAN lang=3DEN-GB style=3D"FONT-SIZE: =
10pt">DSL Line=20
                    Attributes "</SPAN></FONT><FONT face=3DArial =
size=3D2><SPAN=20
                    lang=3DEN-GB style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"> is=20
                    mandatory or optional. </SPAN></FONT><SPAN=20
                    lang=3DDE><o:p></o:p></SPAN></P></DIV>
                    <DIV>
                    <P class=3DMsoNormal><FONT face=3DArial =
size=3D2><SPAN lang=3DEN-GB=20
                    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">In =
fact it is=20
                    mandatory because some of its SubTLVs are mandatory. =

                    </SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P></DIV>
                    <DIV>
                    <P class=3DMsoNormal><FONT face=3DArial =
size=3D2><SPAN lang=3DEN-GB=20
                    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">We =
should spent=20
                    a sentence to make this clear.</SPAN></FONT><SPAN=20
                    lang=3DDE><o:p></o:p></SPAN></P></DIV>
                    <DIV>
                    <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                    lang=3DDE=20
                    style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
                    <DIV>
                    <P class=3DMsoNormal><FONT face=3DArial =
size=3D2><SPAN lang=3DDE=20
                    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">It is =
not=20
                    clearly stated,&nbsp;if the TLV =
&nbsp;"</SPAN></FONT><FONT=20
                    size=3D2><SPAN lang=3DEN-GB=20
                    style=3D"FONT-SIZE: =
10pt">Service-Profile-Name"</SPAN></FONT><FONT=20
                    face=3DArial size=3D2><SPAN lang=3DEN-GB=20
                    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"> is =
mandatory or=20
                    optional.</SPAN></FONT><SPAN=20
                    lang=3DDE><o:p></o:p></SPAN></P></DIV>
                    <DIV>
                    <P class=3DMsoNormal><FONT face=3DArial =
size=3D2><SPAN lang=3DEN-GB=20
                    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">I =
prefer=20
                    mandatory because it is essetial for the use case =
Line=20
                    Config.&nbsp;</SPAN></FONT><FONT face=3DArial =
size=3D2><SPAN=20
                    lang=3DDE=20
                    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></P></DIV>
                    <DIV>
                    <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                    lang=3DDE=20
                    style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
                    <DIV>
                    <P class=3DMsoNormal><FONT face=3DArial =
size=3D2><SPAN lang=3DDE=20
                    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Section 5.4.3=20
                    Line Config, where the TLVs are mentioned (page=20
                    35):</SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P></DIV>
                    <DIV>
                    <P class=3DMsoNormal><FONT face=3DArial =
size=3D2><SPAN lang=3DDE=20
                    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp; =

                    ...defined in section 5.4.1....&nbsp;&nbsp;&nbsp; =
must be=20
                    corrected to&nbsp;&nbsp;&nbsp; ...defined in section =

                    5.4.2........</SPAN></FONT><SPAN=20
                    lang=3DDE><o:p></o:p></SPAN></P></DIV>
                    <DIV>
                    <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                    lang=3DDE=20
                    style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
                    <DIV>
                    <DIV>
                    <P class=3DMsoNormal><FONT face=3DArial =
size=3D2><SPAN lang=3DDE=20
                    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Section=20
                    5.4.4&nbsp;OAM, where the TLVs are mentioned (page =
36 and=20
                    page 38):</SPAN></FONT><FONT size=3D2><SPAN =
lang=3DDE=20
                    style=3D"FONT-SIZE: =
10pt"><o:p></o:p></SPAN></FONT></P></DIV>
                    <DIV>
                    <P class=3DMsoNormal><FONT face=3DArial =
size=3D2><SPAN lang=3DDE=20
                    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">&nbsp; =

                    ...defined in section 5.4.1....&nbsp;&nbsp;&nbsp; =
must be=20
                    corrected to&nbsp;&nbsp;&nbsp; ...defined in section =

                    5.4.2........</SPAN></FONT><FONT size=3D2><SPAN =
lang=3DDE=20
                    style=3D"FONT-SIZE: =
10pt"><o:p></o:p></SPAN></FONT></P></DIV>
                    <DIV>
                    <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D2><SPAN=20
                    lang=3DDE=20
                    style=3D"FONT-SIZE: =
10pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
                    <DIV>
                    <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                    lang=3DDE=20
                    style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV></DIV>
                    <DIV>
                    <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                    lang=3DDE=20
                    style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
                    <DIV>
                    <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                    lang=3DDE=20
                    style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
                    <P><FONT face=3D"Times New Roman" color=3Dnavy =
size=3D3><SPAN=20
                    lang=3DDE style=3D"FONT-SIZE: 12pt; COLOR: =
navy">Best Regards;=20
                    Freundliche Gr=FC=DFe <o:p></o:p></SPAN></FONT></P>
                    <P><B><FONT face=3D"Times New Roman" color=3Dnavy =
size=3D3><SPAN=20
                    lang=3DDE=20
                    style=3D"FONT-WEIGHT: bold; FONT-SIZE: 12pt; COLOR: =
navy">Michael=20
                    Busser<o:p></o:p></SPAN></FONT></B></P>
                    <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D1><SPAN=20
                    lang=3DDE style=3D"FONT-SIZE: 8pt">T-Systems =
Enterprise Services=20
                    GmbH </SPAN></FONT><FONT size=3D1><SPAN lang=3DDE=20
                    style=3D"FONT-SIZE: =
7.5pt"><o:p></o:p></SPAN></FONT></P>
                    <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D1><SPAN=20
                    lang=3DDE style=3D"FONT-SIZE: 7.5pt">Production Line =
Network=20
                    Centric Systems<o:p></o:p></SPAN></FONT></P>
                    <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D1><SPAN=20
                    lang=3DDE style=3D"FONT-SIZE: 7.5pt">ICT-Systems=20
                    Integration<o:p></o:p></SPAN></FONT></P>
                    <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D1><SPAN=20
                    lang=3DDE style=3D"FONT-SIZE: 7.5pt">Network =
Integration=20
                    Services<o:p></o:p></SPAN></FONT></P>
                    <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D1><SPAN=20
                    lang=3DDE=20
                    style=3D"FONT-SIZE: =
7.5pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
                    <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
color=3Dblack=20
                    size=3D1><SPAN lang=3DDE=20
                    style=3D"FONT-SIZE: 7.5pt; COLOR: black">Br=FCckes 2 =
-8, 55545=20
                    Bad Kreuznach<BR>Postfach 9100, 55541 Bad =
Kreuznach<BR>+49=20
                    671 8333 8911 (Phone)<BR>+49 521&nbsp;9210&nbsp;3859 =

                    (Fax)<BR>+49 151 1211&nbsp;9689 (Mobile)<BR>E-Mail: =
<A=20
                    =
href=3D"mailto:michael.busser@t-systems.com">michael.busser@t-systems.com=
</A></SPAN></FONT><FONT=20
                    size=3D1><SPAN lang=3DDE=20
                    style=3D"FONT-SIZE: =
8pt"><o:p></o:p></SPAN></FONT></P>
                    <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D1><SPAN=20
                    lang=3DDE style=3D"FONT-SIZE: 8pt">Internet: <A=20
                    href=3D"http://www.t-systems.com/"=20
                    target=3D_parent><p:onmouseclick =
hyperlinktype=3D"url"=20
                    =
href=3D"http://www.t-systems.com/"></p:onmouseclick><FONT=20
                    color=3D#6699ff><SPAN=20
                    style=3D"COLOR: =
#6699ff">http://www.t-systems.com</SPAN></FONT></A>=20
                    </SPAN></FONT><FONT size=3D1><SPAN lang=3DDE=20
                    style=3D"FONT-SIZE: =
7.5pt"><o:p></o:p></SPAN></FONT></P>
                    <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D1><SPAN=20
                    lang=3DDE=20
                    style=3D"FONT-SIZE: =
7.5pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
                    <P class=3DMsoNormal><FONT face=3DArial =
color=3Dblack size=3D1><SPAN=20
                    lang=3DDE=20
                    style=3D"FONT-SIZE: 7.5pt; COLOR: black; =
FONT-FAMILY: Arial">T-Systems=20
                    Enterprise Services GmbH<BR>Aufsichtsrat: Ren=E9 =
Obermann=20
                    (Vorsitzender)<BR>Executive Committee: Reinhard =
Clemens=20
                    (Vorsitzender)*, Helmut Binder, Albert Henn, Olaf =
Heyden*,=20
                    Katrin Horstmann, Ulrich Kemp, Wilfried =
Peters*,<BR>Dr.=20
                    Herbert Schaaff*, Zvezdana =
Seeger*<BR>Handelsregister:=20
                    Amtsgericht Frankfurt am Main HRB 55933<BR>Sitz der=20
                    Gesellschaft: Frankfurt am Main<BR>WEEE-Reg.-Nr.=20
                    DE87523644<BR>*Gesch=E4ftsf=FChrer gem. =A7 35=20
                    GmbHG</SPAN></FONT><FONT size=3D1><SPAN lang=3DDE=20
                    style=3D"FONT-SIZE: =
7.5pt"><o:p></o:p></SPAN></FONT></P>
                    <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D1><SPAN=20
                    lang=3DDE=20
                    style=3D"FONT-SIZE: =
7.5pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
                    <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D1><SPAN=20
                    lang=3DDE style=3D"FONT-SIZE: 7.5pt">Notice: This =
transmittal=20
                    and/or attachments may be privileged or =
confidential. If you=20
                    are not the intended recipient, you are hereby =
notified that=20
                    you have received this transmittal in error; any =
review,=20
                    dissemination, or copying is strictly prohibited. If =
you=20
                    received this transmittal in error, please notify us =

                    immediately by reply and immediately delete this =
message and=20
                    all its attachments. Thank you. <BR>T-Systems =
&#8211; Business=20
                    flexibility </SPAN></FONT><FONT size=3D1><SPAN =
lang=3DDE=20
                    style=3D"FONT-SIZE: =
8pt"><o:p></o:p></SPAN></FONT></P>
                    <DIV>
                    <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D1><SPAN=20
                    lang=3DDE=20
                    style=3D"FONT-SIZE: =
7.5pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
                    <BLOCKQUOTE=20
                    style=3D"MARGIN-TOP: 5pt; MARGIN-BOTTOM: 5pt; =
MARGIN-RIGHT: 0in">
                      <P class=3DMsoNormal><FONT face=3DArial =
color=3Dnavy=20
                      size=3D2><SPAN lang=3DDE=20
                      style=3D"FONT-SIZE: 10pt; COLOR: navy; =
FONT-FAMILY: Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
                      <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: =
center"=20
                      align=3Dcenter><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                      lang=3DDE style=3D"FONT-SIZE: 12pt">
                      <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" =
SIZE=3D2>
                      </SPAN></FONT></DIV>
                      <DIV>
                      <P class=3DMsoNormal><B><FONT face=3DTahoma =
size=3D2><SPAN=20
                      lang=3DDE=20
                      style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; =
FONT-FAMILY: Tahoma">Von:</SPAN></FONT></B><FONT=20
                      face=3DTahoma size=3D2><SPAN lang=3DDE=20
                      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">=20
                      ancp-bounces@ietf.org =
[mailto:ancp-bounces@ietf.org]=20
                      <B><SPAN style=3D"FONT-WEIGHT: bold">Im Auftrag =
von=20
                      </SPAN></B>Wojciech Dec (wdec)<BR><B><SPAN=20
                      style=3D"FONT-WEIGHT: bold">Gesendet:</SPAN></B> =
Mittwoch,=20
                      23. April 2008 14:54<BR><B><SPAN=20
                      style=3D"FONT-WEIGHT: bold">An:</SPAN></B>=20
                      ancp@ietf.org<BR><B><SPAN=20
                      style=3D"FONT-WEIGHT: bold">Betreff:</SPAN></B> =
[ANCP]=20
                      Mandatory TLVs in draft-ietf-ancp-protocol=20
                      proposal</SPAN></FONT><SPAN=20
                      lang=3DDE><o:p></o:p></SPAN></P></DIV>
                      <P class=3DMsoNormal><FONT face=3D"Times New =
Roman"=20
                      size=3D3><SPAN lang=3DDE=20
                      style=3D"FONT-SIZE: =
12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
                      <P><FONT face=3DArial size=3D2><SPAN lang=3DEN-GB=20
                      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Hi=20
                      All,</SPAN></FONT><SPAN lang=3DEN-GB> </SPAN><SPAN =

                      lang=3DDE><o:p></o:p></SPAN></P>
                      <P><FONT face=3DArial size=3D2><SPAN lang=3DEN-GB=20
                      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Continuing=20
                      with the series of e-mails regarding basic =
protocol issues=20
                      still to be addressed, I now would now like to ask =
your=20
                      feedback regarding the distinction the protocol =
places on=20
                      mandatory TLVs. Given the length of this mail I'll =
first=20
                      cut to the proposal, and after it you can find the =
problem=20
                      description.</SPAN></FONT><SPAN=20
                      lang=3DDE><o:p></o:p></SPAN></P>
                      <P><FONT face=3DArial size=3D2><SPAN lang=3DEN-GB=20
                      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">The =
proposal=20
                      which I am putting in front of the WG is to define =
a new=20
                      TLV format which contains at a minimum a Mandatory =
flag=20
                      (much like Radius VSAs do). We could have this TLV =
Flag be=20
                      defined only for new =
applications.</SPAN></FONT><SPAN=20
                      lang=3DDE><o:p></o:p></SPAN></P>
                      <P><FONT face=3DArial size=3D2><SPAN lang=3DEN-GB=20
                      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">A =
second=20
                      proposal would be try to make this flag work with =
existing=20
                      ones by for example defining the highest order bit =
of the=20
                      TLV# field to mean "Mandatory" when set to "0". =
This would=20
                      be invisible to exiting implementations, but newer =
ones=20
                      may have problems in communicating with older ones =
when=20
                      the latter do not send all TLVs. But that can also =
be=20
                      addressed by simply forming the set of mandatory =
TLVs to=20
                      be the ones that all implementations currently =
send by=20
                      default.</SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P>
                      <P><FONT face=3DArial size=3D2><SPAN lang=3DEN-GB=20
                      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Without=20
                      additional feedback, I will assume that the WG is =
fine=20
                      with the first proposal, and also with the 2nd one =

                      conditional on deriving a suitable "commonly used" =
TLV=20
                      set.</SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P>
                      <P><FONT face=3DArial size=3D2><SPAN lang=3DEN-GB=20
                      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">The =
problem in=20
                      more detail: </SPAN></FONT><SPAN=20
                      lang=3DDE><o:p></o:p></SPAN></P>
                      <P><FONT face=3DArial size=3D2><SPAN lang=3DEN-GB=20
                      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Currently the=20
                      situation is that Mandatory TLVs are only stated =
to be as=20
                      such in the body of the protocol draft spec, with =
an=20
                      implementer having to scour fairly attentively the =
text.=20
                      Eg "Type (Access-Loop-Circuit-ID =3D 0x01): This =
is a=20
                      mandatory TLV", etc.</SPAN></FONT><SPAN=20
                      lang=3DDE><o:p></o:p></SPAN></P>
                      <P><FONT face=3DArial size=3D2><SPAN lang=3DEN-GB=20
                      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">The =
behaviour=20
                      of an implementation that receives a message with =
a=20
                      missing mandatory TLV is not defined at all, and =
the=20
                      opposite is handled but not very robustly, i.e. =
when=20
                      receiving a TLV but not recognizing it, and =
implementation=20
                      is free to discard it (even if it is mandatory!). =
This is=20
                      a recipe for interoperability problems and an=20
                      implementation mine field.</SPAN></FONT><SPAN=20
                      lang=3DDE><o:p></o:p></SPAN></P>
                      <P><FONT face=3DArial size=3D2><SPAN lang=3DEN-GB=20
                      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">This =
problem=20
                      is complicated by different applications. For =
example the=20
                      current OAM section states the following regarding =
TLVs=20
                      that are to be carried in the request message (my=20
                      italics):</SPAN></FONT><SPAN=20
lang=3DDE><o:p></o:p></SPAN></P>
                      <P><FONT face=3DArial size=3D2><SPAN lang=3DEN-GB=20
                      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">"</SPAN></FONT><SPAN=20
                      lang=3DDE> <BR></SPAN><FONT face=3D"Courier New" =
color=3Dblack=20
                      size=3D2><SPAN=20
                      style=3D"FONT-SIZE: 10pt; COLOR: black; =
FONT-FAMILY: 'Courier New'">Following=20
                      TLVs<B><I><SPAN=20
                      style=3D"FONT-WEIGHT: bold; FONT-STYLE: italic">=20
                      can</SPAN></I></B> appear in this message:=20
                      </SPAN></FONT><SPAN =
lang=3DDE><o:p></o:p></SPAN></P>
                      <P><FONT face=3D"Courier New" color=3Dblack =
size=3D2><SPAN=20
                      style=3D"FONT-SIZE: 10pt; COLOR: black; =
FONT-FAMILY: 'Courier New'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
                      o Type (Access-Loop-Circuit-ID =3D 0x01) : defined =
in=20
                      section 5.4.1&nbsp;&nbsp;&nbsp; =
</SPAN></FONT><SPAN=20
                      lang=3DDE><o:p></o:p></SPAN></P>
                      <P><FONT face=3D"Courier New" color=3Dblack =
size=3D2><SPAN=20
                      style=3D"FONT-SIZE: 10pt; COLOR: black; =
FONT-FAMILY: 'Courier New'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
                      o Type (Access-Aggregation-Circuit-ID-Binary =3D =
0x06):=20
                      defined in </SPAN></FONT><SPAN =
lang=3DDE><BR></SPAN><FONT=20
                      face=3D"Courier New" color=3Dblack size=3D2><SPAN=20
                      style=3D"FONT-SIZE: 10pt; COLOR: black; =
FONT-FAMILY: 'Courier =
New'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
                      section 5.4.1. </SPAN></FONT><SPAN=20
                      lang=3DDE><BR></SPAN><FONT face=3D"Courier New" =
color=3Dblack=20
                      size=3D2><SPAN=20
                      style=3D"FONT-SIZE: 10pt; COLOR: black; =
FONT-FAMILY: 'Courier New'">&nbsp;</SPAN></FONT><SPAN=20
                      lang=3DDE> <BR></SPAN><FONT face=3D"Courier New" =
color=3Dblack=20
                      size=3D2><SPAN=20
                      style=3D"FONT-SIZE: 10pt; COLOR: black; =
FONT-FAMILY: 'Courier New'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
                      o Type (Access-Aggregation-Circuit-ID-ASCII =3D =
0x03):=20
                      defined in section </SPAN></FONT><SPAN=20
                      lang=3DDE><BR></SPAN><FONT face=3D"Courier New" =
color=3Dblack=20
                      size=3D2><SPAN=20
                      style=3D"FONT-SIZE: 10pt; COLOR: black; =
FONT-FAMILY: 'Courier =
New'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
                      5.4.1.&nbsp; </SPAN></FONT><SPAN=20
                      lang=3DDE><o:p></o:p></SPAN></P>
                      <P><FONT face=3D"Courier New" color=3Dblack =
size=3D2><SPAN=20
                      style=3D"FONT-SIZE: 10pt; COLOR: black; =
FONT-FAMILY: 'Courier New'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
                      o Type (OAM-Loopback-Test-Parameters =3D 0x07): =
Parameters=20
                      related to&nbsp; </SPAN></FONT><SPAN=20
                      lang=3DDE><BR></SPAN><FONT face=3D"Courier New" =
color=3Dblack=20
                      size=3D2><SPAN=20
                      style=3D"FONT-SIZE: 10pt; COLOR: black; =
FONT-FAMILY: 'Courier =
New'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
                      loopback test. This is an optional TLV. If this =
TLV is not=20
                      present </SPAN></FONT><SPAN =
lang=3DDE><BR></SPAN><FONT=20
                      face=3D"Courier New" color=3Dblack size=3D2><SPAN=20
                      style=3D"FONT-SIZE: 10pt; COLOR: black; =
FONT-FAMILY: 'Courier =
New'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
                      in the request message, the DSLAM SHOULD use =
locally=20
                      determined </SPAN></FONT><SPAN =
lang=3DDE><BR></SPAN><FONT=20
                      face=3D"Courier New" color=3Dblack size=3D2><SPAN=20
                      style=3D"FONT-SIZE: 10pt; COLOR: black; =
FONT-FAMILY: 'Courier =
New'">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
                      default values for the test parameters.&nbsp;=20
                      </SPAN></FONT><SPAN lang=3DDE><BR></SPAN><FONT=20
                      face=3D"Courier New" color=3Dblack size=3D2><SPAN=20
                      style=3D"FONT-SIZE: 10pt; COLOR: black; =
FONT-FAMILY: 'Courier New'">"</SPAN></FONT><SPAN=20
                      lang=3DDE> <BR></SPAN><FONT face=3DArial =
color=3Dblack=20
                      size=3D2><SPAN=20
                      style=3D"FONT-SIZE: 10pt; COLOR: black; =
FONT-FAMILY: Arial">(NOTE:=20
                      The last "SHOULD" appears to be inappropriate. If =
the TLV=20
                      is missing, the DSLAM MUST have some default =
parameters,=20
                      or return an error)</SPAN></FONT><SPAN=20
                      lang=3DDE><o:p></o:p></SPAN></P>
                      <P><FONT face=3DArial color=3Dblack size=3D2><SPAN =

                      style=3D"FONT-SIZE: 10pt; COLOR: black; =
FONT-FAMILY: Arial">The=20
                      "can" above indicates that they're all optional, =
while=20
                      clearly the application cannot run its course =
without one=20
                      or more of these fields. Here we have a case where =
one=20
                      could have a perfectly compliant implementation =
that=20
                      ignores all these TLVs&#8230;</SPAN></FONT><SPAN=20
                      lang=3DDE><o:p></o:p></SPAN></P>
                      <P><FONT face=3DArial color=3Dblack size=3D2><SPAN =

                      style=3D"FONT-SIZE: 10pt; COLOR: black; =
FONT-FAMILY: Arial">-Woj.</SPAN></FONT>=20
                      <SPAN lang=3DDE><o:p></o:p></SPAN></P>
                      <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: =
12pt"><FONT=20
                      face=3D"Times New Roman" size=3D3><SPAN lang=3DDE=20
                      style=3D"FONT-SIZE: =
12pt"><BR><BR><BR><BR><BR><BR><BR><BR><BR><o:p></o:p></SPAN></FONT></P></=
BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUO=
TE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BOD=
Y></HTML>

------_=_NextPart_001_01C8AFD7.7E33EDD8--

--===============1172968506==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1172968506==--


From ancp-bounces@ietf.org  Wed May  7 00:53:00 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 47E0F28C63D;
	Wed,  7 May 2008 00:48:05 -0700 (PDT)
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 7173F28C6C3
	for <ancp@core3.amsl.com>; Wed,  7 May 2008 00:40:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.165
X-Spam-Level: 
X-Spam-Status: No, score=-6.165 tagged_above=-999 required=5 tests=[AWL=0.433, 
	BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 9kOjFnPHNpKs for <ancp@core3.amsl.com>;
	Wed,  7 May 2008 00:39:10 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id C24093A7107
	for <ancp@ietf.org>; Wed,  7 May 2008 00:32:15 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,446,1204498800"; d="scan'208,217";a="8217067"
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 07 May 2008 09:32:00 +0200
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m477W0UB006323; 
	Wed, 7 May 2008 09:32:00 +0200
Received: from xbh-ams-332.emea.cisco.com (xbh-ams-332.cisco.com
	[144.254.231.87])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m477W0bo025731;
	Wed, 7 May 2008 07:32:00 GMT
Received: from xmb-ams-33b.cisco.com ([144.254.231.86]) by
	xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 7 May 2008 09:31:59 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 7 May 2008 09:31:56 +0200
Message-ID: <D9872168DBD43A41BD71FFC4713274D4050438A2@xmb-ams-33b.emea.cisco.com>
In-Reply-To: <9BD5D7887235424FA97DFC223CAE3C280AB43A61@proton.jnpr.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ANCP] Bulk Transaction Message
thread-index: AcihZWeDZVeOVtxMS1uttRBEffcNEwAVDjfgAEod1tAAAWRvoAMsB4yQAADCZxAAAKZHUAAJVuxQABJPrxA=
References: <D9872168DBD43A41BD71FFC4713274D405043771@xmb-ams-33b.emea.cisco.com>
	<9BD5D7887235424FA97DFC223CAE3C280AB43A61@proton.jnpr.net>
From: "Wojciech Dec (wdec)" <wdec@cisco.com>
To: "Sanjay Wadhwa" <swadhwa@juniper.net>,
	"Peter Arberg" <parberg@redback.com>, <ancp@ietf.org>
X-OriginalArrivalTime: 07 May 2008 07:31:59.0951 (UTC)
	FILETIME=[6FAD1DF0:01C8B014]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=28373; t=1210145520;
	x=1211009520; c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=wdec@cisco.com;
	z=From:=20=22Wojciech=20Dec=20(wdec)=22=20<wdec@cisco.com>
	|Subject:=20RE=3A=20[ANCP]=20Bulk=20Transaction=20Message
	|Sender:=20; bh=AqI8A1AogiZIQ4vwsHu4SS9PBuDPpXOnIAZ0vots4qI=;
	b=GW5a2HExkb1dRe0DKd5PXzz5dZOPOZE/HMiBWwXrgs8yzO8uB4qPuupOa0
	dtUgbEA4xb1Pte0dFHP02EUht9kGA2P3uQLzdi0icK337MBxlJRdyU9n/njC
	Pkz0E6jOhM;
Authentication-Results: ams-dkim-1; header.From=wdec@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
Subject: Re: [ANCP] Bulk Transaction Message
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/pipermail/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>
Content-Type: multipart/mixed; boundary="===============0744551955=="
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0744551955==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8B014.6F851F19"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8B014.6F851F19
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Sanjay,
=20
inline


________________________________

	From: Sanjay Wadhwa [mailto:swadhwa@juniper.net]=20
	Sent: 07 May 2008 02:03
	To: Wojciech Dec (wdec); Peter Arberg; ancp@ietf.org
	Subject: RE: [ANCP] Bulk Transaction Message
=09
=09
	Even with transport being TCP, I see atleast a couple of
benefits:
	=20
	1. If a sender knows it has a bunch of messages to send (e.g.
ANCP adjacency flaps, and all the port-up messages need to re-played),
then bulking by definition allows the application to invoke TCP fewer
times to transmit everything that it needs to transmit, which in a lot
of systems can translate to significant compute and memory efficiency
(specially, if we are considering a large amount of state). This is not
to say one can't realize this in an implementation specific way. =20
	=20
	Woj> Even with bulking one needs to realize the TCP interaction
with some thought. Perhaps bulking indeed offers the opportunity for a
delveloper to think about that, but I seriously doubt that anyone
familar with TCP app development would overlook this aspect in the first
place.
	=20
	However, if neeeded, bulking also has the benefit of affording
optimized acking (e.g. if no error is encountered in proccessing all the
sub-messages in the bundled message, it is possible for the receiver to
send a cummulative ack to the sender rather than individual acks).=20
	=20
	Woj> A cumulatitive ack would appear to be desirable in some
cases, but I see this as very different to the bulk ack currently
described which essenatially carries in bulk all of the individal acks.
The bulking mechanism is quite clear in saying that each ANCP message is
bundled header and all, and acted upon individually by the recipient,
and whether it's a request or an ack is secondary. I'm sure you'll agree
that this is undesirable overhead and complexity for what it's worth,
also in view of the fact that "something" on the recipient side would
need to decide what ack/nack goes into a bulk response and what doesn't.

	Having a cumulatitive ack is an all thogether different thing,
which I would support, and it should not involve the "bulking" of each
indivdual ack, and is an item that for which proposals are welcome.
	=20
	2. Bulking also provides a nice solution if one ever needed to
atomically receive and process *distinct* ANCP message types. =20
	=20
	Woj> There appears to be no such thing; in bulking, presumably
the reciever would have to buffer all the way until the end of the bulk
message, and then process each message individually. This seems rather
overweight when compared to simply sending each message again.
	=20
	What is the downside of having it? It is negotiable as an
optional capability.=20
	=20
	Woj> A couple of reasons come to the fore; i) no body saw a good
reason so far to implement it/use it ii) it's added protocol "stuff"
that has no clear benefit, does not realize any new use-case, does not
optimize much, and in fact as mentioned above it appears to rather have
some downsides such as extra overhead, buffering and delay. Let's now
have the axe fall...
	=20
	Cheers,
	Woj.
	=20
	Cheers
	-Sanjay

		-----Original Message-----
		From: Wojciech Dec (wdec) [mailto:wdec@cisco.com]
		Sent: Tuesday, May 06, 2008 1:24 PM
		To: Sanjay Wadhwa; Peter Arberg; ancp@ietf.org
		Subject: RE: [ANCP] Bulk Transaction Message
	=09
	=09
		Sanjay,
		=20
		can you please present to the WG and myself how bulk
transaction capability is useful in any way in terms of scaling for
example? And by the way, please treat this discussion is orthogonal to
any other.
		=20
		Cheers,
		Woj.
		=20


________________________________

			From: Sanjay Wadhwa [mailto:swadhwa@juniper.net]

			Sent: 06 May 2008 19:08
			To: Wojciech Dec (wdec); Peter Arberg;
ancp@ietf.org
			Subject: RE: [ANCP] Bulk Transaction Message
		=09
		=09
			Woj
			  It is a bad idea to remove bulk-transaction
capability from the draft. On one hand you are trying to add "marginally
useful" extensions (with TLVs), and on the other hand you are arguing
for removing useful abstractions which can help with scaling. If
bulk-transaction capability needs to be augmented or modified, then we
should consider augmenting it, rather than removing it from the draft.
			=20
			Cheers
			-Sanjay

				-----Original Message-----
				From: ancp-bounces@ietf.org
[mailto:ancp-bounces@ietf.org]On Behalf Of Wojciech Dec (wdec)
				Sent: Tuesday, May 06, 2008 12:42 PM
				To: Peter Arberg; ancp@ietf.org
				Subject: Re: [ANCP] Bulk Transaction
Message
			=09
			=09
				Hi Folks,
				=20
				given that no discernable use of Bulk
messaging has been identified, nor there being a good reason for it
given the fact that ANCP is bound to the TCP transport (or equivalent),
I would like to propose to remove all of the text relating to this
capability and associated message from the protocol spec draft.
				=20
				Regards,
				Woj.


________________________________

				From: ancp-bounces@ietf.org
[mailto:ancp-bounces@ietf.org] On Behalf Of Wojciech Dec (wdec)
				Sent: 20 April 2008 15:18
				To: Peter Arberg; ancp@ietf.org
				Subject: Re: [ANCP] Bulk Transaction
Message
			=09
			=09
				Should also have added: Given that
currently the bulk message does not appear to have had any practical
adoption, having the DTeam adopt it/modify it, or possibly have it
removed from the spec all together are all valid options.
				=20
				-Woj.


________________________________

				From: ancp-bounces@ietf.org
[mailto:ancp-bounces@ietf.org] On Behalf Of Wojciech Dec (wdec)
				Sent: 20 April 2008 14:39
				To: Peter Arberg; ancp@ietf.org
				Subject: Re: [ANCP] Bulk Transaction
Message
			=09
			=09
				It's all simple:
				- the Design Team is looking at the
possibility of using this message
				- the message in its current form does
not appear to be terribly useful, and could be removed from the spec.
				=20
				-Woj.
				=20


________________________________

				From: ancp-bounces@ietf.org
[mailto:ancp-bounces@ietf.org] On Behalf Of Peter Arberg
				Sent: 19 April 2008 03:07
				To: Wojciech Dec (wdec); ancp@ietf.org
				Subject: Re: [ANCP] Bulk Transaction
Message
			=09
			=09
				Hi Woj,
				=20
				can you give a little background to why
you are looking for vendor
				implementation support for this specific
capability & message ?
				=20
				thanks,
				Peter


________________________________

				From: ancp-bounces@ietf.org
[mailto:ancp-bounces@ietf.org] On Behalf Of Wojciech Dec (wdec)
				Sent: 18. april 2008 08:04
				To: ancp@ietf.org
				Subject: [ANCP] Bulk Transaction Message
			=09
			=09

				Hi Folks,=20

				Could you please let me/us know if you
currently have an implementation of ANCP that supports the Bulk
Transaction Capability and Message?

				Thanks,=20
				Woj.=20


------_=_NextPart_001_01C8B014.6F851F19
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Bulk Transaction Message</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3314" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D395133206-07052008><FONT =
face=3DArial=20
size=3D2>Sanjay,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D395133206-07052008><FONT =
face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D395133206-07052008><FONT =
face=3DArial=20
size=3D2>inline</FONT></SPAN></DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Sanjay Wadhwa=20
  [mailto:swadhwa@juniper.net] <BR><B>Sent:</B> 07 May 2008 =
02:03<BR><B>To:</B>=20
  Wojciech Dec (wdec); Peter Arberg; ancp@ietf.org<BR><B>Subject:</B> =
RE: [ANCP]=20
  Bulk Transaction Message<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D155264721-06052008>Even=20
  with transport being TCP, I see atleast a couple of=20
  benefits:</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D155264721-06052008></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT color=3D#0000ff><SPAN class=3D155264721-06052008><FONT =
face=3DArial><FONT=20
  size=3D2>1. If a&nbsp;sender knows it has a bunch of messages to send =
(e.g. ANCP=20
  adjacency flaps, and all the port-up messages need to re-played), then =
bulking=20
  by definition&nbsp;allows the application to invoke TCP fewer times to =

  transmit&nbsp;everything that it needs to transmit, which&nbsp;in a =
lot of=20
  systems can translate to significant&nbsp;compute and memory =
efficiency=20
  (specially, if we are considering a large amount of state). =
This&nbsp;is not=20
  to say one can't&nbsp;realize this&nbsp;in an implementation specific=20
  way.&nbsp;<SPAN class=3D395133206-07052008><FONT=20
  color=3D#000000>&nbsp;</FONT></SPAN></FONT></FONT></SPAN></FONT></DIV>
  <DIV><FONT color=3D#0000ff><SPAN class=3D155264721-06052008><FONT =
face=3DArial><FONT=20
  size=3D2><SPAN=20
  =
class=3D395133206-07052008></SPAN></FONT></FONT></SPAN></FONT>&nbsp;</DIV=
>
  <DIV><FONT size=3D+0><SPAN class=3D155264721-06052008><FONT =
face=3DArial><FONT=20
  size=3D2><SPAN class=3D395133206-07052008>Woj&gt; Even with bulking =
one needs to=20
  realize the TCP interaction with some thought. Perhaps bulking=20
  indeed&nbsp;offers the opportunity for a delveloper to think about =
that, but I=20
  seriously doubt that anyone familar with TCP app =
development&nbsp;would=20
  overlook this aspect in the first=20
  place.</SPAN></FONT></FONT></SPAN></FONT></DIV>
  <DIV><FONT color=3D#0000ff><SPAN class=3D155264721-06052008><FONT =
face=3DArial><FONT=20
  size=3D2><SPAN=20
  =
class=3D395133206-07052008></SPAN></FONT></FONT></SPAN></FONT>&nbsp;</DIV=
>
  <DIV><FONT color=3D#0000ff><SPAN class=3D155264721-06052008><FONT =
face=3DArial><FONT=20
  size=3D2>However,&nbsp;if neeeded, bulking also&nbsp;has the benefit =
of=20
  affording optimized acking (e.g. if no error is encountered in =
proccessing all=20
  the sub-messages in the bundled message, it&nbsp;is possible&nbsp;for =
the=20
  receiver to send a cummulative ack to the sender rather than =
individual=20
  acks).<SPAN class=3D395133206-07052008><FONT=20
  color=3D#000000>&nbsp;</FONT></SPAN></FONT></FONT></SPAN></FONT></DIV>
  <DIV><FONT color=3D#0000ff><SPAN class=3D155264721-06052008><FONT =
face=3DArial><FONT=20
  size=3D2><SPAN=20
  =
class=3D395133206-07052008></SPAN></FONT></FONT></SPAN></FONT>&nbsp;</DIV=
>
  <DIV><FONT color=3D#0000ff><SPAN class=3D155264721-06052008><FONT =
face=3DArial><FONT=20
  size=3D2><SPAN class=3D395133206-07052008><FONT =
color=3D#000000>Woj&gt;&nbsp;A=20
  cumulatitive ack would appear to be desirable in some cases, but I see =
this as=20
  very&nbsp;different to the&nbsp;bulk ack currently described which=20
  essenatially carries in bulk all of the individal acks.&nbsp;The =
bulking=20
  mechanism is quite clear in saying that each ANCP message </FONT><FONT =

  color=3D#000000>is&nbsp;bundled header and all, and acted upon =
individually by=20
  the recipient, and whether it's a request or an ack is secondary. I'm =
sure=20
  you'll agree that this is undesirable overhead and complexity for what =
it's=20
  worth, also in view of the fact that "something" on the recipient side =
would=20
  need to decide what ack/nack goes into a bulk response and what =
doesn't.=20
  </FONT></SPAN></FONT></FONT></SPAN></FONT></DIV>
  <DIV><FONT color=3D#0000ff><SPAN class=3D155264721-06052008><FONT =
face=3DArial><FONT=20
  size=3D2><SPAN class=3D395133206-07052008><FONT color=3D#000000>Having =
a=20
  cumulatitive ack is an all thogether different thing, which I=20
  would&nbsp;support, and it should not involve the "bulking" of each =
indivdual=20
  ack, and is an item that&nbsp;for which&nbsp;proposals are=20
  welcome.</FONT></SPAN></FONT></FONT></SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D155264721-06052008></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT color=3D#0000ff><SPAN class=3D155264721-06052008><FONT =
face=3DArial><FONT=20
  size=3D2>2. Bulking also provides a nice solution if one&nbsp;ever =
needed to=20
  atomically receive and process *distinct* ANCP message =
types.&nbsp;<SPAN=20
  class=3D395133206-07052008><FONT=20
  color=3D#000000>&nbsp;</FONT></SPAN></FONT></FONT></SPAN></FONT></DIV>
  <DIV><FONT color=3D#0000ff><SPAN class=3D155264721-06052008><FONT =
face=3DArial><FONT=20
  size=3D2><SPAN=20
  =
class=3D395133206-07052008></SPAN></FONT></FONT></SPAN></FONT>&nbsp;</DIV=
>
  <DIV><FONT color=3D#0000ff><SPAN class=3D155264721-06052008><FONT =
face=3DArial><FONT=20
  size=3D2><SPAN class=3D395133206-07052008><FONT =
color=3D#000000>Woj&gt;&nbsp;There=20
  appears to be no such thing; in bulking, presumably the reciever would =
have to=20
  buffer all the way until the end of the bulk message, and then process =
each=20
  message individually. This seems rather overweight when compared to =
simply=20
  sending each message =
again.</FONT></SPAN></FONT></FONT></SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D155264721-06052008></SPAN></FONT><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2><SPAN class=3D155264721-06052008></SPAN></FONT><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2><SPAN =
class=3D155264721-06052008></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT color=3D#0000ff><SPAN class=3D155264721-06052008><FONT =
face=3DArial><FONT=20
  size=3D2>What is the downside of having it? It is&nbsp;negotiable as =
an optional=20
  capability.<SPAN class=3D395133206-07052008><FONT=20
  color=3D#000000>&nbsp;</FONT></SPAN></FONT></FONT></SPAN></FONT></DIV>
  <DIV><FONT color=3D#0000ff><SPAN class=3D155264721-06052008><FONT =
face=3DArial><FONT=20
  size=3D2><SPAN=20
  =
class=3D395133206-07052008></SPAN></FONT></FONT></SPAN></FONT>&nbsp;</DIV=
>
  <DIV><FONT color=3D#0000ff><SPAN class=3D155264721-06052008><FONT =
face=3DArial><FONT=20
  size=3D2><SPAN class=3D395133206-07052008><FONT =
color=3D#000000>Woj&gt; A couple of=20
  reasons come to the fore; i) no body saw a good reason so far to =
implement=20
  it/use it ii) it's added protocol "stuff" that has no clear benefit, =
does not=20
  realize any new use-case,&nbsp;does not optimize much, and in fact as=20
  mentioned above it appears to rather have some downsides such as extra =

  overhead, buffering and delay. Let's now have the axe=20
  fall...</FONT></SPAN></FONT></FONT></SPAN></FONT></DIV>
  <DIV><FONT color=3D#0000ff><SPAN class=3D155264721-06052008><FONT =
face=3DArial><FONT=20
  color=3D#000000 size=3D2><SPAN=20
  =
class=3D395133206-07052008></SPAN></FONT></FONT></SPAN></FONT>&nbsp;</DIV=
>
  <DIV><FONT color=3D#0000ff><SPAN class=3D155264721-06052008><FONT =
face=3DArial><FONT=20
  color=3D#000000 size=3D2><SPAN=20
  =
class=3D395133206-07052008>Cheers,</SPAN></FONT></FONT></SPAN></FONT></DI=
V>
  <DIV><FONT color=3D#0000ff><SPAN class=3D155264721-06052008><FONT =
face=3DArial><FONT=20
  color=3D#000000 size=3D2><SPAN=20
  =
class=3D395133206-07052008>Woj.</SPAN></FONT></FONT></SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D155264721-06052008></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D155264721-06052008>Cheers</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D155264721-06052008>-Sanjay</SPAN></FONT></DIV>
  <BLOCKQUOTE dir=3Dltr=20
  style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
    <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
    size=3D2>-----Original Message-----<BR><B>From:</B> Wojciech Dec =
(wdec)=20
    [mailto:wdec@cisco.com]<BR><B>Sent:</B> Tuesday, May 06, 2008 1:24=20
    PM<BR><B>To:</B> Sanjay Wadhwa; Peter Arberg;=20
    ancp@ietf.org<BR><B>Subject:</B> RE: [ANCP] Bulk Transaction=20
    Message<BR><BR></FONT></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D967002017-06052008><FONT =
face=3DArial=20
    size=3D2>Sanjay,</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D967002017-06052008><FONT =
face=3DArial=20
    size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D967002017-06052008><FONT =
face=3DArial=20
    size=3D2>can you please present to the WG and myself how bulk =
transaction=20
    capability is useful in any way in terms of scaling for example? And =
by the=20
    way, please treat this discussion is orthogonal to any=20
    other.</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D967002017-06052008><FONT =
face=3DArial=20
    size=3D2></FONT></SPAN>&nbsp;</DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D967002017-06052008><FONT =
face=3DArial=20
    size=3D2>Cheers,</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D967002017-06052008><FONT =
face=3DArial=20
    size=3D2>Woj.</FONT></SPAN></DIV>
    <DIV dir=3Dltr align=3Dleft><SPAN class=3D967002017-06052008><FONT =
face=3DArial=20
    size=3D2></FONT></SPAN>&nbsp;</DIV><BR>
    <BLOCKQUOTE dir=3Dltr=20
    style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 =
2px solid; MARGIN-RIGHT: 0px">
      <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
      <HR tabIndex=3D-1>
      <FONT face=3DTahoma size=3D2><B>From:</B> Sanjay Wadhwa=20
      [mailto:swadhwa@juniper.net] <BR><B>Sent:</B> 06 May 2008=20
      19:08<BR><B>To:</B> Wojciech Dec (wdec); Peter Arberg;=20
      ancp@ietf.org<BR><B>Subject:</B> RE: [ANCP] Bulk Transaction=20
      Message<BR></FONT><BR></DIV>
      <DIV></DIV>
      <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
      class=3D093250117-06052008>Woj</SPAN></FONT></DIV>
      <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
      class=3D093250117-06052008>&nbsp; It is a bad idea to remove=20
      bulk-transaction capability from the draft. On one hand you are =
trying to=20
      add "marginally useful" extensions (with TLVs), and on the other =
hand you=20
      are arguing for removing useful abstractions which can help with =
scaling.=20
      </SPAN></FONT><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
      class=3D093250117-06052008>If bulk-transaction capability needs to =
be=20
      augmented or modified, then we should consider augmenting it, =
rather than=20
      removing it from the draft.</SPAN></FONT></DIV>
      <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
      class=3D093250117-06052008></SPAN></FONT>&nbsp;</DIV>
      <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
      class=3D093250117-06052008>Cheers</SPAN></FONT></DIV>
      <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
      class=3D093250117-06052008>-Sanjay</SPAN></FONT></DIV>
      <BLOCKQUOTE dir=3Dltr=20
      style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff =
2px solid; MARGIN-RIGHT: 0px">
        <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
        size=3D2>-----Original Message-----<BR><B>From:</B> =
ancp-bounces@ietf.org=20
        [mailto:ancp-bounces@ietf.org]<B>On Behalf Of </B>Wojciech Dec=20
        (wdec)<BR><B>Sent:</B> Tuesday, May 06, 2008 12:42 =
PM<BR><B>To:</B>=20
        Peter Arberg; ancp@ietf.org<BR><B>Subject:</B> Re: [ANCP] Bulk=20
        Transaction Message<BR><BR></FONT></DIV>
        <DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
        class=3D811403916-06052008>Hi Folks,</SPAN></FONT></DIV>
        <DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
        class=3D811403916-06052008></SPAN></FONT>&nbsp;</DIV>
        <DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
        class=3D811403916-06052008>given that no discernable use of Bulk =
messaging=20
        has been identified, nor&nbsp;there being a good reason for it =
given the=20
        fact that ANCP is bound to the TCP transport (or =
equivalent),&nbsp;I=20
        would like to propose to remove all of the text relating to this =

        capability and associated message from the protocol spec=20
        draft.</SPAN></FONT></DIV>
        <DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
        class=3D811403916-06052008></SPAN></FONT>&nbsp;</DIV>
        <DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
        class=3D811403916-06052008>Regards,</SPAN></FONT></DIV>
        <DIV dir=3Dltr align=3Dleft><FONT face=3DArial size=3D2><SPAN=20
        class=3D811403916-06052008>Woj.</SPAN></FONT></DIV><BR>
        <BLOCKQUOTE dir=3Dltr=20
        style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: =
#000000 2px solid; MARGIN-RIGHT: 0px">
          <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
          <HR tabIndex=3D-1>
          <FONT face=3DTahoma size=3D2><B>From:</B> =
ancp-bounces@ietf.org=20
          [mailto:ancp-bounces@ietf.org] <B>On Behalf Of </B>Wojciech =
Dec=20
          (wdec)<BR><B>Sent:</B> 20 April 2008 15:18<BR><B>To:</B> Peter =
Arberg;=20
          ancp@ietf.org<BR><B>Subject:</B> Re: [ANCP] Bulk Transaction=20
          Message<BR></FONT><BR></DIV>
          <DIV></DIV>
          <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D490440813-20042008><FONT=20
          face=3DArial size=3D2>Should also have added: Given that=20
          currently&nbsp;the bulk message does not appear to have had =
any=20
          practical&nbsp;adoption, having the DTeam adopt it/modify it, =
or=20
          possibly have it removed from the spec all together&nbsp;are =
all valid=20
          options.</FONT></SPAN></DIV>
          <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D490440813-20042008><FONT=20
          face=3DArial size=3D2></FONT></SPAN>&nbsp;</DIV>
          <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D490440813-20042008><FONT=20
          face=3DArial size=3D2>-Woj.</FONT></SPAN></DIV><BR>
          <BLOCKQUOTE dir=3Dltr=20
          style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: =
#000000 2px solid; MARGIN-RIGHT: 0px">
            <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
            <HR tabIndex=3D-1>
            <FONT face=3DTahoma size=3D2><B>From:</B> =
ancp-bounces@ietf.org=20
            [mailto:ancp-bounces@ietf.org] <B>On Behalf Of </B>Wojciech =
Dec=20
            (wdec)<BR><B>Sent:</B> 20 April 2008 14:39<BR><B>To:</B> =
Peter=20
            Arberg; ancp@ietf.org<BR><B>Subject:</B> Re: [ANCP] Bulk =
Transaction=20
            Message<BR></FONT><BR></DIV>
            <DIV></DIV>
            <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D668522812-20042008><FONT=20
            face=3DArial size=3D2>It's all simple:</FONT></SPAN></DIV>
            <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D668522812-20042008><FONT=20
            face=3DArial size=3D2>-&nbsp;the Design Team is looking at =
the=20
            possibility of using this message</FONT></SPAN></DIV>
            <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D668522812-20042008><FONT=20
            face=3DArial size=3D2>- the message in its current form does =
not appear=20
            to be terribly useful, and could be&nbsp;removed from the=20
            spec.</FONT></SPAN></DIV>
            <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D668522812-20042008><FONT=20
            face=3DArial size=3D2></FONT></SPAN>&nbsp;</DIV>
            <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D668522812-20042008><FONT=20
            face=3DArial size=3D2>-Woj.</FONT></SPAN></DIV>
            <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D668522812-20042008><FONT=20
            face=3DArial size=3D2></FONT></SPAN>&nbsp;</DIV><BR>
            <BLOCKQUOTE dir=3Dltr=20
            style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: =
#000000 2px solid; MARGIN-RIGHT: 0px">
              <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
              <HR tabIndex=3D-1>
              <FONT face=3DTahoma size=3D2><B>From:</B> =
ancp-bounces@ietf.org=20
              [mailto:ancp-bounces@ietf.org] <B>On Behalf Of </B>Peter=20
              Arberg<BR><B>Sent:</B> 19 April 2008 03:07<BR><B>To:</B> =
Wojciech=20
              Dec (wdec); ancp@ietf.org<BR><B>Subject:</B> Re: [ANCP] =
Bulk=20
              Transaction Message<BR></FONT><BR></DIV>
              <DIV></DIV>
              <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D197410601-19042008><FONT=20
              face=3DArial color=3D#0000ff size=3D2>Hi =
Woj,</FONT></SPAN></DIV>
              <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D197410601-19042008><FONT=20
              face=3DArial color=3D#0000ff =
size=3D2></FONT></SPAN>&nbsp;</DIV>
              <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D197410601-19042008><FONT=20
              face=3DArial color=3D#0000ff size=3D2>can you give a =
little background=20
              to why you are looking for vendor</FONT></SPAN></DIV>
              <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D197410601-19042008><FONT=20
              face=3DArial color=3D#0000ff size=3D2>implementation =
support for this=20
              specific capability &amp; message ?</FONT></SPAN></DIV>
              <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D197410601-19042008><FONT=20
              face=3DArial color=3D#0000ff =
size=3D2></FONT></SPAN>&nbsp;</DIV>
              <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D197410601-19042008><FONT=20
              face=3DArial color=3D#0000ff =
size=3D2>thanks,</FONT></SPAN></DIV>
              <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D197410601-19042008><FONT=20
              face=3DArial color=3D#0000ff =
size=3D2>Peter</FONT></SPAN></DIV><BR>
              <BLOCKQUOTE dir=3Dltr=20
              style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: =
#0000ff 2px solid; MARGIN-RIGHT: 0px">
                <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
                <HR tabIndex=3D-1>
                <FONT face=3DTahoma size=3D2><B>From:</B> =
ancp-bounces@ietf.org=20
                [mailto:ancp-bounces@ietf.org] <B>On Behalf Of =
</B>Wojciech Dec=20
                (wdec)<BR><B>Sent:</B> 18. april 2008 =
08:04<BR><B>To:</B>=20
                ancp@ietf.org<BR><B>Subject:</B> [ANCP] Bulk Transaction =

                Message<BR></FONT><BR></DIV>
                <DIV></DIV><!-- Converted from text/rtf format -->
                <P><SPAN lang=3Den-gb><FONT face=3DArial size=3D2>Hi=20
                Folks,</FONT></SPAN> </P>
                <P><SPAN lang=3Den-gb><FONT face=3DArial size=3D2>Could =
you please let=20
                me/us know if you currently have an implementation of =
ANCP that=20
                supports the Bulk Transaction Capability and=20
                Message?</FONT></SPAN></P>
                <P><SPAN lang=3Den-gb><FONT face=3DArial=20
                size=3D2>Thanks,</FONT></SPAN> <BR><SPAN =
lang=3Den-gb><FONT=20
                face=3DArial size=3D2>Woj.</FONT></SPAN><SPAN =
lang=3Den-us></SPAN>=20
              =
</P></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BL=
OCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C8B014.6F851F19--

--===============0744551955==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============0744551955==--


From ancp-bounces@ietf.org  Wed May  7 05:14:25 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7D78A28C5FD;
	Wed,  7 May 2008 05:14:25 -0700 (PDT)
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 C18E23A68C0
	for <ancp@core3.amsl.com>; Wed,  7 May 2008 05:14:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.773
X-Spam-Level: 
X-Spam-Status: No, score=-2.773 tagged_above=-999 required=5
	tests=[AWL=-3.176, BAYES_00=-2.599, HTML_MESSAGE=0.001,
	HTML_OBFUSCATE_05_10=0.001, J_BACKHAIR_21=1, J_BACKHAIR_22=1,
	J_BACKHAIR_23=1, J_BACKHAIR_24=1, J_BACKHAIR_25=1, J_BACKHAIR_26=1,
	J_BACKHAIR_27=1, RCVD_IN_DNSWL_MED=-4]
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 TvewWIJDCqTO for <ancp@core3.amsl.com>;
	Wed,  7 May 2008 05:14:19 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id 6CAF328C5FD
	for <ancp@ietf.org>; Wed,  7 May 2008 05:14:15 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,448,1204498800"; d="scan'208,217";a="8257060"
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 07 May 2008 14:14:11 +0200
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m47CEBW7008951; 
	Wed, 7 May 2008 14:14:11 +0200
Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com
	[144.254.231.71])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m47CEBKf005495;
	Wed, 7 May 2008 12:14:11 GMT
Received: from xmb-ams-33b.cisco.com ([144.254.231.86]) by
	xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 7 May 2008 14:14:11 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 7 May 2008 14:13:57 +0200
Message-ID: <D9872168DBD43A41BD71FFC4713274D405043B12@xmb-ams-33b.emea.cisco.com>
In-Reply-To: <BAC301C0C1697C4EBDF97C805A273CBC9909C5@esealmw104.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ANCP] question regarding  Labels in ANCP port up messages
thread-index: Aciqkn5nSPBPuwuySsamcvxF1uU6kQAZ9dQQAAE415AABe3TAABN80lQAA1w7OAAutMtAAAtn1MQ
References: <48C276B536524E478C659685995F6AA539DBBBE370@RBSJX.ad.redback.com><9BD5D7887235424FA97DFC223CAE3C280AB43A10@proton.jnpr.net><48C276B536524E478C659685995F6AA539DBBBE577@RBSJX.ad.redback.com><9BD5D7887235424FA97DFC223CAE3C28102EB5AA@proton.jnpr.net>
	<48C276B536524E478C659685995F6AA539DBBBEF99@RBSJX.ad.redback.com>
	<BAC301C0C1697C4EBDF97C805A273CBC9909C5@esealmw104.eemea.ericsson.se>
From: "Wojciech Dec (wdec)" <wdec@cisco.com>
To: "Ole Helleberg Andersen" <ole.helleberg.andersen@ericsson.com>,
	"Peter Arberg" <parberg@redback.com>,
	"Sanjay Wadhwa" <swadhwa@juniper.net>, "Tina TSOU" <tena@huawei.com>,
	"Maglione Roberta" <roberta.maglione@telecomitalia.it>
X-OriginalArrivalTime: 07 May 2008 12:14:11.0822 (UTC)
	FILETIME=[DBDB98E0:01C8B03B]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=176767; t=1210162452;
	x=1211026452; c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=wdec@cisco.com;
	z=From:=20=22Wojciech=20Dec=20(wdec)=22=20<wdec@cisco.com>
	|Subject:=20RE=3A=20[ANCP]=20question=20regarding=20=20Labe
	ls=20in=20ANCP=20port=20up=20messages |Sender:=20;
	bh=ABgH0HdnCGHt1/IS4W+MeKD/g9lOFy4DtMpITc3swFE=;
	b=rFaHgsU1xPBeh8JbLF8vXHxd3wFk2WCxe968F8LmtwEFolZWsMUk5OgS3M
	GDkuTXwqBfLDL7u9k59+NG/FvFc9ieQuebCdXVqB/PPzDa+dr2PmoKQOIYbM
	3mMwcyMzZ2;
Authentication-Results: ams-dkim-1; header.From=wdec@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
Cc: ancp@ietf.org
Subject: Re: [ANCP] question regarding  Labels in ANCP port up messages
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/pipermail/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>
Content-Type: multipart/mixed; boundary="===============1157695667=="
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1157695667==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8B03B.DB96000F"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8B03B.DB96000F
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi All,
=20
it's with a certain amount of incredulity that I view the proposals on
this thread for changing the version number of the protocol. Were such
proposals to be accepted, by definition it would make most likely the
ANCP draft incompatible with *all* current implementations, or at the
very least introduce a compatibility mess in existing deployments short
of a flag day change over, not to mention the issue of depreciating the
old version.
There really seems to be no reason to go through with a version change
due to what may be attributed as a day 1 draft problem but *not* a day 1
implementation problem. Also, it is not the first time that the protocol
spec draft has had some inaccuracies, and we've visited this aspect
previously resulting in the following versioning strategy being laid
out: http://www.ietf.org/mail-archive/web/ancp/current/msg00152.html .
While the strategy states that an ANCP version change will not be
considered due to "incompatibilities arising from implementations of
pre-RFC drafts", neither does it state that the draft cannot change to
reflect current implementations while keeping the version.
=20
Now, given that there seems to be some uneasiness (but thankfully not
absolute) in the WG to come forward publicly with details of what is
currently implemented, I have conducted a behind the scenes
investigation of sorts, and present the summarized findings below:
- There are 10 distinct implementations of ANCP
- Out of these 9 either directly implement the label field format in as
per section 5.3 of draft-gsmpv3-base-spec-08, or each is known to be
compatible with at least 2 implementations that do so. By association,
it seems reasonable to claim that all of these ANCP implementations use
the draft-gsmpv3-base-spec-08 format. Also, all use version 3.1 as the
protocol version, and the base protocol header also as per
draft-gsmpv3-base-spec-08=20
- One implementation is known to use the draft-ietf-ancp-protocol-02
format of the label field format, ie the rfc3292 format. This
implementation is not known to be compatible with any of the others.
=20
Based on this, but not only, the obvious answer to the problem is *not*
to do a version change, but rather fix the draft. Granted, this is a far
from ideal situation for the one implementation affected, and it's a
true shame that the problem wasn't spotted earlier. Like Peter I also
wonder how any interop was achieved, but the fact that it is there is a
significant one that should not be undone by hasty version changes. As
such option 2 below is not one we'll be taking forward. Option 1 however
also comes short as it does not quite follow the logic of simply
documenting what is known to be interoperable in the WG draft. If
specific implementations choose to realize knobs or other, fine, but
this is not part of the protocol spec, and there is no such thing as
"old label format". Please do consider the third option, ie fixing the
draft to reflect what is already done.
=20
This fact in general highlights the problems we're having in carrying
with the GSMPv3 (rfc3292) legacy, alongside adopted amendments from
draft-gsmpv3-base-spec (this Label issue not being the only adopted
item), alongside new protocol work. I trust that all of you agree that
getting maximum clarity on all the legacy issues and dependencies in the
protocol spec is in the WG's best interest, and that we are still some
way off from that. As such I also expect the WG to support
moves/proposals aimed at getting that clarity, with resolving this issue
being not the first and not the last such move.
=20
Regards,
Woj.
=20
=20
=20


________________________________

	From: Ole Helleberg Andersen
[mailto:ole.helleberg.andersen@ericsson.com]=20
	Sent: 06 May 2008 14:04
	To: Peter Arberg; Sanjay Wadhwa; Tina TSOU; Maglione Roberta;
Wojciech Dec (wdec)
	Cc: ancp@ietf.org
	Subject: RE: [ANCP] question regarding Labels in ANCP port up
messages
=09
=09
	Hi All,
	=20
=09
	I think the main issue is to ensure interoperability with
existing implementations, and to allow for upgrading nodes that are
already in service to a WG-draft compliant version. To do that in a
manageable way we must allow for version negotiation per adjacency. We
therefore need to change the WG-draft as suggested by Sanjay in his
option 2.
	=20
	Concerning the encoding issue I prefer to make the WG-draft in
line with existing implementations. However, if the WG decides to change
it, differences in this encoding would also be solved by choosing
Sanjay's option 2.
	=20
	Cheers,
	Ole

________________________________

	From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On
Behalf Of Peter Arberg
	Sent: 2. maj 2008 20:52
	To: Sanjay Wadhwa; Tina TSOU; Maglione Roberta; Wojciech Dec
(wdec)
	Cc: ancp@ietf.org
	Subject: Re: [ANCP] question regarding Labels in ANCP port up
messages
=09
=09
	Hi Sanjay,
	=20
	yes apparently I missed your point in the last email, but I'm
glad we agree something is needed
	to make existing ANCP implementations and the current draft to
co-exist.
	=20
	I do not like your option 1) as if you need a config knob for
interoperability, it is too easy to
	get into trouble.
	=20
	I think option 2) is the best way forward with the differences
already identified, or we can=20
	continue to get a show of hands of ANCP implementations, and see
if anyone is actually
	deployed based on the WG-draft.
	=20
	There is no beneficial reasons to base the event-message of
RFC3292, it could as well be a message
	described bit by bit in the ANCP draft, and then we can keep the
label space at 8 as many
	implementations alreday do.
	=20
	cheers,
	Peter
	=20
	=20
	=20


________________________________

		From: Sanjay Wadhwa [mailto:swadhwa@juniper.net]=20
		Sent: 2. maj 2008 05:35
		To: Peter Arberg; Tina TSOU; Maglione Roberta; Wojciech
Dec (wdec)
		Cc: ancp@ietf.org
		Subject: RE: [ANCP] question regarding Labels in ANCP
port up messages
	=09
	=09

		Peter

		 You missed my point below. The ANCP draft since
becoming a WG draft does NOT refer to the old GSMP drafts. Any
implementations based on this WG-draft are expected to be interoperable.
You are pointing to pre-WG-draft versions of ANCP, and these were indeed
based on expired GSMP drafts that evolved past RFC3292.=20

		There is incompatibility between the current ANCP
WG-draft and previous non-WG versions (TLV clash, label format..). As
mentioned earlier it is prudent for older implementations to start
supporting the WG-draft version as soon as possible.=20

		=20

		For interoperability of WG-draft with the older pre-WG
versions, I see the following options:

		=20

		1. Versioning starts with the WG-draft i.e. WG-draft is
version =3D 3, sub-version =3D 1. For any interop issues between older
non-WG versions and the WG-draft, one needs to look at solving it within
implementations (e.g. an AN that implements the WG-draft, could based on
a configuration knob, generate a PORT-UP message with old label format
the will be accepted by BNG implementing pre-WG versions of the draft).=20

		=20

		2. Change the WG-draft (current draft) to use version =3D
3 and sub-version =3D 2. This is assuming there is no deployed
implementation of current WG-draft that already uses 3.1 as the version,
and also assuming the old pre-WG implementations use 3.1. There will be
no backwards compatibility i.e. version 3.1 BNG will not work with
version 3.2 AN (we will need to list this as caveat in the appendix
section). AN and BNG will need to negotiate the same version in order
for ANCP adjacency to come up. A BNG supporting both versions 3.1 and
3.2 could simultaneously become adjacent with one AN supporting 3.1 and
another AN supporting 3.2. (i.e. version compatibility is per
adjacency).

		Also, major version number change (e.g. from 3 to 4)
should only correspond to a major change in the protocol (e.g. different
mechanism, different transport etc).

		=20

		My vote would be to adopt option 2 above only if further
changes to WG-draft happen that render it incompatible with the current
WG-draft. Any interoperability issues with pre-WG versions could be
handled via option 1.

		=20

		Cheers

		-Sanjay

		=20

	=09
________________________________


		From: Peter Arberg [mailto:parberg@redback.com]=20
		Sent: Wednesday, April 30, 2008 7:20 PM
		To: Sanjay Wadhwa; Tina TSOU; Maglione Roberta; Wojciech
Dec (wdec)
		Cc: ancp@ietf.org
		Subject: RE: [ANCP] question regarding Labels in ANCP
port up messages

		=20

		Sanjay,

		=20

		What do you mean "why I reference an old draft"
????????????

		=20

		I'm surprised you even ask...  please take a look at
YOUR own internet-draft that most

		of the ANCP working implementations are based on, in
case you do not have this old

		internet-draft, I have attached it to the document.

		=20

		If you look at the reference for this ancp-draft, you
will see that in the reference section

		you point to this old gsmp-draft...  Yes and I know this
has been changed in the later

		versions of the ANCP draft, but that do not change the
fact that many of the implementations

		today was developed when the attached draft was current.

		=20

		I think a very good question is brought up here, and
that is what is implemented and

		running in networks today ?

		=20

		My take on this is that when the reference was change
from the old gsmp-draft to the older

		RFC3292, apparently no one paid any attention to the
fact the label definition in the event

		message was different and not compatible.

		=20

		What current implementations do today is an important
factor in this discussion, and I think

		it is time to come to realization that we might need a
new version number for ANCP since

		it continues to look like there is big holes open for
interpretation. So if I did a ANCP

		implementation there is bound to be interoperability
issues with existing implementations

		runnig.

		=20

		cheers,

		Peter

		=20

		=20

		=20

			=20

		=09
________________________________


			From: Sanjay Wadhwa [mailto:swadhwa@juniper.net]

			Sent: 30. april 2008 14:42
			To: Peter Arberg; Tina TSOU; Maglione Roberta;
Wojciech Dec (wdec)
			Cc: ancp@ietf.org
			Subject: RE: [ANCP] question regarding Labels in
ANCP port up messages

			Peter
			  The ANCP draft as it currently stands is based
on RFC3292. It provides extensions and modifications to relevant
constructs in RFC3292. There is no mention (implicit or explicit) of
expired GSMP drafts in the ANCP draft. In order to implement the ANCP
draft, I am not sure why one would look at the expired GSMP drafts. Do
you see a reason to do this based on anything that you read in the ANCP
draft? Bringing up reference to expired gsmp draft in this thread just
adds to the confusion. For GSMPv3 objects in the messages (such as Label
Type), one has to look at RFC3292 (this is clearly stated in the ANCP
draft - section 2 and I am quoting it below) :

			ANCP uses a subset of GSMPv3 messages to
implement currently defined use-cases. These relevant GSMPv3 messages
are identified in section 5. GSMPv3 procedures with suitable extensions,
as used by ANCP, are described in sections 5.1, 5.2 and 5.3. GSMPv3
general extensions and GSMPv3 message specific extensions required by
ANCP are described in sub-sections of 5.4. In addition to specifying
extensions and modifications to relevant GSMP messages applicable to
ANCP, this draft also defines the usage of these messages by ANCP, and
indicates the values that ANCP should set for relevant fields in these
GSMP messages. However, to understand the basic semantics of various
fields in GSMP messages, the reader is referred to [4]. =3D> RFC 3292.
		=09
			What existing implementations currently do is an
important but separate issue. These implementations for most part
precede the current ANCP draft. It is fine to poll where these
implementations diverge from the current draft. It is then upto the
implementations (including the one that I am somewhat familiar with) to
work towards compliance with the draft.=20

			On the following points from  Woj:

			Woj>2) The current version of the spec is not
accurate, and does not reflect the fact that the known implementations
follow the label field definition from draft-gsmpv3-base-spec.

			It is not for the protocol draft to point out
what current implementations do.  The best we can do is to further
clarify in the draft that type and value fields of the Label object
(defined in RFC3292) should be set to 0 in the port-up message (we
already mention the lable object as a whole should be set to all 0s).=20

			Woj> This would be a good thing for the WG to
discuss. There most evidently is a fair amount of "dead wood" in the
current spec, ie stuff that nobody yet implements or cares about.  In
the former case, we could re-cast that material using the new
notions/extensions, in the latter case simply chop it out.

			I agree. We are based on GSMPv3 (RFC3292)
messages, and obviously not everything in these messages is leveraged by
ANCP.  However, the sync rate and OAM uses-cases are implemented and in
use (ideally we should leave these alone...i.e. no change beyond adding
more clarity if needed). For anything new (such as multicast) we are
defining new messages (no legacy). =20

			-Sanjay
		=09
			>-----Original Message-----
			>From: Peter Arberg [mailto:parberg@redback.com
<mailto:parberg@redback.com> ]
			>Sent: Wednesday, April 30, 2008 3:56 PM
			>To: Tina TSOU; Maglione Roberta; Sanjay Wadhwa;
Wojciech Dec (wdec)
			>Cc: ancp@ietf.org
			>Subject: RE: [ANCP] question regarding Labels
in ANCP port up messages
			>
			>
			>Hi,
			>
			>some times I think it is amazing we ever got
interoperability
			>of ANCP :-)
			>because looking at the label discussion is a
very good example that the
			>whole GSMP - ANCP reference have not worked
very well.
			>
			>In the ANCP draft, section 5.4.2 the event
message is shown like this:
			>
			>0                   1                   2
3
			>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
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
			>| Vers  |  Sub  | Message Type  | Result|
Code           |
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
			>| Partition ID  |            Transaction
Identifier             |
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
			>|I|      SubMessage Number      |
Length              |
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
			>|                             Port
|
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
			>|                      Port Session Number
|
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
			>|                     Event Sequence Number
|
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
			>|x|S|x|x|
|
			>+-+-+-+-+                     Label
|
			>~
~
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
			>|x|x|x|x|x|x|x|x| Message Type  |   Tech Type
| Block Length  |
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
			>|
|
			>~                         Extension Value
~
			>|
|
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
			>
			>
			>This is the exact same event message defined in
			>draft-ietf-gsmp-v3-base-spec-08.txt  section
11.
			>
			>And in this gsmp-draft, section 5.1.3 the label
space is defined
			>as minimum 8 bytes if the length=3D0 and as such
no value, and this
			>is because the gsmp-draft has a new "label
adaptaion" field.
			>
			>
			>
			>BUT in RFC3292 the event message is show in
section 9, like this:
			>
			>0                   1                   2
3
			>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
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
			>|    Version    | Message Type  |    Result
|     Code      |
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
			>| Partition ID  |            Transaction
Identifier             |
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
			>|I|      SubMessage Number      |
Length              |
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
			>|                             Port
|
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
			>|                      Port Session Number
|
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
			>|                     Event Sequence Number
|
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
			>|x|S|x|x|
|
			>+-+-+-+-+                     Label
|
			>~
~
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
			>
			>
			>So a different Event Message picture/definition
than what is shown
			>in the ANCP draft, and in RFC3292 section 3.1.3
the label field
			>is defined as 4 bytes if length=3D0 and as such
no value.
			>
			>
			>
			>So I very much agree with Woj that we need this
issue to be resolved,
			>and proabably a show of hands what is actually
done in different
			>implementations, so we can nail down how the
event message is
			>suppose to look like in ANCP.
			>
			>
			>I know at least 1 implementation which uses 8
bytes for the
			>label field.
			>
			>
			>cheers,
			>Peter
			>
			>
			>
			>
			>
			>
			>________________________________
			>
			>        From: ancp-bounces@ietf.org
			>[mailto:ancp-bounces@ietf.org
<mailto:ancp-bounces@ietf.org> ] On Behalf Of Tina TSOU
			>        Sent: 30. april 2008 00:19
			>        To: Maglione Roberta; Sanjay Wadhwa;
Wojciech Dec (wdec)
			>        Cc: ancp@ietf.org
			>        Subject: Re: [ANCP] question regarding
Labels in ANCP
			>port up messages
			>
			>
			>        Hi all,
			>        It is clear to me that if Label Length
is filled as 0,
			>there is nothing to be filled into Label Value.
The whole
			>Label part is 4 bytes, not 8 bytes.
			>
			>        Cheers from the last working day before
Labor's Day
			>holidays in some countries:)
			>
			>        Tina
			>
			>                ----- Original Message -----
			>                From: Wojciech Dec (wdec)
<mailto:wdec@cisco.com <mailto:wdec@cisco.com> >
			>                To: Sanjay Wadhwa
<mailto:swadhwa@juniper.net <mailto:swadhwa@juniper.net> >
			> ; Maglione Roberta
<mailto:roberta.maglione@telecomitalia.it
<mailto:roberta.maglione@telecomitalia.it> >
			>                Cc: ancp@ietf.org
			>                Sent: Wednesday, April 30, 2008
1:12 AM
			>                Subject: Re: [ANCP] question
regarding Labels
			>in ANCP port up messages
			>
			>                Sanjay, All,
			>
			>                What is stated below runs
counter to at least
			>a handful of ANCP
			>                implementations, all of which
are known to be
			>interoperable.
			>                There are really two options:
			>                1) The current version of the
spec is correct,
			>and the known
			>                interoperable implementations
do not follow it
			>                2) The current version of the
spec is not
			>accurate, and does not reflect
			>                the fact that the known
implementations follow
			>the label field
			>                definition from
draft-gsmpv3-base-spec.
			>
			>                I would like to ask you, as the
lead editor of
			>the spec, to work with
			>                the WG in resolving what the
problem is, and
			>clearing up what the WG
			>                spec says about and if 1) holds
to be true,
			>then proposing an
			>                interoperability fix.
			>
			>                In either case, the issue
highlights the fact
			>that there is still
			>                lingering confusion as to the
dependencies
			>ANCP has on rfc3292, or
			>                draft-gsmpv3-base-spec, or
both. It seems to
			>be in the best interest of
			>                all to address these.
			>
			>                Regards,
			>                Woj.
			>
			>                > -----Original Message-----
			>                > From: Sanjay Wadhwa
[mailto:swadhwa@juniper.net <mailto:swadhwa@juniper.net> ]
			>                > Sent: 29 April 2008 17:29
			>                > To: Maglione Roberta
			>                > Cc: Wojciech Dec (wdec);
ancp@ietf.org;
			>Philippe Champagne (pchamp)
			>                > Subject: RE: question
regarding Labels in
			>ANCP port up messages
			>                >
			>                > Hi Maglione
			>                >   Yes, the label format is as
defined in RFC
			>3292. The ANCP draft is
			>                > based on RFC 3292 and
proposes
			>extensions/modifications where
			>                > required.
			>                > This is clearly stated
upfront both in the
			>abstract and in
			>                > section 2. In
			>                > section 5.4.2, it clearly
specifies the
			>format of "port up" message
			>                > (based on RFC 3292), and
explicitly states
			>the label field
			>                > should be set
			>                > to 0. Following is what the
draft currently states:
			>                >
			>                >
			>                > 5.4.2 Topology Discovery
Extensions
			>                >
			>                > The GSMP Event message with
PORT UP message
			>type (80) is used for
			>                > conveying DSL line attributes
to the NAS.
			>The version field should be
			>                > set to 3, and the sub field
should be set to
			>1. The I and subMessage
			>                > fields SHOULD be set to 1 to
signify no
			>fragmentation. The Port and
			>                > Label fields should be set to
0.
			>                >
			>                >  0                   1
2 =20
			>                3
			>                >          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
			>                >
			>                >
			>                >
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
			>                >         | Vers  |  Sub  |
Message Type  |
			>Result|        Code
			>                > |
			>                >
			>                >
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
			>                >         | Partition ID  |

			>Transaction Identifier
			>                > |
			>                >
			>                >
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
			>                >         |I|      SubMessage
Number      |  =20
			>       Length
			>                > |
			>                >
			>                >
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
			>                >         |
Port
			>                > |
			>                >
			>                >
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
			>                >         |
Port Session Number
			>                > |
			>                >
			>                >
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
			>                >         |
Event Sequence Number
			>                > |
			>                >
			>                >
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
			>                >         |x|S|x|x|
			>                > |
			>                >         +-+-+-+-+
Label
			>                > |
			>                >         ~
			>                > ~
			>                >
			>                >
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
			>                >         |x|x|x|x|x|x|x|x|
Message Type  | =20
			>Tech Type   | Block Length
			>                > |
			>                >
			>                >
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
			>                >         |
			>                > |
			>                >         ~
Extension Value
			>                > ~
			>                >         |
			>                > |
			>                >
			>                >
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
			>                >
			>                > When we say the label field
should be set to
			>0, the intention
			>                > is for the
			>                > type and length fields in the
label TLV to
			>be set to 0. We can
			>                > explicitly state this for
clarity.
			>                >
			>                > -Sanjay
			>                >
			>                > >-----Original Message-----
			>                > >From: Maglione Roberta
			>[mailto:roberta.maglione@telecomitalia.it
<mailto:roberta.maglione@telecomitalia.it> ]
			>                > >Sent: Tuesday, April 29,
2008 8:06 AM
			>                > >To: Sanjay Wadhwa
			>                > >Cc: Wojciech Dec (wdec);
ancp@ietf.org;
			>pchamp@cisco.com
			>                > >Subject: RE: question
regarding Labels in
			>ANCP port up messages
			>                > >
			>                > >
			>                > >Hi Sanjay and All,
			>                > >     I was reading the
current ancp
			>protocol draft in order to
			>                > > understand which should be
the correct
			>format for the label
			>                > >field in the ancp port Up
message.
			>                > >Actually as it was already
pointed out in
			>the alias the draft
			>                > >in section 5.4.2 says "GSMP
Event message
			>with PORT UP message
			>                > >type (80) is used"  thus I
am assuming that
			>the label in the
			>                > >port UP message should
follow the message
			>format defined in
			>                > >RFC 3292, section 3.1.3:
			>                > >
			>                > >    0                   1

			>2                   3
			>                > >    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
			>                > > =20
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
			>                > >   |x|S|x|x|       Label
Type      |      =20
			>  Label Length         |
			>                > > =20
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
			>                > >   |

			>                       |
			>                > >   ~
Label Value =20
			>                       ~
			>                > >   |

			>                       |
			>                > > =20
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
			>                > >
			>                > >but from what I have seen
different
			>implementations use
			>                > >different format for label
field: in
			>particular several
			>                > >implementations use  a label
format that is
			>similar to the one
			>                > >specified in the expired
draft
			>draft-ietf-gsmp-v3-base-spec:
			>                > >
			>                > >     0                   1

			> 2                   3
			>                > >       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
			>                > >
			>                >
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
			>                > >
|x|S|x|x|x|x|x|x|x|x|x|x|x|x|x|x|   =20
			>       Label
			>                > Type         |
			>                > >
			>                >
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
			>                > >      |    Label Adaptation
|   =20
			>     Label
			>                > Length         |
			>                > >
			>                >
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
			>                > >      |
			>                >          |
			>                > >      ~
Label Value
			>                >          ~
			>                > >      |
			>                >          |
			>                > >
			>                >
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
			>                > >
			>                > >
			>                > >Even if ancp does not care
about the label
			>field, having this
			>                > >field somehow not clearly
specified in the
			>current ancp draft
			>                > >can easily lead to
interoperability issues,
			>thus I think it
			>                > >would be very helpful if you
and/or the
			>other editors can
			>                > >clarify what should be the
correct format
			>for the label field
			>                > >to be used in the ancp Port
Up message.
			>                > >
			>                > >Thanks and best regards,
			>                > >Roberta
			>                > >
			>                >
>________________________________________
			>                > >From: Philippe Champagne
(pchamp) [pchamp@cisco.com]
			>                > >Sent: Thursday, April 24,
2008 7:14 PM
			>                > >To: Sanjay Wadhwa
			>                > >Cc: Maglione Roberta;
Wojciech Dec (wdec);
			>ancp@ietf.org
			>                > >Subject: question regarding
Labels in ANCP
			>port up messages
			>                > >
			>                > >Hi Sanjay
			>                > >
			>                > >In section 5.4.2 of the
draft, we have:
			>                > >
			>                > >
			>                > >         0
1                   2
			>                >         3
			>                > >         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
			>                > >
			>                >
=09
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
			>                > >        | Vers  |  Sub  |
Message Type  |
			>Result|        Code
			>                > >         |
			>                > >
			>                >
=09
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
			>                > >        | Partition ID  |

			>Transaction Identifier
			>                > >         |
			>                > >
			>                >
=09
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
			>                > >        |I|      SubMessage
Number      | =20
			>        Length
			>                > >         |
			>                > >
			>                >
=09
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
			>                > >        |
Port
			>                > >         |
			>                > >
			>                >
=09
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
			>                > >        |
Port Session Number
			>                > >         |
			>                > >
			>                >
=09
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
			>                > >        |
Event Sequence Number
			>                > >         |
			>                > >
			>                >
=09
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
			>                > >        |x|S|x|x|
			>                > >         |
			>                > >        +-+-+-+-+
Label
			>                > >         |
			>                > >        ~
			>                > >         ~
			>                > >
			>                >
=09
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
			>                > >        |x|x|x|x|x|x|x|x|
Message Type  | =20
			>Tech Type   |
			>                > >Block Length  |
			>                > >
			>                >
=09
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
			>                > >        |
			>                > >         |
			>                > >        ~
Extension Value
			>                > >         ~
			>                > >        |
			>                > >         |
			>                > >
			>                >
=09
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
			>                > >Where Label I suppose is
taken from the RFC
			>3292, section
			>                > >3.1.3: (well, I'm guessing)
			>                > >
			>                > >   A summary of TLV labels
supported in
			>this version of the
			>                > protocol is
			>                > >   listed below:
			>                > >
			>                > >      TLV Label      Type
Section Title
			>                > >      ---------      ----
-------------
			>                > >      ATM Label      0x100
ATM TLV Labels
			>                > >      FR Label       0x101
Frame Relay
			>TLV Labels
			>                > >      MPLS Gen Label 0x102
MPLS
			>Generic TLV Labels
			>                > >      FEC Label      0x103
FEC TLV Labels
			>                > >
			>                > >   All Labels will be
designated as follow:
			>                > >
			>                > >    0                   1

			>2                   3
			>                > >    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
			>                > > =20
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
			>                > >   |x|S|x|x|       Label
Type      |      =20
			>  Label Length         |
			>                > > =20
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
			>                > >   |

			>                       |
			>                > >   ~
Label Value =20
			>                       ~
			>                > >   |

			>                       |
			>                > > =20
=09
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
			>                > >
			>                > >      x: Reserved Flags.
			>                > >         These are generally
used by
			>specific messages and will be
			>                > >         defined in those
messages.
			>                > >
			>                > >      S: Stacked Label
Indicator
			>                > >         Label Stacking is
discussed below
			>in section 3.1.3.5
			>                > >
			>                > >      Label Type
			>                > >         A 12-bit field
indicating the type
			>of label.
			>                > >
			>                > >      Label Length
			>                > >         A 16-bit field
indicating the
			>length of the Label
			>                > Value field
			>                > >         in bytes.
			>                > >
			>                > >      Label Value
			>                > >         A variable length
field that is an
			>integer number of 32 bit
			>                > >         words long.  The
Label Value field
			>is interpreted
			>                > according to
			>                > >         the Label Type as
described in the
			>following sections.
			>                > >
			>                > >
			>                > >The draft is a bit obscure
about this and
			>since it doesn't
			>                > >specify much, it can lead to
			>misinterpretation for the unused
			>                > >part. Moreover, it would
appear that
			>several implementations
			>                > >currently use another format
for the label
			>field. Can you
			>                > >explain?  I mean, how come
what's in the
			>current draft doesn't
			>                > >match what's known to be
implemented?
			>                > >
			>                > >I'm still wondering why we
carried over
			>pieces from GSMP that
			>                > >we do not intend to use.
			>                > >
			>                > >I would recommend that if we
are to keep
			>them but not use
			>                > >them, we should mention
precisely how we
			>intend not to use
			>                > >them: that is how many 0
filled bytes this
			>is expected to use
			>                > >
			>                > >The rfc 3292 doesn't cover
the case where
			>this field is not used.
			>                > >
			>                > >Can you shed some ligths on
this?
			>                > >
			>                > >Thanks
			>                > >Regards
			>                > >Phil
			>                > >
			>                > >
			>                > >
			>                >
=09
>>--------------------------------------------------------------------
			>                > >
			>                > >CONFIDENTIALITY NOTICE
			>                > >
			>                > >This message and its
attachments are
			>addressed solely to the
			>                > >persons above and may
contain confidential
			>information. If you
			>                > >have received the message in
error, be
			>informed that any use
			>                > >of the content hereof is
prohibited. Please
			>return it
			>                > >immediately to the sender
and delete the
			>message. Should you
			>                > >have any questions, please
contact us by replying to
			>                > >webmaster@telecomitalia.it.
			>                > >
			>                > >        Thank you
			>                > >
			>                > >

			>www.telecomitalia.it
			>                > >
			>                >
=09
>>--------------------------------------------------------------------
			>                > >
			>                > >
			>                >
			>
_______________________________________________
			>                ANCP mailing list
			>                ANCP@ietf.org
			>
https://www.ietf.org/mailman/listinfo/ancp
<https://www.ietf.org/mailman/listinfo/ancp>=20
			>
			>=20


------_=_NextPart_001_01C8B03B.DB96000F
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:st1 =3D=20
"urn:schemas-microsoft-com:office:smarttags"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3314" name=3DGENERATOR><!--[if !mso]>
<STYLE>v\:* {
	BEHAVIOR: url(#default#VML)
}
o\:* {
	BEHAVIOR: url(#default#VML)
}
w\:* {
	BEHAVIOR: url(#default#VML)
}
.shape {
	BEHAVIOR: url(#default#VML)
}
</STYLE>
<![endif]--><o:SmartTagType name=3D"PersonName"=20
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"></o:SmartTagT=
ype><!--[if !mso]>
<STYLE>st1\:* {
	BEHAVIOR: url(#default#ieooui)
}
</STYLE>
<![endif]-->
<STYLE>@font-face {
	font-family: Tahoma;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: blue; TEXT-DECORATION: underline
}
P {
	FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: =
"Times New Roman"; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto
}
SPAN.EmailStyle18 {
	COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal-reply
}
DIV.Section1 {
	page: Section1
}
</STYLE>
</HEAD>
<BODY lang=3DEN-US vLink=3Dblue link=3Dblue>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D757493909-07052008><FONT =
face=3DArial=20
size=3D2>Hi All,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D757493909-07052008><FONT =
face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D757493909-07052008><FONT =
face=3DArial=20
size=3D2>it's with a certain amount of incredulity that I view&nbsp;the =
proposals=20
on this thread&nbsp;for changing the version&nbsp;number of the =
protocol. Were=20
such proposals to be accepted, by definition it would make most likely =
the ANCP=20
draft incompatible with *all* current implementations, or at the =
very&nbsp;least=20
introduce a compatibility mess in existing deployments short of a flag=20
day&nbsp;change over, not to mention the issue of depreciating the old=20
version.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN =
class=3D757493909-07052008></SPAN><SPAN=20
class=3D757493909-07052008><FONT face=3DArial size=3D2>There really =
seems to be no=20
reason to go through with a version change due to what may be =
attributed&nbsp;as=20
a&nbsp;day 1 draft problem but *not* a day 1 implementation problem. =
Also, it is=20
not the first time that the protocol spec draft has had some =
inaccuracies, and=20
we've visited this aspect previously resulting in the following =
versioning=20
strategy being laid out: <A=20
href=3D"http://www.ietf.org/mail-archive/web/ancp/current/msg00152.html">=
http://www.ietf.org/mail-archive/web/ancp/current/msg00152.html</A>&nbsp;=
.=20
While&nbsp;the strategy states that an ANCP version change will not be=20
considered due to "incompatibilities arising from implementations of =
pre-RFC=20
drafts", neither does it state that the draft cannot change to reflect =
current=20
implementations&nbsp;while keeping the version.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D757493909-07052008><FONT =
face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D757493909-07052008><FONT =
face=3DArial=20
size=3D2>Now, given that there seems to be&nbsp;some&nbsp;uneasiness =
(but=20
thankfully not absolute) in the WG&nbsp;to come forward =
publicly&nbsp;with=20
details of what&nbsp;is currently implemented, I have conducted a behind =
the=20
scenes investigation of sorts,&nbsp;and present the =
summarized&nbsp;findings=20
below:</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D757493909-07052008><FONT =
face=3DArial size=3D2>-=20
There are&nbsp;10 distinct implementations of ANCP</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D757493909-07052008><FONT =
face=3DArial size=3D2>-=20
Out of these&nbsp;9 either directly implement the label field format in =
as per=20
section 5.3&nbsp;of draft-gsmpv3-base-spec-08, or each&nbsp;is known to =
be=20
compatible with at least 2&nbsp;implementations that do so. By =
association, it=20
seems reasonable to claim that all of these ANCP implementations use the =

draft-gsmpv3-base-spec-08 format. Also,&nbsp;all use version 3.1 as the =
protocol=20
version, and the base protocol header also as per =
draft-gsmpv3-base-spec-08=20
</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D757493909-07052008><FONT =
face=3DArial=20
size=3D2>-&nbsp;One implementation is known to use the =
draft-ietf-ancp-protocol-02=20
format of the label field format, ie the rfc3292 format. This =
implementation is=20
not known to be compatible with any of the others.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D757493909-07052008><FONT =
face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D757493909-07052008><FONT =
face=3DArial=20
size=3D2>Based on this, but not only, the obvious answer to the problem =
is *not*=20
to do a version change, but rather fix the draft. Granted, this is a far =
from=20
ideal situation for the&nbsp;one implementation affected, and it's a =
true shame=20
that the problem wasn't spotted earlier. Like Peter I also wonder how =
any=20
interop was achieved, but the fact that it is there is a significant one =
that=20
should not be undone by hasty version changes. As such option 2 below is =
not one=20
we'll be taking forward. Option 1 however also comes short as =
it&nbsp;does not=20
quite&nbsp;follow the logic of simply documenting what is known to be=20
interoperable in the WG draft. If specific implementations choose to =
realize=20
knobs or other, fine, but this is not part of the protocol spec, and =
there is no=20
such thing as "old label format". Please do consider the third option, =
ie fixing=20
the draft to reflect what is already done.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D757493909-07052008><FONT =
face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D757493909-07052008><FONT =
face=3DArial=20
size=3D2>This fact in general highlights the problems we're having in =
carrying=20
with the GSMPv3 (rfc3292) legacy, alongside adopted amendments from=20
draft-gsmpv3-base-spec (this Label issue not being the only adopted =
item),=20
alongside new protocol work. I trust that all of you agree that getting =
maximum=20
clarity on all the legacy issues and dependencies in the protocol spec =
is in the=20
WG's best interest, and that we are still some way off from that. As =
such I also=20
expect the WG to support moves/proposals aimed at getting that clarity, =
with=20
resolving this issue being not the first and not the last such=20
move.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D757493909-07052008><FONT =
face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D757493909-07052008><FONT =
face=3DArial=20
size=3D2>Regards,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D757493909-07052008><FONT =
face=3DArial=20
size=3D2>Woj.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D757493909-07052008><FONT =
face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D757493909-07052008><FONT =
face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D757493909-07052008><FONT =
face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Ole Helleberg Andersen=20
  [mailto:ole.helleberg.andersen@ericsson.com] <BR><B>Sent:</B> 06 May =
2008=20
  14:04<BR><B>To:</B> Peter Arberg; Sanjay Wadhwa; Tina TSOU; Maglione =
Roberta;=20
  Wojciech Dec (wdec)<BR><B>Cc:</B> ancp@ietf.org<BR><B>Subject:</B> RE: =
[ANCP]=20
  question regarding Labels in ANCP port up =
messages<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV><SPAN class=3D093315311-06052008><FONT face=3DArial =
color=3D#0000ff size=3D2>Hi=20
  All,</FONT></SPAN></DIV>
  <DIV><SPAN class=3D093315311-06052008><FONT face=3DArial =
color=3D#0000ff=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=3D093315311-06052008>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D531344506-06052008>I=20
  think the main issue is to ensure interoperability with existing=20
  implementations, and to allow for upgrading nodes that are already in =
service=20
  to a WG-draft compliant version. To do that in a manageable way we =
must allow=20
  for version negotiation per adjacency. </SPAN></FONT><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2><SPAN class=3D531344506-06052008>We therefore =
need to=20
  change the WG-draft as suggested by Sanjay in his option=20
2.</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D531344506-06052008></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D531344506-06052008>Concerning the encoding issue I prefer to =
make the=20
  WG-draft in line with existing implementations. However, if the WG =
decides to=20
  change it, differences in this encoding would also be solved by =
choosing=20
  Sanjay's option 2.</SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D531344506-06052008></SPAN></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D531344506-06052008><SPAN=20
  class=3D093315311-06052008>Cheers,</SPAN></SPAN></FONT></DIV>
  <DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D531344506-06052008><SPAN=20
  =
class=3D093315311-06052008>Ole</SPAN></SPAN></FONT></DIV></SPAN></DIV><BR=
>
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> ancp-bounces@ietf.org=20
  [mailto:ancp-bounces@ietf.org] <B>On Behalf Of </B>Peter=20
  Arberg<BR><B>Sent:</B> 2. maj 2008 20:52<BR><B>To:</B> Sanjay Wadhwa; =
Tina=20
  TSOU; Maglione Roberta; Wojciech Dec (wdec)<BR><B>Cc:</B>=20
  ancp@ietf.org<BR><B>Subject:</B> Re: [ANCP] question regarding Labels =
in ANCP=20
  port up messages<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>Hi Sanjay,</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>yes apparently I missed your point in the =
last email, but=20
  I'm glad we agree something is needed</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>to make existing ANCP implementations and the =
current=20
  draft to co-exist.</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>I do not like your option 1) as if you need a =
config knob=20
  for interoperability, it is too easy to</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>get into trouble.</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>I think option 2) is the best way forward =
with the=20
  differences already identified, or we can </FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>continue to get a show of hands of ANCP =
implementations,=20
  and see if anyone is actually</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>deployed based on the =
WG-draft.</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>There is no beneficial reasons to base the =
event-message=20
  of RFC3292, it could as well be a message</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>described bit by bit in the ANCP draft, and =
then we can=20
  keep the label space at 8 as many</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>implementations alreday =
do.</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>cheers,</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>Peter</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D364084418-02052008><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV><BR>
  <BLOCKQUOTE dir=3Dltr=20
  style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
    <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
    <HR tabIndex=3D-1>
    <FONT face=3DTahoma size=3D2><B>From:</B> Sanjay Wadhwa=20
    [mailto:swadhwa@juniper.net] <BR><B>Sent:</B> 2. maj 2008=20
    05:35<BR><B>To:</B> Peter Arberg; Tina TSOU; Maglione Roberta; =
Wojciech Dec=20
    (wdec)<BR><B>Cc:</B> ancp@ietf.org<BR><B>Subject:</B> RE: [ANCP] =
question=20
    regarding Labels in ANCP port up messages<BR></FONT><BR></DIV>
    <DIV></DIV>
    <DIV class=3DSection1>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial">Peter<o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">&nbsp;You =

    mis<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>d my point below. The =
ANCP draft=20
    since becoming a WG draft does NOT refer to the old GSMP drafts. Any =

    implementations ba<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>d on this WG-draft are =
expected to=20
    be interoperable. You are pointing to pre-WG-draft versions of ANCP, =
and=20
    the<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName> were indeed =
ba<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>d on expired GSMP drafts =
that=20
    evolved past RFC3292. <o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">There is=20
    incompatibility between the current ANCP WG-draft and previous =
non-WG=20
    versions (TLV clash, label format..). As mentioned earlier it is =
prudent for=20
    older implementations to start supporting the WG-draft version as =
soon as=20
    possible. <o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">For=20
    interoperability of WG-draft with the older pre-WG versions, I=20
    <st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>e the following=20
    options:<o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">1. =
Versioning=20
    starts with the WG-draft i.e. WG-draft is version =3D 3, sub-version =
=3D 1. For=20
    any interop issues between older non-WG versions and the WG-draft, =
one needs=20
    to look at solving it within implementations (e.g. an AN that =
implements the=20
    WG-draft, could ba<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>d on a configuration =
knob, generate=20
    a PORT-UP message with old label format the will be accepted by BNG=20
    implementing pre-WG versions of the draft). =
<o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">2. Change =
the=20
    WG-draft (current draft) to u<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName> version =3D 3 and =
sub-version =3D 2.=20
    This is assuming there is no deployed implementation of current =
WG-draft=20
    that already u<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>s 3.1 as the version, =
and also=20
    assuming the old pre-WG implementations u<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName> 3.1. There will be no =
backwards=20
    compatibility i.e. version 3.1 BNG will not work with version 3.2 AN =
(we=20
    will need to list this as caveat in the appendix <st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>ction). AN and BNG will =
need to=20
    negotiate the same version in order for ANCP adjacency to come up. A =
BNG=20
    supporting both versions 3.1 and 3.2 could simultaneously become =
adjacent=20
    with one AN supporting 3.1 and another AN supporting 3.2. (i.e. =
version=20
    compatibility is per adjacency).<o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Also, =
major version=20
    number change (e.g. from 3 to 4) should only correspond to a major =
change in=20
    the protocol (e.g. different mechanism, different transport=20
    etc).<o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">My vote =
would be to=20
    adopt option 2 above only if further changes to WG-draft happen that =
render=20
    it incompatible with the current WG-draft. Any interoperability =
issues with=20
    pre-WG versions could be handled via option =
1.<o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial">Cheers<o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial">-Sanjay<o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
    <DIV>
    <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
    face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
    <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
    </SPAN></FONT></DIV>
    <P class=3DMsoNormal><B><FONT face=3DTahoma size=3D2><SPAN=20
    style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
    face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma"> Peter=20
    Arberg [mailto:parberg@redback.com] <BR><B><SPAN=20
    style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Wednesday, April 30, =
2008 7:20=20
    PM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Sanjay =
Wadhwa; Tina=20
    TSOU; Maglione Roberta; Wojciech Dec (wdec)<BR><B><SPAN=20
    style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B> ancp@ietf.org<BR><B><SPAN =

    style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [ANCP] question =
regarding=20
    Labels in ANCP port up messages</SPAN></FONT><o:p></o:p></P></DIV>
    <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
    style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Sanjay,</SPAN></FONT><o:p></o:p></P>
    <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
    style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">What do =
you mean=20
    "why I reference an old draft"&nbsp;=20
    ????????????</SPAN></FONT><o:p></o:p></P>
    <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
    style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">I'm=20
    surpri<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>d you even ask...&nbsp;=20
    plea<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName> take a look at YOUR own =

    internet-draft that most</SPAN></FONT><o:p></o:p></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">of the =
ANCP working=20
    implementations are ba<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>d on, in =
ca<st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName> you do not have this=20
    old</SPAN></FONT><o:p></o:p></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">internet-draft, I=20
    have attached it to the document.</SPAN></FONT><o:p></o:p></P>
    <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
    style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">If you =
look at the=20
    reference for this ancp-draft, you will <st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 w:st=3D"on">se</st1:PersonName>e that in the reference=20
    <st1:PersonName=20
    style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
    tabIndex=3D0 =
w:st=3D"on">se</st1:PersonName>ction</SPAN></FONT><o:p></o:p></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">you point =
to this=20
    old gsmp-draft...&nbsp; Yes and I know this has been changed in the=20
    later</SPAN></FONT><o:p></o:p></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">versions =
of the=20
    ANCP draft, but that do not change the fact that many of the=20
    implementations</SPAN></FONT><o:p></o:p></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">today was =
developed=20
    when the attached draft was current.</SPAN></FONT><o:p></o:p></P>
    <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
    style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">I think a =
very good=20
    question is brought up here, and that is what is implemented=20
    and</SPAN></FONT><o:p></o:p></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">running =
in networks=20
    today ?</SPAN></FONT><o:p></o:p></P>
    <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
    style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">My take =
on this is=20
    that when the reference was change from the old gsmp-draft to the=20
    older</SPAN></FONT><o:p></o:p></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">RFC3292, =
apparently=20
    no one paid any attention to the fact the label definition in the=20
    event</SPAN></FONT><o:p></o:p></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">message =
was=20
    different and not compatible.</SPAN></FONT><o:p></o:p></P>
    <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
    style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">What =
current=20
    implementations do today is an important factor in this discussion, =
and I=20
    think</SPAN></FONT><o:p></o:p></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">it is =
time to come=20
    to realization that we might need a new version number for ANCP=20
    since</SPAN></FONT><o:p></o:p></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">it =
continues to=20
    look like there is big holes open for interpretation. So if I did a=20
    ANCP</SPAN></FONT><o:p></o:p></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">implementation=20
    there is bound to be interoperability issues with existing=20
    implementations</SPAN></FONT><o:p></o:p></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">runnig.</SPAN></FONT><o:p></o:p></P>
    <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
    style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">cheers,</SPAN></FONT><o:p></o:p></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Peter</SPAN></FONT><o:p></o:p></P>
    <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
    style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
    style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
    style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
    <BLOCKQUOTE=20
    style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: 5pt 0in 5pt =
3.75pt; BORDER-LEFT: blue 1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none">
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =

      style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
      <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
      face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
      <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
      </SPAN></FONT></DIV>
      <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><B><FONT =
face=3DTahoma=20
      size=3D2><SPAN=20
      style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
      face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Tahoma">=20
      Sanjay Wadhwa [mailto:swadhwa@juniper.net] <BR><B><SPAN=20
      style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> 30. april 2008=20
      14:42<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Peter =
Arberg;=20
      Tina TSOU; Maglione Roberta; Wojciech Dec (wdec)<BR><B><SPAN=20
      style=3D"FONT-WEIGHT: bold">Cc:</SPAN></B> =
ancp@ietf.org<BR><B><SPAN=20
      style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [ANCP] =
question=20
      regarding Labels in ANCP port up =
messages</SPAN></FONT><o:p></o:p></P>
      <P><FONT face=3D"Times New Roman" size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt">Peter<BR>&nbsp; The ANCP draft as it =
currently=20
      stands is ba<st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName>d on RFC3292. It =
provides=20
      extensions and modifications to relevant constructs in RFC3292. =
There is=20
      no mention (implicit or explicit) of expired GSMP drafts in the =
ANCP=20
      draft. In order to implement the ANCP draft, I am not sure why one =
would=20
      look at the expired GSMP drafts. Do you <st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName>e a reason to do this=20
      ba<st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName>d on anything that you =
read in the=20
      ANCP draft? Bringing up reference to expired gsmp draft in this=20
      thread&nbsp;just adds to the confusion. For GSMPv3 objects in the =
messages=20
      (such as Label Type), one has to look at RFC3292 (this is clearly =
stated=20
      in the ANCP draft - <st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName>ction 2 and I am =
quoting it below)=20
      :</SPAN></FONT><o:p></o:p></P>
      <P><FONT face=3D"Times New Roman" color=3Dblue size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: blue">ANCP u<st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName>s a sub<st1:PersonName =

      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName>t of GSMPv3 messages =
to implement=20
      currently defined u<st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName>-ca<st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName>s. The<st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName> relevant GSMPv3 =
messages are=20
      identified in <st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName>ction 5. GSMPv3 =
procedures with=20
      suitable extensions, as u<st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName>d by ANCP, are =
described in=20
      <st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName>ctions 5.1, 5.2 and =
5.3. GSMPv3=20
      general extensions and GSMPv3 message specific extensions required =
by ANCP=20
      are described in sub-<st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName>ctions of 5.4. In =
addition to=20
      specifying extensions and modifications to relevant GSMP messages=20
      applicable to ANCP, this draft also defines the usage of=20
      the<st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName> messages by ANCP, and =
indicates=20
      the values that ANCP should <st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName>t for relevant fields =
in=20
      the<st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName> GSMP messages. =
However, to=20
      understand the basic <st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName>mantics of various =
fields in GSMP=20
      messages, the reader is referred to [4].&nbsp;=3D&gt; RFC=20
      3292.</SPAN></FONT><FONT size=3D2><SPAN style=3D"FONT-SIZE: =
10pt"><BR><BR>What=20
      existing implementations currently do is an important but =
<st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName>parate issue. =
The<st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName> implementations for =
most part=20
      precede the current ANCP draft. It is fine to poll where=20
      the<st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName> implementations =
diverge from the=20
      current draft. It is then upto the implementations (including the =
one that=20
      I am somewhat familiar with) to work towards compliance with the =
draft.=20
      </SPAN></FONT><o:p></o:p></P>
      <P><FONT face=3D"Times New Roman" size=3D2><SPAN =
style=3D"FONT-SIZE: 10pt">On=20
      the following points&nbsp;from =
&nbsp;Woj:</SPAN></FONT><o:p></o:p></P>
      <P><FONT face=3D"Times New Roman" size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt">Woj&gt;2) The current version of the =
spec is not=20
      accurate, and does not reflect&nbsp;the fact that the known=20
      implementations follow the label field definition from=20
      draft-gsmpv3-ba<st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0=20
w:st=3D"on">se</st1:PersonName>-spec.</SPAN></FONT><o:p></o:p></P>
      <P><FONT face=3D"Times New Roman" size=3D2><SPAN =
style=3D"FONT-SIZE: 10pt">It is=20
      not for the protocol draft to point out what current =
implementations=20
      do.&nbsp;&nbsp;The best we can do is to further clarify in the =
draft that=20
      type and value fields of the Label object (defined in RFC3292) =
should be=20
      <st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName>t to 0 in the port-up =
message (we=20
      already&nbsp;mention the lable object as a whole should be =
<st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName>t to all 0s).=20
      </SPAN></FONT><o:p></o:p></P>
      <P><FONT face=3D"Times New Roman" size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt">Woj&gt; This would be a good thing for =
the WG to=20
      discuss. There most evidently is a fair amount of&nbsp;"dead wood" =
in the=20
      current spec, ie stuff that nobody yet&nbsp;implements or cares =
about.=20
      &nbsp;In the former ca<st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName>, we could re-cast =
that material=20
      using the new notions/extensions, in the latter ca<st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName> simply chop it=20
      out.</SPAN></FONT><o:p></o:p></P>
      <P><FONT face=3D"Times New Roman" size=3D2><SPAN =
style=3D"FONT-SIZE: 10pt">I=20
      agree. We are ba<st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName>d on GSMPv3 (RFC3292)=20
      &nbsp;messages, and obviously not everything in the<st1:PersonName =

      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName> messages is leveraged =
by=20
      ANCP.&nbsp; However, the sync rate and OAM u<st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName>s-ca<st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName>s are implemented and =
in=20
      u<st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName> (ideally we should =
leave=20
      the<st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName> alone...i.e. no =
change beyond=20
      adding more clarity if needed). For anything new (such as =
multicast) we=20
      are defining new messages&nbsp;(no legacy).&nbsp;=20
      </SPAN></FONT><o:p></o:p></P>
      <P><FONT face=3D"Times New Roman" size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt">-Sanjay<BR><BR>&gt;-----Original=20
      Message-----<BR>&gt;From: Peter Arberg [</SPAN></FONT><A=20
      href=3D"mailto:parberg@redback.com"><FONT size=3D2><SPAN=20
      style=3D"FONT-SIZE: =
10pt">mailto:parberg@redback.com</SPAN></FONT></A><FONT=20
      size=3D2><SPAN style=3D"FONT-SIZE: 10pt">]<BR>&gt;Sent: Wednesday, =
April 30,=20
      2008 3:56 PM<BR>&gt;To: Tina TSOU; Maglione Roberta; Sanjay =
Wadhwa;=20
      Wojciech Dec (wdec)<BR>&gt;Cc: ancp@ietf.org<BR>&gt;Subject: RE: =
[ANCP]=20
      question regarding Labels in ANCP port up=20
      messages<BR>&gt;<BR>&gt;<BR>&gt;Hi,<BR>&gt;<BR>&gt;some times I =
think it=20
      is amazing we ever got interoperability<BR>&gt;of ANCP=20
      :-)<BR>&gt;becau<st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName> looking at the label =
discussion=20
      is a very good example that the<BR>&gt;whole GSMP - ANCP reference =
have=20
      not worked very well.<BR>&gt;<BR>&gt;In the ANCP draft, =
<st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName>ction 5.4.2 the event =
message is=20
      shown like=20
      =
this:<BR>&gt;<BR>&gt;0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      3<BR>&gt;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=20
      =
1<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+<BR>&gt;|=20
      Vers&nbsp; |&nbsp; Sub&nbsp; | Message Type&nbsp; |=20
      Result|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      Code&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
|<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+<BR>&gt;|=20
      Partition ID&nbsp;=20
      =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      Transaction=20
      =
Identifier&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;=20
      =
|<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+<BR>&gt;|I|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      SubMessage Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;=20
      =
|<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+<BR>&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
Port&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
|<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+<BR>&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      Port Session=20
      =
Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
|<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+<BR>&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      Event Sequence=20
      =
Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
|<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+<BR>&gt;|x|S|x|x|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
|<BR>&gt;+-+-+-+-+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
Label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
|<BR>&gt;~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;=20
      =
~<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+<BR>&gt;|x|x|x|x|x|x|x|x|=20
      Message Type&nbsp; |&nbsp;&nbsp; Tech Type&nbsp;&nbsp; | Block=20
      Length&nbsp;=20
      =
|<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+<BR>&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;=20
      =
|<BR>&gt;~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;=20
      Extension=20
      =
Value&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
~<BR>&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;=20
      =
|<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+<BR>&gt;<BR>&gt;<BR>&gt;This=20
      is the exact same event message defined=20
      in<BR>&gt;draft-ietf-gsmp-v3-ba<st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName>-spec-08.txt&nbsp; =
<st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName>ction =
11.<BR>&gt;<BR>&gt;And in=20
      this gsmp-draft, <st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName>ction 5.1.3 the label =
space is=20
      defined<BR>&gt;as minimum 8 bytes if the length=3D0 and as such no =
value,=20
      and this<BR>&gt;is becau<st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName> the gsmp-draft has a =
new "label=20
      adaptaion" field.<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt;BUT in RFC3292 =
the event=20
      message is show in <st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName>ction 9, like=20
      =
this:<BR>&gt;<BR>&gt;0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      3<BR>&gt;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=20
      =
1<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+<BR>&gt;|&nbsp;&nbsp;&nbsp;=20
      Version&nbsp;&nbsp;&nbsp; | Message Type&nbsp; |&nbsp;&nbsp;&nbsp; =

      Result&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;=20
      Code&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
|<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+<BR>&gt;|=20
      Partition ID&nbsp;=20
      =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      Transaction=20
      =
Identifier&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;=20
      =
|<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+<BR>&gt;|I|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      SubMessage Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;=20
      =
|<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+<BR>&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
Port&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
|<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+<BR>&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      Port Session=20
      =
Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
|<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+<BR>&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      Event Sequence=20
      =
Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
|<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+<BR>&gt;|x|S|x|x|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
|<BR>&gt;+-+-+-+-+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
Label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
|<BR>&gt;~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;=20
      =
~<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-=
+<BR>&gt;<BR>&gt;<BR>&gt;So=20
      a different Event Message picture/definition than what is =
shown<BR>&gt;in=20
      the ANCP draft, and in RFC3292 <st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName>ction 3.1.3 the label=20
      field<BR>&gt;is defined as 4 bytes if length=3D0 and as such no=20
      value.<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt;So I very much agree with =
Woj that=20
      we need this issue to be resolved,<BR>&gt;and proabably a show of =
hands=20
      what is actually done in different<BR>&gt;implementations, so we =
can nail=20
      down how the event message is<BR>&gt;suppo<st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName> to look like in=20
      ANCP.<BR>&gt;<BR>&gt;<BR>&gt;I know at least 1 implementation =
which=20
      u<st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName>s 8 bytes for =
the<BR>&gt;label=20
      =
field.<BR>&gt;<BR>&gt;<BR>&gt;cheers,<BR>&gt;Peter<BR>&gt;<BR>&gt;<BR>&gt=
;<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt;________________________________<BR>&gt;=
<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      From: ancp-bounces@ietf.org<BR>&gt;[</SPAN></FONT><A=20
      href=3D"mailto:ancp-bounces@ietf.org"><FONT size=3D2><SPAN=20
      style=3D"FONT-SIZE: =
10pt">mailto:ancp-bounces@ietf.org</SPAN></FONT></A><FONT=20
      size=3D2><SPAN style=3D"FONT-SIZE: 10pt">] On Behalf Of Tina=20
      TSOU<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Sent: 30. =
april=20
      2008 00:19<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; To: =
Maglione=20
      Roberta; Sanjay Wadhwa; Wojciech Dec=20
      (wdec)<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Cc:=20
      ancp@ietf.org<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Subject:=20
      Re: [ANCP] question regarding Labels in ANCP<BR>&gt;port up=20
      =
messages<BR>&gt;<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;=20
      Hi all,<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; It is =
clear to=20
      me that if Label Length is filled as 0,<BR>&gt;there is nothing to =
be=20
      filled into Label Value. The whole<BR>&gt;Label part is 4 bytes, =
not 8=20
      bytes.<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Cheers=20
      from the last working day before Labor's Day<BR>&gt;holidays in =
some=20
      =
countries:)<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
Tina<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      ----- Original Message=20
      =
-----<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      From: Wojciech Dec (wdec) &lt;</SPAN></FONT><A=20
      href=3D"mailto:wdec@cisco.com"><FONT size=3D2><SPAN=20
      style=3D"FONT-SIZE: =
10pt">mailto:wdec@cisco.com</SPAN></FONT></A><FONT=20
      size=3D2><SPAN=20
      style=3D"FONT-SIZE: =
10pt">&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      To: Sanjay Wadhwa &lt;</SPAN></FONT><A=20
      href=3D"mailto:swadhwa@juniper.net"><FONT size=3D2><SPAN=20
      style=3D"FONT-SIZE: =
10pt">mailto:swadhwa@juniper.net</SPAN></FONT></A><FONT=20
      size=3D2><SPAN style=3D"FONT-SIZE: 10pt">&gt;<BR>&gt; ; Maglione =
Roberta=20
      &lt;</SPAN></FONT><A =
href=3D"mailto:roberta.maglione@telecomitalia.it"><FONT=20
      size=3D2><SPAN=20
      style=3D"FONT-SIZE: =
10pt">mailto:roberta.maglione@telecomitalia.it</SPAN></FONT></A><FONT=20
      size=3D2><SPAN=20
      style=3D"FONT-SIZE: =
10pt">&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      Cc:=20
      =
ancp@ietf.org<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      Sent: Wednesday, April 30, 2008 1:12=20
      =
AM<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      Subject: Re: [ANCP] question regarding Labels<BR>&gt;in ANCP port =
up=20
      =
messages<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      Sanjay,=20
      =
All,<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      What is stated below runs counter to at least<BR>&gt;a handful of=20
      =
ANCP<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      implementations, all of which are known to=20
      =
be<BR>&gt;interoperable.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      There are really two=20
      =
options:<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      1) The current version of the spec is correct,<BR>&gt;and the=20
      =
known<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      interoperable implementations do not follow=20
      =
it<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      2) The current version of the spec is not<BR>&gt;accurate, and =
does not=20
      =
reflect<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      the fact that the known implementations follow<BR>&gt;the label=20
      =
field<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      definition from draft-gsmpv3-ba<st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0=20
      =
w:st=3D"on">se</st1:PersonName>-spec.<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      I would like to ask you, as the lead editor of<BR>&gt;the spec, to =
work=20
      =
with<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      the WG in resolving what the problem is, and<BR>&gt;clearing up =
what the=20
      =
WG<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      spec says about and if 1) holds to be true,<BR>&gt;then proposing=20
      =
an<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      interoperability=20
      =
fix.<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      In either ca<st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName>, the issue highlights =
the=20
      fact<BR>&gt;that there is=20
      =
still<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      lingering confusion as to the dependencies<BR>&gt;ANCP has on =
rfc3292,=20
      =
or<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      draft-gsmpv3-ba<st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName>-spec, or both. It =
<st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName>ems to<BR>&gt;be in =
the best=20
      interest=20
      =
of<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      all to address the<st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0=20
      =
w:st=3D"on">se</st1:PersonName>.<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
Regards,<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
Woj.<BR>&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; -----Original=20
      =
Message-----<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; From: Sanjay Wadhwa [</SPAN></FONT><A=20
      href=3D"mailto:swadhwa@juniper.net"><FONT size=3D2><SPAN=20
      style=3D"FONT-SIZE: =
10pt">mailto:swadhwa@juniper.net</SPAN></FONT></A><FONT=20
      size=3D2><SPAN=20
      style=3D"FONT-SIZE: =
10pt">]<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; Sent: 29 April 2008=20
      =
17:29<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; To: Maglione=20
      =
Roberta<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; Cc: Wojciech Dec (wdec); ancp@ietf.org;<BR>&gt;Philippe =
Champagne=20
      =
(pchamp)<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; Subject: RE: question regarding Labels in<BR>&gt;ANCP port up =

      =
messages<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; Hi=20
      =
Maglione<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;&nbsp;&nbsp; Yes, the label format is as defined in =
RFC<BR>&gt;3292.=20
      The ANCP draft=20
      =
is<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; ba<st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName>d on RFC 3292 and=20
      propo<st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 =
w:st=3D"on">se</st1:PersonName>s<BR>&gt;extensions/modifications=20
      =
where<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
required.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; This is clearly stated upfront both in the<BR>&gt;abstract =
and=20
      =
in<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; <st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName>ction 2.=20
      =
In<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; <st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName>ction 5.4.2, it =
clearly&nbsp;=20
      specifies the<BR>&gt;format of "port up"=20
      =
message<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; (ba<st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName>d on RFC 3292), and =
explicitly=20
      states<BR>&gt;the label=20
      =
field<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; should be <st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0=20
      =
w:st=3D"on">se</st1:PersonName>t<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; to 0. Following is what the draft currently=20
      =
states:<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; 5.4.2 Topology Discovery=20
      =
Extensions<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; The GSMP Event message with PORT UP message<BR>&gt;type (80) =
is=20
      u<st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName>d=20
      =
for<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; conveying DSL line attributes to the NAS.<BR>&gt;The version =
field=20
      should=20
      =
be<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; <st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName>t to 3, and the sub =
field should=20
      be <st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName>t to<BR>&gt;1. The I =
and=20
      =
subMessage<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; fields SHOULD be <st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName>t to 1 to signify=20
      no<BR>&gt;fragmentation. The Port=20
      =
and<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; Label fields should be <st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName>t to=20
      =
0.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;&nbsp;=20
      =
0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
2&nbsp;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
3<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0 1 2 3 =
4 5 6 7=20
      8 9 0 1 2 3 4 5 6 7<BR>&gt;8 9 0 1 2 3 4=20
      =
5<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; 6 7 8 9 0=20
      =
1<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
&gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Vers&nbsp; =
|&nbsp;=20
      Sub&nbsp; | Message Type&nbsp;=20
      |<BR>&gt;Result|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
Code<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
&gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Partition =
ID&nbsp;=20
      =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&g=
t;Transaction=20
      =
Identifier<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
&gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      |I|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SubMessage=20
      Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      |&nbsp;&nbsp;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
Length<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
&gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;=20
      =
Port<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
&gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      Port Session=20
      =
Number<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
&gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      Event Sequence=20
      =
Number<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
&gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
|x|S|x|x|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
+-+-+-+-+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
Label<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
~<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
~<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
&gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|x|x|x|x|x|x|x|x|=20
      Message Type&nbsp; |&nbsp;&nbsp;<BR>&gt;Tech Type&nbsp;&nbsp; | =
Block=20
      =
Length<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
&gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =

      Extension=20
      =
Value<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
~<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
&gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; When we say the label field should be <st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName>t to<BR>&gt;0, the=20
      =
intention<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; is for=20
      =
the<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; type and length fields in the label TLV to<BR>&gt;be =
<st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName>t to 0. We=20
      =
can<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; explicitly state this for=20
      =
clarity.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
-Sanjay<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;-----Original=20
      =
Message-----<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;From: Maglione Roberta<BR>&gt;[</SPAN></FONT><A=20
      href=3D"mailto:roberta.maglione@telecomitalia.it"><FONT =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: =
10pt">mailto:roberta.maglione@telecomitalia.it</SPAN></FONT></A><FONT=20
      size=3D2><SPAN=20
      style=3D"FONT-SIZE: =
10pt">]<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;Sent: Tuesday, April 29, 2008 8:06=20
      =
AM<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;To: Sanjay=20
      =
Wadhwa<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;Cc: Wojciech Dec (wdec);=20
      =
ancp@ietf.org;<BR>&gt;pchamp@cisco.com<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;Subject: RE: question regarding Labels in<BR>&gt;ANCP =
port up=20
      =
messages<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;Hi Sanjay and=20
      =
All,<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp; I was reading the current=20
      ancp<BR>&gt;protocol draft in order=20
      =
to<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt; understand which should be the correct<BR>&gt;format for =
the=20
      =
label<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;field in the ancp port Up=20
      =
message.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;Actually as it was already pointed out in<BR>&gt;the =
alias the=20
      =
draft<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;in <st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName>ction 5.4.2 says "GSMP =
Event=20
      message<BR>&gt;with PORT UP=20
      =
message<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;type (80) is u<st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName>d"&nbsp; thus I am =
assuming=20
      that<BR>&gt;the label in=20
      =
the<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;port UP message should follow the message<BR>&gt;format =
defined=20
      =
in<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;RFC 3292, <st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName>ction=20
      =
3.1.3:<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;=20
      =
0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt;2&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;=20
      =
3<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp; 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8=20
      9<BR>&gt;0 1 2 3 4 5 6 7 8 9 0=20
      =
1<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
&gt;&nbsp;&nbsp;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp; =
|x|S|x|x|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Label=20
      Type&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt;&nbsp; Label=20
      Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
&gt;&nbsp;&nbsp;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;=20
      =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;=20
      =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;=20
      =
~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;=20
      Label=20
      =
Value&nbsp;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;=20
      =
~<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;=20
      =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;=20
      =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
&gt;&nbsp;&nbsp;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;but from what I have <st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName>en=20
      different<BR>&gt;implementations u<st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0=20
      =
w:st=3D"on">se</st1:PersonName><BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;different format for label field: in<BR>&gt;particular=20
      <st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0=20
      =
w:st=3D"on">se</st1:PersonName>veral<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;implementations u<st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName>&nbsp; a label format =
that=20
      is<BR>&gt;similar to the=20
      =
one<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;specified in the expired=20
      draft<BR>&gt;draft-ietf-gsmp-v3-ba<st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0=20
      =
w:st=3D"on">se</st1:PersonName>-spec:<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt;=20
      =
2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
3<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0 1 2 3 4 5 6 7 8 9 =
0 1 2 3=20
      4 5 6 7<BR>&gt;8 9 0 1 2 3 4 5=20
      =
6<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; 7 8 9 0=20
      =
1<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
&gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
|x|S|x|x|x|x|x|x|x|x|x|x|x|x|x|x|&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
Label<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; Type&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
&gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp; Label=20
      =
Adaptation&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      |&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
Label<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
&gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;=20
      Label=20
      =
Value<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
~<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
&gt;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;Even if ancp does not care about the label<BR>&gt;field, =
having=20
      =
this<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;field somehow not clearly specified in the<BR>&gt;current =
ancp=20
      =
draft<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;can easily lead to interoperability issues,<BR>&gt;thus I =
think=20
      =
it<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;would be very helpful if you and/or the<BR>&gt;other =
editors=20
      =
can<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;clarify what should be the correct format<BR>&gt;for the =
label=20
      =
field<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;to be u<st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName>d in the ancp Port Up=20
      =
message.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;Thanks and best=20
      =
regards,<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
&gt;Roberta<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
&gt;________________________________________<BR>&gt;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;From: Philippe Champagne (pchamp)=20
      =
[pchamp@cisco.com]<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;Sent: Thursday, April 24, 2008 7:14=20
      =
PM<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;To: Sanjay=20
      =
Wadhwa<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;Cc: Maglione Roberta; Wojciech Dec=20
      =
(wdec);<BR>&gt;ancp@ietf.org<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;Subject: question regarding&nbsp; Labels in =
ANCP<BR>&gt;port up=20
      =
messages<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;Hi=20
      =
Sanjay<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;In <st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName>ction 5.4.2 of the =
draft, we=20
      =
have:<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
2<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
3<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0 1 2 3 =
4 5 6 7=20
      8 9 0 1 2 3 4 5 6<BR>&gt;7 8 9 0 1 2 3 4 5=20
      =
6<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;7 8 9 0=20
      =
1<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
&gt;<BR>&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Vers&nbsp; =
|&nbsp;=20
      Sub&nbsp; | Message Type&nbsp;=20
      |<BR>&gt;Result|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
Code<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
&gt;<BR>&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Partition =
ID&nbsp;=20
      =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&g=
t;Transaction=20
      =
Identifier<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
&gt;<BR>&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      |I|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SubMessage=20
      Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      |&nbsp;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
Length<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
&gt;<BR>&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;=20
      =
Port<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
&gt;<BR>&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      Port Session=20
      =
Number<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
&gt;<BR>&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      Event Sequence=20
      =
Number<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
&gt;<BR>&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
|x|S|x|x|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
+-+-+-+-+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
Label<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
~<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
~<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
&gt;<BR>&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|x|x|x|x|x|x|x|x|=20
      Message Type&nbsp; |&nbsp;&nbsp;<BR>&gt;Tech Type&nbsp;&nbsp;=20
      =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;Block Length&nbsp;=20
      =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
&gt;<BR>&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =

      Extension=20
      =
Value<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
~<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
&gt;<BR>&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;Where Label I suppo<st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName> is taken from the=20
      RFC<BR>&gt;3292, <st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0=20
      =
w:st=3D"on">se</st1:PersonName>ction<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;3.1.3: (well, I'm=20
      =
guessing)<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp; A summary of TLV labels supported =
in<BR>&gt;this=20
      version of=20
      =
the<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; protocol=20
      =
is<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp; listed=20
      =
below:<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; TLV=20
      Label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      Type&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Section=20
      =
Title<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      ---------&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      ----&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
-------------<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ATM=20
      Label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
0x100&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      ATM TLV=20
      =
Labels<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; FR=20
      Label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      0x101&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Frame Relay<BR>&gt;TLV=20
      =
Labels<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MPLS Gen Label=20
      0x102&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MPLS<BR>&gt;Generic TLV=20
      =
Labels<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; FEC=20
      Label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
0x103&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      FEC TLV=20
      =
Labels<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp; All Labels will be designated as=20
      =
follow:<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;=20
      =
0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt;2&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;=20
      =
3<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp; 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8=20
      9<BR>&gt;0 1 2 3 4 5 6 7 8 9 0=20
      =
1<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
&gt;&nbsp;&nbsp;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp; =
|x|S|x|x|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Label=20
      Type&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&gt;&nbsp; Label=20
      Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
&gt;&nbsp;&nbsp;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;=20
      =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;=20
      =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;=20
      =
~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;=20
      Label=20
      =
Value&nbsp;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;=20
      =
~<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;=20
      =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;=20
      =
|<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
&gt;&nbsp;&nbsp;<BR>&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
-+-+-+-+-+-+-+-+<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; x: Re<st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName>rved=20
      =
Flags.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      The<st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName> are generally =
u<st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName>d by<BR>&gt;specific =
messages and=20
      will=20
      =
be<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; defined =
in=20
      tho<st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName>=20
      =
messages.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; S: Stacked Label=20
      =
Indicator<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Label =
Stacking=20
      is discus<st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName>d below<BR>&gt;in =
<st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName>ction=20
      =
3.1.3.5<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Label=20
      =
Type<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A 12-bit =
field=20
      indicating the type<BR>&gt;of=20
      =
label.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Label=20
      =
Length<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A 16-bit =
field=20
      indicating the<BR>&gt;length of the=20
      =
Label<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; Value=20
      =
field<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; in=20
      =
bytes.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Label=20
      =
Value<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A =
variable=20
      length field that is an<BR>&gt;integer number of 32=20
      =
bit<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; words=20
      long.&nbsp; The Label Value field<BR>&gt;is=20
      =
interpreted<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; according=20
      =
to<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the =
Label Type=20
      as described in the<BR>&gt;following <st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0=20
      =
w:st=3D"on">se</st1:PersonName>ctions.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;The draft is a bit obscure about this and<BR>&gt;since it =

      =
doesn't<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;specify much, it can lead to<BR>&gt;misinterpretation for =
the=20
      unu<st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0=20
      =
w:st=3D"on">se</st1:PersonName>d<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;part. Moreover, it would appear =
that<BR>&gt;<st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName>veral=20
      =
implementations<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;currently u<st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName> another format for =
the=20
      label<BR>&gt;field. Can=20
      =
you<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;explain?&nbsp; I mean, how come what's in =
the<BR>&gt;current=20
      draft=20
      =
doesn't<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;match what's known to be=20
      =
implemented?<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;I'm still wondering why we carried over<BR>&gt;pieces =
from GSMP=20
      =
that<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;we do not intend to u<st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0=20
      =
w:st=3D"on">se</st1:PersonName>.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;I would recommend that if we are to keep<BR>&gt;them but =
not=20
      u<st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0=20
      =
w:st=3D"on">se</st1:PersonName><BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;them, we should mention preci<st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName>ly how =
we<BR>&gt;intend not to=20
      u<st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0=20
      =
w:st=3D"on">se</st1:PersonName><BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;them: that is how many 0 filled bytes this<BR>&gt;is =
expected to=20
      u<st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0=20
      =
w:st=3D"on">se</st1:PersonName><BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;The rfc 3292 doesn't cover the ca<st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName> where<BR>&gt;this =
field is not=20
      u<st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0=20
      =
w:st=3D"on">se</st1:PersonName>d.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;Can you shed some ligths on=20
      =
this?<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
&gt;Thanks<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
&gt;Regards<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
&gt;Phil<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
&gt;<BR>&gt;&gt;---------------------------------------------------------=
-----------<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;CONFIDENTIALITY=20
      =
NOTICE<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;This message and its attachments =
are<BR>&gt;addres<st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName>d solely to=20
      =
the<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;persons above and may contain =
confidential<BR>&gt;information. If=20
      =
you<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;have received the message in error, be<BR>&gt;informed =
that any=20
      u<st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0=20
      =
w:st=3D"on">se</st1:PersonName><BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;of the content hereof is prohibited. Plea<st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName><BR>&gt;return=20
      =
it<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;immediately to the <st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName>nder and delete=20
      the<BR>&gt;message. Should=20
      =
you<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;have any questions, plea<st1:PersonName=20
      style=3D"BACKGROUND-POSITION: left bottom; BACKGROUND-IMAGE: =
url(res://ietag.dll/#34/#1001); BACKGROUND-REPEAT: repeat-x"=20
      tabIndex=3D0 w:st=3D"on">se</st1:PersonName> contact us by =
replying=20
      =
to<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
&gt;webmaster@telecomitalia.it.<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Thank=20
      =
you<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;<BR>&gt;www.telecomitalia.it<BR>&gt;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =

      &gt;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
&gt;<BR>&gt;&gt;---------------------------------------------------------=
-----------<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      &gt;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
&gt;<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
_______________________________________________<BR>&gt;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =

      ANCP mailing=20
      =
list<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      =
ANCP@ietf.org<BR>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
      </SPAN></FONT><A =
href=3D"https://www.ietf.org/mailman/listinfo/ancp"=20
      target=3D_blank><FONT size=3D2><SPAN=20
      style=3D"FONT-SIZE: =
10pt">https://www.ietf.org/mailman/listinfo/ancp</SPAN></FONT></A><BR><FO=
NT=20
      size=3D2><SPAN style=3D"FONT-SIZE: =
10pt">&gt;<BR>&gt;</SPAN></FONT>=20
      =
<o:p></o:p></P></BLOCKQUOTE></DIV></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML=
>

------_=_NextPart_001_01C8B03B.DB96000F--

--===============1157695667==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1157695667==--


From ancp-bounces@ietf.org  Wed May  7 07:04:53 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 18BA83A7167;
	Wed,  7 May 2008 07:04:53 -0700 (PDT)
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 C15803A7168
	for <ancp@core3.amsl.com>; Wed,  7 May 2008 07:04:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.598
X-Spam-Level: 
X-Spam-Status: No, score=-1.598 tagged_above=-999 required=5
	tests=[AWL=-5.000, BAYES_00=-2.599, HTML_MESSAGE=0.001,
	J_BACKHAIR_12=1, J_BACKHAIR_21=1, J_BACKHAIR_22=1, J_BACKHAIR_23=1,
	J_BACKHAIR_24=1, J_BACKHAIR_25=1, J_BACKHAIR_27=1, J_BACKHAIR_32=1,
	J_BACKHAIR_42=1, J_BACKHAIR_52=1, RCVD_IN_DNSWL_MED=-4]
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 N2k0f9H-0oxh for <ancp@core3.amsl.com>;
	Wed,  7 May 2008 07:03:38 -0700 (PDT)
Received: from exprod7og107.obsmtp.com (exprod7og107.obsmtp.com [64.18.2.167])
	by core3.amsl.com (Postfix) with ESMTP id 08E4D3A7166
	for <ancp@ietf.org>; Wed,  7 May 2008 07:03:36 -0700 (PDT)
Received: from source ([66.129.224.36]) by exprod7ob107.postini.com
	([64.18.6.12]) with SMTP; Wed, 07 May 2008 07:03:31 PDT
Received: from proton.jnpr.net ([10.10.2.37]) by emailsmtp55.jnpr.net with
	Microsoft SMTPSVC(6.0.3790.1830); Wed, 7 May 2008 07:02:30 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 7 May 2008 10:02:26 -0400
Message-ID: <9BD5D7887235424FA97DFC223CAE3C28105B8B41@proton.jnpr.net>
In-Reply-To: <D9872168DBD43A41BD71FFC4713274D4050438A2@xmb-ams-33b.emea.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ANCP] Bulk Transaction Message
Thread-Index: AcihZWeDZVeOVtxMS1uttRBEffcNEwAVDjfgAEod1tAAAWRvoAMsB4yQAADCZxAAAKZHUAAJVuxQABJPrxAADmDeEA==
References: <D9872168DBD43A41BD71FFC4713274D405043771@xmb-ams-33b.emea.cisco.com>
	<9BD5D7887235424FA97DFC223CAE3C280AB43A61@proton.jnpr.net>
	<D9872168DBD43A41BD71FFC4713274D4050438A2@xmb-ams-33b.emea.cisco.com>
From: "Sanjay Wadhwa" <swadhwa@juniper.net>
To: "Wojciech Dec (wdec)" <wdec@cisco.com>,
	"Peter Arberg" <parberg@redback.com>, <ancp@ietf.org>
X-OriginalArrivalTime: 07 May 2008 14:02:30.0252 (UTC)
	FILETIME=[FD3952C0:01C8B04A]
Subject: Re: [ANCP] Bulk Transaction Message
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/pipermail/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>
Content-Type: multipart/mixed; boundary="===============1775166401=="
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1775166401==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8B04A.FC1FCB32"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8B04A.FC1FCB32
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Woj

  Inline [SW].

=20

________________________________

From: Wojciech Dec (wdec) [mailto:wdec@cisco.com]=20
Sent: Wednesday, May 07, 2008 3:32 AM
To: Sanjay Wadhwa; Peter Arberg; ancp@ietf.org
Subject: RE: [ANCP] Bulk Transaction Message

=20

Sanjay,

=20

inline

	=20

=09
________________________________


	From: Sanjay Wadhwa [mailto:swadhwa@juniper.net]=20
	Sent: 07 May 2008 02:03
	To: Wojciech Dec (wdec); Peter Arberg; ancp@ietf.org
	Subject: RE: [ANCP] Bulk Transaction Message

	Even with transport being TCP, I see atleast a couple of
benefits:

	=20

	1. If a sender knows it has a bunch of messages to send (e.g.
ANCP adjacency flaps, and all the port-up messages need to re-played),
then bulking by definition allows the application to invoke TCP fewer
times to transmit everything that it needs to transmit, which in a lot
of systems can translate to significant compute and memory efficiency
(specially, if we are considering a large amount of state). This is not
to say one can't realize this in an implementation specific way. =20

	=20

	Woj> Even with bulking one needs to realize the TCP interaction
with some thought. Perhaps bulking indeed offers the opportunity for a
delveloper to think about that, but I seriously doubt that anyone
familar with TCP app development would overlook this aspect in the first
place.

	=20

	[[SW]] I would like to believe it. History doesn't bear this
though.

	=20

	However, if neeeded, bulking also has the benefit of affording
optimized acking (e.g. if no error is encountered in proccessing all the
sub-messages in the bundled message, it is possible for the receiver to
send a cummulative ack to the sender rather than individual acks).=20

	=20

	Woj> A cumulatitive ack would appear to be desirable in some
cases, but I see this as very different to the bulk ack currently
described which essenatially carries in bulk all of the individal acks.
The bulking mechanism is quite clear in saying that each ANCP message is
bundled header and all, and acted upon individually by the recipient,
and whether it's a request or an ack is secondary. I'm sure you'll agree
that this is undesirable overhead and complexity for what it's worth,
also in view of the fact that "something" on the recipient side would
need to decide what ack/nack goes into a bulk response and what doesn't.


	Having a cumulatitive ack is an all thogether different thing,
which I would support, and it should not involve the "bulking" of each
indivdual ack, and is an item that for which proposals are welcome.

	[[SW]] Sorry, I should have been clearer. Bulking adds an
overall header for the individual messages being bulked. If all the
messages succeed, we can define the behavior to send a single ACK (NOT a
bulk ACK composed of individual sub-messages carrying ACK) with the
transaction-ID of the main header reflected back in the ACK.  This
provides an elegant way to address cumulative ACK. This is not defined
in the draft today (see "if needed" above), but is easily provided by
bulking, and can be added if we agree.

	Far as request message is concerned, having individual messages
(with their own header) in the request reduces complexity, provides a
way to bulk messages of different types if needed. It allows each
sub-message to be individually NACK'd where required. Bulking in such a
way allows the flexibility of treating individual sub-messages as
completely independent or related.

	=20

	2. Bulking also provides a nice solution if one ever needed to
atomically receive and process *distinct* ANCP message types. =20

	=20

	Woj> There appears to be no such thing;=20

	[[SW]] Today, but as you mentioned in another thread, we need to
design the protocol to be generic in anticipation of such requirements.

	=20

	=20

	in bulking, presumably the reciever would have to buffer all the
way until the end of the bulk message, and then process each message
individually. This seems rather overweight when compared to simply
sending each message again.

	[[SW]] Draft doesn't impose on how much you bulk. If atomicity
in handling of bulked messages is warranted by a use-case, then yes you
want to get the entire message. If not, you could presumably process as
you receive each complete sub-message within the bundle.

	=20

	What is the downside of having it? It is negotiable as an
optional capability.=20

	=20

	Woj> A couple of reasons come to the fore; i) no body saw a good
reason so far to implement it/use it ii) it's added protocol "stuff"
that has no clear benefit, does not realize any new use-case, does not
optimize much, and in fact as mentioned above it appears to rather have
some downsides such as extra overhead, buffering and delay.

	=20

	Let's now have the axe fall...

	[[SW]] Let us please not be dismissive towards something that
has benefits (as outlined above).

	=20

	Cheers

	-Sanjay

	=20

	=20

	=20

		-----Original Message-----
		From: Wojciech Dec (wdec) [mailto:wdec@cisco.com]
		Sent: Tuesday, May 06, 2008 1:24 PM
		To: Sanjay Wadhwa; Peter Arberg; ancp@ietf.org
		Subject: RE: [ANCP] Bulk Transaction Message

		Sanjay,

		=20

		can you please present to the WG and myself how bulk
transaction capability is useful in any way in terms of scaling for
example? And by the way, please treat this discussion is orthogonal to
any other.

		=20

		Cheers,

		Woj.

		=20

			=20

		=09
________________________________


			From: Sanjay Wadhwa [mailto:swadhwa@juniper.net]

			Sent: 06 May 2008 19:08
			To: Wojciech Dec (wdec); Peter Arberg;
ancp@ietf.org
			Subject: RE: [ANCP] Bulk Transaction Message

			Woj

			  It is a bad idea to remove bulk-transaction
capability from the draft. On one hand you are trying to add "marginally
useful" extensions (with TLVs), and on the other hand you are arguing
for removing useful abstractions which can help with scaling. If
bulk-transaction capability needs to be augmented or modified, then we
should consider augmenting it, rather than removing it from the draft.

			=20

			Cheers

			-Sanjay

				-----Original Message-----
				From: ancp-bounces@ietf.org
[mailto:ancp-bounces@ietf.org]On Behalf Of Wojciech Dec (wdec)
				Sent: Tuesday, May 06, 2008 12:42 PM
				To: Peter Arberg; ancp@ietf.org
				Subject: Re: [ANCP] Bulk Transaction
Message

				Hi Folks,

				=20

				given that no discernable use of Bulk
messaging has been identified, nor there being a good reason for it
given the fact that ANCP is bound to the TCP transport (or equivalent),
I would like to propose to remove all of the text relating to this
capability and associated message from the protocol spec draft.

				=20

				Regards,

				Woj.

				=20

			=09
________________________________


				From: ancp-bounces@ietf.org
[mailto:ancp-bounces@ietf.org] On Behalf Of Wojciech Dec (wdec)
				Sent: 20 April 2008 15:18
				To: Peter Arberg; ancp@ietf.org
				Subject: Re: [ANCP] Bulk Transaction
Message

				Should also have added: Given that
currently the bulk message does not appear to have had any practical
adoption, having the DTeam adopt it/modify it, or possibly have it
removed from the spec all together are all valid options.

				=20

				-Woj.

				=20

			=09
________________________________


				From: ancp-bounces@ietf.org
[mailto:ancp-bounces@ietf.org] On Behalf Of Wojciech Dec (wdec)
				Sent: 20 April 2008 14:39
				To: Peter Arberg; ancp@ietf.org
				Subject: Re: [ANCP] Bulk Transaction
Message

				It's all simple:

				- the Design Team is looking at the
possibility of using this message

				- the message in its current form does
not appear to be terribly useful, and could be removed from the spec.

				=20

				-Woj.

				=20

				=20

			=09
________________________________


				From: ancp-bounces@ietf.org
[mailto:ancp-bounces@ietf.org] On Behalf Of Peter Arberg
				Sent: 19 April 2008 03:07
				To: Wojciech Dec (wdec); ancp@ietf.org
				Subject: Re: [ANCP] Bulk Transaction
Message

				Hi Woj,

				=20

				can you give a little background to why
you are looking for vendor

				implementation support for this specific
capability & message ?

				=20

				thanks,

				Peter

				=20

			=09
________________________________


				From: ancp-bounces@ietf.org
[mailto:ancp-bounces@ietf.org] On Behalf Of Wojciech Dec (wdec)
				Sent: 18. april 2008 08:04
				To: ancp@ietf.org
				Subject: [ANCP] Bulk Transaction Message

				Hi Folks,=20

				Could you please let me/us know if you
currently have an implementation of ANCP that supports the Bulk
Transaction Capability and Message?

				Thanks,=20
				Woj.=20


------_=_NextPart_001_01C8B04A.FC1FCB32
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<title>Bulk Transaction Message</title>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p
	{mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3D"#993366" face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:#993366'>Woj<o:p></o:p>=
</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3D"#993366" face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:#993366'>&nbsp; Inline =
[SW].<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> =
Wojciech Dec
(wdec) [mailto:wdec@cisco.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Wednesday, May 07, =
2008 3:32
AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Sanjay Wadhwa; Peter =
Arberg;
ancp@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [ANCP] Bulk
Transaction Message</span></font><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Sanjay,</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>inline</span></font><o:p></o:p></p>

<blockquote style=3D'border:none;border-left:solid black =
1.5pt;padding:0in 0in 0in 4.0pt;
margin-left:3.75pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'=
>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabIndex=3D-1>

</span></font></div>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><b><font size=3D2 =
face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma;font-weight:bold'>From:</spa=
n></font></b><font
size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'> Sanjay
Wadhwa [mailto:swadhwa@juniper.net] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> 07 May 2008 =
02:03<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Wojciech Dec (wdec); =
Peter
Arberg; ancp@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [ANCP] Bulk
Transaction Message</span></font><o:p></o:p></p>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>Even with transport being TCP, I =
<st1:PersonName
w:st=3D"on">se</st1:PersonName>e atleast a couple of =
benefits:</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>1. If a&nbsp;<st1:PersonName =
w:st=3D"on">se</st1:PersonName>nder
knows it has a bunch of messages to <st1:PersonName =
w:st=3D"on">se</st1:PersonName>nd
(e.g. ANCP adjacency flaps, and all the port-up messages need to =
re-played),
then bulking by definition&nbsp;allows the application to invoke TCP =
fewer
times to transmit&nbsp;everything that it needs to transmit, =
which&nbsp;in a
lot of systems can translate to significant&nbsp;compute and memory =
efficiency
(specially, if we are considering a large amount of state). This&nbsp;is =
not to
say one can't&nbsp;realize this&nbsp;in an implementation specific =
way.&nbsp;</span></font><font
size=3D2 color=3Dblack face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:black'>&nbsp;</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Woj&gt; Even with bulking one needs to realize the =
TCP
interaction with some thought. Perhaps bulking indeed&nbsp;offers the
opportunity for a delveloper to think about that, but I <st1:PersonName =
w:st=3D"on">se</st1:PersonName>riously
doubt that anyone familar with TCP app development&nbsp;would overlook =
this
aspect in the first place.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3D"#993366" face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:#993366'>[[SW]] I =
would like to
believe it. History doesn&#8217;t bear this =
though.<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>However,&nbsp;</span></font><b><font=

size=3D2 color=3Dred face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:red;font-weight:bold'>if neeeded</span></font></b><font size=3D2
color=3Dblue face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:blue'>, bulking also&nbsp;has the benefit of affording optimized =
acking
(e.g. if no error is encountered in proccessing all the sub-messages in =
the
bundled message, it&nbsp;is possible&nbsp;for the receiver to =
<st1:PersonName
w:st=3D"on">se</st1:PersonName>nd a cummulative ack to the =
<st1:PersonName w:st=3D"on">se</st1:PersonName>nder
rather than individual acks).</span></font><font size=3D2 color=3Dblack =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:black'>&nbsp;</span></f=
ont><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:black'>Woj&gt;&nbsp;A cumulatitive ack =
would
appear to be desirable in some ca<st1:PersonName =
w:st=3D"on">se</st1:PersonName>s,
but I <st1:PersonName w:st=3D"on">se</st1:PersonName>e this as
very&nbsp;different to the&nbsp;bulk ack currently described which =
es<st1:PersonName
w:st=3D"on">se</st1:PersonName>natially carries in bulk all of the =
individal
acks.&nbsp;The bulking mechanism is quite clear in saying that each ANCP
message is&nbsp;bundled header and all, and acted upon individually by =
the
recipient, and whether it's a request or an ack is <st1:PersonName =
w:st=3D"on">se</st1:PersonName>condary.
I'm sure you'll agree that this is undesirable overhead and complexity =
for what
it's worth, also in view of the fact that &quot;something&quot; on the
recipient side would need to decide what ack/nack goes into a bulk =
respon<st1:PersonName
w:st=3D"on">se</st1:PersonName> and what doesn't. =
</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:black'>Having a cumulatitive ack is an =
all
thogether different thing, which I would&nbsp;support, and it should not
involve the &quot;bulking&quot; of each indivdual ack, and is an item
that&nbsp;for which&nbsp;proposals are welcome.</span></font><font =
size=3D2
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'><o:p></o:p></span></font></p=
>

<p class=3DMsoNormal><font size=3D2 color=3D"#993366" face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:#993366'>[[SW]] Sorry, =
I should
have been clearer. Bulking adds an overall header for the individual =
messages
being bulked. If all the messages succeed, we can define the behavior to =
<st1:PersonName
w:st=3D"on">se</st1:PersonName>nd a single ACK (NOT a bulk ACK =
compo<st1:PersonName
w:st=3D"on">se</st1:PersonName>d of individual sub-messages carrying =
ACK) with
the transaction-ID of the main header reflected back in the ACK. =
&nbsp;This
provides an elegant way to address cumulative ACK. This is not defined =
in the
draft today (<st1:PersonName w:st=3D"on">se</st1:PersonName>e &#8220;if =
needed&#8221;
above), but is easily provided by bulking, and can be added if we =
agree.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3D"#993366" face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:#993366'>Far as =
request message
is concerned, having individual messages (with their own header) in the =
request
reduces complexity, provides a way to bulk messages of different types =
if
needed. It allows each sub-message to be individually NACK&#8217;d where =
required.
Bulking in such a way allows the flexibility of treating individual
sub-messages as completely independent or =
related.<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>2. Bulking also provides a nice =
solution
if one&nbsp;ever needed to atomically receive and process *distinct* =
ANCP
message types.&nbsp;</span></font><font size=3D2 color=3Dblack =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:black'>&nbsp;</span></f=
ont><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><b><i><font size=3D2 color=3Dnavy =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy;font-weight:bold;
font-style:italic'><o:p>&nbsp;</o:p></span></font></i></b></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:black'>Woj&gt;&nbsp;There appears to be =
no such
thing; </span></font><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3D"#993366" face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:#993366'>[[SW]] Today, =
but as
you mentioned in another thread, we need to design the protocol to be =
generic
in anticipation of such requirements.<i><span =
style=3D'font-style:italic'><o:p></o:p></span></i></span></font></p>

<p class=3DMsoNormal><b><i><font size=3D2 color=3Dnavy =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy;font-weight:bold;
font-style:italic'><o:p>&nbsp;</o:p></span></font></i></b></p>

<p class=3DMsoNormal><b><i><font size=3D2 color=3Dnavy =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy;font-weight:bold;
font-style:italic'><o:p>&nbsp;</o:p></span></font></i></b></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:black'>in bulking, presumably the =
reciever would
have to buffer all the way until the end of the bulk message, and then =
process
each message individually. This <st1:PersonName =
w:st=3D"on">se</st1:PersonName>ems
rather overweight when compared to simply <st1:PersonName =
w:st=3D"on">se</st1:PersonName>nding
each message again.</span></font><font size=3D2 color=3Dnavy =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy'><o:p></o:p></span=
></font></p>

<p class=3DMsoNormal><font size=3D2 color=3D"#993366" face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:#993366'>[[SW]] Draft =
doesn&#8217;t
impo<st1:PersonName w:st=3D"on">se</st1:PersonName> on how much you =
bulk. If
atomicity in handling of bulked messages is warranted by a =
u<st1:PersonName
w:st=3D"on">se</st1:PersonName>-ca<st1:PersonName =
w:st=3D"on">se</st1:PersonName>,
then yes you want to get the entire message. If not, you could =
presumably
process as you receive each complete sub-message within the =
bundle.<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>What is the downside of having it? =
It
is&nbsp;negotiable as an optional capability.</span></font><font =
size=3D2
color=3Dblack face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:black'>&nbsp;</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:black'>Woj&gt; A couple of reasons come =
to the
fore; i) no body saw a good reason so far to implement =
it/u<st1:PersonName
w:st=3D"on">se</st1:PersonName> it ii) it's added protocol =
&quot;stuff&quot; that
has no clear benefit, does not realize any new u<st1:PersonName =
w:st=3D"on">se</st1:PersonName>-ca<st1:PersonName
w:st=3D"on">se</st1:PersonName>,&nbsp;does not optimize much, and in =
fact as
mentioned above it appears to rather have some downsides such as extra
overhead, buffering and delay.</span></font><b><i><font size=3D2 =
color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy;
font-weight:bold;font-style:italic'><o:p></o:p></span></font></i></b></p>=


<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:black'>Let's now have the axe =
fall...</span></font><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3D"#993366" face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:#993366'>[[SW]] Let us =
plea<st1:PersonName
w:st=3D"on">se</st1:PersonName> not be dismissive towards something that =
has benefits
(as outlined above).<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3D"#993366" face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:#993366'>Cheers<o:p></o=
:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3D"#993366" face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:#993366'>-Sanjay<o:p></=
o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

<blockquote style=3D'border:none;border-left:solid blue =
1.5pt;padding:0in 0in 0in 4.0pt;
margin-left:3.75pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'=
>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><font size=3D2 =
face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma'>-----Original =
Message-----<br>
<b><span style=3D'font-weight:bold'>From:</span></b> Wojciech Dec (wdec)
[mailto:wdec@cisco.com]<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Tuesday, May 06, =
2008 1:24
PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Sanjay Wadhwa; Peter =
Arberg;
ancp@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [ANCP] Bulk
Transaction Message</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Sanjay,</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>can you plea<st1:PersonName =
w:st=3D"on">se</st1:PersonName>
pre<st1:PersonName w:st=3D"on">se</st1:PersonName>nt to the WG and =
my<st1:PersonName
w:st=3D"on">se</st1:PersonName>lf how bulk transaction capability is =
u<st1:PersonName
w:st=3D"on">se</st1:PersonName>ful in any way in terms of scaling for =
example?
And by the way, plea<st1:PersonName w:st=3D"on">se</st1:PersonName> =
treat this
discussion is orthogonal to any other.</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Cheers,</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Woj.</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

<blockquote style=3D'border:none;border-left:solid black =
1.5pt;padding:0in 0in 0in 4.0pt;
margin-left:3.75pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'=
>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabIndex=3D-1>

</span></font></div>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><b><font size=3D2 =
face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma;font-weight:bold'>From:</spa=
n></font></b><font
size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'> Sanjay
Wadhwa [mailto:swadhwa@juniper.net] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> 06 May 2008 =
19:08<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Wojciech Dec (wdec); =
Peter
Arberg; ancp@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [ANCP] Bulk
Transaction Message</span></font><o:p></o:p></p>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>Woj</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>&nbsp; It is a bad idea to remove
bulk-transaction capability from the draft. On one hand you are trying =
to add
&quot;marginally u<st1:PersonName =
w:st=3D"on">se</st1:PersonName>ful&quot;
extensions (with TLVs), and on the other hand you are arguing for =
removing u<st1:PersonName
w:st=3D"on">se</st1:PersonName>ful abstractions which can help with =
scaling. If
bulk-transaction capability needs to be augmented or modified, then we =
should
consider augmenting it, rather than removing it from the =
draft.</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>Cheers</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>-Sanjay</span></font><o:p></o:p></p>=


</div>

<blockquote style=3D'border:none;border-left:solid blue =
1.5pt;padding:0in 0in 0in 4.0pt;
margin-left:3.75pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'=
>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><font size=3D2 =
face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma'>-----Original =
Message-----<br>
<b><span style=3D'font-weight:bold'>From:</span></b> =
ancp-bounces@ietf.org
[mailto:ancp-bounces@ietf.org]<b><span style=3D'font-weight:bold'>On =
Behalf Of </span></b>Wojciech
Dec (wdec)<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Tuesday, May 06, =
2008 12:42
PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Peter Arberg; =
ancp@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> Re: [ANCP] Bulk
Transaction Message</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Hi Folks,</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>given that no discernable u<st1:PersonName =
w:st=3D"on">se</st1:PersonName>
of Bulk messaging has been identified, nor&nbsp;there being a good =
reason for
it given the fact that ANCP is bound to the TCP transport (or
equivalent),&nbsp;I would like to propo<st1:PersonName =
w:st=3D"on">se</st1:PersonName>
to remove all of the text relating to this capability and associated =
message
from the protocol spec draft.</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Regards,</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Woj.</span></font><o:p></o:p></p>

<blockquote style=3D'border:none;border-left:solid black =
1.5pt;padding:0in 0in 0in 4.0pt;
margin-left:3.75pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'=
>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabIndex=3D-1>

</span></font></div>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><b><font size=3D2 =
face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma;font-weight:bold'>From:</spa=
n></font></b><font
size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'>
ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] <b><span =
style=3D'font-weight:
bold'>On Behalf Of </span></b>Wojciech Dec (wdec)<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> 20 April 2008 =
15:18<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Peter Arberg; =
ancp@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> Re: [ANCP] Bulk
Transaction Message</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Should also have added: Given that currently&nbsp;the =
bulk
message does not appear to have had any practical&nbsp;adoption, having =
the
DTeam adopt it/modify it, or possibly have it removed from the spec all
together&nbsp;are all valid options.</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>-Woj.</span></font><o:p></o:p></p>

<blockquote style=3D'border:none;border-left:solid black =
1.5pt;padding:0in 0in 0in 4.0pt;
margin-left:3.75pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'=
>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabIndex=3D-1>

</span></font></div>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><b><font size=3D2 =
face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma;font-weight:bold'>From:</spa=
n></font></b><font
size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'>
ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] <b><span =
style=3D'font-weight:
bold'>On Behalf Of </span></b>Wojciech Dec (wdec)<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> 20 April 2008 =
14:39<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Peter Arberg; =
ancp@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> Re: [ANCP] Bulk
Transaction Message</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>It's all simple:</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>-&nbsp;the Design Team is looking at the possibility =
of
using this message</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>- the message in its current form does not appear to =
be
terribly u<st1:PersonName w:st=3D"on">se</st1:PersonName>ful, and could
be&nbsp;removed from the spec.</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>-Woj.</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

<blockquote style=3D'border:none;border-left:solid black =
1.5pt;padding:0in 0in 0in 4.0pt;
margin-left:3.75pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'=
>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabIndex=3D-1>

</span></font></div>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><b><font size=3D2 =
face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma;font-weight:bold'>From:</spa=
n></font></b><font
size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'>
ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] <b><span =
style=3D'font-weight:
bold'>On Behalf Of </span></b>Peter Arberg<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> 19 April 2008 =
03:07<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Wojciech Dec (wdec);
ancp@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> Re: [ANCP] Bulk
Transaction Message</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>Hi =
Woj,</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>can you give a little background to =
why
you are looking for vendor</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>implementation support for this =
specific
capability &amp; message ?</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>thanks,</span></font><o:p></o:p></p>=


<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>Peter</span></font><o:p></o:p></p>

<blockquote style=3D'border:none;border-left:solid blue =
1.5pt;padding:0in 0in 0in 4.0pt;
margin-left:3.75pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'=
>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabIndex=3D-1>

</span></font></div>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><b><font size=3D2 =
face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma;font-weight:bold'>From:</spa=
n></font></b><font
size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'>
ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] <b><span =
style=3D'font-weight:
bold'>On Behalf Of </span></b>Wojciech Dec (wdec)<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> 18. april 2008 =
08:04<br>
<b><span style=3D'font-weight:bold'>To:</span></b> ancp@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> [ANCP] Bulk =
Transaction
Message</span></font><o:p></o:p></p>

<p><font size=3D2 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:
Arial'><!-- Converted from text/rtf format -->Hi =
Folks,</span></font><span
lang=3DEN-GB> </span><o:p></o:p></p>

<p><font size=3D2 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:
Arial'>Could you plea<st1:PersonName w:st=3D"on">se</st1:PersonName> let =
me/us
know if you currently have an implementation of ANCP that supports the =
Bulk
Transaction Capability and Message?</span></font><o:p></o:p></p>

<p><font size=3D2 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:
Arial'>Thanks,</span></font> <br>
<font size=3D2 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:
Arial'>Woj.</span></font><span lang=3DEN-GB> </span><o:p></o:p></p>

</blockquote>

</blockquote>

</blockquote>

</blockquote>

</blockquote>

</blockquote>

</blockquote>

</blockquote>

</div>

</body>

</html>

------_=_NextPart_001_01C8B04A.FC1FCB32--

--===============1775166401==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1775166401==--


From ancp-bounces@ietf.org  Wed May  7 07:32:19 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 7692228C6BF;
	Wed,  7 May 2008 07:32:18 -0700 (PDT)
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 E4C4C28C622
	for <ancp@core3.amsl.com>; Wed,  7 May 2008 07:31:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.638
X-Spam-Level: 
X-Spam-Status: No, score=-0.638 tagged_above=-999 required=5
	tests=[AWL=-4.040, BAYES_00=-2.599, HTML_MESSAGE=0.001,
	J_BACKHAIR_12=1, J_BACKHAIR_21=1, J_BACKHAIR_22=1, J_BACKHAIR_23=1,
	J_BACKHAIR_24=1, J_BACKHAIR_25=1, J_BACKHAIR_27=1, J_BACKHAIR_32=1,
	J_BACKHAIR_42=1, J_BACKHAIR_52=1, RCVD_IN_DNSWL_MED=-4]
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 M3ai7iXgW+AH for <ancp@core3.amsl.com>;
	Wed,  7 May 2008 07:31:09 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id CBAA528C6C1
	for <ancp@ietf.org>; Wed,  7 May 2008 07:27:36 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,448,1204498800"; d="scan'208,217";a="8275649"
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 07 May 2008 16:27:23 +0200
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m47ERMtj023317; 
	Wed, 7 May 2008 16:27:22 +0200
Received: from xbh-ams-332.emea.cisco.com (xbh-ams-332.cisco.com
	[144.254.231.87])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m47ERL7o005906;
	Wed, 7 May 2008 14:27:21 GMT
Received: from xmb-ams-33b.cisco.com ([144.254.231.86]) by
	xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 7 May 2008 16:27:21 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 7 May 2008 16:26:44 +0200
Message-ID: <D9872168DBD43A41BD71FFC4713274D405043C34@xmb-ams-33b.emea.cisco.com>
In-Reply-To: <9BD5D7887235424FA97DFC223CAE3C28105B8B41@proton.jnpr.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ANCP] Bulk Transaction Message
thread-index: AcihZWeDZVeOVtxMS1uttRBEffcNEwAVDjfgAEod1tAAAWRvoAMsB4yQAADCZxAAAKZHUAAJVuxQABJPrxAADmDeEAABcgAQ
References: <D9872168DBD43A41BD71FFC4713274D405043771@xmb-ams-33b.emea.cisco.com>
	<9BD5D7887235424FA97DFC223CAE3C280AB43A61@proton.jnpr.net>
	<D9872168DBD43A41BD71FFC4713274D4050438A2@xmb-ams-33b.emea.cisco.com>
	<9BD5D7887235424FA97DFC223CAE3C28105B8B41@proton.jnpr.net>
From: "Wojciech Dec (wdec)" <wdec@cisco.com>
To: "Sanjay Wadhwa" <swadhwa@juniper.net>,
	"Peter Arberg" <parberg@redback.com>, <ancp@ietf.org>
X-OriginalArrivalTime: 07 May 2008 14:27:21.0856 (UTC)
	FILETIME=[764A0800:01C8B04E]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=56240; t=1210170442;
	x=1211034442; c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=wdec@cisco.com;
	z=From:=20=22Wojciech=20Dec=20(wdec)=22=20<wdec@cisco.com>
	|Subject:=20RE=3A=20[ANCP]=20Bulk=20Transaction=20Message
	|Sender:=20; bh=FRI1r2UsXtNzRXAJV6WmGrIKmlg349BlCrt6ubViIYs=;
	b=thYMQhgtwNneHiDMSJyY1Y9im685BesgFMYhTSeXR1vuB8dN94ghYWe44F
	15hSfEloECDbmfbbqH4UJuf1AqEik6ek+V0gzxsbNHWBDZLgFSAbegPVRqrl
	PURzFTamwv;
Authentication-Results: ams-dkim-1; header.From=wdec@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
Subject: Re: [ANCP] Bulk Transaction Message
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/pipermail/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>
Content-Type: multipart/mixed; boundary="===============2034357513=="
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org

This is a multi-part message in MIME format.

--===============2034357513==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8B04E.75FC742D"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8B04E.75FC742D
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Sanjay,
=20
inline woj#2>


________________________________

	From: Sanjay Wadhwa [mailto:swadhwa@juniper.net]=20
	Sent: 07 May 2008 16:02
	To: Wojciech Dec (wdec); Peter Arberg; ancp@ietf.org
	Subject: RE: [ANCP] Bulk Transaction Message
=09
=09

	Woj

	  Inline [SW].

	=20

=09
________________________________


	From: Wojciech Dec (wdec) [mailto:wdec@cisco.com]=20
	Sent: Wednesday, May 07, 2008 3:32 AM
	To: Sanjay Wadhwa; Peter Arberg; ancp@ietf.org
	Subject: RE: [ANCP] Bulk Transaction Message

	=20

	Sanjay,

	=20

	inline

		=20

	=09
________________________________


		From: Sanjay Wadhwa [mailto:swadhwa@juniper.net]=20
		Sent: 07 May 2008 02:03
		To: Wojciech Dec (wdec); Peter Arberg; ancp@ietf.org
		Subject: RE: [ANCP] Bulk Transaction Message

		Even with transport being TCP, I see atleast a couple of
benefits:

		=20

		1. If a sender knows it has a bunch of messages to send
(e.g. ANCP adjacency flaps, and all the port-up messages need to
re-played), then bulking by definition allows the application to invoke
TCP fewer times to transmit everything that it needs to transmit, which
in a lot of systems can translate to significant compute and memory
efficiency (specially, if we are considering a large amount of state).
This is not to say one can't realize this in an implementation specific
way. =20

		=20

		Woj> Even with bulking one needs to realize the TCP
interaction with some thought. Perhaps bulking indeed offers the
opportunity for a delveloper to think about that, but I seriously doubt
that anyone familar with TCP app development would overlook this aspect
in the first place.

		=20

		[[SW]] I would like to believe it. History doesn't bear
this though.=20

		=20

		Woj#2> Unless the spec forces Bulking to be used for
every single multi-message exchange, the bunching effect will not
appear, nor will any optimization.

		=20

		However, if neeeded, bulking also has the benefit of
affording optimized acking (e.g. if no error is encountered in
proccessing all the sub-messages in the bundled message, it is possible
for the receiver to send a cummulative ack to the sender rather than
individual acks).=20

		=20

		Woj> A cumulatitive ack would appear to be desirable in
some cases, but I see this as very different to the bulk ack currently
described which essenatially carries in bulk all of the individal acks.
The bulking mechanism is quite clear in saying that each ANCP message is
bundled header and all, and acted upon individually by the recipient,
and whether it's a request or an ack is secondary. I'm sure you'll agree
that this is undesirable overhead and complexity for what it's worth,
also in view of the fact that "something" on the recipient side would
need to decide what ack/nack goes into a bulk response and what doesn't.


		Having a cumulatitive ack is an all thogether different
thing, which I would support, and it should not involve the "bulking" of
each indivdual ack, and is an item that for which proposals are welcome.

		[[SW]] Sorry, I should have been clearer. Bulking adds
an overall header for the individual messages being bulked. If all the
messages succeed, we can define the behavior to send a single ACK (NOT a
bulk ACK composed of individual sub-messages carrying ACK) with the
transaction-ID of the main header reflected back in the ACK.  This
provides an elegant way to address cumulative ACK. This is not defined
in the draft today (see "if needed" above), but is easily provided by
bulking, and can be added if we agree.

		Far as request message is concerned, having individual
messages (with their own header) in the request reduces complexity,
provides a way to bulk messages of different types if needed. It allows
each sub-message to be individually NACK'd where required. Bulking in
such a way allows the flexibility of treating individual sub-messages as
completely independent or related.=20

		=20

		Woj#2> The above, in principle is fine, BUT it is far
removed from the current bulking mechanism. The order would be to have a
proposal regarding this on its own right.=20

		=20

		2. Bulking also provides a nice solution if one ever
needed to atomically receive and process *distinct* ANCP message types.


		=20

		Woj> There appears to be no such thing;=20

		[[SW]] Today, but as you mentioned in another thread, we
need to design the protocol to be generic in anticipation of such
requirements.=20

		=20

		Woj#2> What tentative requirements are you referring to,
a relay? If so, bulking doesn't help there. This is also much different
from a discussion about a generic TLV format that is to be used by the
protocol.

		=20

		=20

		in bulking, presumably the reciever would have to buffer
all the way until the end of the bulk message, and then process each
message individually. This seems rather overweight when compared to
simply sending each message again.

		[[SW]] Draft doesn't impose on how much you bulk. If
atomicity in handling of bulked messages is warranted by a use-case,
then yes you want to get the entire message. If not, you could
presumably process as you receive each complete sub-message within the
bundle.=20

		=20

		Woj#2> Adding a single bulk envelope and sending inside
it 100 messages vs 2 bulk envelopes with 50 messages is also pretty
pointless, and an exercise in optimizing something that isn't needed in
the first place: In each case you're still sending 100 messages! The
downside is that in either of the bulked messages case you generally
will have to wait till the full message is received. There are betterTCP
access=20

		=20

		What is the downside of having it? It is negotiable as
an optional capability.=20

		=20

		Woj> A couple of reasons come to the fore; i) no body
saw a good reason so far to implement it/use it ii) it's added protocol
"stuff" that has no clear benefit, does not realize any new use-case,
does not optimize much, and in fact as mentioned above it appears to
rather have some downsides such as extra overhead, buffering and delay.

		=20

		Let's now have the axe fall...

		[[SW]] Let us please not be dismissive towards something
that has benefits (as outlined above).=20

		=20

		Wo#2j>  With the exception of cumulative ack, which does
deserve a standalone proposal to be put forward, neither me nor other
members of the WG do appear to share the views regarding the purported
benefits on bulking, nor a desire to retain it in the spec. Sorry, it
just needs to go.

		=20

		Cheers,

		Woj.

		=20

		Cheers

		-Sanjay

		=20

		=20

		=20

			-----Original Message-----
			From: Wojciech Dec (wdec)
[mailto:wdec@cisco.com]
			Sent: Tuesday, May 06, 2008 1:24 PM
			To: Sanjay Wadhwa; Peter Arberg; ancp@ietf.org
			Subject: RE: [ANCP] Bulk Transaction Message

			Sanjay,

			=20

			can you please present to the WG and myself how
bulk transaction capability is useful in any way in terms of scaling for
example? And by the way, please treat this discussion is orthogonal to
any other.

			=20

			Cheers,

			Woj.

			=20

				=20

			=09
________________________________


				From: Sanjay Wadhwa
[mailto:swadhwa@juniper.net]=20
				Sent: 06 May 2008 19:08
				To: Wojciech Dec (wdec); Peter Arberg;
ancp@ietf.org
				Subject: RE: [ANCP] Bulk Transaction
Message

				Woj

				  It is a bad idea to remove
bulk-transaction capability from the draft. On one hand you are trying
to add "marginally useful" extensions (with TLVs), and on the other hand
you are arguing for removing useful abstractions which can help with
scaling. If bulk-transaction capability needs to be augmented or
modified, then we should consider augmenting it, rather than removing it
from the draft.

				=20

				Cheers

				-Sanjay

				-----Original Message-----
				From: ancp-bounces@ietf.org
[mailto:ancp-bounces@ietf.org]On Behalf Of Wojciech Dec (wdec)
				Sent: Tuesday, May 06, 2008 12:42 PM
				To: Peter Arberg; ancp@ietf.org
				Subject: Re: [ANCP] Bulk Transaction
Message

				Hi Folks,

				=20

				given that no discernable use of Bulk
messaging has been identified, nor there being a good reason for it
given the fact that ANCP is bound to the TCP transport (or equivalent),
I would like to propose to remove all of the text relating to this
capability and associated message from the protocol spec draft.

				=20

				Regards,

				Woj.

				=20

			=09
________________________________


				From: ancp-bounces@ietf.org
[mailto:ancp-bounces@ietf.org] On Behalf Of Wojciech Dec (wdec)
				Sent: 20 April 2008 15:18
				To: Peter Arberg; ancp@ietf.org
				Subject: Re: [ANCP] Bulk Transaction
Message

				Should also have added: Given that
currently the bulk message does not appear to have had any practical
adoption, having the DTeam adopt it/modify it, or possibly have it
removed from the spec all together are all valid options.

				=20

				-Woj.

				=20

			=09
________________________________


				From: ancp-bounces@ietf.org
[mailto:ancp-bounces@ietf.org] On Behalf Of Wojciech Dec (wdec)
				Sent: 20 April 2008 14:39
				To: Peter Arberg; ancp@ietf.org
				Subject: Re: [ANCP] Bulk Transaction
Message

				It's all simple:

				- the Design Team is looking at the
possibility of using this message

				- the message in its current form does
not appear to be terribly useful, and could be removed from the spec.

				=20

				-Woj.

				=20

				=20

			=09
________________________________


				From: ancp-bounces@ietf.org
[mailto:ancp-bounces@ietf.org] On Behalf Of Peter Arberg
				Sent: 19 April 2008 03:07
				To: Wojciech Dec (wdec); ancp@ietf.org
				Subject: Re: [ANCP] Bulk Transaction
Message

				Hi Woj,

				=20

				can you give a little background to why
you are looking for vendor

				implementation support for this specific
capability & message ?

				=20

				thanks,

				Peter

				=20

			=09
________________________________


				From: ancp-bounces@ietf.org
[mailto:ancp-bounces@ietf.org] On Behalf Of Wojciech Dec (wdec)
				Sent: 18. april 2008 08:04
				To: ancp@ietf.org
				Subject: [ANCP] Bulk Transaction Message

				Hi Folks,=20

				Could you please let me/us know if you
currently have an implementation of ANCP that supports the Bulk
Transaction Capability and Message?

				Thanks,=20
				Woj.=20


------_=_NextPart_001_01C8B04E.75FC742D
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:st1 =3D=20
"urn:schemas-microsoft-com:office:smarttags"><HEAD><TITLE>Bulk =
Transaction Message</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3314" name=3DGENERATOR><!--[if !mso]>
<STYLE>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</STYLE>
<![endif]--><o:SmartTagType name=3D"PersonName"=20
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"></o:SmartTagT=
ype><!--[if !mso]>
<STYLE>
st1\:*{behavior:url(#default#ieooui) }
</STYLE>
<![endif]-->
<STYLE>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p
	{mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</STYLE>
</HEAD>
<BODY lang=3DEN-US vLink=3Dpurple link=3Dblue>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D625490414-07052008><FONT =
face=3DArial=20
size=3D2>Sanjay,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D625490414-07052008><FONT =
face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D625490414-07052008><FONT =
face=3DArial=20
size=3D2>inline woj#2&gt;</FONT></SPAN></DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Sanjay Wadhwa=20
  [mailto:swadhwa@juniper.net] <BR><B>Sent:</B> 07 May 2008 =
16:02<BR><B>To:</B>=20
  Wojciech Dec (wdec); Peter Arberg; ancp@ietf.org<BR><B>Subject:</B> =
RE: [ANCP]=20
  Bulk Transaction Message<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV class=3DSection1>
  <P class=3DMsoNormal><FONT face=3DArial color=3D#993366 size=3D2><SPAN =

  style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: =
Arial">Woj<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3D#993366 size=3D2><SPAN =

  style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: Arial">&nbsp; =
Inline=20
  [SW].<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <DIV>
  <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
  face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
  <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
  </SPAN></FONT></DIV>
  <P class=3DMsoNormal><B><FONT face=3DTahoma size=3D2><SPAN=20
  style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
  face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">=20
  Wojciech Dec (wdec) [mailto:wdec@cisco.com] <BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Wednesday, May 07, 2008 =
3:32=20
  AM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Sanjay =
Wadhwa; Peter=20
  Arberg; ancp@ietf.org<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [ANCP] Bulk =
Transaction=20
  Message</SPAN></FONT><o:p></o:p></P></DIV>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Sanjay,</SPAN></FONT><o:p></o:p></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">inline</SPAN></FONT><o:p></o:p></P>
  <BLOCKQUOTE=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: 5pt 0in 5pt =
3.75pt; BORDER-LEFT: black 1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none">
    <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
    style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
    <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
    face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
    <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
    </SPAN></FONT></DIV>
    <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><B><FONT =
face=3DTahoma=20
    size=3D2><SPAN=20
    style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
    face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">=20
    Sanjay Wadhwa [mailto:swadhwa@juniper.net] <BR><B><SPAN=20
    style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> 07 May 2008 =
02:03<BR><B><SPAN=20
    style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Wojciech Dec (wdec); =
Peter Arberg;=20
    ancp@ietf.org<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">Subject:</SPAN></B> RE:=20
    [ANCP] Bulk Transaction Message</SPAN></FONT><o:p></o:p></P>
    <DIV>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">Even with =
transport=20
    being TCP, I <st1:PersonName w:st=3D"on">se</st1:PersonName>e =
atleast a couple=20
    of benefits:</SPAN></FONT><o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
    style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
    <DIV>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">1. If=20
    a&nbsp;<st1:PersonName w:st=3D"on">se</st1:PersonName>nder knows it =
has a=20
    bunch of messages to <st1:PersonName =
w:st=3D"on">se</st1:PersonName>nd (e.g.=20
    ANCP adjacency flaps, and all the port-up messages need to =
re-played), then=20
    bulking by definition&nbsp;allows the application to invoke TCP =
fewer times=20
    to transmit&nbsp;everything that it needs to transmit, which&nbsp;in =
a lot=20
    of systems can translate to significant&nbsp;compute and memory =
efficiency=20
    (specially, if we are considering a large amount of state). =
This&nbsp;is not=20
    to say one can't&nbsp;realize this&nbsp;in an implementation =
specific=20
    way.&nbsp;</SPAN></FONT><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
    style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
    <DIV>
    <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Woj&gt; Even with =
bulking one=20
    needs to realize the TCP interaction with some thought. Perhaps =
bulking=20
    indeed&nbsp;offers the opportunity for a delveloper to think about =
that, but=20
    I <st1:PersonName w:st=3D"on">se</st1:PersonName>riously doubt that =
anyone=20
    familar with TCP app development&nbsp;would overlook this aspect in =
the=20
    first place.<o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT color=3D#993366><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: Arial">[[SW]] =
I would=20
    like to believe it. History doesn&#8217;t bear this though.<FONT=20
    color=3D#000000><SPAN=20
    class=3D625490414-07052008>&nbsp;</SPAN></FONT></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT color=3D#993366><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: Arial"><FONT=20
    color=3D#000000><SPAN=20
    class=3D625490414-07052008></SPAN></FONT></SPAN></FONT>&nbsp;</P>
    <P class=3DMsoNormal><FONT color=3D#993366><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: Arial"><FONT=20
    color=3D#000000><SPAN =
class=3D625490414-07052008>Woj#2&gt;&nbsp;Unless the spec=20
    forces Bulking to be used for every single multi-message exchange, =
the=20
    bunching effect will not appear, nor will any=20
    optimization.</SPAN></FONT></SPAN></FONT></P></DIV>
    <DIV>
    <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
    style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
    <DIV>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">However,&nbsp;</SPAN></FONT><B><FONT=20
    face=3DArial color=3Dred size=3D2><SPAN=20
    style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: red; =
FONT-FAMILY: Arial">if=20
    neeeded</SPAN></FONT></B><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">, bulking =

    also&nbsp;has the benefit of affording optimized acking (e.g. if no =
error is=20
    encountered in proccessing all the sub-messages in the bundled =
message,=20
    it&nbsp;is possible&nbsp;for the receiver to <st1:PersonName=20
    w:st=3D"on">se</st1:PersonName>nd a cummulative ack to the =
<st1:PersonName=20
    w:st=3D"on">se</st1:PersonName>nder rather than individual=20
    acks).</SPAN></FONT><FONT face=3DArial color=3Dblack size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
    style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
    <DIV>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =

    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Woj&gt;&nbsp;A=20
    cumulatitive ack would appear to be desirable in some =
ca<st1:PersonName=20
    w:st=3D"on">se</st1:PersonName>s, but I <st1:PersonName=20
    w:st=3D"on">se</st1:PersonName>e this as very&nbsp;different to =
the&nbsp;bulk=20
    ack currently described which es<st1:PersonName=20
    w:st=3D"on">se</st1:PersonName>natially carries in bulk all of the =
individal=20
    acks.&nbsp;The bulking mechanism is quite clear in saying that each =
ANCP=20
    message is&nbsp;bundled header and all, and acted upon individually =
by the=20
    recipient, and whether it's a request or an ack is <st1:PersonName=20
    w:st=3D"on">se</st1:PersonName>condary. I'm sure you'll agree that =
this is=20
    undesirable overhead and complexity for what it's worth, also in =
view of the=20
    fact that "something" on the recipient side would need to decide =
what=20
    ack/nack goes into a bulk respon<st1:PersonName=20
    w:st=3D"on">se</st1:PersonName> and what doesn't.=20
    </SPAN></FONT><o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =

    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Having a =

    cumulatitive ack is an all thogether different thing, which I=20
    would&nbsp;support, and it should not involve the "bulking" of each=20
    indivdual ack, and is an item that&nbsp;for which&nbsp;proposals are =

    welcome.</SPAN></FONT><FONT face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: Arial">[[SW]] =
Sorry, I=20
    should have been clearer. Bulking adds an overall header for the =
individual=20
    messages being bulked. If all the messages succeed, we can define =
the=20
    behavior to <st1:PersonName w:st=3D"on">se</st1:PersonName>nd a =
single ACK=20
    (NOT a bulk ACK compo<st1:PersonName =
w:st=3D"on">se</st1:PersonName>d of=20
    individual sub-messages carrying ACK) with the transaction-ID of the =
main=20
    header reflected back in the ACK. &nbsp;This provides an elegant way =
to=20
    address cumulative ACK. This is not defined in the draft today=20
    (<st1:PersonName w:st=3D"on">se</st1:PersonName>e &#8220;if =
needed&#8221; above), but is=20
    easily provided by bulking, and can be added if we=20
    agree.<o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT color=3D#993366><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: Arial">Far as =
request=20
    message is concerned, having individual messages (with their own =
header) in=20
    the request reduces complexity, provides a way to bulk messages of =
different=20
    types if needed. It allows each sub-message to be individually =
NACK&#8217;d where=20
    required. Bulking in such a way allows the flexibility of treating=20
    individual sub-messages as completely independent or related.<FONT=20
    color=3D#000000><SPAN=20
    class=3D625490414-07052008>&nbsp;</SPAN></FONT></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT color=3D#993366><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: Arial"><FONT=20
    color=3D#000000><SPAN=20
    class=3D625490414-07052008></SPAN></FONT></SPAN></FONT>&nbsp;</P>
    <P class=3DMsoNormal><FONT color=3D#993366><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: Arial"><FONT=20
    color=3D#000000><SPAN class=3D625490414-07052008>Woj#2&gt; The =
above, in=20
    principle is fine, BUT it is far removed from the current bulking =
mechanism.=20
    The order would be to have a proposal regarding this&nbsp;on its own =

    right.&nbsp;</SPAN><o:p></o:p></FONT></SPAN></FONT></P></DIV>
    <DIV>
    <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
    style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
    <DIV>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">2. =
Bulking also=20
    provides a nice solution if one&nbsp;ever needed to atomically =
receive and=20
    process *distinct* ANCP message types.&nbsp;</SPAN></FONT><FONT =
face=3DArial=20
    color=3Dblack size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><FONT=20
    face=3DArial color=3Dnavy size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><B><I><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
    style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: navy; =
FONT-STYLE: italic; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></I></B></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =

    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Woj&gt;&nbsp;There=20
    appears to be no such thing; </SPAN></FONT><FONT face=3DArial =
color=3Dnavy=20
    size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT color=3D#993366><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: Arial">[[SW]] =
Today,=20
    but as you mentioned in another thread, we need to design the =
protocol to be=20
    generic in anticipation of such requirements.<FONT =
color=3D#000000><SPAN=20
    class=3D625490414-07052008>&nbsp;</SPAN></FONT></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT color=3D#993366><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: Arial"><FONT=20
    color=3D#000000><SPAN=20
    class=3D625490414-07052008></SPAN></FONT></SPAN></FONT>&nbsp;</P>
    <P class=3DMsoNormal><FONT color=3D#993366><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: Arial"><FONT=20
    color=3D#000000><SPAN class=3D625490414-07052008>Woj#2&gt; What =
tentative=20
    requirements are you referring to, a&nbsp;relay?&nbsp;If =
so,&nbsp;bulking=20
    doesn't help there. This is also much different from a discussion =
about a=20
    generic TLV format that is to be used by the=20
    protocol.</SPAN></FONT></SPAN></FONT></P>
    <P class=3DMsoNormal><B><I><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
    style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: navy; =
FONT-STYLE: italic; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></I></B></P>
    <P class=3DMsoNormal><B><I><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
    style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: navy; =
FONT-STYLE: italic; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></I></B></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =

    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">in =
bulking,=20
    presumably the reciever would have to buffer all the way until the =
end of=20
    the bulk message, and then process each message individually. This=20
    <st1:PersonName w:st=3D"on">se</st1:PersonName>ems rather overweight =
when=20
    compared to simply <st1:PersonName =
w:st=3D"on">se</st1:PersonName>nding each=20
    message again.</SPAN></FONT><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT color=3D#993366><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: Arial">[[SW]] =
Draft=20
    doesn&#8217;t impo<st1:PersonName w:st=3D"on">se</st1:PersonName> on =
how much you=20
    bulk. If atomicity in handling of bulked messages is warranted by a=20
    u<st1:PersonName w:st=3D"on">se</st1:PersonName>-ca<st1:PersonName=20
    w:st=3D"on">se</st1:PersonName>, then yes you want to get the entire =
message.=20
    If not, you could presumably process as you receive each complete=20
    sub-message within the bundle.<FONT color=3D#000000><SPAN=20
    class=3D625490414-07052008>&nbsp;</SPAN></FONT></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT color=3D#993366><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: Arial"><FONT=20
    color=3D#000000><SPAN=20
    class=3D625490414-07052008></SPAN></FONT></SPAN></FONT>&nbsp;</P>
    <P class=3DMsoNormal><FONT color=3D#993366><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: Arial"><FONT=20
    color=3D#000000><SPAN class=3D625490414-07052008>Woj#2&gt; Adding a =
single bulk=20
    envelope and sending inside it&nbsp;100 messages vs 2 bulk envelopes =
with 50=20
    messages is also pretty pointless, and an exercise in optimizing =
something=20
    that isn't needed in the first place: In each case you're still =
sending 100=20
    messages! The downside is that in either of the bulked messages case =
you=20
    generally will have to wait till the full message is received. There =
are=20
    betterTCP access </SPAN></FONT></SPAN></FONT></P></DIV>
    <DIV>
    <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
    style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
    <DIV>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">What is =
the=20
    downside of having it? It is&nbsp;negotiable as an optional=20
    capability.</SPAN></FONT><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><o:p></o:p></P></DIV>
    <DIV>
    <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
    style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
    <DIV>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =

    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Woj&gt; =
A couple=20
    of reasons come to the fore; i) no body saw a good reason so far to=20
    implement it/u<st1:PersonName w:st=3D"on">se</st1:PersonName> it ii) =
it's=20
    added protocol "stuff" that has no clear benefit, does not realize =
any new=20
    u<st1:PersonName w:st=3D"on">se</st1:PersonName>-ca<st1:PersonName=20
    w:st=3D"on">se</st1:PersonName>,&nbsp;does not optimize much, and in =
fact as=20
    mentioned above it appears to rather have some downsides such as =
extra=20
    overhead, buffering and delay.</SPAN></FONT><B><I><FONT face=3DArial =

    color=3Dnavy size=3D2><SPAN=20
    style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: navy; =
FONT-STYLE: italic; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></I></B></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPAN =

    style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Let's =
now have the=20
    axe fall...</SPAN></FONT><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT color=3D#993366><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: Arial">[[SW]] =
Let us=20
    plea<st1:PersonName w:st=3D"on">se</st1:PersonName> not be =
dismissive towards=20
    something that has benefits (as outlined above).<FONT =
color=3D#000000><SPAN=20
    class=3D625490414-07052008>&nbsp;</SPAN></FONT></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT color=3D#993366><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: Arial"><FONT=20
    color=3D#000000><SPAN=20
    class=3D625490414-07052008></SPAN></FONT></SPAN></FONT>&nbsp;</P>
    <P class=3DMsoNormal><FONT color=3D#993366><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: Arial"><FONT=20
    color=3D#000000><SPAN class=3D625490414-07052008>Wo#2j&gt; =
&nbsp;With the=20
    exception of cumulative ack, which does deserve a standalone =
proposal to be=20
    put forward, neither me nor&nbsp;other members of the&nbsp;WG =
do&nbsp;appear=20
    to share the views regarding the purported benefits on bulking, nor =
a desire=20
    to retain it in the spec.&nbsp;Sorry, it just needs to=20
    go.</SPAN></FONT></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT color=3D#993366><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: Arial"><FONT=20
    color=3D#000000><SPAN=20
    class=3D625490414-07052008></SPAN></FONT></SPAN></FONT>&nbsp;</P>
    <P class=3DMsoNormal><FONT color=3D#993366><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: Arial"><FONT=20
    color=3D#000000><SPAN=20
    class=3D625490414-07052008>Cheers,</SPAN></FONT></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT color=3D#993366><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: Arial"><FONT=20
    color=3D#000000><SPAN=20
    class=3D625490414-07052008>Woj.</SPAN></FONT></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: =
Arial">Cheers<o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: =
Arial">-Sanjay<o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P></DIV>
    <DIV>
    <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
    style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
    <DIV>
    <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
    style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P></DIV>
    <BLOCKQUOTE=20
    style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: 5pt 0in 5pt =
3.75pt; BORDER-LEFT: blue 1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none">
      <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><FONT =
face=3DTahoma=20
      size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">-----Original=20
      Message-----<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">From:</SPAN></B>=20
      Wojciech Dec (wdec) [mailto:wdec@cisco.com]<BR><B><SPAN=20
      style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Tuesday, May 06, 2008 =
1:24=20
      PM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Sanjay =
Wadhwa;=20
      Peter Arberg; ancp@ietf.org<BR><B><SPAN=20
      style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [ANCP] Bulk =
Transaction=20
      Message</SPAN></FONT><o:p></o:p></P>
      <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Sanjay,</SPAN></FONT><o:p></o:p></P>
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =

      style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">can you =
plea<st1:PersonName=20
      w:st=3D"on">se</st1:PersonName> pre<st1:PersonName=20
      w:st=3D"on">se</st1:PersonName>nt to the WG and my<st1:PersonName=20
      w:st=3D"on">se</st1:PersonName>lf how bulk transaction capability =
is=20
      u<st1:PersonName w:st=3D"on">se</st1:PersonName>ful in any way in =
terms of=20
      scaling for example? And by the way, plea<st1:PersonName=20
      w:st=3D"on">se</st1:PersonName> treat this discussion is =
orthogonal to any=20
      other.</SPAN></FONT><o:p></o:p></P>
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =

      style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Cheers,</SPAN></FONT><o:p></o:p></P>
      <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Woj.</SPAN></FONT><o:p></o:p></P>
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =

      style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
      <BLOCKQUOTE=20
      style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; =
BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: =
5pt 0in 5pt 3.75pt; BORDER-LEFT: black 1.5pt solid; PADDING-TOP: 0in; =
BORDER-BOTTOM: medium none">
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
        style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
        <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
        face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: =
12pt">
        <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
        </SPAN></FONT></DIV>
        <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><B><FONT =
face=3DTahoma=20
        size=3D2><SPAN=20
        style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
        face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Tahoma">=20
        Sanjay Wadhwa [mailto:swadhwa@juniper.net] <BR><B><SPAN=20
        style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> 06 May 2008 =
19:08<BR><B><SPAN=20
        style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Wojciech Dec (wdec); =
Peter=20
        Arberg; ancp@ietf.org<BR><B><SPAN=20
        style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [ANCP] Bulk=20
        Transaction Message</SPAN></FONT><o:p></o:p></P>
        <DIV>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Woj</SPAN></FONT><o:p></o:p></P></DIV>
        <DIV>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp; It is a=20
        bad idea to remove bulk-transaction capability from the draft. =
On one=20
        hand you are trying to add "marginally u<st1:PersonName=20
        w:st=3D"on">se</st1:PersonName>ful" extensions (with TLVs), and =
on the=20
        other hand you are arguing for removing u<st1:PersonName=20
        w:st=3D"on">se</st1:PersonName>ful abstractions which can help =
with=20
        scaling. If bulk-transaction capability needs to be augmented or =

        modified, then we should consider augmenting it, rather than =
removing it=20
        from the draft.</SPAN></FONT><o:p></o:p></P></DIV>
        <DIV>
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
        style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
        <DIV>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Cheers</SPAN></FONT><o:p></o:p></P></DIV>
        <DIV>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">-Sanjay</SPAN></FONT><o:p></o:p></P></DIV>
        <BLOCKQUOTE=20
        style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; =
BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: =
5pt 0in 5pt 3.75pt; BORDER-LEFT: blue 1.5pt solid; PADDING-TOP: 0in; =
BORDER-BOTTOM: medium none">
          <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><FONT =
face=3DTahoma=20
          size=3D2><SPAN=20
          style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">-----Original=20
          Message-----<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">From:</SPAN></B>=20
          ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org]<B><SPAN=20
          style=3D"FONT-WEIGHT: bold">On Behalf Of </SPAN></B>Wojciech =
Dec=20
          (wdec)<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">Sent:</SPAN></B> Tuesday,=20
          May 06, 2008 12:42 PM<BR><B><SPAN=20
          style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Peter Arberg;=20
          ancp@ietf.org<BR><B><SPAN=20
          style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> Re: [ANCP] =
Bulk=20
          Transaction Message</SPAN></FONT><o:p></o:p></P>
          <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
          style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Hi=20
          Folks,</SPAN></FONT><o:p></o:p></P>
          <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
          style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
          <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
          style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">given that no =
discernable=20
          u<st1:PersonName w:st=3D"on">se</st1:PersonName> of Bulk =
messaging has=20
          been identified, nor&nbsp;there being a good reason for it =
given the=20
          fact that ANCP is bound to the TCP transport (or =
equivalent),&nbsp;I=20
          would like to propo<st1:PersonName =
w:st=3D"on">se</st1:PersonName> to=20
          remove all of the text relating to this capability and =
associated=20
          message from the protocol spec =
draft.</SPAN></FONT><o:p></o:p></P>
          <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
          style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
          <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
          style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Regards,</SPAN></FONT><o:p></o:p></P>
          <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
          style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Woj.</SPAN></FONT><o:p></o:p></P>
          <BLOCKQUOTE=20
          style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; =
BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: =
5pt 0in 5pt 3.75pt; BORDER-LEFT: black 1.5pt solid; PADDING-TOP: 0in; =
BORDER-BOTTOM: medium none">
            <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
            style=3D"FONT-SIZE: =
12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
            <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
            face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: =
12pt">
            <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
            </SPAN></FONT></DIV>
            <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><B><FONT =
face=3DTahoma=20
            size=3D2><SPAN=20
            style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
            face=3DTahoma size=3D2><SPAN=20
            style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma"> =
ancp-bounces@ietf.org=20
            [mailto:ancp-bounces@ietf.org] <B><SPAN =
style=3D"FONT-WEIGHT: bold">On=20
            Behalf Of </SPAN></B>Wojciech Dec (wdec)<BR><B><SPAN=20
            style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> 20 April 2008=20
            15:18<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> =
Peter=20
            Arberg; ancp@ietf.org<BR><B><SPAN=20
            style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> Re: [ANCP] =
Bulk=20
            Transaction Message</SPAN></FONT><o:p></o:p></P>
            <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
            style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Should also =
have added:=20
            Given that currently&nbsp;the bulk message does not appear =
to have=20
            had any practical&nbsp;adoption, having the DTeam adopt =
it/modify=20
            it, or possibly have it removed from the spec all =
together&nbsp;are=20
            all valid options.</SPAN></FONT><o:p></o:p></P>
            <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
            style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
            <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
            style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">-Woj.</SPAN></FONT><o:p></o:p></P>
            <BLOCKQUOTE=20
            style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; =
BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: =
5pt 0in 5pt 3.75pt; BORDER-LEFT: black 1.5pt solid; PADDING-TOP: 0in; =
BORDER-BOTTOM: medium none">
              <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
              style=3D"FONT-SIZE: =
12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
              <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
              face=3D"Times New Roman" size=3D3><SPAN =
style=3D"FONT-SIZE: 12pt">
              <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
              </SPAN></FONT></DIV>
              <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: =
12pt"><B><FONT=20
              face=3DTahoma size=3D2><SPAN=20
              style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
              face=3DTahoma size=3D2><SPAN=20
              style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">=20
              ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] =
<B><SPAN=20
              style=3D"FONT-WEIGHT: bold">On Behalf Of =
</SPAN></B>Wojciech Dec=20
              (wdec)<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">Sent:</SPAN></B> 20=20
              April 2008 14:39<BR><B><SPAN=20
              style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Peter Arberg;=20
              ancp@ietf.org<BR><B><SPAN=20
              style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> Re: [ANCP] =
Bulk=20
              Transaction Message</SPAN></FONT><o:p></o:p></P>
              <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
              style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">It's all=20
              simple:</SPAN></FONT><o:p></o:p></P>
              <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
              style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">-&nbsp;the =
Design Team=20
              is looking at the possibility of using this=20
              message</SPAN></FONT><o:p></o:p></P>
              <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
              style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">- the =
message in its=20
              current form does not appear to be terribly =
u<st1:PersonName=20
              w:st=3D"on">se</st1:PersonName>ful, and could =
be&nbsp;removed from=20
              the spec.</SPAN></FONT><o:p></o:p></P>
              <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
              style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
              <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
              style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">-Woj.</SPAN></FONT><o:p></o:p></P>
              <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
              style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
              <BLOCKQUOTE=20
              style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; =
BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: =
5pt 0in 5pt 3.75pt; BORDER-LEFT: black 1.5pt solid; PADDING-TOP: 0in; =
BORDER-BOTTOM: medium none">
                <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                style=3D"FONT-SIZE: =
12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
                <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center"=20
                align=3Dcenter><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                style=3D"FONT-SIZE: 12pt">
                <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" =
SIZE=3D2>
                </SPAN></FONT></DIV>
                <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: =
12pt"><B><FONT=20
                face=3DTahoma size=3D2><SPAN=20
                style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; =
FONT-FAMILY: Tahoma">From:</SPAN></FONT></B><FONT=20
                face=3DTahoma size=3D2><SPAN=20
                style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">=20
                ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] =
<B><SPAN=20
                style=3D"FONT-WEIGHT: bold">On Behalf Of =
</SPAN></B>Peter=20
                Arberg<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">Sent:</SPAN></B> 19=20
                April 2008 03:07<BR><B><SPAN=20
                style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Wojciech Dec =
(wdec);=20
                ancp@ietf.org<BR><B><SPAN=20
                style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> Re: =
[ANCP] Bulk=20
                Transaction Message</SPAN></FONT><o:p></o:p></P>
                <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
                style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Hi=20
                Woj,</SPAN></FONT><o:p></o:p></P>
                <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
                <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
                style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">can you=20
                give a little background to why you are looking for=20
                vendor</SPAN></FONT><o:p></o:p></P>
                <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
                style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">implementation=20
                support for this specific capability &amp; message=20
                ?</SPAN></FONT><o:p></o:p></P>
                <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
                <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
                style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">thanks,</SPAN></FONT><o:p></o:p></P>
                <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
                style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Peter</SPAN></FONT><o:p></o:p></P>
                <BLOCKQUOTE=20
                style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; =
BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: =
5pt 0in 5pt 3.75pt; BORDER-LEFT: blue 1.5pt solid; PADDING-TOP: 0in; =
BORDER-BOTTOM: medium none">
                  <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                  style=3D"FONT-SIZE: =
12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
                  <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center"=20
                  align=3Dcenter><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                  style=3D"FONT-SIZE: 12pt">
                  <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" =
SIZE=3D2>
                  </SPAN></FONT></DIV>
                  <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: =
12pt"><B><FONT=20
                  face=3DTahoma size=3D2><SPAN=20
                  style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; =
FONT-FAMILY: Tahoma">From:</SPAN></FONT></B><FONT=20
                  face=3DTahoma size=3D2><SPAN=20
                  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">=20
                  ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] =
<B><SPAN=20
                  style=3D"FONT-WEIGHT: bold">On Behalf Of =
</SPAN></B>Wojciech Dec=20
                  (wdec)<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">Sent:</SPAN></B>=20
                  18. april 2008 08:04<BR><B><SPAN=20
                  style=3D"FONT-WEIGHT: bold">To:</SPAN></B>=20
                  ancp@ietf.org<BR><B><SPAN=20
                  style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> [ANCP] =
Bulk=20
                  Transaction Message</SPAN></FONT><o:p></o:p></P>
                  <P><FONT face=3DArial size=3D2><SPAN lang=3DEN-GB=20
                  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"><!-- =
Converted from text/rtf format -->Hi=20
                  Folks,</SPAN></FONT><SPAN lang=3DEN-GB> =
</SPAN><o:p></o:p></P>
                  <P><FONT face=3DArial size=3D2><SPAN lang=3DEN-GB=20
                  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Could =
you=20
                  plea<st1:PersonName w:st=3D"on">se</st1:PersonName> =
let me/us=20
                  know if you currently have an implementation of ANCP =
that=20
                  supports the Bulk Transaction Capability and=20
                  Message?</SPAN></FONT><o:p></o:p></P>
                  <P><FONT face=3DArial size=3D2><SPAN lang=3DEN-GB=20
                  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Thanks,</SPAN></FONT>=20
                  <BR><FONT face=3DArial size=3D2><SPAN lang=3DEN-GB=20
                  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Woj.</SPAN></FONT><SPAN=20
                  lang=3DEN-GB>=20
            =
</SPAN><o:p></o:p></P></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE=
></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></DIV></BLOCKQUOTE><=
/BODY></HTML>

------_=_NextPart_001_01C8B04E.75FC742D--

--===============2034357513==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============2034357513==--


From ancp-bounces@ietf.org  Wed May  7 07:47:11 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B31943A6D41;
	Wed,  7 May 2008 07:47:11 -0700 (PDT)
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 EF83F3A6D41
	for <ancp@core3.amsl.com>; Wed,  7 May 2008 07:47:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.035
X-Spam-Level: 
X-Spam-Status: No, score=0.035 tagged_above=-999 required=5 tests=[AWL=-3.367, 
	BAYES_00=-2.599, HTML_MESSAGE=0.001, J_BACKHAIR_12=1,
	J_BACKHAIR_21=1, 
	J_BACKHAIR_22=1, J_BACKHAIR_23=1, J_BACKHAIR_24=1, J_BACKHAIR_25=1,
	J_BACKHAIR_27=1, J_BACKHAIR_32=1, J_BACKHAIR_42=1, J_BACKHAIR_52=1,
	RCVD_IN_DNSWL_MED=-4]
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 c3mP-w92-i66 for <ancp@core3.amsl.com>;
	Wed,  7 May 2008 07:46:58 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id 1812A3A6938
	for <ancp@ietf.org>; Wed,  7 May 2008 07:46:56 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,449,1204498800"; d="scan'208,217";a="8278379"
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 07 May 2008 16:46:53 +0200
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m47Ekr75003465; 
	Wed, 7 May 2008 16:46:53 +0200
Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com
	[144.254.231.71])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m47Ekrg0014618;
	Wed, 7 May 2008 14:46:53 GMT
Received: from xmb-ams-33b.cisco.com ([144.254.231.86]) by
	xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 7 May 2008 16:46:53 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 7 May 2008 16:46:49 +0200
Message-ID: <D9872168DBD43A41BD71FFC4713274D405043C65@xmb-ams-33b.emea.cisco.com>
In-Reply-To: <D9872168DBD43A41BD71FFC4713274D405043C34@xmb-ams-33b.emea.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ANCP] Bulk Transaction Message
thread-index: AcihZWeDZVeOVtxMS1uttRBEffcNEwAVDjfgAEod1tAAAWRvoAMsB4yQAADCZxAAAKZHUAAJVuxQABJPrxAADmDeEAABcgAQAAFBHxA=
References: <D9872168DBD43A41BD71FFC4713274D405043771@xmb-ams-33b.emea.cisco.com><9BD5D7887235424FA97DFC223CAE3C280AB43A61@proton.jnpr.net><D9872168DBD43A41BD71FFC4713274D4050438A2@xmb-ams-33b.emea.cisco.com><9BD5D7887235424FA97DFC223CAE3C28105B8B41@proton.jnpr.net>
	<D9872168DBD43A41BD71FFC4713274D405043C34@xmb-ams-33b.emea.cisco.com>
From: "Wojciech Dec (wdec)" <wdec@cisco.com>
To: "Wojciech Dec (wdec)" <wdec@cisco.com>,
	"Sanjay Wadhwa" <swadhwa@juniper.net>,
	"Peter Arberg" <parberg@redback.com>, <ancp@ietf.org>
X-OriginalArrivalTime: 07 May 2008 14:46:53.0566 (UTC)
	FILETIME=[30AEC9E0:01C8B051]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=59345; t=1210171613;
	x=1211035613; c=relaxed/simple; s=amsdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=wdec@cisco.com;
	z=From:=20=22Wojciech=20Dec=20(wdec)=22=20<wdec@cisco.com>
	|Subject:=20RE=3A=20[ANCP]=20Bulk=20Transaction=20Message
	|Sender:=20; bh=hLGTc9LF+N77TK4v1165a/DvwzXun8b9/D7hoq8kqEU=;
	b=vu4lIoxWdR5b/XUYZ3WGu1uvehKP428yBOmSmgIqTRFsJ4YpfFDcCYVL4I
	V+B8XFL0+oQSN33iI6zA1JPC2G0xM9Y4/W8zgqXI2A1GsSIfI85H3R+0MU6b
	mfBknlOHLx;
Authentication-Results: ams-dkim-2; header.From=wdec@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim2001 verified; ); 
Subject: Re: [ANCP] Bulk Transaction Message
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/pipermail/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>
Content-Type: multipart/mixed; boundary="===============0385066466=="
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0385066466==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8B051.3056705B"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8B051.3056705B
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Should have added: Please feel free to put forward a bulk ack proposal
to the WG. Just axe the existing bulking text before someone goes starts
thinking of actually adopting it.
=20
-Woj.


________________________________

	From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On
Behalf Of Wojciech Dec (wdec)
	Sent: 07 May 2008 16:27
	To: Sanjay Wadhwa; Peter Arberg; ancp@ietf.org
	Subject: Re: [ANCP] Bulk Transaction Message
=09
=09
	Sanjay,
	=20
	inline woj#2>


________________________________

		From: Sanjay Wadhwa [mailto:swadhwa@juniper.net]=20
		Sent: 07 May 2008 16:02
		To: Wojciech Dec (wdec); Peter Arberg; ancp@ietf.org
		Subject: RE: [ANCP] Bulk Transaction Message
	=09
	=09

		Woj

		  Inline [SW].

		=20

	=09
________________________________


		From: Wojciech Dec (wdec) [mailto:wdec@cisco.com]=20
		Sent: Wednesday, May 07, 2008 3:32 AM
		To: Sanjay Wadhwa; Peter Arberg; ancp@ietf.org
		Subject: RE: [ANCP] Bulk Transaction Message

		=20

		Sanjay,

		=20

		inline

			=20

		=09
________________________________


			From: Sanjay Wadhwa [mailto:swadhwa@juniper.net]

			Sent: 07 May 2008 02:03
			To: Wojciech Dec (wdec); Peter Arberg;
ancp@ietf.org
			Subject: RE: [ANCP] Bulk Transaction Message

			Even with transport being TCP, I see atleast a
couple of benefits:

			=20

			1. If a sender knows it has a bunch of messages
to send (e.g. ANCP adjacency flaps, and all the port-up messages need to
re-played), then bulking by definition allows the application to invoke
TCP fewer times to transmit everything that it needs to transmit, which
in a lot of systems can translate to significant compute and memory
efficiency (specially, if we are considering a large amount of state).
This is not to say one can't realize this in an implementation specific
way. =20

			=20

			Woj> Even with bulking one needs to realize the
TCP interaction with some thought. Perhaps bulking indeed offers the
opportunity for a delveloper to think about that, but I seriously doubt
that anyone familar with TCP app development would overlook this aspect
in the first place.

			=20

			[[SW]] I would like to believe it. History
doesn't bear this though.=20

			=20

			Woj#2> Unless the spec forces Bulking to be used
for every single multi-message exchange, the bunching effect will not
appear, nor will any optimization.

			=20

			However, if neeeded, bulking also has the
benefit of affording optimized acking (e.g. if no error is encountered
in proccessing all the sub-messages in the bundled message, it is
possible for the receiver to send a cummulative ack to the sender rather
than individual acks).=20

			=20

			Woj> A cumulatitive ack would appear to be
desirable in some cases, but I see this as very different to the bulk
ack currently described which essenatially carries in bulk all of the
individal acks. The bulking mechanism is quite clear in saying that each
ANCP message is bundled header and all, and acted upon individually by
the recipient, and whether it's a request or an ack is secondary. I'm
sure you'll agree that this is undesirable overhead and complexity for
what it's worth, also in view of the fact that "something" on the
recipient side would need to decide what ack/nack goes into a bulk
response and what doesn't.=20

			Having a cumulatitive ack is an all thogether
different thing, which I would support, and it should not involve the
"bulking" of each indivdual ack, and is an item that for which proposals
are welcome.

			[[SW]] Sorry, I should have been clearer.
Bulking adds an overall header for the individual messages being bulked.
If all the messages succeed, we can define the behavior to send a single
ACK (NOT a bulk ACK composed of individual sub-messages carrying ACK)
with the transaction-ID of the main header reflected back in the ACK.
This provides an elegant way to address cumulative ACK. This is not
defined in the draft today (see "if needed" above), but is easily
provided by bulking, and can be added if we agree.

			Far as request message is concerned, having
individual messages (with their own header) in the request reduces
complexity, provides a way to bulk messages of different types if
needed. It allows each sub-message to be individually NACK'd where
required. Bulking in such a way allows the flexibility of treating
individual sub-messages as completely independent or related.=20

			=20

			Woj#2> The above, in principle is fine, BUT it
is far removed from the current bulking mechanism. The order would be to
have a proposal regarding this on its own right.=20

			=20

			2. Bulking also provides a nice solution if one
ever needed to atomically receive and process *distinct* ANCP message
types. =20

			=20

			Woj> There appears to be no such thing;=20

			[[SW]] Today, but as you mentioned in another
thread, we need to design the protocol to be generic in anticipation of
such requirements.=20

			=20

			Woj#2> What tentative requirements are you
referring to, a relay? If so, bulking doesn't help there. This is also
much different from a discussion about a generic TLV format that is to
be used by the protocol.

			=20

			=20

			in bulking, presumably the reciever would have
to buffer all the way until the end of the bulk message, and then
process each message individually. This seems rather overweight when
compared to simply sending each message again.

			[[SW]] Draft doesn't impose on how much you
bulk. If atomicity in handling of bulked messages is warranted by a
use-case, then yes you want to get the entire message. If not, you could
presumably process as you receive each complete sub-message within the
bundle.=20

			=20

			Woj#2> Adding a single bulk envelope and sending
inside it 100 messages vs 2 bulk envelopes with 50 messages is also
pretty pointless, and an exercise in optimizing something that isn't
needed in the first place: In each case you're still sending 100
messages! The downside is that in either of the bulked messages case you
generally will have to wait till the full message is received. There are
betterTCP access=20

			=20

			What is the downside of having it? It is
negotiable as an optional capability.=20

			=20

			Woj> A couple of reasons come to the fore; i) no
body saw a good reason so far to implement it/use it ii) it's added
protocol "stuff" that has no clear benefit, does not realize any new
use-case, does not optimize much, and in fact as mentioned above it
appears to rather have some downsides such as extra overhead, buffering
and delay.

			=20

			Let's now have the axe fall...

			[[SW]] Let us please not be dismissive towards
something that has benefits (as outlined above).=20

			=20

			Wo#2j>  With the exception of cumulative ack,
which does deserve a standalone proposal to be put forward, neither me
nor other members of the WG do appear to share the views regarding the
purported benefits on bulking, nor a desire to retain it in the spec.
Sorry, it just needs to go.

			=20

			Cheers,

			Woj.

			=20

			Cheers

			-Sanjay

			=20

			=20

			=20

				-----Original Message-----
				From: Wojciech Dec (wdec)
[mailto:wdec@cisco.com]
				Sent: Tuesday, May 06, 2008 1:24 PM
				To: Sanjay Wadhwa; Peter Arberg;
ancp@ietf.org
				Subject: RE: [ANCP] Bulk Transaction
Message

				Sanjay,

				=20

				can you please present to the WG and
myself how bulk transaction capability is useful in any way in terms of
scaling for example? And by the way, please treat this discussion is
orthogonal to any other.

				=20

				Cheers,

				Woj.

				=20

				=20

			=09
________________________________


				From: Sanjay Wadhwa
[mailto:swadhwa@juniper.net]=20
				Sent: 06 May 2008 19:08
				To: Wojciech Dec (wdec); Peter Arberg;
ancp@ietf.org
				Subject: RE: [ANCP] Bulk Transaction
Message

				Woj

				  It is a bad idea to remove
bulk-transaction capability from the draft. On one hand you are trying
to add "marginally useful" extensions (with TLVs), and on the other hand
you are arguing for removing useful abstractions which can help with
scaling. If bulk-transaction capability needs to be augmented or
modified, then we should consider augmenting it, rather than removing it
from the draft.

				=20

				Cheers

				-Sanjay

				-----Original Message-----
				From: ancp-bounces@ietf.org
[mailto:ancp-bounces@ietf.org]On Behalf Of Wojciech Dec (wdec)
				Sent: Tuesday, May 06, 2008 12:42 PM
				To: Peter Arberg; ancp@ietf.org
				Subject: Re: [ANCP] Bulk Transaction
Message

				Hi Folks,

				=20

				given that no discernable use of Bulk
messaging has been identified, nor there being a good reason for it
given the fact that ANCP is bound to the TCP transport (or equivalent),
I would like to propose to remove all of the text relating to this
capability and associated message from the protocol spec draft.

				=20

				Regards,

				Woj.

				=20

			=09
________________________________


				From: ancp-bounces@ietf.org
[mailto:ancp-bounces@ietf.org] On Behalf Of Wojciech Dec (wdec)
				Sent: 20 April 2008 15:18
				To: Peter Arberg; ancp@ietf.org
				Subject: Re: [ANCP] Bulk Transaction
Message

				Should also have added: Given that
currently the bulk message does not appear to have had any practical
adoption, having the DTeam adopt it/modify it, or possibly have it
removed from the spec all together are all valid options.

				=20

				-Woj.

				=20

			=09
________________________________


				From: ancp-bounces@ietf.org
[mailto:ancp-bounces@ietf.org] On Behalf Of Wojciech Dec (wdec)
				Sent: 20 April 2008 14:39
				To: Peter Arberg; ancp@ietf.org
				Subject: Re: [ANCP] Bulk Transaction
Message

				It's all simple:

				- the Design Team is looking at the
possibility of using this message

				- the message in its current form does
not appear to be terribly useful, and could be removed from the spec.

				=20

				-Woj.

				=20

				=20

			=09
________________________________


				From: ancp-bounces@ietf.org
[mailto:ancp-bounces@ietf.org] On Behalf Of Peter Arberg
				Sent: 19 April 2008 03:07
				To: Wojciech Dec (wdec); ancp@ietf.org
				Subject: Re: [ANCP] Bulk Transaction
Message

				Hi Woj,

				=20

				can you give a little background to why
you are looking for vendor

				implementation support for this specific
capability & message ?

				=20

				thanks,

				Peter

				=20

			=09
________________________________


				From: ancp-bounces@ietf.org
[mailto:ancp-bounces@ietf.org] On Behalf Of Wojciech Dec (wdec)
				Sent: 18. april 2008 08:04
				To: ancp@ietf.org
				Subject: [ANCP] Bulk Transaction Message

				Hi Folks,=20

				Could you please let me/us know if you
currently have an implementation of ANCP that supports the Bulk
Transaction Capability and Message?

				Thanks,=20
				Woj.=20


------_=_NextPart_001_01C8B051.3056705B
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:st1 =3D=20
"urn:schemas-microsoft-com:office:smarttags"><HEAD><TITLE>Bulk =
Transaction Message</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3314" name=3DGENERATOR><!--[if !mso]>
<STYLE>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</STYLE>
<![endif]--><o:SmartTagType=20
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"=20
name=3D"PersonName"></o:SmartTagType><!--[if !mso]>
<STYLE>
st1\:*{behavior:url(#default#ieooui) }
</STYLE>
<![endif]-->
<STYLE>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p
	{mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</STYLE>
</HEAD>
<BODY lang=3DEN-US vLink=3Dpurple link=3Dblue>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D627444014-07052008><FONT =
face=3DArial=20
size=3D2>Should have added: Please feel free to put forward a bulk ack =
proposal to=20
the WG. Just axe the existing bulking text before someone goes starts =
thinking=20
of actually adopting it.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D627444014-07052008><FONT =
face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D627444014-07052008><FONT =
face=3DArial=20
size=3D2>-Woj.</FONT></SPAN></DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> ancp-bounces@ietf.org=20
  [mailto:ancp-bounces@ietf.org] <B>On Behalf Of </B>Wojciech Dec=20
  (wdec)<BR><B>Sent:</B> 07 May 2008 16:27<BR><B>To:</B> Sanjay Wadhwa; =
Peter=20
  Arberg; ancp@ietf.org<BR><B>Subject:</B> Re: [ANCP] Bulk Transaction=20
  Message<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D625490414-07052008><FONT =
face=3DArial=20
  size=3D2>Sanjay,</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D625490414-07052008><FONT =
face=3DArial=20
  size=3D2></FONT></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D625490414-07052008><FONT =
face=3DArial=20
  size=3D2>inline woj#2&gt;</FONT></SPAN></DIV><BR>
  <BLOCKQUOTE dir=3Dltr=20
  style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px =
solid; MARGIN-RIGHT: 0px">
    <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
    <HR tabIndex=3D-1>
    <FONT face=3DTahoma size=3D2><B>From:</B> Sanjay Wadhwa=20
    [mailto:swadhwa@juniper.net] <BR><B>Sent:</B> 07 May 2008=20
    16:02<BR><B>To:</B> Wojciech Dec (wdec); Peter Arberg;=20
    ancp@ietf.org<BR><B>Subject:</B> RE: [ANCP] Bulk Transaction=20
    Message<BR></FONT><BR></DIV>
    <DIV></DIV>
    <DIV class=3DSection1>
    <P class=3DMsoNormal><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: =
Arial">Woj<o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: Arial">&nbsp; =
Inline=20
    [SW].<o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
    <DIV>
    <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
    face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
    <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
    </SPAN></FONT></DIV>
    <P class=3DMsoNormal><B><FONT face=3DTahoma size=3D2><SPAN=20
    style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
    face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">=20
    Wojciech Dec (wdec) [mailto:wdec@cisco.com] <BR><B><SPAN=20
    style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Wednesday, May 07, 2008 =
3:32=20
    AM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Sanjay =
Wadhwa; Peter=20
    Arberg; ancp@ietf.org<BR><B><SPAN=20
    style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [ANCP] Bulk =
Transaction=20
    Message</SPAN></FONT><o:p></o:p></P></DIV>
    <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
    style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Sanjay,</SPAN></FONT><o:p></o:p></P>
    <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
    style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">inline</SPAN></FONT><o:p></o:p></P>
    <BLOCKQUOTE=20
    style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: 5pt 0in 5pt =
3.75pt; BORDER-LEFT: black 1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none">
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =

      style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
      <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
      face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
      <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
      </SPAN></FONT></DIV>
      <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><B><FONT =
face=3DTahoma=20
      size=3D2><SPAN=20
      style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
      face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Tahoma">=20
      Sanjay Wadhwa [mailto:swadhwa@juniper.net] <BR><B><SPAN=20
      style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> 07 May 2008 =
02:03<BR><B><SPAN=20
      style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Wojciech Dec (wdec); =
Peter=20
      Arberg; ancp@ietf.org<BR><B><SPAN=20
      style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [ANCP] Bulk =
Transaction=20
      Message</SPAN></FONT><o:p></o:p></P>
      <DIV>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">Even =
with=20
      transport being TCP, I <st1:PersonName =
w:st=3D"on">se</st1:PersonName>e=20
      atleast a couple of benefits:</SPAN></FONT><o:p></o:p></P></DIV>
      <DIV>
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =

      style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
      <DIV>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">1. If=20
      a&nbsp;<st1:PersonName w:st=3D"on">se</st1:PersonName>nder knows =
it has a=20
      bunch of messages to <st1:PersonName =
w:st=3D"on">se</st1:PersonName>nd (e.g.=20
      ANCP adjacency flaps, and all the port-up messages need to =
re-played),=20
      then bulking by definition&nbsp;allows the application to invoke =
TCP fewer=20
      times to transmit&nbsp;everything that it needs to transmit, =
which&nbsp;in=20
      a lot of systems can translate to significant&nbsp;compute and =
memory=20
      efficiency (specially, if we are considering a large amount of =
state).=20
      This&nbsp;is not to say one can't&nbsp;realize this&nbsp;in an=20
      implementation specific way.&nbsp;</SPAN></FONT><FONT face=3DArial =

      color=3Dblack size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><o:p></o:p></P></DIV>
      <DIV>
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =

      style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
      <DIV>
      <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Woj&gt; Even with =
bulking one=20
      needs to realize the TCP interaction with some thought. Perhaps =
bulking=20
      indeed&nbsp;offers the opportunity for a delveloper to think about =
that,=20
      but I <st1:PersonName w:st=3D"on">se</st1:PersonName>riously doubt =
that=20
      anyone familar with TCP app development&nbsp;would overlook this =
aspect in=20
      the first place.<o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT color=3D#993366><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: =
Arial">[[SW]] I would=20
      like to believe it. History doesn&#8217;t bear this though.<FONT=20
      color=3D#000000><SPAN=20
      class=3D625490414-07052008>&nbsp;</SPAN></FONT></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT color=3D#993366><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: =
Arial"><FONT=20
      color=3D#000000><SPAN=20
      class=3D625490414-07052008></SPAN></FONT></SPAN></FONT>&nbsp;</P>
      <P class=3DMsoNormal><FONT color=3D#993366><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: =
Arial"><FONT=20
      color=3D#000000><SPAN =
class=3D625490414-07052008>Woj#2&gt;&nbsp;Unless the=20
      spec forces Bulking to be used for every single multi-message =
exchange,=20
      the bunching effect will not appear, nor will any=20
      optimization.</SPAN></FONT></SPAN></FONT></P></DIV>
      <DIV>
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =

      style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
      <DIV>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">However,&nbsp;</SPAN></FONT><B><FONT=20
      face=3DArial color=3Dred size=3D2><SPAN=20
      style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: red; =
FONT-FAMILY: Arial">if=20
      neeeded</SPAN></FONT></B><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">, =
bulking=20
      also&nbsp;has the benefit of affording optimized acking (e.g. if =
no error=20
      is encountered in proccessing all the sub-messages in the bundled =
message,=20
      it&nbsp;is possible&nbsp;for the receiver to <st1:PersonName=20
      w:st=3D"on">se</st1:PersonName>nd a cummulative ack to the =
<st1:PersonName=20
      w:st=3D"on">se</st1:PersonName>nder rather than individual=20
      acks).</SPAN></FONT><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><o:p></o:p></P></DIV>
      <DIV>
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =

      style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
      <DIV>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Woj&gt;&nbsp;A=20
      cumulatitive ack would appear to be desirable in some =
ca<st1:PersonName=20
      w:st=3D"on">se</st1:PersonName>s, but I <st1:PersonName=20
      w:st=3D"on">se</st1:PersonName>e this as very&nbsp;different to=20
      the&nbsp;bulk ack currently described which es<st1:PersonName=20
      w:st=3D"on">se</st1:PersonName>natially carries in bulk all of the =
individal=20
      acks.&nbsp;The bulking mechanism is quite clear in saying that =
each ANCP=20
      message is&nbsp;bundled header and all, and acted upon =
individually by the=20
      recipient, and whether it's a request or an ack is <st1:PersonName =

      w:st=3D"on">se</st1:PersonName>condary. I'm sure you'll agree that =
this is=20
      undesirable overhead and complexity for what it's worth, also in =
view of=20
      the fact that "something" on the recipient side would need to =
decide what=20
      ack/nack goes into a bulk respon<st1:PersonName=20
      w:st=3D"on">se</st1:PersonName> and what doesn't.=20
      </SPAN></FONT><o:p></o:p></P></DIV>
      <DIV>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Having =
a=20
      cumulatitive ack is an all thogether different thing, which I=20
      would&nbsp;support, and it should not involve the "bulking" of =
each=20
      indivdual ack, and is an item that&nbsp;for which&nbsp;proposals =
are=20
      welcome.</SPAN></FONT><FONT face=3DArial size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: =
Arial">[[SW]] Sorry,=20
      I should have been clearer. Bulking adds an overall header for the =

      individual messages being bulked. If all the messages succeed, we =
can=20
      define the behavior to <st1:PersonName =
w:st=3D"on">se</st1:PersonName>nd a=20
      single ACK (NOT a bulk ACK compo<st1:PersonName=20
      w:st=3D"on">se</st1:PersonName>d of individual sub-messages =
carrying ACK)=20
      with the transaction-ID of the main header reflected back in the =
ACK.=20
      &nbsp;This provides an elegant way to address cumulative ACK. This =
is not=20
      defined in the draft today (<st1:PersonName =
w:st=3D"on">se</st1:PersonName>e=20
      &#8220;if needed&#8221; above), but is easily provided by bulking, =
and can be added if=20
      we agree.<o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT color=3D#993366><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: Arial">Far =
as request=20
      message is concerned, having individual messages (with their own =
header)=20
      in the request reduces complexity, provides a way to bulk messages =
of=20
      different types if needed. It allows each sub-message to be =
individually=20
      NACK&#8217;d where required. Bulking in such a way allows the =
flexibility of=20
      treating individual sub-messages as completely independent or=20
      related.<FONT color=3D#000000><SPAN=20
      class=3D625490414-07052008>&nbsp;</SPAN></FONT></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT color=3D#993366><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: =
Arial"><FONT=20
      color=3D#000000><SPAN=20
      class=3D625490414-07052008></SPAN></FONT></SPAN></FONT>&nbsp;</P>
      <P class=3DMsoNormal><FONT color=3D#993366><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: =
Arial"><FONT=20
      color=3D#000000><SPAN class=3D625490414-07052008>Woj#2&gt; The =
above, in=20
      principle is fine, BUT it is far removed from the current bulking=20
      mechanism. The order would be to have a proposal regarding =
this&nbsp;on=20
      its own =
right.&nbsp;</SPAN><o:p></o:p></FONT></SPAN></FONT></P></DIV>
      <DIV>
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =

      style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
      <DIV>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">2. =
Bulking also=20
      provides a nice solution if one&nbsp;ever needed to atomically =
receive and=20
      process *distinct* ANCP message types.&nbsp;</SPAN></FONT><FONT =
face=3DArial=20
      color=3Dblack size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><FONT=20
      face=3DArial color=3Dnavy size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><B><I><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
      style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: navy; =
FONT-STYLE: italic; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></I></B></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Woj&gt;&nbsp;There=20
      appears to be no such thing; </SPAN></FONT><FONT face=3DArial =
color=3Dnavy=20
      size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT color=3D#993366><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: =
Arial">[[SW]] Today,=20
      but as you mentioned in another thread, we need to design the =
protocol to=20
      be generic in anticipation of such requirements.<FONT =
color=3D#000000><SPAN=20
      class=3D625490414-07052008>&nbsp;</SPAN></FONT></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT color=3D#993366><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: =
Arial"><FONT=20
      color=3D#000000><SPAN=20
      class=3D625490414-07052008></SPAN></FONT></SPAN></FONT>&nbsp;</P>
      <P class=3DMsoNormal><FONT color=3D#993366><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: =
Arial"><FONT=20
      color=3D#000000><SPAN class=3D625490414-07052008>Woj#2&gt; What =
tentative=20
      requirements are you referring to, a&nbsp;relay?&nbsp;If =
so,&nbsp;bulking=20
      doesn't help there. This is also much different from a discussion =
about a=20
      generic TLV format that is to be used by the=20
      protocol.</SPAN></FONT></SPAN></FONT></P>
      <P class=3DMsoNormal><B><I><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
      style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: navy; =
FONT-STYLE: italic; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></I></B></P>
      <P class=3DMsoNormal><B><I><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
      style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: navy; =
FONT-STYLE: italic; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></I></B></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">in =
bulking,=20
      presumably the reciever would have to buffer all the way until the =
end of=20
      the bulk message, and then process each message individually. This =

      <st1:PersonName w:st=3D"on">se</st1:PersonName>ems rather =
overweight when=20
      compared to simply <st1:PersonName =
w:st=3D"on">se</st1:PersonName>nding each=20
      message again.</SPAN></FONT><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT color=3D#993366><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: =
Arial">[[SW]] Draft=20
      doesn&#8217;t impo<st1:PersonName w:st=3D"on">se</st1:PersonName> =
on how much you=20
      bulk. If atomicity in handling of bulked messages is warranted by =
a=20
      u<st1:PersonName w:st=3D"on">se</st1:PersonName>-ca<st1:PersonName =

      w:st=3D"on">se</st1:PersonName>, then yes you want to get the =
entire=20
      message. If not, you could presumably process as you receive each =
complete=20
      sub-message within the bundle.<FONT color=3D#000000><SPAN=20
      class=3D625490414-07052008>&nbsp;</SPAN></FONT></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT color=3D#993366><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: =
Arial"><FONT=20
      color=3D#000000><SPAN=20
      class=3D625490414-07052008></SPAN></FONT></SPAN></FONT>&nbsp;</P>
      <P class=3DMsoNormal><FONT color=3D#993366><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: =
Arial"><FONT=20
      color=3D#000000><SPAN class=3D625490414-07052008>Woj#2&gt; Adding =
a single=20
      bulk envelope and sending inside it&nbsp;100 messages vs 2 bulk =
envelopes=20
      with 50 messages is also pretty pointless, and an exercise in =
optimizing=20
      something that isn't needed in the first place: In each case =
you're still=20
      sending 100 messages! The downside is that in either of the bulked =

      messages case you generally will have to wait till the full =
message is=20
      received. There are betterTCP access=20
</SPAN></FONT></SPAN></FONT></P></DIV>
      <DIV>
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =

      style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
      <DIV>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">What is =
the=20
      downside of having it? It is&nbsp;negotiable as an optional=20
      capability.</SPAN></FONT><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><o:p></o:p></P></DIV>
      <DIV>
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =

      style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
      <DIV>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Woj&gt; A couple=20
      of reasons come to the fore; i) no body saw a good reason so far =
to=20
      implement it/u<st1:PersonName w:st=3D"on">se</st1:PersonName> it =
ii) it's=20
      added protocol "stuff" that has no clear benefit, does not realize =
any new=20
      u<st1:PersonName w:st=3D"on">se</st1:PersonName>-ca<st1:PersonName =

      w:st=3D"on">se</st1:PersonName>,&nbsp;does not optimize much, and =
in fact as=20
      mentioned above it appears to rather have some downsides such as =
extra=20
      overhead, buffering and delay.</SPAN></FONT><B><I><FONT =
face=3DArial=20
      color=3Dnavy size=3D2><SPAN=20
      style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: navy; =
FONT-STYLE: italic; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></I></B></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Let's =
now have=20
      the axe fall...</SPAN></FONT><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT color=3D#993366><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: =
Arial">[[SW]] Let us=20
      plea<st1:PersonName w:st=3D"on">se</st1:PersonName> not be =
dismissive=20
      towards something that has benefits (as outlined above).<FONT=20
      color=3D#000000><SPAN=20
      class=3D625490414-07052008>&nbsp;</SPAN></FONT></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT color=3D#993366><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: =
Arial"><FONT=20
      color=3D#000000><SPAN=20
      class=3D625490414-07052008></SPAN></FONT></SPAN></FONT>&nbsp;</P>
      <P class=3DMsoNormal><FONT color=3D#993366><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: =
Arial"><FONT=20
      color=3D#000000><SPAN class=3D625490414-07052008>Wo#2j&gt; =
&nbsp;With the=20
      exception of cumulative ack, which does deserve a standalone =
proposal to=20
      be put forward, neither me nor&nbsp;other members of the&nbsp;WG=20
      do&nbsp;appear to share the views regarding the purported benefits =
on=20
      bulking, nor a desire to retain it in the spec.&nbsp;Sorry, it =
just needs=20
      to go.</SPAN></FONT></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT color=3D#993366><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: =
Arial"><FONT=20
      color=3D#000000><SPAN=20
      class=3D625490414-07052008></SPAN></FONT></SPAN></FONT>&nbsp;</P>
      <P class=3DMsoNormal><FONT color=3D#993366><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: =
Arial"><FONT=20
      color=3D#000000><SPAN=20
      class=3D625490414-07052008>Cheers,</SPAN></FONT></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT color=3D#993366><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: =
Arial"><FONT=20
      color=3D#000000><SPAN=20
      class=3D625490414-07052008>Woj.</SPAN></FONT></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: =
Arial">Cheers<o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: =
Arial">-Sanjay<o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P></DIV>
      <DIV>
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =

      style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
      <DIV>
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =

      style=3D"FONT-SIZE: =
12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P></DIV>
      <BLOCKQUOTE=20
      style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; =
BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: =
5pt 0in 5pt 3.75pt; BORDER-LEFT: blue 1.5pt solid; PADDING-TOP: 0in; =
BORDER-BOTTOM: medium none">
        <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><FONT =
face=3DTahoma=20
        size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">-----Original=20
        Message-----<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">From:</SPAN></B>=20
        Wojciech Dec (wdec) [mailto:wdec@cisco.com]<BR><B><SPAN=20
        style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Tuesday, May 06, =
2008 1:24=20
        PM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Sanjay =
Wadhwa;=20
        Peter Arberg; ancp@ietf.org<BR><B><SPAN=20
        style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [ANCP] Bulk=20
        Transaction Message</SPAN></FONT><o:p></o:p></P>
        <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Sanjay,</SPAN></FONT><o:p></o:p></P>
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
        style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">can you =
plea<st1:PersonName=20
        w:st=3D"on">se</st1:PersonName> pre<st1:PersonName=20
        w:st=3D"on">se</st1:PersonName>nt to the WG and =
my<st1:PersonName=20
        w:st=3D"on">se</st1:PersonName>lf how bulk transaction =
capability is=20
        u<st1:PersonName w:st=3D"on">se</st1:PersonName>ful in any way =
in terms of=20
        scaling for example? And by the way, plea<st1:PersonName=20
        w:st=3D"on">se</st1:PersonName> treat this discussion is =
orthogonal to any=20
        other.</SPAN></FONT><o:p></o:p></P>
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
        style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Cheers,</SPAN></FONT><o:p></o:p></P>
        <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Woj.</SPAN></FONT><o:p></o:p></P>
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
        style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
        <BLOCKQUOTE=20
        style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; =
BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: =
5pt 0in 5pt 3.75pt; BORDER-LEFT: black 1.5pt solid; PADDING-TOP: 0in; =
BORDER-BOTTOM: medium none">
          <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
          style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
          <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
          face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: =
12pt">
          <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
          </SPAN></FONT></DIV>
          <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><B><FONT =
face=3DTahoma=20
          size=3D2><SPAN=20
          style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
          face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Tahoma">=20
          Sanjay Wadhwa [mailto:swadhwa@juniper.net] <BR><B><SPAN=20
          style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> 06 May 2008=20
          19:08<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> =
Wojciech=20
          Dec (wdec); Peter Arberg; ancp@ietf.org<BR><B><SPAN=20
          style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [ANCP] =
Bulk=20
          Transaction Message</SPAN></FONT><o:p></o:p></P>
          <DIV>
          <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
          style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Woj</SPAN></FONT><o:p></o:p></P></DIV>
          <DIV>
          <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
          style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp; It is=20
          a bad idea to remove bulk-transaction capability from the =
draft. On=20
          one hand you are trying to add "marginally u<st1:PersonName=20
          w:st=3D"on">se</st1:PersonName>ful" extensions (with TLVs), =
and on the=20
          other hand you are arguing for removing u<st1:PersonName=20
          w:st=3D"on">se</st1:PersonName>ful abstractions which can help =
with=20
          scaling. If bulk-transaction capability needs to be augmented =
or=20
          modified, then we should consider augmenting it, rather than =
removing=20
          it from the draft.</SPAN></FONT><o:p></o:p></P></DIV>
          <DIV>
          <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
          style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
          <DIV>
          <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
          style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Cheers</SPAN></FONT><o:p></o:p></P></DIV>
          <DIV>
          <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
          style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">-Sanjay</SPAN></FONT><o:p></o:p></P></DIV>
          <BLOCKQUOTE=20
          style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; =
BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: =
5pt 0in 5pt 3.75pt; BORDER-LEFT: blue 1.5pt solid; PADDING-TOP: 0in; =
BORDER-BOTTOM: medium none">
            <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><FONT =
face=3DTahoma=20
            size=3D2><SPAN=20
            style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">-----Original =

            Message-----<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">From:</SPAN></B>=20
            ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org]<B><SPAN =

            style=3D"FONT-WEIGHT: bold">On Behalf Of </SPAN></B>Wojciech =
Dec=20
            (wdec)<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">Sent:</SPAN></B>=20
            Tuesday, May 06, 2008 12:42 PM<BR><B><SPAN=20
            style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Peter Arberg;=20
            ancp@ietf.org<BR><B><SPAN=20
            style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> Re: [ANCP] =
Bulk=20
            Transaction Message</SPAN></FONT><o:p></o:p></P>
            <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
            style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Hi=20
            Folks,</SPAN></FONT><o:p></o:p></P>
            <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
            style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
            <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
            style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">given that no=20
            discernable u<st1:PersonName w:st=3D"on">se</st1:PersonName> =
of Bulk=20
            messaging has been identified, nor&nbsp;there being a good =
reason=20
            for it given the fact that ANCP is bound to the TCP =
transport (or=20
            equivalent),&nbsp;I would like to propo<st1:PersonName=20
            w:st=3D"on">se</st1:PersonName> to remove all of the text =
relating to=20
            this capability and associated message from the protocol =
spec=20
            draft.</SPAN></FONT><o:p></o:p></P>
            <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
            style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
            <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
            style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Regards,</SPAN></FONT><o:p></o:p></P>
            <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
            style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Woj.</SPAN></FONT><o:p></o:p></P>
            <BLOCKQUOTE=20
            style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; =
BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: =
5pt 0in 5pt 3.75pt; BORDER-LEFT: black 1.5pt solid; PADDING-TOP: 0in; =
BORDER-BOTTOM: medium none">
              <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
              style=3D"FONT-SIZE: =
12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
              <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
              face=3D"Times New Roman" size=3D3><SPAN =
style=3D"FONT-SIZE: 12pt">
              <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
              </SPAN></FONT></DIV>
              <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: =
12pt"><B><FONT=20
              face=3DTahoma size=3D2><SPAN=20
              style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
              face=3DTahoma size=3D2><SPAN=20
              style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">=20
              ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] =
<B><SPAN=20
              style=3D"FONT-WEIGHT: bold">On Behalf Of =
</SPAN></B>Wojciech Dec=20
              (wdec)<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">Sent:</SPAN></B> 20=20
              April 2008 15:18<BR><B><SPAN=20
              style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Peter Arberg;=20
              ancp@ietf.org<BR><B><SPAN=20
              style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> Re: [ANCP] =
Bulk=20
              Transaction Message</SPAN></FONT><o:p></o:p></P>
              <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
              style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Should also =
have=20
              added: Given that currently&nbsp;the bulk message does not =
appear=20
              to have had any practical&nbsp;adoption, having the DTeam =
adopt=20
              it/modify it, or possibly have it removed from the spec =
all=20
              together&nbsp;are all valid =
options.</SPAN></FONT><o:p></o:p></P>
              <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
              style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
              <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
              style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">-Woj.</SPAN></FONT><o:p></o:p></P>
              <BLOCKQUOTE=20
              style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; =
BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: =
5pt 0in 5pt 3.75pt; BORDER-LEFT: black 1.5pt solid; PADDING-TOP: 0in; =
BORDER-BOTTOM: medium none">
                <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                style=3D"FONT-SIZE: =
12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
                <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center"=20
                align=3Dcenter><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                style=3D"FONT-SIZE: 12pt">
                <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" =
SIZE=3D2>
                </SPAN></FONT></DIV>
                <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: =
12pt"><B><FONT=20
                face=3DTahoma size=3D2><SPAN=20
                style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; =
FONT-FAMILY: Tahoma">From:</SPAN></FONT></B><FONT=20
                face=3DTahoma size=3D2><SPAN=20
                style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">=20
                ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] =
<B><SPAN=20
                style=3D"FONT-WEIGHT: bold">On Behalf Of =
</SPAN></B>Wojciech Dec=20
                (wdec)<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">Sent:</SPAN></B> 20=20
                April 2008 14:39<BR><B><SPAN=20
                style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Peter Arberg; =

                ancp@ietf.org<BR><B><SPAN=20
                style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> Re: =
[ANCP] Bulk=20
                Transaction Message</SPAN></FONT><o:p></o:p></P>
                <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
                style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">It's all=20
                simple:</SPAN></FONT><o:p></o:p></P>
                <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
                style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">-&nbsp;the =
Design=20
                Team is looking at the possibility of using this=20
                message</SPAN></FONT><o:p></o:p></P>
                <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
                style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">- the =
message in its=20
                current form does not appear to be terribly =
u<st1:PersonName=20
                w:st=3D"on">se</st1:PersonName>ful, and could =
be&nbsp;removed from=20
                the spec.</SPAN></FONT><o:p></o:p></P>
                <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
                <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
                style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">-Woj.</SPAN></FONT><o:p></o:p></P>
                <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
                <BLOCKQUOTE=20
                style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; =
BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: =
5pt 0in 5pt 3.75pt; BORDER-LEFT: black 1.5pt solid; PADDING-TOP: 0in; =
BORDER-BOTTOM: medium none">
                  <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                  style=3D"FONT-SIZE: =
12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
                  <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center"=20
                  align=3Dcenter><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                  style=3D"FONT-SIZE: 12pt">
                  <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" =
SIZE=3D2>
                  </SPAN></FONT></DIV>
                  <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: =
12pt"><B><FONT=20
                  face=3DTahoma size=3D2><SPAN=20
                  style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; =
FONT-FAMILY: Tahoma">From:</SPAN></FONT></B><FONT=20
                  face=3DTahoma size=3D2><SPAN=20
                  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">=20
                  ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] =
<B><SPAN=20
                  style=3D"FONT-WEIGHT: bold">On Behalf Of =
</SPAN></B>Peter=20
                  Arberg<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">Sent:</SPAN></B>=20
                  19 April 2008 03:07<BR><B><SPAN=20
                  style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Wojciech =
Dec (wdec);=20
                  ancp@ietf.org<BR><B><SPAN=20
                  style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> Re: =
[ANCP] Bulk=20
                  Transaction Message</SPAN></FONT><o:p></o:p></P>
                  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
                  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Hi=20
                  Woj,</SPAN></FONT><o:p></o:p></P>
                  <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                  style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
                  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
                  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">can=20
                  you give a little background to why you are looking =
for=20
                  vendor</SPAN></FONT><o:p></o:p></P>
                  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
                  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">implementation=20
                  support for this specific capability &amp; message=20
                  ?</SPAN></FONT><o:p></o:p></P>
                  <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                  style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
                  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
                  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">thanks,</SPAN></FONT><o:p></o:p></P>
                  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
                  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Peter</SPAN></FONT><o:p></o:p></P>
                  <BLOCKQUOTE=20
                  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: =
0in; BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; =
MARGIN: 5pt 0in 5pt 3.75pt; BORDER-LEFT: blue 1.5pt solid; PADDING-TOP: =
0in; BORDER-BOTTOM: medium none">
                    <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                    style=3D"FONT-SIZE: =
12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
                    <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center"=20
                    align=3Dcenter><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                    style=3D"FONT-SIZE: 12pt">
                    <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" =
SIZE=3D2>
                    </SPAN></FONT></DIV>
                    <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: =
12pt"><B><FONT=20
                    face=3DTahoma size=3D2><SPAN=20
                    style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; =
FONT-FAMILY: Tahoma">From:</SPAN></FONT></B><FONT=20
                    face=3DTahoma size=3D2><SPAN=20
                    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">=20
                    ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] =

                    <B><SPAN style=3D"FONT-WEIGHT: bold">On Behalf Of=20
                    </SPAN></B>Wojciech Dec (wdec)<BR><B><SPAN=20
                    style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> 18. =
april 2008=20
                    08:04<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">To:</SPAN></B>=20
                    ancp@ietf.org<BR><B><SPAN=20
                    style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> =
[ANCP] Bulk=20
                    Transaction Message</SPAN></FONT><o:p></o:p></P>
                    <P><FONT face=3DArial size=3D2><SPAN lang=3DEN-GB=20
                    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"><!-- =
Converted from text/rtf format -->Hi=20
                    Folks,</SPAN></FONT><SPAN lang=3DEN-GB> =
</SPAN><o:p></o:p></P>
                    <P><FONT face=3DArial size=3D2><SPAN lang=3DEN-GB=20
                    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Could =
you=20
                    plea<st1:PersonName w:st=3D"on">se</st1:PersonName> =
let me/us=20
                    know if you currently have an implementation of ANCP =
that=20
                    supports the Bulk Transaction Capability and=20
                    Message?</SPAN></FONT><o:p></o:p></P>
                    <P><FONT face=3DArial size=3D2><SPAN lang=3DEN-GB=20
                    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Thanks,</SPAN></FONT>=20
                    <BR><FONT face=3DArial size=3D2><SPAN lang=3DEN-GB=20
                    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Woj.</SPAN></FONT><SPAN=20
                    lang=3DEN-GB>=20
              =
</SPAN><o:p></o:p></P></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE=
></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></DIV></BLOCKQUOTE><=
/BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C8B051.3056705B--

--===============0385066466==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============0385066466==--


From ancp-bounces@ietf.org  Wed May  7 09:08:37 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 8CBF23A6C7D;
	Wed,  7 May 2008 09:08:37 -0700 (PDT)
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 925633A687D
	for <ancp@core3.amsl.com>; Wed,  7 May 2008 09:08:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.348
X-Spam-Level: 
X-Spam-Status: No, score=-0.348 tagged_above=-999 required=5
	tests=[AWL=-3.750, BAYES_00=-2.599, HTML_MESSAGE=0.001,
	J_BACKHAIR_12=1, J_BACKHAIR_21=1, J_BACKHAIR_22=1, J_BACKHAIR_23=1,
	J_BACKHAIR_24=1, J_BACKHAIR_25=1, J_BACKHAIR_27=1, J_BACKHAIR_32=1,
	J_BACKHAIR_42=1, J_BACKHAIR_52=1, RCVD_IN_DNSWL_MED=-4]
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 jn4dG60hFD3H for <ancp@core3.amsl.com>;
	Wed,  7 May 2008 09:08:04 -0700 (PDT)
Received: from exprod7og107.obsmtp.com (exprod7og107.obsmtp.com [64.18.2.167])
	by core3.amsl.com (Postfix) with ESMTP id 0748E3A6C7D
	for <ancp@ietf.org>; Wed,  7 May 2008 09:08:02 -0700 (PDT)
Received: from source ([66.129.224.36]) by exprod7ob107.postini.com
	([64.18.6.12]) with SMTP; Wed, 07 May 2008 09:07:54 PDT
Received: from proton.jnpr.net ([10.10.2.37]) by emailsmtp56.jnpr.net with
	Microsoft SMTPSVC(6.0.3790.3959); Wed, 7 May 2008 09:07:15 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 7 May 2008 12:07:12 -0400
Message-ID: <9BD5D7887235424FA97DFC223CAE3C28105B8C39@proton.jnpr.net>
In-Reply-To: <D9872168DBD43A41BD71FFC4713274D405043C65@xmb-ams-33b.emea.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ANCP] Bulk Transaction Message
Thread-Index: AcihZWeDZVeOVtxMS1uttRBEffcNEwAVDjfgAEod1tAAAWRvoAMsB4yQAADCZxAAAKZHUAAJVuxQABJPrxAADmDeEAABcgAQAAFBHxAAAJXZIA==
References: <D9872168DBD43A41BD71FFC4713274D405043771@xmb-ams-33b.emea.cisco.com><9BD5D7887235424FA97DFC223CAE3C280AB43A61@proton.jnpr.net><D9872168DBD43A41BD71FFC4713274D4050438A2@xmb-ams-33b.emea.cisco.com><9BD5D7887235424FA97DFC223CAE3C28105B8B41@proton.jnpr.net>
	<D9872168DBD43A41BD71FFC4713274D405043C34@xmb-ams-33b.emea.cisco.com>
	<D9872168DBD43A41BD71FFC4713274D405043C65@xmb-ams-33b.emea.cisco.com>
From: "Sanjay Wadhwa" <swadhwa@juniper.net>
To: "Wojciech Dec (wdec)" <wdec@cisco.com>,
	"Peter Arberg" <parberg@redback.com>, <ancp@ietf.org>
X-OriginalArrivalTime: 07 May 2008 16:07:15.0706 (UTC)
	FILETIME=[6AE6F5A0:01C8B05C]
Subject: Re: [ANCP] Bulk Transaction Message
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/pipermail/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>
Content-Type: multipart/mixed; boundary="===============0731122708=="
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0731122708==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8B05C.699B1245"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8B05C.699B1245
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Inline again [SW2]

=20

-Sanjay

=20

________________________________

From: Wojciech Dec (wdec) [mailto:wdec@cisco.com]=20
Sent: Wednesday, May 07, 2008 10:47 AM
To: Wojciech Dec (wdec); Sanjay Wadhwa; Peter Arberg; ancp@ietf.org
Subject: RE: [ANCP] Bulk Transaction Message

=20

Should have added: Please feel free to put forward a bulk ack proposal
to the WG. Just axe the existing bulking text before someone goes starts
thinking of actually adopting it.

=20

-Woj.

	=20

=09
________________________________


	From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On
Behalf Of Wojciech Dec (wdec)
	Sent: 07 May 2008 16:27
	To: Sanjay Wadhwa; Peter Arberg; ancp@ietf.org
	Subject: Re: [ANCP] Bulk Transaction Message

	Sanjay,

	=20

	inline woj#2>

		=20

	=09
________________________________


		From: Sanjay Wadhwa [mailto:swadhwa@juniper.net]=20
		Sent: 07 May 2008 16:02
		To: Wojciech Dec (wdec); Peter Arberg; ancp@ietf.org
		Subject: RE: [ANCP] Bulk Transaction Message

		Woj

		  Inline [SW].

		=20

	=09
________________________________


		From: Wojciech Dec (wdec) [mailto:wdec@cisco.com]=20
		Sent: Wednesday, May 07, 2008 3:32 AM
		To: Sanjay Wadhwa; Peter Arberg; ancp@ietf.org
		Subject: RE: [ANCP] Bulk Transaction Message

		=20

		Sanjay,

		=20

		inline

			=20

		=09
________________________________


			From: Sanjay Wadhwa [mailto:swadhwa@juniper.net]

			Sent: 07 May 2008 02:03
			To: Wojciech Dec (wdec); Peter Arberg;
ancp@ietf.org
			Subject: RE: [ANCP] Bulk Transaction Message

			Even with transport being TCP, I see atleast a
couple of benefits:

			=20

			1. If a sender knows it has a bunch of messages
to send (e.g. ANCP adjacency flaps, and all the port-up messages need to
re-played), then bulking by definition allows the application to invoke
TCP fewer times to transmit everything that it needs to transmit, which
in a lot of systems can translate to significant compute and memory
efficiency (specially, if we are considering a large amount of state).
This is not to say one can't realize this in an implementation specific
way. =20

			=20

			Woj> Even with bulking one needs to realize the
TCP interaction with some thought. Perhaps bulking indeed offers the
opportunity for a delveloper to think about that, but I seriously doubt
that anyone familar with TCP app development would overlook this aspect
in the first place.

			=20

			[[SW]] I would like to believe it. History
doesn't bear this though.=20

			=20

			Woj#2> Unless the spec forces Bulking to be used
for every single multi-message exchange, the bunching effect will not
appear, nor will any optimization.

			=20

			However, if neeeded, bulking also has the
benefit of affording optimized acking (e.g. if no error is encountered
in proccessing all the sub-messages in the bundled message, it is
possible for the receiver to send a cummulative ack to the sender rather
than individual acks).=20

			=20

			Woj> A cumulatitive ack would appear to be
desirable in some cases, but I see this as very different to the bulk
ack currently described which essenatially carries in bulk all of the
individal acks. The bulking mechanism is quite clear in saying that each
ANCP message is bundled header and all, and acted upon individually by
the recipient, and whether it's a request or an ack is secondary. I'm
sure you'll agree that this is undesirable overhead and complexity for
what it's worth, also in view of the fact that "something" on the
recipient side would need to decide what ack/nack goes into a bulk
response and what doesn't.=20

			Having a cumulatitive ack is an all thogether
different thing, which I would support, and it should not involve the
"bulking" of each indivdual ack, and is an item that for which proposals
are welcome.

			[[SW]] Sorry, I should have been clearer.
Bulking adds an overall header for the individual messages being bulked.
If all the messages succeed, we can define the behavior to send a single
ACK (NOT a bulk ACK composed of individual sub-messages carrying ACK)
with the transaction-ID of the main header reflected back in the ACK.
This provides an elegant way to address cumulative ACK. This is not
defined in the draft today (see "if needed" above), but is easily
provided by bulking, and can be added if we agree.

			Far as request message is concerned, having
individual messages (with their own header) in the request reduces
complexity, provides a way to bulk messages of different types if
needed. It allows each sub-message to be individually NACK'd where
required. Bulking in such a way allows the flexibility of treating
individual sub-messages as completely independent or related.=20

			=20

			Woj#2> The above, in principle is fine, BUT it
is far removed from the current bulking mechanism. The order would be to
have a proposal regarding this on its own right.=20

			=20

			[[SW2]] It can easily be extended and doesn't
need to be done right away. Rehashing (new proposal) when you have the
basis for in the draft is not justifiable.

			=20

			2. Bulking also provides a nice solution if one
ever needed to atomically receive and process *distinct* ANCP message
types. =20

			=20

			Woj> There appears to be no such thing;=20

			[[SW]] Today, but as you mentioned in another
thread, we need to design the protocol to be generic in anticipation of
such requirements.=20

			=20

			Woj#2> What tentative requirements are you
referring to, a relay? If so, bulking doesn't help there. This is also
much different from a discussion about a generic TLV format that is to
be used by the protocol.

			=20

			=20

			in bulking, presumably the reciever would have
to buffer all the way until the end of the bulk message, and then
process each message individually. This seems rather overweight when
compared to simply sending each message again.

			[[SW]] Draft doesn't impose on how much you
bulk. If atomicity in handling of bulked messages is warranted by a
use-case, then yes you want to get the entire message. If not, you could
presumably process as you receive each complete sub-message within the
bundle.=20

			=20

			Woj#2> Adding a single bulk envelope and sending
inside it 100 messages vs 2 bulk envelopes with 50 messages is also
pretty pointless, and an exercise in optimizing something that isn't
needed in the first place: In each case you're still sending 100
messages! The downside is that in either of the bulked messages case you
generally will have to wait till the full message is received. There are
betterTCP access=20

			=20

			 [[SW2]] Sorry to repeat. If you need atomicity
for the sub-messages in the bundle, then you need to wait. If not then
you don't have to. This is providing you the flexibility, which you
don't easily have with individual messages (e.g atomic handling is hard
to realize with individual messages).

			=20

			What is the downside of having it? It is
negotiable as an optional capability.=20

			=20

			Woj> A couple of reasons come to the fore; i) no
body saw a good reason so far to implement it/use it ii) it's added
protocol "stuff" that has no clear benefit, does not realize any new
use-case, does not optimize much, and in fact as mentioned above it
appears to rather have some downsides such as extra overhead, buffering
and delay.

			=20

			Let's now have the axe fall...

			[[SW]] Let us please not be dismissive towards
something that has benefits (as outlined above).=20

			=20

			Wo#2j>  With the exception of cumulative ack,
which does deserve a standalone proposal to be put forward, neither me
nor other members of the WG do appear to share the views regarding the
purported benefits on bulking, nor a desire to retain it in the spec.=20

			[[SW2]] See above. This has been in the draft
for a while, and I have not seen any technical arguments from anyone
else on removing it from the draft. I have clearly outlined the benefits
above, and don't see convincing technical reasons for this to go.=20

			=20

			=20

			Sorry, it just needs to go.

			=20

			[[SW2]] Is this with your chair hat on or as an
individual WG member?=20

			=20

			Cheers,

			Woj.

			=20

			Cheers

			-Sanjay

			=20

			=20

			=20

				-----Original Message-----
				From: Wojciech Dec (wdec)
[mailto:wdec@cisco.com]
				Sent: Tuesday, May 06, 2008 1:24 PM
				To: Sanjay Wadhwa; Peter Arberg;
ancp@ietf.org
				Subject: RE: [ANCP] Bulk Transaction
Message

				Sanjay,

				=20

				can you please present to the WG and
myself how bulk transaction capability is useful in any way in terms of
scaling for example? And by the way, please treat this discussion is
orthogonal to any other.

				=20

				Cheers,

				Woj.

				=20

				=20

			=09
________________________________


				From: Sanjay Wadhwa
[mailto:swadhwa@juniper.net]=20
				Sent: 06 May 2008 19:08
				To: Wojciech Dec (wdec); Peter Arberg;
ancp@ietf.org
				Subject: RE: [ANCP] Bulk Transaction
Message

				Woj

				  It is a bad idea to remove
bulk-transaction capability from the draft. On one hand you are trying
to add "marginally useful" extensions (with TLVs), and on the other hand
you are arguing for removing useful abstractions which can help with
scaling. If bulk-transaction capability needs to be augmented or
modified, then we should consider augmenting it, rather than removing it
from the draft.

				=20

				Cheers

				-Sanjay

				-----Original Message-----
				From: ancp-bounces@ietf.org
[mailto:ancp-bounces@ietf.org]On Behalf Of Wojciech Dec (wdec)
				Sent: Tuesday, May 06, 2008 12:42 PM
				To: Peter Arberg; ancp@ietf.org
				Subject: Re: [ANCP] Bulk Transaction
Message

				Hi Folks,

				=20

				given that no discernable use of Bulk
messaging has been identified, nor there being a good reason for it
given the fact that ANCP is bound to the TCP transport (or equivalent),
I would like to propose to remove all of the text relating to this
capability and associated message from the protocol spec draft.

				=20

				Regards,

				Woj.

				=20

			=09
________________________________


				From: ancp-bounces@ietf.org
[mailto:ancp-bounces@ietf.org] On Behalf Of Wojciech Dec (wdec)
				Sent: 20 April 2008 15:18
				To: Peter Arberg; ancp@ietf.org
				Subject: Re: [ANCP] Bulk Transaction
Message

				Should also have added: Given that
currently the bulk message does not appear to have had any practical
adoption, having the DTeam adopt it/modify it, or possibly have it
removed from the spec all together are all valid options.

				=20

				-Woj.

				=20

			=09
________________________________


				From: ancp-bounces@ietf.org
[mailto:ancp-bounces@ietf.org] On Behalf Of Wojciech Dec (wdec)
				Sent: 20 April 2008 14:39
				To: Peter Arberg; ancp@ietf.org
				Subject: Re: [ANCP] Bulk Transaction
Message

				It's all simple:

				- the Design Team is looking at the
possibility of using this message

				- the message in its current form does
not appear to be terribly useful, and could be removed from the spec.

				=20

				-Woj.

				=20

				=20

			=09
________________________________


				From: ancp-bounces@ietf.org
[mailto:ancp-bounces@ietf.org] On Behalf Of Peter Arberg
				Sent: 19 April 2008 03:07
				To: Wojciech Dec (wdec); ancp@ietf.org
				Subject: Re: [ANCP] Bulk Transaction
Message

				Hi Woj,

				=20

				can you give a little background to why
you are looking for vendor

				implementation support for this specific
capability & message ?

				=20

				thanks,

				Peter

				=20

			=09
________________________________


				From: ancp-bounces@ietf.org
[mailto:ancp-bounces@ietf.org] On Behalf Of Wojciech Dec (wdec)
				Sent: 18. april 2008 08:04
				To: ancp@ietf.org
				Subject: [ANCP] Bulk Transaction Message

				Hi Folks,=20

				Could you please let me/us know if you
currently have an implementation of ANCP that supports the Bulk
Transaction Capability and Message?

				Thanks,=20
				Woj.=20


------_=_NextPart_001_01C8B05C.699B1245
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<title>Bulk Transaction Message</title>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p
	{mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman";}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:Arial;
	color:navy;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><b><font size=3D2 color=3D"#333399" =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:#333399;font-weight:bol=
d'>Inline
again</span></font></b><b><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:#993366;font-weight:bol=
d'> </span></font></b><b><font
size=3D2 color=3D"#333399" face=3DArial><span =
style=3D'font-size:10.0pt;font-family:
Arial;color:#333399;font-weight:bold'>[SW2]<o:p></o:p></span></font></b><=
/p>

<p class=3DMsoNormal><b><font size=3D2 color=3D"#993366" =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:#993366;font-weight:bol=
d'><o:p>&nbsp;</o:p></span></font></b></p>

<p class=3DMsoNormal><b><font size=3D2 color=3D"#333399" =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:#333399;font-weight:bol=
d'>-Sanjay</span></font></b><font
size=3D2 color=3D"#333399" face=3DArial><span =
style=3D'font-size:10.0pt;font-family:
Arial;color:#333399'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> =
Wojciech Dec
(wdec) [mailto:wdec@cisco.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Wednesday, May 07, =
2008
10:47 AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Wojciech Dec (wdec); =
Sanjay
Wadhwa; Peter Arberg; ancp@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [ANCP] Bulk
Transaction Message</span></font><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Should have added: Plea<st1:PersonName =
w:st=3D"on">se</st1:PersonName>
feel free to put forward a bulk ack proposal to the WG. Just axe the =
existing
bulking text before someone goes starts thinking of actually adopting =
it.</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>-Woj.</span></font><o:p></o:p></p>

<blockquote style=3D'border:none;border-left:solid black =
1.5pt;padding:0in 0in 0in 4.0pt;
margin-left:3.75pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'=
>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabIndex=3D-1>

</span></font></div>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><b><font size=3D2 =
face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma;font-weight:bold'>From:</spa=
n></font></b><font
size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'>
ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] <b><span =
style=3D'font-weight:
bold'>On Behalf Of </span></b>Wojciech Dec (wdec)<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> 07 May 2008 =
16:27<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Sanjay Wadhwa; Peter =
Arberg;
ancp@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> Re: [ANCP] Bulk
Transaction Message</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Sanjay,</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>inline woj#2&gt;</span></font><o:p></o:p></p>

<blockquote style=3D'border:none;border-left:solid black =
1.5pt;padding:0in 0in 0in 4.0pt;
margin-left:3.75pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'=
>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabIndex=3D-1>

</span></font></div>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><b><font size=3D2 =
face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma;font-weight:bold'>From:</spa=
n></font></b><font
size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'> Sanjay
Wadhwa [mailto:swadhwa@juniper.net] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> 07 May 2008 =
16:02<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Wojciech Dec (wdec); =
Peter
Arberg; ancp@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [ANCP] Bulk
Transaction Message</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3D"#993366" face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:#993366'>Woj<o:p></o:p>=
</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3D"#993366" face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:#993366'>&nbsp; Inline =
[SW].<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabIndex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> =
Wojciech Dec
(wdec) [mailto:wdec@cisco.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Wednesday, May 07, =
2008 3:32
AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Sanjay Wadhwa; Peter =
Arberg;
ancp@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [ANCP] Bulk
Transaction Message</span></font><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Sanjay,</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>inline</span></font><o:p></o:p></p>

<blockquote style=3D'border:none;border-left:solid black =
1.5pt;padding:0in 0in 0in 4.0pt;
margin-left:3.75pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'=
>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabIndex=3D-1>

</span></font></div>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><b><font size=3D2 =
face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma;font-weight:bold'>From:</spa=
n></font></b><font
size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'> Sanjay
Wadhwa [mailto:swadhwa@juniper.net] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> 07 May 2008 =
02:03<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Wojciech Dec (wdec); =
Peter
Arberg; ancp@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [ANCP] Bulk
Transaction Message</span></font><o:p></o:p></p>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>Even with transport being TCP, I =
<st1:PersonName
w:st=3D"on">se</st1:PersonName>e atleast a couple of =
benefits:</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>1. If a&nbsp;<st1:PersonName =
w:st=3D"on">se</st1:PersonName>nder
knows it has a bunch of messages to <st1:PersonName =
w:st=3D"on">se</st1:PersonName>nd
(e.g. ANCP adjacency flaps, and all the port-up messages need to =
re-played),
then bulking by definition&nbsp;allows the application to invoke TCP =
fewer
times to transmit&nbsp;everything that it needs to transmit, =
which&nbsp;in a
lot of systems can translate to significant&nbsp;compute and memory =
efficiency
(specially, if we are considering a large amount of state). This&nbsp;is =
not to
say one can't&nbsp;realize this&nbsp;in an implementation specific =
way.&nbsp;</span></font><font
size=3D2 color=3Dblack face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:black'>&nbsp;</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Woj&gt; Even with bulking one needs to realize the =
TCP
interaction with some thought. Perhaps bulking indeed&nbsp;offers the
opportunity for a delveloper to think about that, but I <st1:PersonName =
w:st=3D"on">se</st1:PersonName>riously
doubt that anyone familar with TCP app development&nbsp;would overlook =
this
aspect in the first place.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3D"#993366" face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:#993366'>[[SW]] I =
would like to
believe it. History doesn&#8217;t bear this though.</span></font><font =
size=3D2
color=3Dblack face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:black'>&nbsp;</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:black'>Woj#2&gt;&nbsp;Unless the spec =
forces
Bulking to be u<st1:PersonName w:st=3D"on">se</st1:PersonName>d for =
every single
multi-message exchange, the bunching effect will not appear, nor will =
any
optimization.</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>However,&nbsp;</span></font><b><font=

size=3D2 color=3Dred face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:red;font-weight:bold'>if neeeded</span></font></b><font size=3D2
color=3Dblue face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:blue'>, bulking also&nbsp;has the benefit of affording optimized =
acking
(e.g. if no error is encountered in proccessing all the sub-messages in =
the
bundled message, it&nbsp;is possible&nbsp;for the receiver to =
<st1:PersonName
w:st=3D"on">se</st1:PersonName>nd a cummulative ack to the =
<st1:PersonName w:st=3D"on">se</st1:PersonName>nder
rather than individual acks).</span></font><font size=3D2 color=3Dblack =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:black'>&nbsp;</span></f=
ont><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:black'>Woj&gt;&nbsp;A cumulatitive ack =
would
appear to be desirable in some ca<st1:PersonName =
w:st=3D"on">se</st1:PersonName>s,
but I <st1:PersonName w:st=3D"on">se</st1:PersonName>e this as
very&nbsp;different to the&nbsp;bulk ack currently described which =
es<st1:PersonName
w:st=3D"on">se</st1:PersonName>natially carries in bulk all of the =
individal
acks.&nbsp;The bulking mechanism is quite clear in saying that each ANCP
message is&nbsp;bundled header and all, and acted upon individually by =
the
recipient, and whether it's a request or an ack is <st1:PersonName =
w:st=3D"on">se</st1:PersonName>condary.
I'm sure you'll agree that this is undesirable overhead and complexity =
for what
it's worth, also in view of the fact that &quot;something&quot; on the
recipient side would need to decide what ack/nack goes into a bulk =
respon<st1:PersonName
w:st=3D"on">se</st1:PersonName> and what doesn't. =
</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:black'>Having a cumulatitive ack is an =
all
thogether different thing, which I would&nbsp;support, and it should not
involve the &quot;bulking&quot; of each indivdual ack, and is an item
that&nbsp;for which&nbsp;proposals are welcome.</span></font><font =
size=3D2
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'><o:p></o:p></span></font></p=
>

<p class=3DMsoNormal><font size=3D2 color=3D"#993366" face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:#993366'>[[SW]] Sorry, =
I should
have been clearer. Bulking adds an overall header for the individual =
messages
being bulked. If all the messages succeed, we can define the behavior to =
<st1:PersonName
w:st=3D"on">se</st1:PersonName>nd a single ACK (NOT a bulk ACK =
compo<st1:PersonName
w:st=3D"on">se</st1:PersonName>d of individual sub-messages carrying =
ACK) with
the transaction-ID of the main header reflected back in the ACK. =
&nbsp;This
provides an elegant way to address cumulative ACK. This is not defined =
in the
draft today (<st1:PersonName w:st=3D"on">se</st1:PersonName>e &#8220;if
needed&#8221; above), but is easily provided by bulking, and can be =
added if we
agree.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3D"#993366" face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:#993366'>Far as =
request message
is concerned, having individual messages (with their own header) in the =
request
reduces complexity, provides a way to bulk messages of different types =
if
needed. It allows each sub-message to be individually NACK&#8217;d where
required. Bulking in such a way allows the flexibility of treating =
individual
sub-messages as completely independent or related.</span></font><font =
size=3D2
color=3Dblack face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:black'>&nbsp;</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:black'>Woj#2&gt; The above, in principle =
is
fine, BUT it is far removed from the current bulking mechanism. The =
order would
be to have a proposal regarding this&nbsp;on its own =
right.&nbsp;</span></font><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><b><font size=3D2 color=3Dnavy face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy;font-weight:bold'>=
[[SW2]] It
can easily be extended and doesn&#8217;t need to be done right away. =
Rehashing
(new proposal) when you have the basis for in the draft is not =
justifiable.</span></font></b><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>2. Bulking also provides a nice =
solution
if one&nbsp;ever needed to atomically receive and process *distinct* =
ANCP
message types.&nbsp;</span></font><font size=3D2 color=3Dblack =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:black'>&nbsp;</span></f=
ont><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><b><i><font size=3D2 color=3Dnavy =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy;font-weight:bold;
font-style:italic'><o:p>&nbsp;</o:p></span></font></i></b></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:black'>Woj&gt;&nbsp;There appears to be =
no such
thing; </span></font><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3D"#993366" face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:#993366'>[[SW]] Today, =
but as
you mentioned in another thread, we need to design the protocol to be =
generic
in anticipation of such requirements.</span></font><font size=3D2 =
color=3Dblack
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:black'>&nbsp;</span></f=
ont><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:black'>Woj#2&gt; What tentative =
requirements are
you referring to, a&nbsp;relay?&nbsp;If so,&nbsp;bulking doesn't help =
there.
This is also much different from a discussion about a generic TLV format =
that
is to be u<st1:PersonName w:st=3D"on">se</st1:PersonName>d by the =
protocol.</span></font><o:p></o:p></p>

<p class=3DMsoNormal><b><i><font size=3D2 color=3Dnavy =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy;font-weight:bold;
font-style:italic'><o:p>&nbsp;</o:p></span></font></i></b></p>

<p class=3DMsoNormal><b><i><font size=3D2 color=3Dnavy =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy;font-weight:bold;
font-style:italic'><o:p>&nbsp;</o:p></span></font></i></b></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:black'>in bulking, presumably the =
reciever would
have to buffer all the way until the end of the bulk message, and then =
process
each message individually. This <st1:PersonName =
w:st=3D"on">se</st1:PersonName>ems
rather overweight when compared to simply <st1:PersonName =
w:st=3D"on">se</st1:PersonName>nding
each message again.</span></font><font size=3D2 color=3Dnavy =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy'><o:p></o:p></span=
></font></p>

<p class=3DMsoNormal><font size=3D2 color=3D"#993366" face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:#993366'>[[SW]] Draft
doesn&#8217;t impo<st1:PersonName w:st=3D"on">se</st1:PersonName> on how =
much you
bulk. If atomicity in handling of bulked messages is warranted by a =
u<st1:PersonName
w:st=3D"on">se</st1:PersonName>-ca<st1:PersonName =
w:st=3D"on">se</st1:PersonName>,
then yes you want to get the entire message. If not, you could =
presumably
process as you receive each complete sub-message within the =
bundle.</span></font><font
size=3D2 color=3Dblack face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:black'>&nbsp;</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:black'>Woj#2&gt; Adding a single bulk =
envelope
and <st1:PersonName w:st=3D"on">se</st1:PersonName>nding inside =
it&nbsp;100
messages vs 2 bulk envelopes with 50 messages is also pretty pointless, =
and an
exerci<st1:PersonName w:st=3D"on">se</st1:PersonName> in optimizing =
something
that isn't needed in the first place: In each ca<st1:PersonName =
w:st=3D"on">se</st1:PersonName>
you're still <st1:PersonName w:st=3D"on">se</st1:PersonName>nding 100 =
messages!
The downside is that in either of the bulked messages ca<st1:PersonName =
w:st=3D"on">se</st1:PersonName>
you generally will have to wait till the full message is received. There =
are
betterTCP access </span></font><font size=3D2 face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><b><i><font size=3D2 color=3Dnavy =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy;font-weight:bold;
font-style:italic'><o:p>&nbsp;</o:p></span></font></i></b></p>

<p class=3DMsoNormal><b><i><font size=3D2 color=3Dnavy =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy;font-weight:bold;
font-style:italic'>&nbsp;</span></font></i></b><b><font size=3D2 =
color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy;
font-weight:bold'>[[SW2]] Sorry to repeat. If you need atomicity for the =
sub-messages
in the bundle, then you need to wait. If not then you don&#8217;t have =
to. This
is providing you the flexibility, which you don&#8217;t easily have with
individual messages (e.g atomic handling is hard to realize with =
individual
messages).</span></font></b><font size=3D2 color=3Dnavy =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy'><o:p></o:p></span=
></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>What is the downside of having it? =
It
is&nbsp;negotiable as an optional capability.</span></font><font =
size=3D2
color=3Dblack face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:black'>&nbsp;</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:black'>Woj&gt; A couple of reasons come =
to the
fore; i) no body saw a good reason so far to implement =
it/u<st1:PersonName
w:st=3D"on">se</st1:PersonName> it ii) it's added protocol =
&quot;stuff&quot; that
has no clear benefit, does not realize any new u<st1:PersonName =
w:st=3D"on">se</st1:PersonName>-ca<st1:PersonName
w:st=3D"on">se</st1:PersonName>,&nbsp;does not optimize much, and in =
fact as
mentioned above it appears to rather have some downsides such as extra
overhead, buffering and delay.</span></font><b><i><font size=3D2 =
color=3Dnavy
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;color:navy;
font-weight:bold;font-style:italic'><o:p></o:p></span></font></i></b></p>=


<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:black'>Let's now have the axe =
fall...</span></font><font
size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3D"#993366" face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:#993366'>[[SW]] Let us =
plea<st1:PersonName
w:st=3D"on">se</st1:PersonName> not be dismissive towards something that =
has
benefits (as outlined above).</span></font><font size=3D2 color=3Dblack =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:black'>&nbsp;</span></f=
ont><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:black'>Wo#2j&gt; &nbsp;With the exception =
of
cumulative ack, which does de<st1:PersonName =
w:st=3D"on">se</st1:PersonName>rve a
standalone proposal to be put forward, neither me nor&nbsp;other members =
of the&nbsp;WG
do&nbsp;appear to share the views regarding the purported benefits on =
bulking,
nor a desire to retain it in the spec.&nbsp;</span></font><font size=3D2
color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><b><font size=3D2 color=3Dnavy face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy;font-weight:bold'>=
[[SW2]] See
above. This has been in the draft for a while, and I have not =
<st1:PersonName
w:st=3D"on">se</st1:PersonName>en any technical arguments from anyone =
el<st1:PersonName
w:st=3D"on">se</st1:PersonName> on removing it from the draft. I have =
clearly
outlined the benefits above, and don&#8217;t <st1:PersonName =
w:st=3D"on">se</st1:PersonName>e
convincing technical reasons for this to go. </span></font></b><font =
size=3D2
color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial;
color:navy'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><b><i><font size=3D2 color=3Dnavy =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy;font-weight:bold;
font-style:italic'><o:p>&nbsp;</o:p></span></font></i></b></p>

<p class=3DMsoNormal><b><i><font size=3D2 color=3Dnavy =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy;font-weight:bold;
font-style:italic'><o:p>&nbsp;</o:p></span></font></i></b></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:black'>Sorry, it just needs to =
go.</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><b><font size=3D2 color=3Dnavy face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:navy;font-weight:bold'>=
[[SW2]]
Is this with your chair hat on or as an individual WG member? =
<o:p></o:p></span></font></b></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:black'>Cheers,</span></font><o:p></o:p></p=
>

<p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:black'>Woj.</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3D"#993366" face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:#993366'>Cheers<o:p></o=
:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3D"#993366" face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;color:#993366'>-Sanjay<o:p></=
o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

<blockquote style=3D'border:none;border-left:solid blue =
1.5pt;padding:0in 0in 0in 4.0pt;
margin-left:3.75pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'=
>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><font size=3D2 =
face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma'>-----Original =
Message-----<br>
<b><span style=3D'font-weight:bold'>From:</span></b> Wojciech Dec (wdec)
[mailto:wdec@cisco.com]<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Tuesday, May 06, =
2008 1:24
PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Sanjay Wadhwa; Peter =
Arberg;
ancp@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [ANCP] Bulk
Transaction Message</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Sanjay,</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>can you plea<st1:PersonName =
w:st=3D"on">se</st1:PersonName>
pre<st1:PersonName w:st=3D"on">se</st1:PersonName>nt to the WG and =
my<st1:PersonName
w:st=3D"on">se</st1:PersonName>lf how bulk transaction capability is =
u<st1:PersonName
w:st=3D"on">se</st1:PersonName>ful in any way in terms of scaling for =
example?
And by the way, plea<st1:PersonName w:st=3D"on">se</st1:PersonName> =
treat this
discussion is orthogonal to any other.</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Cheers,</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Woj.</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

<blockquote style=3D'border:none;border-left:solid black =
1.5pt;padding:0in 0in 0in 4.0pt;
margin-left:3.75pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'=
>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabIndex=3D-1>

</span></font></div>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><b><font size=3D2 =
face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma;font-weight:bold'>From:</spa=
n></font></b><font
size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'> Sanjay
Wadhwa [mailto:swadhwa@juniper.net] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> 06 May 2008 =
19:08<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Wojciech Dec (wdec); =
Peter
Arberg; ancp@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: [ANCP] Bulk
Transaction Message</span></font><o:p></o:p></p>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>Woj</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>&nbsp; It is a bad idea to remove
bulk-transaction capability from the draft. On one hand you are trying =
to add
&quot;marginally u<st1:PersonName =
w:st=3D"on">se</st1:PersonName>ful&quot;
extensions (with TLVs), and on the other hand you are arguing for =
removing u<st1:PersonName
w:st=3D"on">se</st1:PersonName>ful abstractions which can help with =
scaling. If
bulk-transaction capability needs to be augmented or modified, then we =
should
consider augmenting it, rather than removing it from the =
draft.</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>Cheers</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>-Sanjay</span></font><o:p></o:p></p>=


</div>

<blockquote style=3D'border:none;border-left:solid blue =
1.5pt;padding:0in 0in 0in 4.0pt;
margin-left:3.75pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'=
>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><font size=3D2 =
face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma'>-----Original =
Message-----<br>
<b><span style=3D'font-weight:bold'>From:</span></b> =
ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org]<b><span
style=3D'font-weight:bold'>On Behalf Of </span></b>Wojciech Dec =
(wdec)<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Tuesday, May 06, =
2008 12:42
PM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Peter Arberg; =
ancp@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> Re: [ANCP] Bulk
Transaction Message</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Hi Folks,</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>given that no discernable u<st1:PersonName =
w:st=3D"on">se</st1:PersonName>
of Bulk messaging has been identified, nor&nbsp;there being a good =
reason for
it given the fact that ANCP is bound to the TCP transport (or
equivalent),&nbsp;I would like to propo<st1:PersonName =
w:st=3D"on">se</st1:PersonName>
to remove all of the text relating to this capability and associated =
message
from the protocol spec draft.</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Regards,</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Woj.</span></font><o:p></o:p></p>

<blockquote style=3D'border:none;border-left:solid black =
1.5pt;padding:0in 0in 0in 4.0pt;
margin-left:3.75pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'=
>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabIndex=3D-1>

</span></font></div>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><b><font size=3D2 =
face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma;font-weight:bold'>From:</spa=
n></font></b><font
size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'>
ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] <b><span =
style=3D'font-weight:
bold'>On Behalf Of </span></b>Wojciech Dec (wdec)<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> 20 April 2008 =
15:18<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Peter Arberg; =
ancp@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> Re: [ANCP] Bulk
Transaction Message</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Should also have added: Given that currently&nbsp;the =
bulk
message does not appear to have had any practical&nbsp;adoption, having =
the
DTeam adopt it/modify it, or possibly have it removed from the spec all
together&nbsp;are all valid options.</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>-Woj.</span></font><o:p></o:p></p>

<blockquote style=3D'border:none;border-left:solid black =
1.5pt;padding:0in 0in 0in 4.0pt;
margin-left:3.75pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'=
>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabIndex=3D-1>

</span></font></div>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><b><font size=3D2 =
face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma;font-weight:bold'>From:</spa=
n></font></b><font
size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'>
ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] <b><span =
style=3D'font-weight:
bold'>On Behalf Of </span></b>Wojciech Dec (wdec)<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> 20 April 2008 =
14:39<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Peter Arberg; =
ancp@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> Re: [ANCP] Bulk
Transaction Message</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>It's all simple:</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>-&nbsp;the Design Team is looking at the possibility =
of
using this message</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>- the message in its current form does not appear to =
be
terribly u<st1:PersonName w:st=3D"on">se</st1:PersonName>ful, and could
be&nbsp;removed from the spec.</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>-Woj.</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

<blockquote style=3D'border:none;border-left:solid black =
1.5pt;padding:0in 0in 0in 4.0pt;
margin-left:3.75pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'=
>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabIndex=3D-1>

</span></font></div>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><b><font size=3D2 =
face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma;font-weight:bold'>From:</spa=
n></font></b><font
size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'>
ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] <b><span =
style=3D'font-weight:
bold'>On Behalf Of </span></b>Peter Arberg<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> 19 April 2008 =
03:07<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Wojciech Dec (wdec);
ancp@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> Re: [ANCP] Bulk =
Transaction
Message</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>Hi =
Woj,</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>can you give a little background to =
why
you are looking for vendor</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>implementation support for this =
specific
capability &amp; message ?</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>thanks,</span></font><o:p></o:p></p>=


<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>Peter</span></font><o:p></o:p></p>

<blockquote style=3D'border:none;border-left:solid blue =
1.5pt;padding:0in 0in 0in 4.0pt;
margin-left:3.75pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'=
>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabIndex=3D-1>

</span></font></div>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><b><font size=3D2 =
face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma;font-weight:bold'>From:</spa=
n></font></b><font
size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'>
ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] <b><span =
style=3D'font-weight:
bold'>On Behalf Of </span></b>Wojciech Dec (wdec)<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> 18. april 2008 =
08:04<br>
<b><span style=3D'font-weight:bold'>To:</span></b> ancp@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> [ANCP] Bulk =
Transaction
Message</span></font><o:p></o:p></p>

<p><font size=3D2 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:
Arial'><!-- Converted from text/rtf format -->Hi =
Folks,</span></font><span
lang=3DEN-GB> </span><o:p></o:p></p>

<p><font size=3D2 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:
Arial'>Could you plea<st1:PersonName w:st=3D"on">se</st1:PersonName> let =
me/us
know if you currently have an implementation of ANCP that supports the =
Bulk
Transaction Capability and Message?</span></font><o:p></o:p></p>

<p><font size=3D2 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:
Arial'>Thanks,</span></font> <br>
<font size=3D2 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:
Arial'>Woj.</span></font><span lang=3DEN-GB> </span><o:p></o:p></p>

</blockquote>

</blockquote>

</blockquote>

</blockquote>

</blockquote>

</blockquote>

</blockquote>

</blockquote>

</blockquote>

</blockquote>

</div>

</body>

</html>

------_=_NextPart_001_01C8B05C.699B1245--

--===============0731122708==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============0731122708==--


From ancp-bounces@ietf.org  Thu May  8 08:31:52 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 3EE1E28C83A;
	Thu,  8 May 2008 08:31:52 -0700 (PDT)
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 9079E28C0D7
	for <ancp@core3.amsl.com>; Thu,  8 May 2008 08:31:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.752
X-Spam-Level: **
X-Spam-Status: No, score=2.752 tagged_above=-999 required=5 tests=[AWL=-5.000, 
	BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001,
	J_BACKHAIR_12=1, 
	J_BACKHAIR_21=1, J_BACKHAIR_22=1, J_BACKHAIR_23=1, J_BACKHAIR_24=1,
	J_BACKHAIR_25=1, J_BACKHAIR_27=1, J_BACKHAIR_32=1, J_BACKHAIR_42=1,
	J_BACKHAIR_52=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 BJCcx7UULBRQ for <ancp@core3.amsl.com>;
	Thu,  8 May 2008 08:30:45 -0700 (PDT)
Received: from smail5.alcatel.fr (smail5.alcatel.fr [62.23.212.27])
	by core3.amsl.com (Postfix) with ESMTP id 63BBF28C5C2
	for <ancp@ietf.org>; Thu,  8 May 2008 06:23:00 -0700 (PDT)
Received: from FRVELSBHS05.ad2.ad.alcatel.com (frvelsbhs05.ad2.ad.alcatel.com
	[155.132.6.77])
	by smail5.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id m48AHur2016669; 
	Thu, 8 May 2008 12:17:56 +0200
Received: from FRVELSMBS22.ad2.ad.alcatel.com ([155.132.6.52]) by
	FRVELSBHS05.ad2.ad.alcatel.com with Microsoft
	SMTPSVC(6.0.3790.2499); Thu, 8 May 2008 12:17:56 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 8 May 2008 12:17:54 +0200
Message-ID: <7A6D4815C5E8F74988784FEBD50F2F1E01B8AE48@FRVELSMBS22.ad2.ad.alcatel.com>
In-Reply-To: <9BD5D7887235424FA97DFC223CAE3C28105B8C39@proton.jnpr.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ANCP] Bulk Transaction Message
Thread-Index: AcihZWeDZVeOVtxMS1uttRBEffcNEwAVDjfgAEod1tAAAWRvoAMsB4yQAADCZxAAAKZHUAAJVuxQABJPrxAADmDeEAABcgAQAAFBHxAAAJXZIAAoMoKQ
References: <D9872168DBD43A41BD71FFC4713274D405043771@xmb-ams-33b.emea.cisco.com><9BD5D7887235424FA97DFC223CAE3C280AB43A61@proton.jnpr.net><D9872168DBD43A41BD71FFC4713274D4050438A2@xmb-ams-33b.emea.cisco.com><9BD5D7887235424FA97DFC223CAE3C28105B8B41@proton.jnpr.net><D9872168DBD43A41BD71FFC4713274D405043C34@xmb-ams-33b.emea.cisco.com><D9872168DBD43A41BD71FFC4713274D405043C65@xmb-ams-33b.emea.cisco.com>
	<9BD5D7887235424FA97DFC223CAE3C28105B8C39@proton.jnpr.net>
From: "DE CNODDER Stefaan" <stefaan.de_cnodder@alcatel-lucent.be>
To: "Sanjay Wadhwa" <swadhwa@juniper.net>,
	"Wojciech Dec (wdec)" <wdec@cisco.com>, <ancp@ietf.org>
X-OriginalArrivalTime: 08 May 2008 10:17:56.0049 (UTC)
	FILETIME=[C862DC10:01C8B0F4]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.13
Subject: Re: [ANCP] Bulk Transaction Message
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/pipermail/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>
Content-Type: multipart/mixed; boundary="===============1171606889=="
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1171606889==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8B0F4.C7F4F6AA"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8B0F4.C7F4F6AA
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Sanjay, Woj,
=20
I see some advantages in having bulk messages to optimize ANCP.
However, bulk messages are not the only solution.  It is wrong to
discuss bulk messages without comparing it with alternatives.  It looks
like a good solution to me but maybe there are better ways in optimizing
ANCP.  So far the working group has not been working a lot on
optimizations.  According to me, keeping bulk messages in the base spec
is wrong and it should be removed.  People are invited to submit
solutions to optimize ANCP in the form of a seperate draft, and one such
draft could be bulk messages.  Then when the working group decides that
it is time to work on optimalisations, the proposed solutions can be
compared and discussed.
=20
regards,
Stefaan

________________________________

From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of
Sanjay Wadhwa
Sent: woensdag 7 mei 2008 18:07
To: Wojciech Dec (wdec); Peter Arberg; ancp@ietf.org
Subject: Re: [ANCP] Bulk Transaction Message



Inline again [SW2]

=20

-Sanjay

=20

________________________________

From: Wojciech Dec (wdec) [mailto:wdec@cisco.com]=20
Sent: Wednesday, May 07, 2008 10:47 AM
To: Wojciech Dec (wdec); Sanjay Wadhwa; Peter Arberg; ancp@ietf.org
Subject: RE: [ANCP] Bulk Transaction Message

=20

Should have added: Please feel free to put forward a bulk ack proposal
to the WG. Just axe the existing bulking text before someone goes starts
thinking of actually adopting it.

=20

-Woj.

	=20

=09
________________________________


	From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On
Behalf Of Wojciech Dec (wdec)
	Sent: 07 May 2008 16:27
	To: Sanjay Wadhwa; Peter Arberg; ancp@ietf.org
	Subject: Re: [ANCP] Bulk Transaction Message

	Sanjay,

	=20

	inline woj#2>

		=20

	=09
________________________________


		From: Sanjay Wadhwa [mailto:swadhwa@juniper.net]=20
		Sent: 07 May 2008 16:02
		To: Wojciech Dec (wdec); Peter Arberg; ancp@ietf.org
		Subject: RE: [ANCP] Bulk Transaction Message

		Woj

		  Inline [SW].

		=20

	=09
________________________________


		From: Wojciech Dec (wdec) [mailto:wdec@cisco.com]=20
		Sent: Wednesday, May 07, 2008 3:32 AM
		To: Sanjay Wadhwa; Peter Arberg; ancp@ietf.org
		Subject: RE: [ANCP] Bulk Transaction Message

		=20

		Sanjay,

		=20

		inline

			=20

		=09
________________________________


			From: Sanjay Wadhwa [mailto:swadhwa@juniper.net]

			Sent: 07 May 2008 02:03
			To: Wojciech Dec (wdec); Peter Arberg;
ancp@ietf.org
			Subject: RE: [ANCP] Bulk Transaction Message

			Even with transport being TCP, I see atleast a
couple of benefits:

			=20

			1. If a sender knows it has a bunch of messages
to send (e.g. ANCP adjacency flaps, and all the port-up messages need to
re-played), then bulking by definition allows the application to invoke
TCP fewer times to transmit everything that it needs to transmit, which
in a lot of systems can translate to significant compute and memory
efficiency (specially, if we are considering a large amount of state).
This is not to say one can't realize this in an implementation specific
way. =20

			=20

			Woj> Even with bulking one needs to realize the
TCP interaction with some thought. Perhaps bulking indeed offers the
opportunity for a delveloper to think about that, but I seriously doubt
that anyone familar with TCP app development would overlook this aspect
in the first place.

			=20

			[[SW]] I would like to believe it. History
doesn't bear this though.=20

			=20

			Woj#2> Unless the spec forces Bulking to be used
for every single multi-message exchange, the bunching effect will not
appear, nor will any optimization.

			=20

			However, if neeeded, bulking also has the
benefit of affording optimized acking (e.g. if no error is encountered
in proccessing all the sub-messages in the bundled message, it is
possible for the receiver to send a cummulative ack to the sender rather
than individual acks).=20

			=20

			Woj> A cumulatitive ack would appear to be
desirable in some cases, but I see this as very different to the bulk
ack currently described which essenatially carries in bulk all of the
individal acks. The bulking mechanism is quite clear in saying that each
ANCP message is bundled header and all, and acted upon individually by
the recipient, and whether it's a request or an ack is secondary. I'm
sure you'll agree that this is undesirable overhead and complexity for
what it's worth, also in view of the fact that "something" on the
recipient side would need to decide what ack/nack goes into a bulk
response and what doesn't.=20

			Having a cumulatitive ack is an all thogether
different thing, which I would support, and it should not involve the
"bulking" of each indivdual ack, and is an item that for which proposals
are welcome.

			[[SW]] Sorry, I should have been clearer.
Bulking adds an overall header for the individual messages being bulked.
If all the messages succeed, we can define the behavior to send a single
ACK (NOT a bulk ACK composed of individual sub-messages carrying ACK)
with the transaction-ID of the main header reflected back in the ACK.
This provides an elegant way to address cumulative ACK. This is not
defined in the draft today (see "if needed" above), but is easily
provided by bulking, and can be added if we agree.

			Far as request message is concerned, having
individual messages (with their own header) in the request reduces
complexity, provides a way to bulk messages of different types if
needed. It allows each sub-message to be individually NACK'd where
required. Bulking in such a way allows the flexibility of treating
individual sub-messages as completely independent or related.=20

			=20

			Woj#2> The above, in principle is fine, BUT it
is far removed from the current bulking mechanism. The order would be to
have a proposal regarding this on its own right.=20

			=20

			[[SW2]] It can easily be extended and doesn't
need to be done right away. Rehashing (new proposal) when you have the
basis for in the draft is not justifiable.

			=20

			2. Bulking also provides a nice solution if one
ever needed to atomically receive and process *distinct* ANCP message
types. =20

			=20

			Woj> There appears to be no such thing;=20

			[[SW]] Today, but as you mentioned in another
thread, we need to design the protocol to be generic in anticipation of
such requirements.=20

			=20

			Woj#2> What tentative requirements are you
referring to, a relay? If so, bulking doesn't help there. This is also
much different from a discussion about a generic TLV format that is to
be used by the protocol.

			=20

			=20

			in bulking, presumably the reciever would have
to buffer all the way until the end of the bulk message, and then
process each message individually. This seems rather overweight when
compared to simply sending each message again.

			[[SW]] Draft doesn't impose on how much you
bulk. If atomicity in handling of bulked messages is warranted by a
use-case, then yes you want to get the entire message. If not, you could
presumably process as you receive each complete sub-message within the
bundle.=20

			=20

			Woj#2> Adding a single bulk envelope and sending
inside it 100 messages vs 2 bulk envelopes with 50 messages is also
pretty pointless, and an exercise in optimizing something that isn't
needed in the first place: In each case you're still sending 100
messages! The downside is that in either of the bulked messages case you
generally will have to wait till the full message is received. There are
betterTCP access=20

			=20

			 [[SW2]] Sorry to repeat. If you need atomicity
for the sub-messages in the bundle, then you need to wait. If not then
you don't have to. This is providing you the flexibility, which you
don't easily have with individual messages (e.g atomic handling is hard
to realize with individual messages).

			=20

			What is the downside of having it? It is
negotiable as an optional capability.=20

			=20

			Woj> A couple of reasons come to the fore; i) no
body saw a good reason so far to implement it/use it ii) it's added
protocol "stuff" that has no clear benefit, does not realize any new
use-case, does not optimize much, and in fact as mentioned above it
appears to rather have some downsides such as extra overhead, buffering
and delay.

			=20

			Let's now have the axe fall...

			[[SW]] Let us please not be dismissive towards
something that has benefits (as outlined above).=20

			=20

			Wo#2j>  With the exception of cumulative ack,
which does deserve a standalone proposal to be put forward, neither me
nor other members of the WG do appear to share the views regarding the
purported benefits on bulking, nor a desire to retain it in the spec.=20

			[[SW2]] See above. This has been in the draft
for a while, and I have not seen any technical arguments from anyone
else on removing it from the draft. I have clearly outlined the benefits
above, and don't see convincing technical reasons for this to go.=20

			=20

			=20

			Sorry, it just needs to go.

			=20

			[[SW2]] Is this with your chair hat on or as an
individual WG member?=20

			=20

			Cheers,

			Woj.

			=20

			Cheers

			-Sanjay

			=20

			=20

			=20

				-----Original Message-----
				From: Wojciech Dec (wdec)
[mailto:wdec@cisco.com]
				Sent: Tuesday, May 06, 2008 1:24 PM
				To: Sanjay Wadhwa; Peter Arberg;
ancp@ietf.org
				Subject: RE: [ANCP] Bulk Transaction
Message

				Sanjay,

				=20

				can you please present to the WG and
myself how bulk transaction capability is useful in any way in terms of
scaling for example? And by the way, please treat this discussion is
orthogonal to any other.

				=20

				Cheers,

				Woj.

				=20

				=20

			=09
________________________________


				From: Sanjay Wadhwa
[mailto:swadhwa@juniper.net]=20
				Sent: 06 May 2008 19:08
				To: Wojciech Dec (wdec); Peter Arberg;
ancp@ietf.org
				Subject: RE: [ANCP] Bulk Transaction
Message

				Woj

				  It is a bad idea to remove
bulk-transaction capability from the draft. On one hand you are trying
to add "marginally useful" extensions (with TLVs), and on the other hand
you are arguing for removing useful abstractions which can help with
scaling. If bulk-transaction capability needs to be augmented or
modified, then we should consider augmenting it, rather than removing it
from the draft.

				=20

				Cheers

				-Sanjay

				-----Original Message-----
				From: ancp-bounces@ietf.org
[mailto:ancp-bounces@ietf.org]On Behalf Of Wojciech Dec (wdec)
				Sent: Tuesday, May 06, 2008 12:42 PM
				To: Peter Arberg; ancp@ietf.org
				Subject: Re: [ANCP] Bulk Transaction
Message

				Hi Folks,

				=20

				given that no discernable use of Bulk
messaging has been identified, nor there being a good reason for it
given the fact that ANCP is bound to the TCP transport (or equivalent),
I would like to propose to remove all of the text relating to this
capability and associated message from the protocol spec draft.

				=20

				Regards,

				Woj.

				=20

			=09
________________________________


				From: ancp-bounces@ietf.org
[mailto:ancp-bounces@ietf.org] On Behalf Of Wojciech Dec (wdec)
				Sent: 20 April 2008 15:18
				To: Peter Arberg; ancp@ietf.org
				Subject: Re: [ANCP] Bulk Transaction
Message

				Should also have added: Given that
currently the bulk message does not appear to have had any practical
adoption, having the DTeam adopt it/modify it, or possibly have it
removed from the spec all together are all valid options.

				=20

				-Woj.

				=20

			=09
________________________________


				From: ancp-bounces@ietf.org
[mailto:ancp-bounces@ietf.org] On Behalf Of Wojciech Dec (wdec)
				Sent: 20 April 2008 14:39
				To: Peter Arberg; ancp@ietf.org
				Subject: Re: [ANCP] Bulk Transaction
Message

				It's all simple:

				- the Design Team is looking at the
possibility of using this message

				- the message in its current form does
not appear to be terribly useful, and could be removed from the spec.

				=20

				-Woj.

				=20

				=20

			=09
________________________________


				From: ancp-bounces@ietf.org
[mailto:ancp-bounces@ietf.org] On Behalf Of Peter Arberg
				Sent: 19 April 2008 03:07
				To: Wojciech Dec (wdec); ancp@ietf.org
				Subject: Re: [ANCP] Bulk Transaction
Message

				Hi Woj,

				=20

				can you give a little background to why
you are looking for vendor

				implementation support for this specific
capability & message ?

				=20

				thanks,

				Peter

				=20

			=09
________________________________


				From: ancp-bounces@ietf.org
[mailto:ancp-bounces@ietf.org] On Behalf Of Wojciech Dec (wdec)
				Sent: 18. april 2008 08:04
				To: ancp@ietf.org
				Subject: [ANCP] Bulk Transaction Message

				Hi Folks,=20

				Could you please let me/us know if you
currently have an implementation of ANCP that supports the Bulk
Transaction Capability and Message?

				Thanks,=20
				Woj.=20


------_=_NextPart_001_01C8B0F4.C7F4F6AA
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:st1 =3D=20
"urn:schemas-microsoft-com:office:smarttags"><HEAD><TITLE>Bulk =
Transaction Message</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3314" name=3DGENERATOR><!--[if !mso]>
<STYLE>v\:* {
	BEHAVIOR: url(#default#VML)
}
o\:* {
	BEHAVIOR: url(#default#VML)
}
w\:* {
	BEHAVIOR: url(#default#VML)
}
.shape {
	BEHAVIOR: url(#default#VML)
}
</STYLE>
<![endif]--><o:SmartTagType name=3D"PersonName"=20
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"></o:SmartTagT=
ype><!--[if !mso]>
<STYLE>st1\:* {
	BEHAVIOR: url(#default#ieooui)
}
</STYLE>
<![endif]-->
<STYLE>@font-face {
	font-family: Tahoma;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline
}
P {
	FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: =
"Times New Roman"; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto
}
SPAN.EmailStyle18 {
	COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal
}
SPAN.EmailStyle19 {
	COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal-reply
}
DIV.Section1 {
	page: Section1
}
</STYLE>
</HEAD>
<BODY lang=3DEN-US vLink=3Dpurple link=3Dblue>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D691280810-08052008>Hi Sanjay, Woj,</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D691280810-08052008></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D691280810-08052008>I see some advantages in having bulk messages =
to=20
optimize ANCP.&nbsp; However, bulk messages are not the only =
solution.&nbsp; It=20
is wrong to discuss bulk messages without comparing it with =
alternatives.&nbsp;=20
It looks like a good solution to me but maybe there are better ways in=20
optimizing ANCP.&nbsp; So far the working group has not been working a =
lot on=20
optimizations.&nbsp; According to me, keeping bulk messages in the base =
spec is=20
wrong and it should be removed.&nbsp; People are invited to submit =
solutions to=20
optimize ANCP in the form of a seperate draft, and one such draft could =
be bulk=20
messages.&nbsp; Then when the working group decides that it is time to =
work on=20
optimalisations, the proposed solutions can be compared and=20
discussed.</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D691280810-08052008></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D691280810-08052008>regards,</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D691280810-08052008>Stefaan</SPAN></FONT></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> ancp-bounces@ietf.org=20
[mailto:ancp-bounces@ietf.org] <B>On Behalf Of </B>Sanjay =
Wadhwa<BR><B>Sent:</B>=20
woensdag 7 mei 2008 18:07<BR><B>To:</B> Wojciech Dec (wdec); Peter =
Arberg;=20
ancp@ietf.org<BR><B>Subject:</B> Re: [ANCP] Bulk Transaction=20
Message<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=3DSection1>
<P class=3DMsoNormal><B><FONT face=3DArial color=3D#333399 =
size=3D2><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: #333399; =
FONT-FAMILY: Arial">Inline=20
again</SPAN></FONT></B><B><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: #993366; =
FONT-FAMILY: Arial">=20
</SPAN></FONT></B><B><FONT face=3DArial color=3D#333399 size=3D2><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: #333399; =
FONT-FAMILY: Arial">[SW2]<o:p></o:p></SPAN></FONT></B></P>
<P class=3DMsoNormal><B><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: #993366; =
FONT-FAMILY: Arial"><o:p>&nbsp;</o:p></SPAN></FONT></B></P>
<P class=3DMsoNormal><B><FONT face=3DArial color=3D#333399 =
size=3D2><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: #333399; =
FONT-FAMILY: Arial">-Sanjay</SPAN></FONT></B><FONT=20
face=3DArial color=3D#333399 size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: #333399; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<DIV>
<DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" align=3Dcenter><FONT =

face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
<HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
</SPAN></FONT></DIV>
<P class=3DMsoNormal><B><FONT face=3DTahoma size=3D2><SPAN=20
style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma"> Wojciech=20
Dec (wdec) [mailto:wdec@cisco.com] <BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Wednesday, May 07, 2008 =
10:47=20
AM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Wojciech Dec =
(wdec);=20
Sanjay Wadhwa; Peter Arberg; ancp@ietf.org<BR><B><SPAN=20
style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [ANCP] Bulk =
Transaction=20
Message</SPAN></FONT><o:p></o:p></P></DIV>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Should have added:=20
Plea<st1:PersonName w:st=3D"on">se</st1:PersonName> feel free to put =
forward a=20
bulk ack proposal to the WG. Just axe the existing bulking text before =
someone=20
goes starts thinking of actually adopting =
it.</SPAN></FONT><o:p></o:p></P>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">-Woj.</SPAN></FONT><o:p></o:p></P>
<BLOCKQUOTE=20
style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: 5pt 0in 5pt =
3.75pt; BORDER-LEFT: black 1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none">
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
  face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
  <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
  </SPAN></FONT></DIV>
  <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><B><FONT =
face=3DTahoma=20
  size=3D2><SPAN=20
  style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
  face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">=20
  ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] <B><SPAN=20
  style=3D"FONT-WEIGHT: bold">On Behalf Of </SPAN></B>Wojciech Dec=20
  (wdec)<BR><B><SPAN style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> 07 May =
2008=20
  16:27<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Sanjay =
Wadhwa;=20
  Peter Arberg; ancp@ietf.org<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> Re: [ANCP] Bulk =
Transaction=20
  Message</SPAN></FONT><o:p></o:p></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Sanjay,</SPAN></FONT><o:p></o:p></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">inline=20
  woj#2&gt;</SPAN></FONT><o:p></o:p></P>
  <BLOCKQUOTE=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: 5pt 0in 5pt =
3.75pt; BORDER-LEFT: black 1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none">
    <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
    style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
    <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
    face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
    <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
    </SPAN></FONT></DIV>
    <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><B><FONT =
face=3DTahoma=20
    size=3D2><SPAN=20
    style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
    face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">=20
    Sanjay Wadhwa [mailto:swadhwa@juniper.net] <BR><B><SPAN=20
    style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> 07 May 2008 =
16:02<BR><B><SPAN=20
    style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Wojciech Dec (wdec); =
Peter Arberg;=20
    ancp@ietf.org<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">Subject:</SPAN></B> RE:=20
    [ANCP] Bulk Transaction Message</SPAN></FONT><o:p></o:p></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: =
Arial">Woj<o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: Arial">&nbsp; =
Inline=20
    [SW].<o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
    <DIV>
    <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
    face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
    <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
    </SPAN></FONT></DIV>
    <P class=3DMsoNormal><B><FONT face=3DTahoma size=3D2><SPAN=20
    style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
    face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">=20
    Wojciech Dec (wdec) [mailto:wdec@cisco.com] <BR><B><SPAN=20
    style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Wednesday, May 07, 2008 =
3:32=20
    AM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Sanjay =
Wadhwa; Peter=20
    Arberg; ancp@ietf.org<BR><B><SPAN=20
    style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [ANCP] Bulk =
Transaction=20
    Message</SPAN></FONT><o:p></o:p></P></DIV>
    <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
    style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Sanjay,</SPAN></FONT><o:p></o:p></P>
    <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
    style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">inline</SPAN></FONT><o:p></o:p></P>
    <BLOCKQUOTE=20
    style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: 5pt 0in 5pt =
3.75pt; BORDER-LEFT: black 1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none">
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =

      style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
      <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
      face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
      <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
      </SPAN></FONT></DIV>
      <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><B><FONT =
face=3DTahoma=20
      size=3D2><SPAN=20
      style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
      face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Tahoma">=20
      Sanjay Wadhwa [mailto:swadhwa@juniper.net] <BR><B><SPAN=20
      style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> 07 May 2008 =
02:03<BR><B><SPAN=20
      style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Wojciech Dec (wdec); =
Peter=20
      Arberg; ancp@ietf.org<BR><B><SPAN=20
      style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [ANCP] Bulk =
Transaction=20
      Message</SPAN></FONT><o:p></o:p></P>
      <DIV>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">Even =
with=20
      transport being TCP, I <st1:PersonName =
w:st=3D"on">se</st1:PersonName>e=20
      atleast a couple of benefits:</SPAN></FONT><o:p></o:p></P></DIV>
      <DIV>
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =

      style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
      <DIV>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">1. If=20
      a&nbsp;<st1:PersonName w:st=3D"on">se</st1:PersonName>nder knows =
it has a=20
      bunch of messages to <st1:PersonName =
w:st=3D"on">se</st1:PersonName>nd (e.g.=20
      ANCP adjacency flaps, and all the port-up messages need to =
re-played),=20
      then bulking by definition&nbsp;allows the application to invoke =
TCP fewer=20
      times to transmit&nbsp;everything that it needs to transmit, =
which&nbsp;in=20
      a lot of systems can translate to significant&nbsp;compute and =
memory=20
      efficiency (specially, if we are considering a large amount of =
state).=20
      This&nbsp;is not to say one can't&nbsp;realize this&nbsp;in an=20
      implementation specific way.&nbsp;</SPAN></FONT><FONT face=3DArial =

      color=3Dblack size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><o:p></o:p></P></DIV>
      <DIV>
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =

      style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
      <DIV>
      <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Woj&gt; Even with =
bulking one=20
      needs to realize the TCP interaction with some thought. Perhaps =
bulking=20
      indeed&nbsp;offers the opportunity for a delveloper to think about =
that,=20
      but I <st1:PersonName w:st=3D"on">se</st1:PersonName>riously doubt =
that=20
      anyone familar with TCP app development&nbsp;would overlook this =
aspect in=20
      the first place.<o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: =
Arial">[[SW]] I would=20
      like to believe it. History doesn&#8217;t bear this =
though.</SPAN></FONT><FONT=20
      face=3DArial color=3Dblack size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><o:p></o:p></P>
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =

      style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Woj#2&gt;&nbsp;Unless=20
      the spec forces Bulking to be u<st1:PersonName=20
      w:st=3D"on">se</st1:PersonName>d for every single multi-message =
exchange,=20
      the bunching effect will not appear, nor will any=20
      optimization.</SPAN></FONT><o:p></o:p></P></DIV>
      <DIV>
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =

      style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
      <DIV>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">However,&nbsp;</SPAN></FONT><B><FONT=20
      face=3DArial color=3Dred size=3D2><SPAN=20
      style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: red; =
FONT-FAMILY: Arial">if=20
      neeeded</SPAN></FONT></B><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">, =
bulking=20
      also&nbsp;has the benefit of affording optimized acking (e.g. if =
no error=20
      is encountered in proccessing all the sub-messages in the bundled =
message,=20
      it&nbsp;is possible&nbsp;for the receiver to <st1:PersonName=20
      w:st=3D"on">se</st1:PersonName>nd a cummulative ack to the =
<st1:PersonName=20
      w:st=3D"on">se</st1:PersonName>nder rather than individual=20
      acks).</SPAN></FONT><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><o:p></o:p></P></DIV>
      <DIV>
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =

      style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
      <DIV>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Woj&gt;&nbsp;A=20
      cumulatitive ack would appear to be desirable in some =
ca<st1:PersonName=20
      w:st=3D"on">se</st1:PersonName>s, but I <st1:PersonName=20
      w:st=3D"on">se</st1:PersonName>e this as very&nbsp;different to=20
      the&nbsp;bulk ack currently described which es<st1:PersonName=20
      w:st=3D"on">se</st1:PersonName>natially carries in bulk all of the =
individal=20
      acks.&nbsp;The bulking mechanism is quite clear in saying that =
each ANCP=20
      message is&nbsp;bundled header and all, and acted upon =
individually by the=20
      recipient, and whether it's a request or an ack is <st1:PersonName =

      w:st=3D"on">se</st1:PersonName>condary. I'm sure you'll agree that =
this is=20
      undesirable overhead and complexity for what it's worth, also in =
view of=20
      the fact that "something" on the recipient side would need to =
decide what=20
      ack/nack goes into a bulk respon<st1:PersonName=20
      w:st=3D"on">se</st1:PersonName> and what doesn't.=20
      </SPAN></FONT><o:p></o:p></P></DIV>
      <DIV>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Having =
a=20
      cumulatitive ack is an all thogether different thing, which I=20
      would&nbsp;support, and it should not involve the "bulking" of =
each=20
      indivdual ack, and is an item that&nbsp;for which&nbsp;proposals =
are=20
      welcome.</SPAN></FONT><FONT face=3DArial size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: =
Arial">[[SW]] Sorry,=20
      I should have been clearer. Bulking adds an overall header for the =

      individual messages being bulked. If all the messages succeed, we =
can=20
      define the behavior to <st1:PersonName =
w:st=3D"on">se</st1:PersonName>nd a=20
      single ACK (NOT a bulk ACK compo<st1:PersonName=20
      w:st=3D"on">se</st1:PersonName>d of individual sub-messages =
carrying ACK)=20
      with the transaction-ID of the main header reflected back in the =
ACK.=20
      &nbsp;This provides an elegant way to address cumulative ACK. This =
is not=20
      defined in the draft today (<st1:PersonName =
w:st=3D"on">se</st1:PersonName>e=20
      &#8220;if needed&#8221; above), but is easily provided by bulking, =
and can be added if=20
      we agree.<o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: Arial">Far =
as request=20
      message is concerned, having individual messages (with their own =
header)=20
      in the request reduces complexity, provides a way to bulk messages =
of=20
      different types if needed. It allows each sub-message to be =
individually=20
      NACK&#8217;d where required. Bulking in such a way allows the =
flexibility of=20
      treating individual sub-messages as completely independent or=20
      related.</SPAN></FONT><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><o:p></o:p></P>
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =

      style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Woj#2&gt; The=20
      above, in principle is fine, BUT it is far removed from the =
current=20
      bulking mechanism. The order would be to have a proposal regarding =

      this&nbsp;on its own right.&nbsp;</SPAN></FONT><FONT face=3DArial =
color=3Dnavy=20
      size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><B><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
      style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: navy; =
FONT-FAMILY: Arial">[[SW2]]=20
      It can easily be extended and doesn&#8217;t need to be done right =
away.=20
      Rehashing (new proposal) when you have the basis for in the draft =
is not=20
      justifiable.</SPAN></FONT></B><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></P></DIV>
      <DIV>
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =

      style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
      <DIV>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">2. =
Bulking also=20
      provides a nice solution if one&nbsp;ever needed to atomically =
receive and=20
      process *distinct* ANCP message types.&nbsp;</SPAN></FONT><FONT =
face=3DArial=20
      color=3Dblack size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><FONT=20
      face=3DArial color=3Dnavy size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><B><I><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
      style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: navy; =
FONT-STYLE: italic; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></I></B></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Woj&gt;&nbsp;There=20
      appears to be no such thing; </SPAN></FONT><FONT face=3DArial =
color=3Dnavy=20
      size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: =
Arial">[[SW]] Today,=20
      but as you mentioned in another thread, we need to design the =
protocol to=20
      be generic in anticipation of such =
requirements.</SPAN></FONT><FONT=20
      face=3DArial color=3Dblack size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><o:p></o:p></P>
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =

      style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Woj#2&gt; What=20
      tentative requirements are you referring to, a&nbsp;relay?&nbsp;If =

      so,&nbsp;bulking doesn't help there. This is also much different =
from a=20
      discussion about a generic TLV format that is to be =
u<st1:PersonName=20
      w:st=3D"on">se</st1:PersonName>d by the=20
      protocol.</SPAN></FONT><o:p></o:p></P>
      <P class=3DMsoNormal><B><I><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
      style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: navy; =
FONT-STYLE: italic; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></I></B></P>
      <P class=3DMsoNormal><B><I><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
      style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: navy; =
FONT-STYLE: italic; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></I></B></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">in =
bulking,=20
      presumably the reciever would have to buffer all the way until the =
end of=20
      the bulk message, and then process each message individually. This =

      <st1:PersonName w:st=3D"on">se</st1:PersonName>ems rather =
overweight when=20
      compared to simply <st1:PersonName =
w:st=3D"on">se</st1:PersonName>nding each=20
      message again.</SPAN></FONT><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: =
Arial">[[SW]] Draft=20
      doesn&#8217;t impo<st1:PersonName w:st=3D"on">se</st1:PersonName> =
on how much you=20
      bulk. If atomicity in handling of bulked messages is warranted by =
a=20
      u<st1:PersonName w:st=3D"on">se</st1:PersonName>-ca<st1:PersonName =

      w:st=3D"on">se</st1:PersonName>, then yes you want to get the =
entire=20
      message. If not, you could presumably process as you receive each =
complete=20
      sub-message within the bundle.</SPAN></FONT><FONT face=3DArial =
color=3Dblack=20
      size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><o:p></o:p></P>
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =

      style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Woj#2&gt; Adding=20
      a single bulk envelope and <st1:PersonName=20
      w:st=3D"on">se</st1:PersonName>nding inside it&nbsp;100 messages =
vs 2 bulk=20
      envelopes with 50 messages is also pretty pointless, and an=20
      exerci<st1:PersonName w:st=3D"on">se</st1:PersonName> in =
optimizing=20
      something that isn't needed in the first place: In each =
ca<st1:PersonName=20
      w:st=3D"on">se</st1:PersonName> you're still <st1:PersonName=20
      w:st=3D"on">se</st1:PersonName>nding 100 messages! The downside is =
that in=20
      either of the bulked messages ca<st1:PersonName=20
      w:st=3D"on">se</st1:PersonName> you generally will have to wait =
till the=20
      full message is received. There are betterTCP access =
</SPAN></FONT><FONT=20
      face=3DArial size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><B><I><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
      style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: navy; =
FONT-STYLE: italic; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></I></B></P>
      <P class=3DMsoNormal><B><I><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
      style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: navy; =
FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT></I></B><B><FONT=20
      face=3DArial color=3Dnavy size=3D2><SPAN=20
      style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: navy; =
FONT-FAMILY: Arial">[[SW2]]=20
      Sorry to repeat. If you need atomicity for the sub-messages in the =
bundle,=20
      then you need to wait. If not then you don&#8217;t have to. This =
is providing=20
      you the flexibility, which you don&#8217;t easily have with =
individual messages=20
      (e.g atomic handling is hard to realize with individual=20
      messages).</SPAN></FONT></B><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></P></DIV>
      <DIV>
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =

      style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
      <DIV>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">What is =
the=20
      downside of having it? It is&nbsp;negotiable as an optional=20
      capability.</SPAN></FONT><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><o:p></o:p></P></DIV>
      <DIV>
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =

      style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
      <DIV>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Woj&gt; A couple=20
      of reasons come to the fore; i) no body saw a good reason so far =
to=20
      implement it/u<st1:PersonName w:st=3D"on">se</st1:PersonName> it =
ii) it's=20
      added protocol "stuff" that has no clear benefit, does not realize =
any new=20
      u<st1:PersonName w:st=3D"on">se</st1:PersonName>-ca<st1:PersonName =

      w:st=3D"on">se</st1:PersonName>,&nbsp;does not optimize much, and =
in fact as=20
      mentioned above it appears to rather have some downsides such as =
extra=20
      overhead, buffering and delay.</SPAN></FONT><B><I><FONT =
face=3DArial=20
      color=3Dnavy size=3D2><SPAN=20
      style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: navy; =
FONT-STYLE: italic; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></I></B></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Let's =
now have=20
      the axe fall...</SPAN></FONT><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: =
Arial">[[SW]] Let us=20
      plea<st1:PersonName w:st=3D"on">se</st1:PersonName> not be =
dismissive=20
      towards something that has benefits (as outlined=20
      above).</SPAN></FONT><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><o:p></o:p></P>
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =

      style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Wo#2j&gt;=20
      &nbsp;With the exception of cumulative ack, which does =
de<st1:PersonName=20
      w:st=3D"on">se</st1:PersonName>rve a standalone proposal to be put =
forward,=20
      neither me nor&nbsp;other members of the&nbsp;WG do&nbsp;appear to =
share=20
      the views regarding the purported benefits on bulking, nor a =
desire to=20
      retain it in the spec.&nbsp;</SPAN></FONT><FONT face=3DArial =
color=3Dnavy=20
      size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><B><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
      style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: navy; =
FONT-FAMILY: Arial">[[SW2]]=20
      See above. This has been in the draft for a while, and I have not=20
      <st1:PersonName w:st=3D"on">se</st1:PersonName>en any technical =
arguments=20
      from anyone el<st1:PersonName w:st=3D"on">se</st1:PersonName> on =
removing it=20
      from the draft. I have clearly outlined the benefits above, and =
don&#8217;t=20
      <st1:PersonName w:st=3D"on">se</st1:PersonName>e convincing =
technical=20
      reasons for this to go. </SPAN></FONT></B><FONT face=3DArial =
color=3Dnavy=20
      size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><B><I><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
      style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: navy; =
FONT-STYLE: italic; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></I></B></P>
      <P class=3DMsoNormal><B><I><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
      style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: navy; =
FONT-STYLE: italic; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></I></B></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Sorry, =
it just=20
      needs to go.</SPAN></FONT><o:p></o:p></P>
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =

      style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><B><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
      style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: navy; =
FONT-FAMILY: Arial">[[SW2]]=20
      Is this with your chair hat on or as an individual WG member?=20
      <o:p></o:p></SPAN></FONT></B></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Cheers,</SPAN></FONT><o:p></o:p></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Woj.</SPAN></FONT><o:p></o:p></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: =
Arial">Cheers<o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: =
Arial">-Sanjay<o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P></DIV>
      <DIV>
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =

      style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
      <DIV>
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =

      style=3D"FONT-SIZE: =
12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P></DIV>
      <BLOCKQUOTE=20
      style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; =
BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: =
5pt 0in 5pt 3.75pt; BORDER-LEFT: blue 1.5pt solid; PADDING-TOP: 0in; =
BORDER-BOTTOM: medium none">
        <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><FONT =
face=3DTahoma=20
        size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">-----Original=20
        Message-----<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">From:</SPAN></B>=20
        Wojciech Dec (wdec) [mailto:wdec@cisco.com]<BR><B><SPAN=20
        style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Tuesday, May 06, =
2008 1:24=20
        PM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Sanjay =
Wadhwa;=20
        Peter Arberg; ancp@ietf.org<BR><B><SPAN=20
        style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [ANCP] Bulk=20
        Transaction Message</SPAN></FONT><o:p></o:p></P>
        <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Sanjay,</SPAN></FONT><o:p></o:p></P>
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
        style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">can you =
plea<st1:PersonName=20
        w:st=3D"on">se</st1:PersonName> pre<st1:PersonName=20
        w:st=3D"on">se</st1:PersonName>nt to the WG and =
my<st1:PersonName=20
        w:st=3D"on">se</st1:PersonName>lf how bulk transaction =
capability is=20
        u<st1:PersonName w:st=3D"on">se</st1:PersonName>ful in any way =
in terms of=20
        scaling for example? And by the way, plea<st1:PersonName=20
        w:st=3D"on">se</st1:PersonName> treat this discussion is =
orthogonal to any=20
        other.</SPAN></FONT><o:p></o:p></P>
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
        style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Cheers,</SPAN></FONT><o:p></o:p></P>
        <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Woj.</SPAN></FONT><o:p></o:p></P>
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
        style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
        <BLOCKQUOTE=20
        style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; =
BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: =
5pt 0in 5pt 3.75pt; BORDER-LEFT: black 1.5pt solid; PADDING-TOP: 0in; =
BORDER-BOTTOM: medium none">
          <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
          style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
          <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
          face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: =
12pt">
          <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
          </SPAN></FONT></DIV>
          <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><B><FONT =
face=3DTahoma=20
          size=3D2><SPAN=20
          style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
          face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Tahoma">=20
          Sanjay Wadhwa [mailto:swadhwa@juniper.net] <BR><B><SPAN=20
          style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> 06 May 2008=20
          19:08<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> =
Wojciech=20
          Dec (wdec); Peter Arberg; ancp@ietf.org<BR><B><SPAN=20
          style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [ANCP] =
Bulk=20
          Transaction Message</SPAN></FONT><o:p></o:p></P>
          <DIV>
          <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
          style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Woj</SPAN></FONT><o:p></o:p></P></DIV>
          <DIV>
          <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
          style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp; It is=20
          a bad idea to remove bulk-transaction capability from the =
draft. On=20
          one hand you are trying to add "marginally u<st1:PersonName=20
          w:st=3D"on">se</st1:PersonName>ful" extensions (with TLVs), =
and on the=20
          other hand you are arguing for removing u<st1:PersonName=20
          w:st=3D"on">se</st1:PersonName>ful abstractions which can help =
with=20
          scaling. If bulk-transaction capability needs to be augmented =
or=20
          modified, then we should consider augmenting it, rather than =
removing=20
          it from the draft.</SPAN></FONT><o:p></o:p></P></DIV>
          <DIV>
          <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
          style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
          <DIV>
          <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
          style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Cheers</SPAN></FONT><o:p></o:p></P></DIV>
          <DIV>
          <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
          style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">-Sanjay</SPAN></FONT><o:p></o:p></P></DIV>
          <BLOCKQUOTE=20
          style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; =
BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: =
5pt 0in 5pt 3.75pt; BORDER-LEFT: blue 1.5pt solid; PADDING-TOP: 0in; =
BORDER-BOTTOM: medium none">
            <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><FONT =
face=3DTahoma=20
            size=3D2><SPAN=20
            style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">-----Original =

            Message-----<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">From:</SPAN></B>=20
            ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org]<B><SPAN =

            style=3D"FONT-WEIGHT: bold">On Behalf Of </SPAN></B>Wojciech =
Dec=20
            (wdec)<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">Sent:</SPAN></B>=20
            Tuesday, May 06, 2008 12:42 PM<BR><B><SPAN=20
            style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Peter Arberg;=20
            ancp@ietf.org<BR><B><SPAN=20
            style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> Re: [ANCP] =
Bulk=20
            Transaction Message</SPAN></FONT><o:p></o:p></P>
            <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
            style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Hi=20
            Folks,</SPAN></FONT><o:p></o:p></P>
            <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
            style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
            <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
            style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">given that no=20
            discernable u<st1:PersonName w:st=3D"on">se</st1:PersonName> =
of Bulk=20
            messaging has been identified, nor&nbsp;there being a good =
reason=20
            for it given the fact that ANCP is bound to the TCP =
transport (or=20
            equivalent),&nbsp;I would like to propo<st1:PersonName=20
            w:st=3D"on">se</st1:PersonName> to remove all of the text =
relating to=20
            this capability and associated message from the protocol =
spec=20
            draft.</SPAN></FONT><o:p></o:p></P>
            <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
            style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
            <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
            style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Regards,</SPAN></FONT><o:p></o:p></P>
            <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
            style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Woj.</SPAN></FONT><o:p></o:p></P>
            <BLOCKQUOTE=20
            style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; =
BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: =
5pt 0in 5pt 3.75pt; BORDER-LEFT: black 1.5pt solid; PADDING-TOP: 0in; =
BORDER-BOTTOM: medium none">
              <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
              style=3D"FONT-SIZE: =
12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
              <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
              face=3D"Times New Roman" size=3D3><SPAN =
style=3D"FONT-SIZE: 12pt">
              <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
              </SPAN></FONT></DIV>
              <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: =
12pt"><B><FONT=20
              face=3DTahoma size=3D2><SPAN=20
              style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
              face=3DTahoma size=3D2><SPAN=20
              style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">=20
              ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] =
<B><SPAN=20
              style=3D"FONT-WEIGHT: bold">On Behalf Of =
</SPAN></B>Wojciech Dec=20
              (wdec)<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">Sent:</SPAN></B> 20=20
              April 2008 15:18<BR><B><SPAN=20
              style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Peter Arberg;=20
              ancp@ietf.org<BR><B><SPAN=20
              style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> Re: [ANCP] =
Bulk=20
              Transaction Message</SPAN></FONT><o:p></o:p></P>
              <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
              style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Should also =
have=20
              added: Given that currently&nbsp;the bulk message does not =
appear=20
              to have had any practical&nbsp;adoption, having the DTeam =
adopt=20
              it/modify it, or possibly have it removed from the spec =
all=20
              together&nbsp;are all valid =
options.</SPAN></FONT><o:p></o:p></P>
              <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
              style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
              <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
              style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">-Woj.</SPAN></FONT><o:p></o:p></P>
              <BLOCKQUOTE=20
              style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; =
BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: =
5pt 0in 5pt 3.75pt; BORDER-LEFT: black 1.5pt solid; PADDING-TOP: 0in; =
BORDER-BOTTOM: medium none">
                <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                style=3D"FONT-SIZE: =
12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
                <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center"=20
                align=3Dcenter><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                style=3D"FONT-SIZE: 12pt">
                <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" =
SIZE=3D2>
                </SPAN></FONT></DIV>
                <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: =
12pt"><B><FONT=20
                face=3DTahoma size=3D2><SPAN=20
                style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; =
FONT-FAMILY: Tahoma">From:</SPAN></FONT></B><FONT=20
                face=3DTahoma size=3D2><SPAN=20
                style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">=20
                ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] =
<B><SPAN=20
                style=3D"FONT-WEIGHT: bold">On Behalf Of =
</SPAN></B>Wojciech Dec=20
                (wdec)<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">Sent:</SPAN></B> 20=20
                April 2008 14:39<BR><B><SPAN=20
                style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Peter Arberg; =

                ancp@ietf.org<BR><B><SPAN=20
                style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> Re: =
[ANCP] Bulk=20
                Transaction Message</SPAN></FONT><o:p></o:p></P>
                <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
                style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">It's all=20
                simple:</SPAN></FONT><o:p></o:p></P>
                <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
                style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">-&nbsp;the =
Design=20
                Team is looking at the possibility of using this=20
                message</SPAN></FONT><o:p></o:p></P>
                <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
                style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">- the =
message in its=20
                current form does not appear to be terribly =
u<st1:PersonName=20
                w:st=3D"on">se</st1:PersonName>ful, and could =
be&nbsp;removed from=20
                the spec.</SPAN></FONT><o:p></o:p></P>
                <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
                <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
                style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">-Woj.</SPAN></FONT><o:p></o:p></P>
                <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
                <BLOCKQUOTE=20
                style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; =
BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: =
5pt 0in 5pt 3.75pt; BORDER-LEFT: black 1.5pt solid; PADDING-TOP: 0in; =
BORDER-BOTTOM: medium none">
                  <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                  style=3D"FONT-SIZE: =
12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
                  <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center"=20
                  align=3Dcenter><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                  style=3D"FONT-SIZE: 12pt">
                  <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" =
SIZE=3D2>
                  </SPAN></FONT></DIV>
                  <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: =
12pt"><B><FONT=20
                  face=3DTahoma size=3D2><SPAN=20
                  style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; =
FONT-FAMILY: Tahoma">From:</SPAN></FONT></B><FONT=20
                  face=3DTahoma size=3D2><SPAN=20
                  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">=20
                  ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] =
<B><SPAN=20
                  style=3D"FONT-WEIGHT: bold">On Behalf Of =
</SPAN></B>Peter=20
                  Arberg<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">Sent:</SPAN></B>=20
                  19 April 2008 03:07<BR><B><SPAN=20
                  style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Wojciech =
Dec (wdec);=20
                  ancp@ietf.org<BR><B><SPAN=20
                  style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> Re: =
[ANCP] Bulk=20
                  Transaction Message</SPAN></FONT><o:p></o:p></P>
                  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
                  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Hi=20
                  Woj,</SPAN></FONT><o:p></o:p></P>
                  <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                  style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
                  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
                  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">can=20
                  you give a little background to why you are looking =
for=20
                  vendor</SPAN></FONT><o:p></o:p></P>
                  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
                  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">implementation=20
                  support for this specific capability &amp; message=20
                  ?</SPAN></FONT><o:p></o:p></P>
                  <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                  style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
                  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
                  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">thanks,</SPAN></FONT><o:p></o:p></P>
                  <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
                  style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Peter</SPAN></FONT><o:p></o:p></P>
                  <BLOCKQUOTE=20
                  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: =
0in; BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; =
MARGIN: 5pt 0in 5pt 3.75pt; BORDER-LEFT: blue 1.5pt solid; PADDING-TOP: =
0in; BORDER-BOTTOM: medium none">
                    <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                    style=3D"FONT-SIZE: =
12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
                    <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center"=20
                    align=3Dcenter><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                    style=3D"FONT-SIZE: 12pt">
                    <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" =
SIZE=3D2>
                    </SPAN></FONT></DIV>
                    <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: =
12pt"><B><FONT=20
                    face=3DTahoma size=3D2><SPAN=20
                    style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; =
FONT-FAMILY: Tahoma">From:</SPAN></FONT></B><FONT=20
                    face=3DTahoma size=3D2><SPAN=20
                    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">=20
                    ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] =

                    <B><SPAN style=3D"FONT-WEIGHT: bold">On Behalf Of=20
                    </SPAN></B>Wojciech Dec (wdec)<BR><B><SPAN=20
                    style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> 18. =
april 2008=20
                    08:04<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">To:</SPAN></B>=20
                    ancp@ietf.org<BR><B><SPAN=20
                    style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> =
[ANCP] Bulk=20
                    Transaction Message</SPAN></FONT><o:p></o:p></P>
                    <P><FONT face=3DArial size=3D2><SPAN lang=3DEN-GB=20
                    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"><!-- =
Converted from text/rtf format -->Hi=20
                    Folks,</SPAN></FONT><SPAN lang=3DEN-GB> =
</SPAN><o:p></o:p></P>
                    <P><FONT face=3DArial size=3D2><SPAN lang=3DEN-GB=20
                    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Could =
you=20
                    plea<st1:PersonName w:st=3D"on">se</st1:PersonName> =
let me/us=20
                    know if you currently have an implementation of ANCP =
that=20
                    supports the Bulk Transaction Capability and=20
                    Message?</SPAN></FONT><o:p></o:p></P>
                    <P><FONT face=3DArial size=3D2><SPAN lang=3DEN-GB=20
                    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Thanks,</SPAN></FONT>=20
                    <BR><FONT face=3DArial size=3D2><SPAN lang=3DEN-GB=20
                    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Woj.</SPAN></FONT><SPAN=20
                    lang=3DEN-GB>=20
              =
</SPAN><o:p></o:p></P></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE=
></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCK=
QUOTE></DIV></BODY></HTML>

------_=_NextPart_001_01C8B0F4.C7F4F6AA--

--===============1171606889==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1171606889==--


From ancp-bounces@ietf.org  Thu May  8 08:56:57 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AE9C028D299;
	Thu,  8 May 2008 08:56:57 -0700 (PDT)
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 0D18828D296
	for <ancp@core3.amsl.com>; Thu,  8 May 2008 08:56:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.516
X-Spam-Level: 
X-Spam-Status: No, score=0.516 tagged_above=-999 required=5 tests=[AWL=-2.886, 
	BAYES_00=-2.599, HTML_MESSAGE=0.001, J_BACKHAIR_12=1,
	J_BACKHAIR_21=1, 
	J_BACKHAIR_22=1, J_BACKHAIR_23=1, J_BACKHAIR_24=1, J_BACKHAIR_25=1,
	J_BACKHAIR_27=1, J_BACKHAIR_32=1, J_BACKHAIR_42=1, J_BACKHAIR_52=1,
	RCVD_IN_DNSWL_MED=-4]
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 1ZpngS+OTxOf for <ancp@core3.amsl.com>;
	Thu,  8 May 2008 08:56:39 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id E688828CFD3
	for <ancp@ietf.org>; Thu,  8 May 2008 06:44:09 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,454,1204498800"; d="scan'208,217";a="8351391"
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 08 May 2008 12:37:41 +0200
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m48AbfjU010932; 
	Thu, 8 May 2008 12:37:41 +0200
Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com
	[144.254.231.71])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m48Abfnm000295;
	Thu, 8 May 2008 10:37:41 GMT
Received: from xmb-ams-33b.cisco.com ([144.254.231.86]) by
	xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 8 May 2008 12:37:41 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 8 May 2008 12:36:57 +0200
Message-ID: <D9872168DBD43A41BD71FFC4713274D405094D90@xmb-ams-33b.emea.cisco.com>
In-Reply-To: <9BD5D7887235424FA97DFC223CAE3C28105B8C39@proton.jnpr.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ANCP] Bulk Transaction Message
thread-index: AcihZWeDZVeOVtxMS1uttRBEffcNEwAVDjfgAEod1tAAAWRvoAMsB4yQAADCZxAAAKZHUAAJVuxQABJPrxAADmDeEAABcgAQAAFBHxAAAJXZIAADrM9g
References: <D9872168DBD43A41BD71FFC4713274D405043771@xmb-ams-33b.emea.cisco.com><9BD5D7887235424FA97DFC223CAE3C280AB43A61@proton.jnpr.net><D9872168DBD43A41BD71FFC4713274D4050438A2@xmb-ams-33b.emea.cisco.com><9BD5D7887235424FA97DFC223CAE3C28105B8B41@proton.jnpr.net>
	<D9872168DBD43A41BD71FFC4713274D405043C34@xmb-ams-33b.emea.cisco.com>
	<D9872168DBD43A41BD71FFC4713274D405043C65@xmb-ams-33b.emea.cisco.com>
	<9BD5D7887235424FA97DFC223CAE3C28105B8C39@proton.jnpr.net>
From: "Wojciech Dec (wdec)" <wdec@cisco.com>
To: "Sanjay Wadhwa" <swadhwa@juniper.net>,
	"Peter Arberg" <parberg@redback.com>, <ancp@ietf.org>
X-OriginalArrivalTime: 08 May 2008 10:37:41.0080 (UTC)
	FILETIME=[8AB83D80:01C8B0F7]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=76701; t=1210243061;
	x=1211107061; c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=wdec@cisco.com;
	z=From:=20=22Wojciech=20Dec=20(wdec)=22=20<wdec@cisco.com>
	|Subject:=20RE=3A=20[ANCP]=20Bulk=20Transaction=20Message
	|Sender:=20; bh=D2eoYzZZq+lfAKm0vpqWAUH5odSS/un/PjxFyg7SfDg=;
	b=c+YPWG0dySK33VP2dmHFycYN+YDJtPXevJOCvKfEMvTgZQx/AQn+U9dstd
	3aRrQPC/vg6O1EsmMqL0nbljyQCvYf2MvMSWHgnKfSTZamWMVM4cRWtr+GL5
	7zGEGwXtKb;
Authentication-Results: ams-dkim-1; header.From=wdec@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
Subject: Re: [ANCP] Bulk Transaction Message
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/pipermail/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>
Content-Type: multipart/mixed; boundary="===============0711124087=="
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0711124087==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8B0F7.8A4F0F5C"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8B0F7.8A4F0F5C
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Sanjay,
=20
(chair hat on) re-hashing arguments already made isn't going to resolve
this. In essence, there appears to be no clear and sound technical
justification/use presented for the existence of this totally *distinct*
functionality, as opposed to a by-product of an other one, whose sole
purpose is to ferry other already fully formed messages that do not
require another layer of message delineation in TCP. There also isn't
any substantial support in the WG for keeping it in the spec, but rather
the contrary (see earlier responses on the thread). Justifying its
presence as a place holder for something quite different (eg "cumulative
ACK" optimization) that is yet to come in the future is undesirable, and
equally so is keeping it on as "optional" material in the protocol that
happens to be of little practical use, if any. One possible original
justification has gone away since it became clear that the WG would not
be adopting other transports for ANCP than TCP (or equivalent) for the
time being.
As stated previously *you or anyone else* are welcome (expected?) to put
forward to the WG a detailed proposal describing "cumulative ACKs" for
acceptance in place of the Bulk Transaction. Other than this, since you
continue to believe firmly in the ANCP Bulk Transaction Mechanism as is,
then what we can offer is to welcome it back in the ANCP WG as an
individual contribution draft, and have another discussion round at
getting WG support for it. Till then, and in view of trying to get the
spec into shape for finishing it, please accept the fact that the text
is to be either removed from the WG draft-ietf-ancp-protocol spec by its
next 03 revision, or be supplanted by a WG accepted cumulative ack
proposal.=20
There appears to be little reason in dragging this discussion out any
further, however if anything here still isn't clear then I do suggest a
private forum for clarifying.
=20
Regards,
Woj.


________________________________

	From: Sanjay Wadhwa [mailto:swadhwa@juniper.net]=20
	Sent: 07 May 2008 18:07
	To: Wojciech Dec (wdec); Peter Arberg; ancp@ietf.org
	Subject: RE: [ANCP] Bulk Transaction Message
=09
=09

	Inline again [SW2]

	=20

	-Sanjay

	=20

=09
________________________________


	From: Wojciech Dec (wdec) [mailto:wdec@cisco.com]=20
	Sent: Wednesday, May 07, 2008 10:47 AM
	To: Wojciech Dec (wdec); Sanjay Wadhwa; Peter Arberg;
ancp@ietf.org
	Subject: RE: [ANCP] Bulk Transaction Message

	=20

	Should have added: Please feel free to put forward a bulk ack
proposal to the WG. Just axe the existing bulking text before someone
goes starts thinking of actually adopting it.

	=20

	-Woj.

		=20

	=09
________________________________


		From: ancp-bounces@ietf.org
[mailto:ancp-bounces@ietf.org] On Behalf Of Wojciech Dec (wdec)
		Sent: 07 May 2008 16:27
		To: Sanjay Wadhwa; Peter Arberg; ancp@ietf.org
		Subject: Re: [ANCP] Bulk Transaction Message

		Sanjay,

		=20

		inline woj#2>

			=20

		=09
________________________________


			From: Sanjay Wadhwa [mailto:swadhwa@juniper.net]

			Sent: 07 May 2008 16:02
			To: Wojciech Dec (wdec); Peter Arberg;
ancp@ietf.org
			Subject: RE: [ANCP] Bulk Transaction Message

			Woj

			  Inline [SW].

			=20

		=09
________________________________


			From: Wojciech Dec (wdec)
[mailto:wdec@cisco.com]=20
			Sent: Wednesday, May 07, 2008 3:32 AM
			To: Sanjay Wadhwa; Peter Arberg; ancp@ietf.org
			Subject: RE: [ANCP] Bulk Transaction Message

			=20

			Sanjay,

			=20

			inline

				=20

			=09
________________________________


				From: Sanjay Wadhwa
[mailto:swadhwa@juniper.net]=20
				Sent: 07 May 2008 02:03
				To: Wojciech Dec (wdec); Peter Arberg;
ancp@ietf.org
				Subject: RE: [ANCP] Bulk Transaction
Message

				Even with transport being TCP, I see
atleast a couple of benefits:

				=20

				1. If a sender knows it has a bunch of
messages to send (e.g. ANCP adjacency flaps, and all the port-up
messages need to re-played), then bulking by definition allows the
application to invoke TCP fewer times to transmit everything that it
needs to transmit, which in a lot of systems can translate to
significant compute and memory efficiency (specially, if we are
considering a large amount of state). This is not to say one can't
realize this in an implementation specific way. =20

				=20

				Woj> Even with bulking one needs to
realize the TCP interaction with some thought. Perhaps bulking indeed
offers the opportunity for a delveloper to think about that, but I
seriously doubt that anyone familar with TCP app development would
overlook this aspect in the first place.

				=20

				[[SW]] I would like to believe it.
History doesn't bear this though.=20

				=20

				Woj#2> Unless the spec forces Bulking to
be used for every single multi-message exchange, the bunching effect
will not appear, nor will any optimization.

				=20

				However, if neeeded, bulking also has
the benefit of affording optimized acking (e.g. if no error is
encountered in proccessing all the sub-messages in the bundled message,
it is possible for the receiver to send a cummulative ack to the sender
rather than individual acks).=20

				=20

				Woj> A cumulatitive ack would appear to
be desirable in some cases, but I see this as very different to the bulk
ack currently described which essenatially carries in bulk all of the
individal acks. The bulking mechanism is quite clear in saying that each
ANCP message is bundled header and all, and acted upon individually by
the recipient, and whether it's a request or an ack is secondary. I'm
sure you'll agree that this is undesirable overhead and complexity for
what it's worth, also in view of the fact that "something" on the
recipient side would need to decide what ack/nack goes into a bulk
response and what doesn't.=20

				Having a cumulatitive ack is an all
thogether different thing, which I would support, and it should not
involve the "bulking" of each indivdual ack, and is an item that for
which proposals are welcome.

				[[SW]] Sorry, I should have been
clearer. Bulking adds an overall header for the individual messages
being bulked. If all the messages succeed, we can define the behavior to
send a single ACK (NOT a bulk ACK composed of individual sub-messages
carrying ACK) with the transaction-ID of the main header reflected back
in the ACK.  This provides an elegant way to address cumulative ACK.
This is not defined in the draft today (see "if needed" above), but is
easily provided by bulking, and can be added if we agree.

				Far as request message is concerned,
having individual messages (with their own header) in the request
reduces complexity, provides a way to bulk messages of different types
if needed. It allows each sub-message to be individually NACK'd where
required. Bulking in such a way allows the flexibility of treating
individual sub-messages as completely independent or related.=20

				=20

				Woj#2> The above, in principle is fine,
BUT it is far removed from the current bulking mechanism. The order
would be to have a proposal regarding this on its own right.=20

				=20

				[[SW2]] It can easily be extended and
doesn't need to be done right away. Rehashing (new proposal) when you
have the basis for in the draft is not justifiable.

				=20

				2. Bulking also provides a nice solution
if one ever needed to atomically receive and process *distinct* ANCP
message types. =20

				=20

				Woj> There appears to be no such thing;=20

				[[SW]] Today, but as you mentioned in
another thread, we need to design the protocol to be generic in
anticipation of such requirements.=20

				=20

				Woj#2> What tentative requirements are
you referring to, a relay? If so, bulking doesn't help there. This is
also much different from a discussion about a generic TLV format that is
to be used by the protocol.

				=20

				=20

				in bulking, presumably the reciever
would have to buffer all the way until the end of the bulk message, and
then process each message individually. This seems rather overweight
when compared to simply sending each message again.

				[[SW]] Draft doesn't impose on how much
you bulk. If atomicity in handling of bulked messages is warranted by a
use-case, then yes you want to get the entire message. If not, you could
presumably process as you receive each complete sub-message within the
bundle.=20

				=20

				Woj#2> Adding a single bulk envelope and
sending inside it 100 messages vs 2 bulk envelopes with 50 messages is
also pretty pointless, and an exercise in optimizing something that
isn't needed in the first place: In each case you're still sending 100
messages! The downside is that in either of the bulked messages case you
generally will have to wait till the full message is received. There are
betterTCP access=20

				=20

				 [[SW2]] Sorry to repeat. If you need
atomicity for the sub-messages in the bundle, then you need to wait. If
not then you don't have to. This is providing you the flexibility, which
you don't easily have with individual messages (e.g atomic handling is
hard to realize with individual messages).

				=20

				What is the downside of having it? It is
negotiable as an optional capability.=20

				=20

				Woj> A couple of reasons come to the
fore; i) no body saw a good reason so far to implement it/use it ii)
it's added protocol "stuff" that has no clear benefit, does not realize
any new use-case, does not optimize much, and in fact as mentioned above
it appears to rather have some downsides such as extra overhead,
buffering and delay.

				=20

				Let's now have the axe fall...

				[[SW]] Let us please not be dismissive
towards something that has benefits (as outlined above).=20

				=20

				Wo#2j>  With the exception of cumulative
ack, which does deserve a standalone proposal to be put forward, neither
me nor other members of the WG do appear to share the views regarding
the purported benefits on bulking, nor a desire to retain it in the
spec.=20

				[[SW2]] See above. This has been in the
draft for a while, and I have not seen any technical arguments from
anyone else on removing it from the draft. I have clearly outlined the
benefits above, and don't see convincing technical reasons for this to
go.=20

				=20

				=20

				Sorry, it just needs to go.

				=20

				[[SW2]] Is this with your chair hat on
or as an individual WG member?=20

				=20

				Cheers,

				Woj.

				=20

				Cheers

				-Sanjay

				=20

				=20

				=20

				-----Original Message-----
				From: Wojciech Dec (wdec)
[mailto:wdec@cisco.com]
				Sent: Tuesday, May 06, 2008 1:24 PM
				To: Sanjay Wadhwa; Peter Arberg;
ancp@ietf.org
				Subject: RE: [ANCP] Bulk Transaction
Message

				Sanjay,

				=20

				can you please present to the WG and
myself how bulk transaction capability is useful in any way in terms of
scaling for example? And by the way, please treat this discussion is
orthogonal to any other.

				=20

				Cheers,

				Woj.

				=20

				=20

			=09
________________________________


				From: Sanjay Wadhwa
[mailto:swadhwa@juniper.net]=20
				Sent: 06 May 2008 19:08
				To: Wojciech Dec (wdec); Peter Arberg;
ancp@ietf.org
				Subject: RE: [ANCP] Bulk Transaction
Message

				Woj

				  It is a bad idea to remove
bulk-transaction capability from the draft. On one hand you are trying
to add "marginally useful" extensions (with TLVs), and on the other hand
you are arguing for removing useful abstractions which can help with
scaling. If bulk-transaction capability needs to be augmented or
modified, then we should consider augmenting it, rather than removing it
from the draft.

				=20

				Cheers

				-Sanjay

				-----Original Message-----
				From: ancp-bounces@ietf.org
[mailto:ancp-bounces@ietf.org]On Behalf Of Wojciech Dec (wdec)
				Sent: Tuesday, May 06, 2008 12:42 PM
				To: Peter Arberg; ancp@ietf.org
				Subject: Re: [ANCP] Bulk Transaction
Message

				Hi Folks,

				=20

				given that no discernable use of Bulk
messaging has been identified, nor there being a good reason for it
given the fact that ANCP is bound to the TCP transport (or equivalent),
I would like to propose to remove all of the text relating to this
capability and associated message from the protocol spec draft.

				=20

				Regards,

				Woj.

				=20

			=09
________________________________


				From: ancp-bounces@ietf.org
[mailto:ancp-bounces@ietf.org] On Behalf Of Wojciech Dec (wdec)
				Sent: 20 April 2008 15:18
				To: Peter Arberg; ancp@ietf.org
				Subject: Re: [ANCP] Bulk Transaction
Message

				Should also have added: Given that
currently the bulk message does not appear to have had any practical
adoption, having the DTeam adopt it/modify it, or possibly have it
removed from the spec all together are all valid options.

				=20

				-Woj.

				=20

			=09
________________________________


				From: ancp-bounces@ietf.org
[mailto:ancp-bounces@ietf.org] On Behalf Of Wojciech Dec (wdec)
				Sent: 20 April 2008 14:39
				To: Peter Arberg; ancp@ietf.org
				Subject: Re: [ANCP] Bulk Transaction
Message

				It's all simple:

				- the Design Team is looking at the
possibility of using this message

				- the message in its current form does
not appear to be terribly useful, and could be removed from the spec.

				=20

				-Woj.

				=20

				=20

			=09
________________________________


				From: ancp-bounces@ietf.org
[mailto:ancp-bounces@ietf.org] On Behalf Of Peter Arberg
				Sent: 19 April 2008 03:07
				To: Wojciech Dec (wdec); ancp@ietf.org
				Subject: Re: [ANCP] Bulk Transaction
Message

				Hi Woj,

				=20

				can you give a little background to why
you are looking for vendor

				implementation support for this specific
capability & message ?

				=20

				thanks,

				Peter

				=20

			=09
________________________________


				From: ancp-bounces@ietf.org
[mailto:ancp-bounces@ietf.org] On Behalf Of Wojciech Dec (wdec)
				Sent: 18. april 2008 08:04
				To: ancp@ietf.org
				Subject: [ANCP] Bulk Transaction Message

				Hi Folks,=20

				Could you please let me/us know if you
currently have an implementation of ANCP that supports the Bulk
Transaction Capability and Message?

				Thanks,=20
				Woj.=20


------_=_NextPart_001_01C8B0F7.8A4F0F5C
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:st1 =3D=20
"urn:schemas-microsoft-com:office:smarttags"><HEAD><TITLE>Bulk =
Transaction Message</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3314" name=3DGENERATOR><!--[if !mso]>
<STYLE>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</STYLE>
<![endif]--><o:SmartTagType name=3D"PersonName"=20
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"></o:SmartTagT=
ype><!--[if !mso]>
<STYLE>
st1\:*{behavior:url(#default#ieooui) }
</STYLE>
<![endif]-->
<STYLE>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p
	{mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman";}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:Arial;
	color:navy;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</STYLE>
</HEAD>
<BODY lang=3DEN-US vLink=3Dpurple link=3Dblue>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D913434216-07052008><FONT =
face=3DArial=20
size=3D2>Sanjay,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D913434216-07052008><FONT =
face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D913434216-07052008><FONT =
face=3DArial=20
size=3D2>(chair hat on)&nbsp;re-hashing arguments already made isn't =
going to=20
resolve this.&nbsp;In essence, there appears to be&nbsp;no clear and =
sound=20
technical justification/use presented for the existence of this totally=20
*distinct*&nbsp;functionality, as opposed to a by-product of&nbsp;an =
other=20
one,&nbsp;whose sole purpose is&nbsp;</FONT></SPAN><SPAN=20
class=3D913434216-07052008><FONT face=3DArial size=3D2>to&nbsp;ferry =
other already=20
fully formed messages that do not require another layer of message =
delineation=20
in TCP.&nbsp;There also isn't any substantial support in the WG for =
keeping it=20
in the spec, but rather the contrary (see earlier responses on the =
thread).=20
Justifying its presence as a place holder&nbsp;for something&nbsp;quite=20
different (eg "cumulative ACK" optimization) that is =
yet&nbsp;to&nbsp;come in=20
the future is undesirable, and equally so is keeping it on as "optional" =

material in the protocol that happens to be of little practical use, if=20
any.&nbsp;One possible original justification has gone away&nbsp;since =
it became=20
clear that the WG would not be adopting other transports for =
ANCP&nbsp;than TCP=20
(or equivalent) for the time being.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D913434216-07052008><FONT =
face=3DArial=20
size=3D2>As stated previously *you or anyone else* are&nbsp;welcome =
(expected?) to=20
put forward to the WG a detailed proposal describing "cumulative =
ACKs"&nbsp;for=20
acceptance in place of the Bulk Transaction.&nbsp;Other than this, since =

you&nbsp;continue to believe firmly in the ANCP Bulk =
Transaction&nbsp;Mechanism=20
as is, then what&nbsp;we can offer is to welcome it back in the ANCP WG =
as an=20
individual contribution draft, and&nbsp;have another discussion round at =
getting=20
WG support for it. Till then, and in view of trying to get the spec into =
shape=20
for finishing it, please accept the fact that the text is to be either=20
removed&nbsp;from the WG draft-ietf-ancp-protocol spec by its next 03 =
revision,=20
or be supplanted by a WG accepted cumulative ack proposal. =
</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D913434216-07052008><FONT =
face=3DArial=20
size=3D2>There appears to be little reason&nbsp;in dragging this =
discussion out=20
any further, however if anything here still&nbsp;isn't clear then&nbsp;I =

do&nbsp;suggest a private forum for clarifying.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D913434216-07052008><FONT =
size=3D2><FONT=20
face=3DArial></FONT></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D913434216-07052008><FONT =
size=3D2><FONT=20
face=3DArial>Regards,</FONT></FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D913434216-07052008><FONT =
size=3D2><FONT=20
face=3DArial>Woj.</FONT></DIV></FONT></SPAN><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Sanjay Wadhwa=20
  [mailto:swadhwa@juniper.net] <BR><B>Sent:</B> 07 May 2008 =
18:07<BR><B>To:</B>=20
  Wojciech Dec (wdec); Peter Arberg; ancp@ietf.org<BR><B>Subject:</B> =
RE: [ANCP]=20
  Bulk Transaction Message<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV class=3DSection1>
  <P class=3DMsoNormal><B><FONT face=3DArial color=3D#333399 =
size=3D2><SPAN=20
  style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: #333399; =
FONT-FAMILY: Arial">Inline=20
  again</SPAN></FONT></B><B><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
  style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: #993366; =
FONT-FAMILY: Arial">=20
  </SPAN></FONT></B><B><FONT face=3DArial color=3D#333399 size=3D2><SPAN =

  style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: #333399; =
FONT-FAMILY: Arial">[SW2]<o:p></o:p></SPAN></FONT></B></P>
  <P class=3DMsoNormal><B><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
  style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: #993366; =
FONT-FAMILY: Arial"><o:p>&nbsp;</o:p></SPAN></FONT></B></P>
  <P class=3DMsoNormal><B><FONT face=3DArial color=3D#333399 =
size=3D2><SPAN=20
  style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: #333399; =
FONT-FAMILY: Arial">-Sanjay</SPAN></FONT></B><FONT=20
  face=3DArial color=3D#333399 size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: #333399; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <DIV>
  <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
  face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
  <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
  </SPAN></FONT></DIV>
  <P class=3DMsoNormal><B><FONT face=3DTahoma size=3D2><SPAN=20
  style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
  face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">=20
  Wojciech Dec (wdec) [mailto:wdec@cisco.com] <BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Wednesday, May 07, 2008 =
10:47=20
  AM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Wojciech Dec =
(wdec);=20
  Sanjay Wadhwa; Peter Arberg; ancp@ietf.org<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [ANCP] Bulk =
Transaction=20
  Message</SPAN></FONT><o:p></o:p></P></DIV>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Should have added:=20
  Plea<st1:PersonName w:st=3D"on">se</st1:PersonName> feel free to put =
forward a=20
  bulk ack proposal to the WG. Just axe the existing bulking text before =
someone=20
  goes starts thinking of actually adopting =
it.</SPAN></FONT><o:p></o:p></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">-Woj.</SPAN></FONT><o:p></o:p></P>
  <BLOCKQUOTE=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: 5pt 0in 5pt =
3.75pt; BORDER-LEFT: black 1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none">
    <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
    style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
    <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
    face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
    <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
    </SPAN></FONT></DIV>
    <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><B><FONT =
face=3DTahoma=20
    size=3D2><SPAN=20
    style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
    face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">=20
    ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] <B><SPAN=20
    style=3D"FONT-WEIGHT: bold">On Behalf Of </SPAN></B>Wojciech Dec=20
    (wdec)<BR><B><SPAN style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> 07 =
May 2008=20
    16:27<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Sanjay =
Wadhwa;=20
    Peter Arberg; ancp@ietf.org<BR><B><SPAN=20
    style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> Re: [ANCP] Bulk =
Transaction=20
    Message</SPAN></FONT><o:p></o:p></P>
    <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Sanjay,</SPAN></FONT><o:p></o:p></P>
    <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
    style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">inline=20
    woj#2&gt;</SPAN></FONT><o:p></o:p></P>
    <BLOCKQUOTE=20
    style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: 5pt 0in 5pt =
3.75pt; BORDER-LEFT: black 1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none">
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =

      style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
      <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
      face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
      <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
      </SPAN></FONT></DIV>
      <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><B><FONT =
face=3DTahoma=20
      size=3D2><SPAN=20
      style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
      face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Tahoma">=20
      Sanjay Wadhwa [mailto:swadhwa@juniper.net] <BR><B><SPAN=20
      style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> 07 May 2008 =
16:02<BR><B><SPAN=20
      style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Wojciech Dec (wdec); =
Peter=20
      Arberg; ancp@ietf.org<BR><B><SPAN=20
      style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [ANCP] Bulk =
Transaction=20
      Message</SPAN></FONT><o:p></o:p></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: =
Arial">Woj<o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: =
Arial">&nbsp; Inline=20
      [SW].<o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
      <DIV>
      <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
      face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
      <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
      </SPAN></FONT></DIV>
      <P class=3DMsoNormal><B><FONT face=3DTahoma size=3D2><SPAN=20
      style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
      face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Tahoma">=20
      Wojciech Dec (wdec) [mailto:wdec@cisco.com] <BR><B><SPAN=20
      style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Wednesday, May 07, =
2008 3:32=20
      AM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Sanjay =
Wadhwa;=20
      Peter Arberg; ancp@ietf.org<BR><B><SPAN=20
      style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [ANCP] Bulk =
Transaction=20
      Message</SPAN></FONT><o:p></o:p></P></DIV>
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =

      style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Sanjay,</SPAN></FONT><o:p></o:p></P>
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN =

      style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">inline</SPAN></FONT><o:p></o:p></P>
      <BLOCKQUOTE=20
      style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; =
BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: =
5pt 0in 5pt 3.75pt; BORDER-LEFT: black 1.5pt solid; PADDING-TOP: 0in; =
BORDER-BOTTOM: medium none">
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
        style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
        <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
        face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: =
12pt">
        <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
        </SPAN></FONT></DIV>
        <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><B><FONT =
face=3DTahoma=20
        size=3D2><SPAN=20
        style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
        face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; =
FONT-FAMILY: Tahoma">=20
        Sanjay Wadhwa [mailto:swadhwa@juniper.net] <BR><B><SPAN=20
        style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> 07 May 2008 =
02:03<BR><B><SPAN=20
        style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Wojciech Dec (wdec); =
Peter=20
        Arberg; ancp@ietf.org<BR><B><SPAN=20
        style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [ANCP] Bulk=20
        Transaction Message</SPAN></FONT><o:p></o:p></P>
        <DIV>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">Even =
with=20
        transport being TCP, I <st1:PersonName =
w:st=3D"on">se</st1:PersonName>e=20
        atleast a couple of benefits:</SPAN></FONT><o:p></o:p></P></DIV>
        <DIV>
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
        style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
        <DIV>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">1. If =

        a&nbsp;<st1:PersonName w:st=3D"on">se</st1:PersonName>nder knows =
it has a=20
        bunch of messages to <st1:PersonName =
w:st=3D"on">se</st1:PersonName>nd=20
        (e.g. ANCP adjacency flaps, and all the port-up messages need to =

        re-played), then bulking by definition&nbsp;allows the =
application to=20
        invoke TCP fewer times to transmit&nbsp;everything that it needs =
to=20
        transmit, which&nbsp;in a lot of systems can translate to=20
        significant&nbsp;compute and memory efficiency (specially, if we =
are=20
        considering a large amount of state). This&nbsp;is not to say =
one=20
        can't&nbsp;realize this&nbsp;in an implementation specific=20
        way.&nbsp;</SPAN></FONT><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><o:p></o:p></P></DIV>
        <DIV>
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
        style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
        <DIV>
        <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Woj&gt; Even with =
bulking=20
        one needs to realize the TCP interaction with some thought. =
Perhaps=20
        bulking indeed&nbsp;offers the opportunity for a delveloper to =
think=20
        about that, but I <st1:PersonName =
w:st=3D"on">se</st1:PersonName>riously=20
        doubt that anyone familar with TCP app development&nbsp;would =
overlook=20
        this aspect in the first place.<o:p></o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: =
Arial">[[SW]] I=20
        would like to believe it. History doesn&#8217;t bear this=20
        though.</SPAN></FONT><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><o:p></o:p></P>
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
        style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Woj#2&gt;&nbsp;Unless=20
        the spec forces Bulking to be u<st1:PersonName=20
        w:st=3D"on">se</st1:PersonName>d for every single multi-message =
exchange,=20
        the bunching effect will not appear, nor will any=20
        optimization.</SPAN></FONT><o:p></o:p></P></DIV>
        <DIV>
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
        style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
        <DIV>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">However,&nbsp;</SPAN></FONT><B><FONT=20
        face=3DArial color=3Dred size=3D2><SPAN=20
        style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: red; =
FONT-FAMILY: Arial">if=20
        neeeded</SPAN></FONT></B><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">, =
bulking=20
        also&nbsp;has the benefit of affording optimized acking (e.g. if =
no=20
        error is encountered in proccessing all the sub-messages in the =
bundled=20
        message, it&nbsp;is possible&nbsp;for the receiver to =
<st1:PersonName=20
        w:st=3D"on">se</st1:PersonName>nd a cummulative ack to the =
<st1:PersonName=20
        w:st=3D"on">se</st1:PersonName>nder rather than individual=20
        acks).</SPAN></FONT><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><o:p></o:p></P></DIV>
        <DIV>
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
        style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
        <DIV>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Woj&gt;&nbsp;A=20
        cumulatitive ack would appear to be desirable in some =
ca<st1:PersonName=20
        w:st=3D"on">se</st1:PersonName>s, but I <st1:PersonName=20
        w:st=3D"on">se</st1:PersonName>e this as very&nbsp;different to=20
        the&nbsp;bulk ack currently described which es<st1:PersonName=20
        w:st=3D"on">se</st1:PersonName>natially carries in bulk all of =
the=20
        individal acks.&nbsp;The bulking mechanism is quite clear in =
saying that=20
        each ANCP message is&nbsp;bundled header and all, and acted upon =

        individually by the recipient, and whether it's a request or an =
ack is=20
        <st1:PersonName w:st=3D"on">se</st1:PersonName>condary. I'm sure =
you'll=20
        agree that this is undesirable overhead and complexity for what =
it's=20
        worth, also in view of the fact that "something" on the =
recipient side=20
        would need to decide what ack/nack goes into a bulk=20
        respon<st1:PersonName w:st=3D"on">se</st1:PersonName> and what =
doesn't.=20
        </SPAN></FONT><o:p></o:p></P></DIV>
        <DIV>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Having a=20
        cumulatitive ack is an all thogether different thing, which I=20
        would&nbsp;support, and it should not involve the "bulking" of =
each=20
        indivdual ack, and is an item that&nbsp;for which&nbsp;proposals =
are=20
        welcome.</SPAN></FONT><FONT face=3DArial size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: =
Arial">[[SW]]=20
        Sorry, I should have been clearer. Bulking adds an overall =
header for=20
        the individual messages being bulked. If all the messages =
succeed, we=20
        can define the behavior to <st1:PersonName=20
        w:st=3D"on">se</st1:PersonName>nd a single ACK (NOT a bulk ACK=20
        compo<st1:PersonName w:st=3D"on">se</st1:PersonName>d of =
individual=20
        sub-messages carrying ACK) with the transaction-ID of the main =
header=20
        reflected back in the ACK. &nbsp;This provides an elegant way to =
address=20
        cumulative ACK. This is not defined in the draft today =
(<st1:PersonName=20
        w:st=3D"on">se</st1:PersonName>e &#8220;if needed&#8221; above), =
but is easily=20
        provided by bulking, and can be added if we=20
        agree.<o:p></o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: =
Arial">Far as=20
        request message is concerned, having individual messages (with =
their own=20
        header) in the request reduces complexity, provides a way to =
bulk=20
        messages of different types if needed. It allows each =
sub-message to be=20
        individually NACK&#8217;d where required. Bulking in such a way =
allows the=20
        flexibility of treating individual sub-messages as completely=20
        independent or related.</SPAN></FONT><FONT face=3DArial =
color=3Dblack=20
        size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><o:p></o:p></P>
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
        style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Woj#2&gt; The=20
        above, in principle is fine, BUT it is far removed from the =
current=20
        bulking mechanism. The order would be to have a proposal =
regarding=20
        this&nbsp;on its own right.&nbsp;</SPAN></FONT><FONT =
face=3DArial=20
        color=3Dnavy size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><B><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
        style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: navy; =
FONT-FAMILY: Arial">[[SW2]]=20
        It can easily be extended and doesn&#8217;t need to be done =
right away.=20
        Rehashing (new proposal) when you have the basis for in the =
draft is not=20
        justifiable.</SPAN></FONT></B><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></P></DIV>
        <DIV>
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
        style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
        <DIV>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">2. =
Bulking also=20
        provides a nice solution if one&nbsp;ever needed to atomically =
receive=20
        and process *distinct* ANCP message =
types.&nbsp;</SPAN></FONT><FONT=20
        face=3DArial color=3Dblack size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><FONT=20
        face=3DArial color=3Dnavy size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><B><I><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
        style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: navy; =
FONT-STYLE: italic; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></I></B></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Woj&gt;&nbsp;There=20
        appears to be no such thing; </SPAN></FONT><FONT face=3DArial =
color=3Dnavy=20
        size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: =
Arial">[[SW]]=20
        Today, but as you mentioned in another thread, we need to design =
the=20
        protocol to be generic in anticipation of such=20
        requirements.</SPAN></FONT><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><o:p></o:p></P>
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
        style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Woj#2&gt; What=20
        tentative requirements are you referring to, =
a&nbsp;relay?&nbsp;If=20
        so,&nbsp;bulking doesn't help there. This is also much different =
from a=20
        discussion about a generic TLV format that is to be =
u<st1:PersonName=20
        w:st=3D"on">se</st1:PersonName>d by the=20
        protocol.</SPAN></FONT><o:p></o:p></P>
        <P class=3DMsoNormal><B><I><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
        style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: navy; =
FONT-STYLE: italic; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></I></B></P>
        <P class=3DMsoNormal><B><I><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
        style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: navy; =
FONT-STYLE: italic; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></I></B></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">in =
bulking,=20
        presumably the reciever would have to buffer all the way until =
the end=20
        of the bulk message, and then process each message individually. =
This=20
        <st1:PersonName w:st=3D"on">se</st1:PersonName>ems rather =
overweight when=20
        compared to simply <st1:PersonName =
w:st=3D"on">se</st1:PersonName>nding=20
        each message again.</SPAN></FONT><FONT face=3DArial color=3Dnavy =

        size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: =
Arial">[[SW]] Draft=20
        doesn&#8217;t impo<st1:PersonName =
w:st=3D"on">se</st1:PersonName> on how much=20
        you bulk. If atomicity in handling of bulked messages is =
warranted by a=20
        u<st1:PersonName =
w:st=3D"on">se</st1:PersonName>-ca<st1:PersonName=20
        w:st=3D"on">se</st1:PersonName>, then yes you want to get the =
entire=20
        message. If not, you could presumably process as you receive =
each=20
        complete sub-message within the bundle.</SPAN></FONT><FONT =
face=3DArial=20
        color=3Dblack size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><o:p></o:p></P>
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
        style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Woj#2&gt;=20
        Adding a single bulk envelope and <st1:PersonName=20
        w:st=3D"on">se</st1:PersonName>nding inside it&nbsp;100 messages =
vs 2 bulk=20
        envelopes with 50 messages is also pretty pointless, and an=20
        exerci<st1:PersonName w:st=3D"on">se</st1:PersonName> in =
optimizing=20
        something that isn't needed in the first place: In each=20
        ca<st1:PersonName w:st=3D"on">se</st1:PersonName> you're still=20
        <st1:PersonName w:st=3D"on">se</st1:PersonName>nding 100 =
messages! The=20
        downside is that in either of the bulked messages =
ca<st1:PersonName=20
        w:st=3D"on">se</st1:PersonName> you generally will have to wait =
till the=20
        full message is received. There are betterTCP access =
</SPAN></FONT><FONT=20
        face=3DArial size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><B><I><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
        style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: navy; =
FONT-STYLE: italic; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></I></B></P>
        <P class=3DMsoNormal><B><I><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
        style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: navy; =
FONT-STYLE: italic; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT></I></B><B><FONT=20
        face=3DArial color=3Dnavy size=3D2><SPAN=20
        style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: navy; =
FONT-FAMILY: Arial">[[SW2]]=20
        Sorry to repeat. If you need atomicity for the sub-messages in =
the=20
        bundle, then you need to wait. If not then you don&#8217;t have =
to. This is=20
        providing you the flexibility, which you don&#8217;t easily have =
with=20
        individual messages (e.g atomic handling is hard to realize with =

        individual messages).</SPAN></FONT></B><FONT face=3DArial =
color=3Dnavy=20
        size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></P></DIV>
        <DIV>
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
        style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
        <DIV>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">What =
is the=20
        downside of having it? It is&nbsp;negotiable as an optional=20
        capability.</SPAN></FONT><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><o:p></o:p></P></DIV>
        <DIV>
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
        style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
        <DIV>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Woj&gt; A=20
        couple of reasons come to the fore; i) no body saw a good reason =
so far=20
        to implement it/u<st1:PersonName w:st=3D"on">se</st1:PersonName> =
it ii)=20
        it's added protocol "stuff" that has no clear benefit, does not =
realize=20
        any new u<st1:PersonName =
w:st=3D"on">se</st1:PersonName>-ca<st1:PersonName=20
        w:st=3D"on">se</st1:PersonName>,&nbsp;does not optimize much, =
and in fact=20
        as mentioned above it appears to rather have some downsides such =
as=20
        extra overhead, buffering and delay.</SPAN></FONT><B><I><FONT =
face=3DArial=20
        color=3Dnavy size=3D2><SPAN=20
        style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: navy; =
FONT-STYLE: italic; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></I></B></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Let's now have=20
        the axe fall...</SPAN></FONT><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: =
Arial">[[SW]] Let=20
        us plea<st1:PersonName w:st=3D"on">se</st1:PersonName> not be =
dismissive=20
        towards something that has benefits (as outlined=20
        above).</SPAN></FONT><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">&nbsp;</SPAN></FONT><o:p></o:p></P>
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
        style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Wo#2j&gt;=20
        &nbsp;With the exception of cumulative ack, which does =
de<st1:PersonName=20
        w:st=3D"on">se</st1:PersonName>rve a standalone proposal to be =
put=20
        forward, neither me nor&nbsp;other members of the&nbsp;WG =
do&nbsp;appear=20
        to share the views regarding the purported benefits on bulking, =
nor a=20
        desire to retain it in the spec.&nbsp;</SPAN></FONT><FONT =
face=3DArial=20
        color=3Dnavy size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><B><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
        style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: navy; =
FONT-FAMILY: Arial">[[SW2]]=20
        See above. This has been in the draft for a while, and I have =
not=20
        <st1:PersonName w:st=3D"on">se</st1:PersonName>en any technical =
arguments=20
        from anyone el<st1:PersonName w:st=3D"on">se</st1:PersonName> on =
removing=20
        it from the draft. I have clearly outlined the benefits above, =
and don&#8217;t=20
        <st1:PersonName w:st=3D"on">se</st1:PersonName>e convincing =
technical=20
        reasons for this to go. </SPAN></FONT></B><FONT face=3DArial =
color=3Dnavy=20
        size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p></o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><B><I><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
        style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: navy; =
FONT-STYLE: italic; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></I></B></P>
        <P class=3DMsoNormal><B><I><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
        style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: navy; =
FONT-STYLE: italic; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></I></B></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Sorry, it just=20
        needs to go.</SPAN></FONT><o:p></o:p></P>
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
        style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><B><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
        style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: navy; =
FONT-FAMILY: Arial">[[SW2]]=20
        Is this with your chair hat on or as an individual WG member?=20
        <o:p></o:p></SPAN></FONT></B></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Cheers,</SPAN></FONT><o:p></o:p></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblack =
size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: =
Arial">Woj.</SPAN></FONT><o:p></o:p></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: =
Arial">Cheers<o:p></o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3D#993366 =
size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: =
Arial">-Sanjay<o:p></o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P></DIV>
        <DIV>
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
        style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
        <DIV>
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
        style=3D"FONT-SIZE: =
12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P></DIV>
        <BLOCKQUOTE=20
        style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; =
BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: =
5pt 0in 5pt 3.75pt; BORDER-LEFT: blue 1.5pt solid; PADDING-TOP: 0in; =
BORDER-BOTTOM: medium none">
          <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><FONT =
face=3DTahoma=20
          size=3D2><SPAN=20
          style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">-----Original=20
          Message-----<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">From:</SPAN></B>=20
          Wojciech Dec (wdec) [mailto:wdec@cisco.com]<BR><B><SPAN=20
          style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Tuesday, May 06, =
2008 1:24=20
          PM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> =
Sanjay Wadhwa;=20
          Peter Arberg; ancp@ietf.org<BR><B><SPAN=20
          style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [ANCP] =
Bulk=20
          Transaction Message</SPAN></FONT><o:p></o:p></P>
          <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
          style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Sanjay,</SPAN></FONT><o:p></o:p></P>
          <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
          style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
          <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
          style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">can you=20
          plea<st1:PersonName w:st=3D"on">se</st1:PersonName> =
pre<st1:PersonName=20
          w:st=3D"on">se</st1:PersonName>nt to the WG and =
my<st1:PersonName=20
          w:st=3D"on">se</st1:PersonName>lf how bulk transaction =
capability is=20
          u<st1:PersonName w:st=3D"on">se</st1:PersonName>ful in any way =
in terms=20
          of scaling for example? And by the way, plea<st1:PersonName=20
          w:st=3D"on">se</st1:PersonName> treat this discussion is =
orthogonal to=20
          any other.</SPAN></FONT><o:p></o:p></P>
          <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
          style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
          <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
          style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Cheers,</SPAN></FONT><o:p></o:p></P>
          <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
          style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Woj.</SPAN></FONT><o:p></o:p></P>
          <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
          style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
          <BLOCKQUOTE=20
          style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; =
BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: =
5pt 0in 5pt 3.75pt; BORDER-LEFT: black 1.5pt solid; PADDING-TOP: 0in; =
BORDER-BOTTOM: medium none">
            <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
            style=3D"FONT-SIZE: =
12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
            <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
            face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: =
12pt">
            <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
            </SPAN></FONT></DIV>
            <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><B><FONT =
face=3DTahoma=20
            size=3D2><SPAN=20
            style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">From:</SPAN></FONT></B><FONT=20
            face=3DTahoma size=3D2><SPAN=20
            style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma"> Sanjay =
Wadhwa=20
            [mailto:swadhwa@juniper.net] <BR><B><SPAN=20
            style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> 06 May 2008=20
            19:08<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> =
Wojciech=20
            Dec (wdec); Peter Arberg; ancp@ietf.org<BR><B><SPAN=20
            style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [ANCP] =
Bulk=20
            Transaction Message</SPAN></FONT><o:p></o:p></P>
            <DIV>
            <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
            style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Woj</SPAN></FONT><o:p></o:p></P></DIV>
            <DIV>
            <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
            style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">&nbsp; It=20
            is a bad idea to remove bulk-transaction capability from the =
draft.=20
            On one hand you are trying to add "marginally =
u<st1:PersonName=20
            w:st=3D"on">se</st1:PersonName>ful" extensions (with TLVs), =
and on the=20
            other hand you are arguing for removing u<st1:PersonName=20
            w:st=3D"on">se</st1:PersonName>ful abstractions which can =
help with=20
            scaling. If bulk-transaction capability needs to be =
augmented or=20
            modified, then we should consider augmenting it, rather than =

            removing it from the =
draft.</SPAN></FONT><o:p></o:p></P></DIV>
            <DIV>
            <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
            style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
            <DIV>
            <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
            style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Cheers</SPAN></FONT><o:p></o:p></P></DIV>
            <DIV>
            <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
            style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">-Sanjay</SPAN></FONT><o:p></o:p></P></DIV>
            <BLOCKQUOTE=20
            style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; =
BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: =
5pt 0in 5pt 3.75pt; BORDER-LEFT: blue 1.5pt solid; PADDING-TOP: 0in; =
BORDER-BOTTOM: medium none">
              <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><FONT =
face=3DTahoma=20
              size=3D2><SPAN=20
              style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Tahoma">-----Original=20
              Message-----<BR><B><SPAN=20
              style=3D"FONT-WEIGHT: bold">From:</SPAN></B> =
ancp-bounces@ietf.org=20
              [mailto:ancp-bounces@ietf.org]<B><SPAN=20
              style=3D"FONT-WEIGHT: bold">On Behalf Of =
</SPAN></B>Wojciech Dec=20
              (wdec)<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">Sent:</SPAN></B>=20
              Tuesday, May 06, 2008 12:42 PM<BR><B><SPAN=20
              style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Peter Arberg;=20
              ancp@ietf.org<BR><B><SPAN=20
              style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> Re: [ANCP] =
Bulk=20
              Transaction Message</SPAN></FONT><o:p></o:p></P>
              <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
              style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Hi=20
              Folks,</SPAN></FONT><o:p></o:p></P>
              <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
              style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
              <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
              style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">given that =
no=20
              discernable u<st1:PersonName =
w:st=3D"on">se</st1:PersonName> of Bulk=20
              messaging has been identified, nor&nbsp;there being a good =
reason=20
              for it given the fact that ANCP is bound to the TCP =
transport (or=20
              equivalent),&nbsp;I would like to propo<st1:PersonName=20
              w:st=3D"on">se</st1:PersonName> to remove all of the text =
relating=20
              to this capability and associated message from the =
protocol spec=20
              draft.</SPAN></FONT><o:p></o:p></P>
              <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
              style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
              <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
              style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Regards,</SPAN></FONT><o:p></o:p></P>
              <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
              style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Woj.</SPAN></FONT><o:p></o:p></P>
              <BLOCKQUOTE=20
              style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; =
BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: =
5pt 0in 5pt 3.75pt; BORDER-LEFT: black 1.5pt solid; PADDING-TOP: 0in; =
BORDER-BOTTOM: medium none">
                <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                style=3D"FONT-SIZE: =
12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
                <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center"=20
                align=3Dcenter><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                style=3D"FONT-SIZE: 12pt">
                <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" =
SIZE=3D2>
                </SPAN></FONT></DIV>
                <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: =
12pt"><B><FONT=20
                face=3DTahoma size=3D2><SPAN=20
                style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; =
FONT-FAMILY: Tahoma">From:</SPAN></FONT></B><FONT=20
                face=3DTahoma size=3D2><SPAN=20
                style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">=20
                ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] =
<B><SPAN=20
                style=3D"FONT-WEIGHT: bold">On Behalf Of =
</SPAN></B>Wojciech Dec=20
                (wdec)<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">Sent:</SPAN></B> 20=20
                April 2008 15:18<BR><B><SPAN=20
                style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Peter Arberg; =

                ancp@ietf.org<BR><B><SPAN=20
                style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> Re: =
[ANCP] Bulk=20
                Transaction Message</SPAN></FONT><o:p></o:p></P>
                <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
                style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Should =
also have=20
                added: Given that currently&nbsp;the bulk message does =
not=20
                appear to have had any practical&nbsp;adoption, having =
the DTeam=20
                adopt it/modify it, or possibly have it removed from the =
spec=20
                all together&nbsp;are all valid=20
                options.</SPAN></FONT><o:p></o:p></P>
                <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
                <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
                style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">-Woj.</SPAN></FONT><o:p></o:p></P>
                <BLOCKQUOTE=20
                style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; =
BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: =
5pt 0in 5pt 3.75pt; BORDER-LEFT: black 1.5pt solid; PADDING-TOP: 0in; =
BORDER-BOTTOM: medium none">
                  <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                  style=3D"FONT-SIZE: =
12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
                  <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center"=20
                  align=3Dcenter><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                  style=3D"FONT-SIZE: 12pt">
                  <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" =
SIZE=3D2>
                  </SPAN></FONT></DIV>
                  <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: =
12pt"><B><FONT=20
                  face=3DTahoma size=3D2><SPAN=20
                  style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; =
FONT-FAMILY: Tahoma">From:</SPAN></FONT></B><FONT=20
                  face=3DTahoma size=3D2><SPAN=20
                  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">=20
                  ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] =
<B><SPAN=20
                  style=3D"FONT-WEIGHT: bold">On Behalf Of =
</SPAN></B>Wojciech Dec=20
                  (wdec)<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">Sent:</SPAN></B>=20
                  20 April 2008 14:39<BR><B><SPAN=20
                  style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Peter =
Arberg;=20
                  ancp@ietf.org<BR><B><SPAN=20
                  style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> Re: =
[ANCP] Bulk=20
                  Transaction Message</SPAN></FONT><o:p></o:p></P>
                  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =

                  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">It's all =

                  simple:</SPAN></FONT><o:p></o:p></P>
                  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =

                  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">-&nbsp;the Design=20
                  Team is looking at the possibility of using this=20
                  message</SPAN></FONT><o:p></o:p></P>
                  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =

                  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">- the =
message in=20
                  its current form does not appear to be terribly=20
                  u<st1:PersonName w:st=3D"on">se</st1:PersonName>ful, =
and could=20
                  be&nbsp;removed from the =
spec.</SPAN></FONT><o:p></o:p></P>
                  <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                  style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
                  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN =

                  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">-Woj.</SPAN></FONT><o:p></o:p></P>
                  <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                  style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
                  <BLOCKQUOTE=20
                  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: =
0in; BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; =
MARGIN: 5pt 0in 5pt 3.75pt; BORDER-LEFT: black 1.5pt solid; PADDING-TOP: =
0in; BORDER-BOTTOM: medium none">
                    <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                    style=3D"FONT-SIZE: =
12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
                    <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center"=20
                    align=3Dcenter><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                    style=3D"FONT-SIZE: 12pt">
                    <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" =
SIZE=3D2>
                    </SPAN></FONT></DIV>
                    <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: =
12pt"><B><FONT=20
                    face=3DTahoma size=3D2><SPAN=20
                    style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; =
FONT-FAMILY: Tahoma">From:</SPAN></FONT></B><FONT=20
                    face=3DTahoma size=3D2><SPAN=20
                    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">=20
                    ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] =

                    <B><SPAN style=3D"FONT-WEIGHT: bold">On Behalf Of=20
                    </SPAN></B>Peter Arberg<BR><B><SPAN=20
                    style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> 19 =
April 2008=20
                    03:07<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">To:</SPAN></B>=20
                    Wojciech Dec (wdec); ancp@ietf.org<BR><B><SPAN=20
                    style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> Re: =
[ANCP]=20
                    Bulk Transaction =
Message</SPAN></FONT><o:p></o:p></P>
                    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
                    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Hi=20
                    Woj,</SPAN></FONT><o:p></o:p></P>
                    <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                    style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
                    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
                    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">can=20
                    you give a little background to why you are looking =
for=20
                    vendor</SPAN></FONT><o:p></o:p></P>
                    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
                    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">implementation=20
                    support for this specific capability &amp; message=20
                    ?</SPAN></FONT><o:p></o:p></P>
                    <P class=3DMsoNormal><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                    style=3D"FONT-SIZE: =
12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
                    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
                    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">thanks,</SPAN></FONT><o:p></o:p></P>
                    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue =
size=3D2><SPAN=20
                    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: =
Arial">Peter</SPAN></FONT><o:p></o:p></P>
                    <BLOCKQUOTE=20
                    style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: =
0in; BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; =
MARGIN: 5pt 0in 5pt 3.75pt; BORDER-LEFT: blue 1.5pt solid; PADDING-TOP: =
0in; BORDER-BOTTOM: medium none">
                      <P class=3DMsoNormal><FONT face=3D"Times New =
Roman"=20
                      size=3D3><SPAN=20
                      style=3D"FONT-SIZE: =
12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
                      <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: =
center"=20
                      align=3Dcenter><FONT face=3D"Times New Roman" =
size=3D3><SPAN=20
                      style=3D"FONT-SIZE: 12pt">
                      <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" =
SIZE=3D2>
                      </SPAN></FONT></DIV>
                      <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: =
12pt"><B><FONT=20
                      face=3DTahoma size=3D2><SPAN=20
                      style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; =
FONT-FAMILY: Tahoma">From:</SPAN></FONT></B><FONT=20
                      face=3DTahoma size=3D2><SPAN=20
                      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">=20
                      ancp-bounces@ietf.org =
[mailto:ancp-bounces@ietf.org]=20
                      <B><SPAN style=3D"FONT-WEIGHT: bold">On Behalf Of=20
                      </SPAN></B>Wojciech Dec (wdec)<BR><B><SPAN=20
                      style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> 18. =
april 2008=20
                      08:04<BR><B><SPAN style=3D"FONT-WEIGHT: =
bold">To:</SPAN></B>=20
                      ancp@ietf.org<BR><B><SPAN=20
                      style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> =
[ANCP] Bulk=20
                      Transaction Message</SPAN></FONT><o:p></o:p></P>
                      <P><FONT face=3DArial size=3D2><SPAN lang=3DEN-GB=20
                      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"><!-- =
Converted from text/rtf format -->Hi=20
                      Folks,</SPAN></FONT><SPAN lang=3DEN-GB>=20
                      </SPAN><o:p></o:p></P>
                      <P><FONT face=3DArial size=3D2><SPAN lang=3DEN-GB=20
                      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Could you=20
                      plea<st1:PersonName =
w:st=3D"on">se</st1:PersonName> let=20
                      me/us know if you currently have an implementation =
of ANCP=20
                      that supports the Bulk Transaction Capability and=20
                      Message?</SPAN></FONT><o:p></o:p></P>
                      <P><FONT face=3DArial size=3D2><SPAN lang=3DEN-GB=20
                      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Thanks,</SPAN></FONT>=20
                      <BR><FONT face=3DArial size=3D2><SPAN lang=3DEN-GB =

                      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Woj.</SPAN></FONT><SPAN=20
                      lang=3DEN-GB>=20
                =
</SPAN><o:p></o:p></P></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE=
></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCK=
QUOTE></DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C8B0F7.8A4F0F5C--

--===============0711124087==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============0711124087==--


From ancp-bounces@ietf.org  Thu May  8 16:17:02 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 734603A6F1A;
	Thu,  8 May 2008 16:17:02 -0700 (PDT)
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 27CAB3A6EE6
	for <ancp@core3.amsl.com>; Thu,  8 May 2008 16:17:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.402
X-Spam-Level: **
X-Spam-Status: No, score=2.402 tagged_above=-999 required=5 tests=[AWL=-5.000, 
	BAYES_00=-2.599, HTML_MESSAGE=0.001, J_BACKHAIR_12=1,
	J_BACKHAIR_21=1, 
	J_BACKHAIR_22=1, J_BACKHAIR_23=1, J_BACKHAIR_24=1, J_BACKHAIR_25=1,
	J_BACKHAIR_27=1, J_BACKHAIR_32=1, J_BACKHAIR_42=1, J_BACKHAIR_52=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 bUn29XFh7cnf for <ancp@core3.amsl.com>;
	Thu,  8 May 2008 16:16:44 -0700 (PDT)
Received: from prattle.redback.com (prattle.redback.com [155.53.12.9])
	by core3.amsl.com (Postfix) with ESMTP id 983523A6F16
	for <ancp@ietf.org>; Thu,  8 May 2008 16:16:43 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by prattle.redback.com (Postfix) with ESMTP id 2620E860CF9;
	Thu,  8 May 2008 16:16:42 -0700 (PDT)
Received: from prattle.redback.com ([127.0.0.1])
	by localhost (prattle [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
	id 28509-10; Thu,  8 May 2008 16:16:41 -0700 (PDT)
Received: from rbsjx.ad.redback.com (rbsjxh1.redback.com [155.53.14.105])
	by prattle.redback.com (Postfix) with ESMTP id DC7A5860CF8;
	Thu,  8 May 2008 16:16:41 -0700 (PDT)
Received: from RBSJX.ad.redback.com ([155.53.14.103]) by
	rbsjxh1.ad.redback.com ([155.53.14.105]) with mapi;
	Thu, 8 May 2008 16:16:41 -0700
From: Peter Arberg <parberg@redback.com>
To: DE CNODDER Stefaan <stefaan.de_cnodder@alcatel-lucent.be>,
	Sanjay Wadhwa <swadhwa@juniper.net>,
	"Wojciech Dec (wdec)" <wdec@cisco.com>, "ancp@ietf.org" <ancp@ietf.org>
Date: Thu, 8 May 2008 16:16:39 -0700
Thread-Topic: Re: [ANCP] Bulk Transaction Message
Thread-Index: AcihZWeDZVeOVtxMS1uttRBEffcNEwAVDjfgAEod1tAAAWRvoAMsB4yQAADCZxAAAKZHUAAJVuxQABJPrxAADmDeEAABcgAQAAFBHxAAAJXZIAAoMoKQABtqXCA=
Message-ID: <48C276B536524E478C659685995F6AA560439CC78B@RBSJX.ad.redback.com>
References: <D9872168DBD43A41BD71FFC4713274D405043771@xmb-ams-33b.emea.cisco.com><9BD5D7887235424FA97DFC223CAE3C280AB43A61@proton.jnpr.net><D9872168DBD43A41BD71FFC4713274D4050438A2@xmb-ams-33b.emea.cisco.com><9BD5D7887235424FA97DFC223CAE3C28105B8B41@proton.jnpr.net><D9872168DBD43A41BD71FFC4713274D405043C34@xmb-ams-33b.emea.cisco.com><D9872168DBD43A41BD71FFC4713274D405043C65@xmb-ams-33b.emea.cisco.com>
	<9BD5D7887235424FA97DFC223CAE3C28105B8C39@proton.jnpr.net>
	<7A6D4815C5E8F74988784FEBD50F2F1E01B8AE48@FRVELSMBS22.ad2.ad.alcatel.com>
In-Reply-To: <7A6D4815C5E8F74988784FEBD50F2F1E01B8AE48@FRVELSMBS22.ad2.ad.alcatel.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-Virus-Scanned: by amavisd-new at redback.com
Subject: Re: [ANCP] Bulk Transaction Message
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/pipermail/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>
Content-Type: multipart/mixed; boundary="===============1765829207=="
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org

--===============1765829207==
Content-Language: en-US
Content-Type: multipart/alternative;
	boundary="_000_48C276B536524E478C659685995F6AA560439CC78BRBSJXadredbac_"

--_000_48C276B536524E478C659685995F6AA560439CC78BRBSJXadredbac_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

I have to say as well that my comment to vote for removal of the Bulk is no=
t
because I do not see value in some optimization, it was for the reason I do
not want to see a non used item delay this draft.

I think we should remove non used items and move the draft forward as
soon as possible, and then open up for new contributions after the base ANC=
P
specifications have been accepted and documented as a rfc.

cheers,
Peter

________________________________
From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of DE =
CNODDER Stefaan
Sent: 8. maj 2008 12:18
To: Sanjay Wadhwa; Wojciech Dec (wdec); ancp@ietf.org
Subject: Re: [ANCP] Bulk Transaction Message

Hi Sanjay, Woj,

I see some advantages in having bulk messages to optimize ANCP.  However, b=
ulk messages are not the only solution.  It is wrong to discuss bulk messag=
es without comparing it with alternatives.  It looks like a good solution t=
o me but maybe there are better ways in optimizing ANCP.  So far the workin=
g group has not been working a lot on optimizations.  According to me, keep=
ing bulk messages in the base spec is wrong and it should be removed.  Peop=
le are invited to submit solutions to optimize ANCP in the form of a sepera=
te draft, and one such draft could be bulk messages.  Then when the working=
 group decides that it is time to work on optimalisations, the proposed sol=
utions can be compared and discussed.

regards,
Stefaan

________________________________
From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of San=
jay Wadhwa
Sent: woensdag 7 mei 2008 18:07
To: Wojciech Dec (wdec); Peter Arberg; ancp@ietf.org
Subject: Re: [ANCP] Bulk Transaction Message

Inline again [SW2]

-Sanjay

________________________________
From: Wojciech Dec (wdec) [mailto:wdec@cisco.com]
Sent: Wednesday, May 07, 2008 10:47 AM
To: Wojciech Dec (wdec); Sanjay Wadhwa; Peter Arberg; ancp@ietf.org
Subject: RE: [ANCP] Bulk Transaction Message

Should have added: Please feel free to put forward a bulk ack proposal to t=
he WG. Just axe the existing bulking text before someone goes starts thinki=
ng of actually adopting it.

-Woj.

________________________________
From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of Woj=
ciech Dec (wdec)
Sent: 07 May 2008 16:27
To: Sanjay Wadhwa; Peter Arberg; ancp@ietf.org
Subject: Re: [ANCP] Bulk Transaction Message
Sanjay,

inline woj#2>

________________________________
From: Sanjay Wadhwa [mailto:swadhwa@juniper.net]
Sent: 07 May 2008 16:02
To: Wojciech Dec (wdec); Peter Arberg; ancp@ietf.org
Subject: RE: [ANCP] Bulk Transaction Message
Woj
  Inline [SW].

________________________________
From: Wojciech Dec (wdec) [mailto:wdec@cisco.com]
Sent: Wednesday, May 07, 2008 3:32 AM
To: Sanjay Wadhwa; Peter Arberg; ancp@ietf.org
Subject: RE: [ANCP] Bulk Transaction Message

Sanjay,

inline

________________________________
From: Sanjay Wadhwa [mailto:swadhwa@juniper.net]
Sent: 07 May 2008 02:03
To: Wojciech Dec (wdec); Peter Arberg; ancp@ietf.org
Subject: RE: [ANCP] Bulk Transaction Message
Even with transport being TCP, I see atleast a couple of benefits:

1. If a sender knows it has a bunch of messages to send (e.g. ANCP adjacenc=
y flaps, and all the port-up messages need to re-played), then bulking by d=
efinition allows the application to invoke TCP fewer times to transmit ever=
ything that it needs to transmit, which in a lot of systems can translate t=
o significant compute and memory efficiency (specially, if we are consideri=
ng a large amount of state). This is not to say one can't realize this in a=
n implementation specific way.

Woj> Even with bulking one needs to realize the TCP interaction with some t=
hought. Perhaps bulking indeed offers the opportunity for a delveloper to t=
hink about that, but I seriously doubt that anyone familar with TCP app dev=
elopment would overlook this aspect in the first place.

[[SW]] I would like to believe it. History doesn't bear this though.

Woj#2> Unless the spec forces Bulking to be used for every single multi-mes=
sage exchange, the bunching effect will not appear, nor will any optimizati=
on.

However, if neeeded, bulking also has the benefit of affording optimized ac=
king (e.g. if no error is encountered in proccessing all the sub-messages i=
n the bundled message, it is possible for the receiver to send a cummulativ=
e ack to the sender rather than individual acks).

Woj> A cumulatitive ack would appear to be desirable in some cases, but I s=
ee this as very different to the bulk ack currently described which essenat=
ially carries in bulk all of the individal acks. The bulking mechanism is q=
uite clear in saying that each ANCP message is bundled header and all, and =
acted upon individually by the recipient, and whether it's a request or an =
ack is secondary. I'm sure you'll agree that this is undesirable overhead a=
nd complexity for what it's worth, also in view of the fact that "something=
" on the recipient side would need to decide what ack/nack goes into a bulk=
 response and what doesn't.
Having a cumulatitive ack is an all thogether different thing, which I woul=
d support, and it should not involve the "bulking" of each indivdual ack, a=
nd is an item that for which proposals are welcome.
[[SW]] Sorry, I should have been clearer. Bulking adds an overall header fo=
r the individual messages being bulked. If all the messages succeed, we can=
 define the behavior to send a single ACK (NOT a bulk ACK composed of indiv=
idual sub-messages carrying ACK) with the transaction-ID of the main header=
 reflected back in the ACK.  This provides an elegant way to address cumula=
tive ACK. This is not defined in the draft today (see "if needed" above), b=
ut is easily provided by bulking, and can be added if we agree.
Far as request message is concerned, having individual messages (with their=
 own header) in the request reduces complexity, provides a way to bulk mess=
ages of different types if needed. It allows each sub-message to be individ=
ually NACK'd where required. Bulking in such a way allows the flexibility o=
f treating individual sub-messages as completely independent or related.

Woj#2> The above, in principle is fine, BUT it is far removed from the curr=
ent bulking mechanism. The order would be to have a proposal regarding this=
 on its own right.

[[SW2]] It can easily be extended and doesn't need to be done right away. R=
ehashing (new proposal) when you have the basis for in the draft is not jus=
tifiable.

2. Bulking also provides a nice solution if one ever needed to atomically r=
eceive and process *distinct* ANCP message types.

Woj> There appears to be no such thing;
[[SW]] Today, but as you mentioned in another thread, we need to design the=
 protocol to be generic in anticipation of such requirements.

Woj#2> What tentative requirements are you referring to, a relay? If so, bu=
lking doesn't help there. This is also much different from a discussion abo=
ut a generic TLV format that is to be used by the protocol.


in bulking, presumably the reciever would have to buffer all the way until =
the end of the bulk message, and then process each message individually. Th=
is seems rather overweight when compared to simply sending each message aga=
in.
[[SW]] Draft doesn't impose on how much you bulk. If atomicity in handling =
of bulked messages is warranted by a use-case, then yes you want to get the=
 entire message. If not, you could presumably process as you receive each c=
omplete sub-message within the bundle.

Woj#2> Adding a single bulk envelope and sending inside it 100 messages vs =
2 bulk envelopes with 50 messages is also pretty pointless, and an exercise=
 in optimizing something that isn't needed in the first place: In each case=
 you're still sending 100 messages! The downside is that in either of the b=
ulked messages case you generally will have to wait till the full message i=
s received. There are betterTCP access

 [[SW2]] Sorry to repeat. If you need atomicity for the sub-messages in the=
 bundle, then you need to wait. If not then you don't have to. This is prov=
iding you the flexibility, which you don't easily have with individual mess=
ages (e.g atomic handling is hard to realize with individual messages).

What is the downside of having it? It is negotiable as an optional capabili=
ty.

Woj> A couple of reasons come to the fore; i) no body saw a good reason so =
far to implement it/use it ii) it's added protocol "stuff" that has no clea=
r benefit, does not realize any new use-case, does not optimize much, and i=
n fact as mentioned above it appears to rather have some downsides such as =
extra overhead, buffering and delay.

Let's now have the axe fall...
[[SW]] Let us please not be dismissive towards something that has benefits =
(as outlined above).

Wo#2j>  With the exception of cumulative ack, which does deserve a standalo=
ne proposal to be put forward, neither me nor other members of the WG do ap=
pear to share the views regarding the purported benefits on bulking, nor a =
desire to retain it in the spec.
[[SW2]] See above. This has been in the draft for a while, and I have not s=
een any technical arguments from anyone else on removing it from the draft.=
 I have clearly outlined the benefits above, and don't see convincing techn=
ical reasons for this to go.


Sorry, it just needs to go.

[[SW2]] Is this with your chair hat on or as an individual WG member?

Cheers,
Woj.

Cheers
-Sanjay



-----Original Message-----
From: Wojciech Dec (wdec) [mailto:wdec@cisco.com]
Sent: Tuesday, May 06, 2008 1:24 PM
To: Sanjay Wadhwa; Peter Arberg; ancp@ietf.org
Subject: RE: [ANCP] Bulk Transaction Message
Sanjay,

can you please present to the WG and myself how bulk transaction capability=
 is useful in any way in terms of scaling for example? And by the way, plea=
se treat this discussion is orthogonal to any other.

Cheers,
Woj.


________________________________
From: Sanjay Wadhwa [mailto:swadhwa@juniper.net]
Sent: 06 May 2008 19:08
To: Wojciech Dec (wdec); Peter Arberg; ancp@ietf.org
Subject: RE: [ANCP] Bulk Transaction Message
Woj
  It is a bad idea to remove bulk-transaction capability from the draft. On=
 one hand you are trying to add "marginally useful" extensions (with TLVs),=
 and on the other hand you are arguing for removing useful abstractions whi=
ch can help with scaling. If bulk-transaction capability needs to be augmen=
ted or modified, then we should consider augmenting it, rather than removin=
g it from the draft.

Cheers
-Sanjay
-----Original Message-----
From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org]On Behalf Of Wojc=
iech Dec (wdec)
Sent: Tuesday, May 06, 2008 12:42 PM
To: Peter Arberg; ancp@ietf.org
Subject: Re: [ANCP] Bulk Transaction Message
Hi Folks,

given that no discernable use of Bulk messaging has been identified, nor th=
ere being a good reason for it given the fact that ANCP is bound to the TCP=
 transport (or equivalent), I would like to propose to remove all of the te=
xt relating to this capability and associated message from the protocol spe=
c draft.

Regards,
Woj.

________________________________
From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of Woj=
ciech Dec (wdec)
Sent: 20 April 2008 15:18
To: Peter Arberg; ancp@ietf.org
Subject: Re: [ANCP] Bulk Transaction Message
Should also have added: Given that currently the bulk message does not appe=
ar to have had any practical adoption, having the DTeam adopt it/modify it,=
 or possibly have it removed from the spec all together are all valid optio=
ns.

-Woj.

________________________________
From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of Woj=
ciech Dec (wdec)
Sent: 20 April 2008 14:39
To: Peter Arberg; ancp@ietf.org
Subject: Re: [ANCP] Bulk Transaction Message
It's all simple:
- the Design Team is looking at the possibility of using this message
- the message in its current form does not appear to be terribly useful, an=
d could be removed from the spec.

-Woj.


________________________________
From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of Pet=
er Arberg
Sent: 19 April 2008 03:07
To: Wojciech Dec (wdec); ancp@ietf.org
Subject: Re: [ANCP] Bulk Transaction Message
Hi Woj,

can you give a little background to why you are looking for vendor
implementation support for this specific capability & message ?

thanks,
Peter

________________________________
From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of Woj=
ciech Dec (wdec)
Sent: 18. april 2008 08:04
To: ancp@ietf.org
Subject: [ANCP] Bulk Transaction Message

Hi Folks,

Could you please let me/us know if you currently have an implementation of =
ANCP that supports the Bulk Transaction Capability and Message?

Thanks,
Woj.

--_000_48C276B536524E478C659685995F6AA560439CC78BRBSJXadredbac_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:v =3D=20
"urn:schemas-microsoft-com:vml" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:st1 =3D=20
"urn:schemas-microsoft-com:office:smarttags"><HEAD><TITLE>Bulk Transaction =
Message</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.6000.16640" name=3DGENERATOR><!--[if !mso]>
<STYLE>v\:* {
	BEHAVIOR: url(#default#VML)
}
o\:* {
	BEHAVIOR: url(#default#VML)
}
w\:* {
	BEHAVIOR: url(#default#VML)
}
.shape {
	BEHAVIOR: url(#default#VML)
}
</STYLE>
<![endif]--><o:SmartTagType=20
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"=20
name=3D"PersonName"></o:SmartTagType><!--[if !mso]>
<STYLE>st1\:* {
	BEHAVIOR: url(#default#ieooui)
}
</STYLE>
<![endif]-->
<STYLE>@font-face {
	font-family: Tahoma;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline
}
P {
	FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: "Times =
New Roman"; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto
}
SPAN.EmailStyle18 {
	COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal
}
SPAN.EmailStyle19 {
	COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal-reply
}
DIV.Section1 {
	page: Section1
}
</STYLE>
</HEAD>
<BODY lang=3DEN-US vLink=3Dpurple link=3Dblue>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D052281323-08052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Hi,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D052281323-08052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D052281323-08052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>I have to say as well that my comment to vote for =
removal=20
of the Bulk is not</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D052281323-08052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>because I do not see value in some optimization, i=
t was for=20
the reason I do</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D052281323-08052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>not want to see a non used item delay this=20
draft.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D052281323-08052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D052281323-08052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>I think we should remove non used items and move t=
he draft=20
forward as</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D052281323-08052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>soon as possible, and then open up for new contrib=
utions=20
after the base ANCP</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D052281323-08052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>specifications have been accepted and documented a=
s a=20
rfc.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D052281323-08052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D052281323-08052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>cheers,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D052281323-08052008><FONT face=3DA=
rial=20
color=3D#0000ff size=3D2>Peter</FONT></SPAN></DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px soli=
d; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> ancp-bounces@ietf.org=20
  [mailto:ancp-bounces@ietf.org] <B>On Behalf Of </B>DE CNODDER=20
  Stefaan<BR><B>Sent:</B> 8. maj 2008 12:18<BR><B>To:</B> Sanjay Wadhwa;=20
  Wojciech Dec (wdec); ancp@ietf.org<BR><B>Subject:</B> Re: [ANCP] Bulk=20
  Transaction Message<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff size=3D2><=
SPAN=20
  class=3D691280810-08052008>Hi Sanjay, Woj,</SPAN></FONT></DIV>
  <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff size=3D2><=
SPAN=20
  class=3D691280810-08052008></SPAN></FONT>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff size=3D2><=
SPAN=20
  class=3D691280810-08052008>I see some advantages in having bulk messages =
to=20
  optimize ANCP.&nbsp; However, bulk messages are not the only solution.&nb=
sp;=20
  It is wrong to discuss bulk messages without comparing it with=20
  alternatives.&nbsp; It looks like a good solution to me but maybe there a=
re=20
  better ways in optimizing ANCP.&nbsp; So far the working group has not be=
en=20
  working a lot on optimizations.&nbsp; According to me, keeping bulk messa=
ges=20
  in the base spec is wrong and it should be removed.&nbsp; People are invi=
ted=20
  to submit solutions to optimize ANCP in the form of a seperate draft, and=
 one=20
  such draft could be bulk messages.&nbsp; Then when the working group deci=
des=20
  that it is time to work on optimalisations, the proposed solutions can be=
=20
  compared and discussed.</SPAN></FONT></DIV>
  <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff size=3D2><=
SPAN=20
  class=3D691280810-08052008></SPAN></FONT>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff size=3D2><=
SPAN=20
  class=3D691280810-08052008>regards,</SPAN></FONT></DIV>
  <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff size=3D2><=
SPAN=20
  class=3D691280810-08052008>Stefaan</SPAN></FONT></DIV><BR>
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> ancp-bounces@ietf.org=20
  [mailto:ancp-bounces@ietf.org] <B>On Behalf Of </B>Sanjay=20
  Wadhwa<BR><B>Sent:</B> woensdag 7 mei 2008 18:07<BR><B>To:</B> Wojciech D=
ec=20
  (wdec); Peter Arberg; ancp@ietf.org<BR><B>Subject:</B> Re: [ANCP] Bulk=20
  Transaction Message<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV class=3DSection1>
  <P class=3DMsoNormal><B><FONT face=3DArial color=3D#333399 size=3D2><SPAN=
=20
  style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: #333399; FONT-FAMILY:=
 Arial">Inline=20
  again</SPAN></FONT></B><B><FONT face=3DArial color=3D#993366 size=3D2><SP=
AN=20
  style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY:=
 Arial">=20
  </SPAN></FONT></B><B><FONT face=3DArial color=3D#333399 size=3D2><SPAN=20
  style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: #333399; FONT-FAMILY:=
 Arial">[SW2]<o:p></o:p></SPAN></FONT></B></P>
  <P class=3DMsoNormal><B><FONT face=3DArial color=3D#993366 size=3D2><SPAN=
=20
  style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY:=
 Arial"><o:p>&nbsp;</o:p></SPAN></FONT></B></P>
  <P class=3DMsoNormal><B><FONT face=3DArial color=3D#333399 size=3D2><SPAN=
=20
  style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: #333399; FONT-FAMILY:=
 Arial">-Sanjay</SPAN></FONT></B><FONT=20
  face=3DArial color=3D#333399 size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: #333399; FONT-FAMILY: Arial"><o:p></o:p>=
</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p>&nbsp;</o=
:p></SPAN></FONT></P>
  <DIV>
  <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" align=3Dcenter><FONT=
=20
  face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
  <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
  </SPAN></FONT></DIV>
  <P class=3DMsoNormal><B><FONT face=3DTahoma size=3D2><SPAN=20
  style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">From:</=
SPAN></FONT></B><FONT=20
  face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahom=
a">=20
  Wojciech Dec (wdec) [mailto:wdec@cisco.com] <BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Wednesday, May 07, 2008 10:4=
7=20
  AM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Wojciech Dec (w=
dec);=20
  Sanjay Wadhwa; Peter Arberg; ancp@ietf.org<BR><B><SPAN=20
  style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [ANCP] Bulk Transacti=
on=20
  Message</SPAN></FONT><o:p></o:p></P></DIV>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Should have added:=20
  Plea<st1:PersonName w:st=3D"on">se</st1:PersonName> feel free to put forw=
ard a=20
  bulk ack proposal to the WG. Just axe the existing bulking text before so=
meone=20
  goes starts thinking of actually adopting it.</SPAN></FONT><o:p></o:p></P=
>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">-Woj.</SPAN></FONT><o:p></o=
:p></P>
  <BLOCKQUOTE=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: mediu=
m none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: 5pt 0in 5pt 3.75pt;=
 BORDER-LEFT: black 1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: medium no=
ne">
    <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
    style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
    <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" align=3Dcenter><FON=
T=20
    face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
    <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
    </SPAN></FONT></DIV>
    <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><B><FONT face=3DTaho=
ma=20
    size=3D2><SPAN=20
    style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">From:=
</SPAN></FONT></B><FONT=20
    face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tah=
oma">=20
    ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] <B><SPAN=20
    style=3D"FONT-WEIGHT: bold">On Behalf Of </SPAN></B>Wojciech Dec=20
    (wdec)<BR><B><SPAN style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> 07 May =
2008=20
    16:27<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Sanjay Wad=
hwa;=20
    Peter Arberg; ancp@ietf.org<BR><B><SPAN=20
    style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> Re: [ANCP] Bulk Transac=
tion=20
    Message</SPAN></FONT><o:p></o:p></P>
    <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Sanjay,</SPAN></FONT><o:p=
></o:p></P>
    <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
    style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
    <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">inline=20
    woj#2&gt;</SPAN></FONT><o:p></o:p></P>
    <BLOCKQUOTE=20
    style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: med=
ium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: 5pt 0in 5pt 3.75p=
t; BORDER-LEFT: black 1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: medium =
none">
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
      style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
      <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" align=3Dcenter><F=
ONT=20
      face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
      <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
      </SPAN></FONT></DIV>
      <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><B><FONT face=3DTa=
homa=20
      size=3D2><SPAN=20
      style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">Fro=
m:</SPAN></FONT></B><FONT=20
      face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: T=
ahoma">=20
      Sanjay Wadhwa [mailto:swadhwa@juniper.net] <BR><B><SPAN=20
      style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> 07 May 2008 16:02<BR><B>=
<SPAN=20
      style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Wojciech Dec (wdec); Peter=
=20
      Arberg; ancp@ietf.org<BR><B><SPAN=20
      style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [ANCP] Bulk Trans=
action=20
      Message</SPAN></FONT><o:p></o:p></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3D#993366 size=3D2><SPA=
N=20
      style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: Arial">Woj<o:p=
></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3D#993366 size=3D2><SPA=
N=20
      style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: Arial">&nbsp; =
Inline=20
      [SW].<o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p>&nbsp=
;</o:p></SPAN></FONT></P>
      <DIV>
      <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" align=3Dcenter><F=
ONT=20
      face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
      <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
      </SPAN></FONT></DIV>
      <P class=3DMsoNormal><B><FONT face=3DTahoma size=3D2><SPAN=20
      style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">Fro=
m:</SPAN></FONT></B><FONT=20
      face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: T=
ahoma">=20
      Wojciech Dec (wdec) [mailto:wdec@cisco.com] <BR><B><SPAN=20
      style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Wednesday, May 07, 2008 =
3:32=20
      AM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Sanjay Wadh=
wa;=20
      Peter Arberg; ancp@ietf.org<BR><B><SPAN=20
      style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [ANCP] Bulk Trans=
action=20
      Message</SPAN></FONT><o:p></o:p></P></DIV>
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
      style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Sanjay,</SPAN></FONT><o=
:p></o:p></P>
      <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
      style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
      <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">inline</SPAN></FONT><o:=
p></o:p></P>
      <BLOCKQUOTE=20
      style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: m=
edium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: 5pt 0in 5pt 3.7=
5pt; BORDER-LEFT: black 1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: mediu=
m none">
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=
=20
        style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
        <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" align=3Dcenter>=
<FONT=20
        face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12pt">
        <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
        </SPAN></FONT></DIV>
        <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><B><FONT face=3D=
Tahoma=20
        size=3D2><SPAN=20
        style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">F=
rom:</SPAN></FONT></B><FONT=20
        face=3DTahoma size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY:=
 Tahoma">=20
        Sanjay Wadhwa [mailto:swadhwa@juniper.net] <BR><B><SPAN=20
        style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> 07 May 2008 02:03<BR><=
B><SPAN=20
        style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Wojciech Dec (wdec); Pet=
er=20
        Arberg; ancp@ietf.org<BR><B><SPAN=20
        style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [ANCP] Bulk=20
        Transaction Message</SPAN></FONT><o:p></o:p></P>
        <DIV>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=
=20
        style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">Even wit=
h=20
        transport being TCP, I <st1:PersonName w:st=3D"on">se</st1:PersonNa=
me>e=20
        atleast a couple of benefits:</SPAN></FONT><o:p></o:p></P></DIV>
        <DIV>
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=
=20
        style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
        <DIV>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=
=20
        style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">1. If=20
        a&nbsp;<st1:PersonName w:st=3D"on">se</st1:PersonName>nder knows it=
 has a=20
        bunch of messages to <st1:PersonName w:st=3D"on">se</st1:PersonName=
>nd=20
        (e.g. ANCP adjacency flaps, and all the port-up messages need to=20
        re-played), then bulking by definition&nbsp;allows the application =
to=20
        invoke TCP fewer times to transmit&nbsp;everything that it needs to=
=20
        transmit, which&nbsp;in a lot of systems can translate to=20
        significant&nbsp;compute and memory efficiency (specially, if we ar=
e=20
        considering a large amount of state). This&nbsp;is not to say one=20
        can't&nbsp;realize this&nbsp;in an implementation specific=20
        way.&nbsp;</SPAN></FONT><FONT face=3DArial color=3Dblack size=3D2><=
SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">&nbsp;<=
/SPAN></FONT><o:p></o:p></P></DIV>
        <DIV>
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=
=20
        style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
        <DIV>
        <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Woj&gt; Even with bul=
king=20
        one needs to realize the TCP interaction with some thought. Perhaps=
=20
        bulking indeed&nbsp;offers the opportunity for a delveloper to thin=
k=20
        about that, but I <st1:PersonName w:st=3D"on">se</st1:PersonName>ri=
ously=20
        doubt that anyone familar with TCP app development&nbsp;would overl=
ook=20
        this aspect in the first place.<o:p></o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=
=20
        style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p>&nb=
sp;</o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3D#993366 size=3D2><S=
PAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: Arial">[[SW]=
] I=20
        would like to believe it. History doesn&#8217;t bear this=20
        though.</SPAN></FONT><FONT face=3DArial color=3Dblack size=3D2><SPA=
N=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">&nbsp;<=
/SPAN></FONT><o:p></o:p></P>
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=
=20
        style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPA=
N=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Woj#2&g=
t;&nbsp;Unless=20
        the spec forces Bulking to be u<st1:PersonName=20
        w:st=3D"on">se</st1:PersonName>d for every single multi-message exc=
hange,=20
        the bunching effect will not appear, nor will any=20
        optimization.</SPAN></FONT><o:p></o:p></P></DIV>
        <DIV>
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=
=20
        style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
        <DIV>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=
=20
        style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">However,=
&nbsp;</SPAN></FONT><B><FONT=20
        face=3DArial color=3Dred size=3D2><SPAN=20
        style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: red; FONT-FAMIL=
Y: Arial">if=20
        neeeded</SPAN></FONT></B><FONT face=3DArial color=3Dblue size=3D2><=
SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">, bulkin=
g=20
        also&nbsp;has the benefit of affording optimized acking (e.g. if no=
=20
        error is encountered in proccessing all the sub-messages in the bun=
dled=20
        message, it&nbsp;is possible&nbsp;for the receiver to <st1:PersonNa=
me=20
        w:st=3D"on">se</st1:PersonName>nd a cummulative ack to the <st1:Per=
sonName=20
        w:st=3D"on">se</st1:PersonName>nder rather than individual=20
        acks).</SPAN></FONT><FONT face=3DArial color=3Dblack size=3D2><SPAN=
=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">&nbsp;<=
/SPAN></FONT><o:p></o:p></P></DIV>
        <DIV>
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=
=20
        style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
        <DIV>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPA=
N=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Woj&gt;=
&nbsp;A=20
        cumulatitive ack would appear to be desirable in some ca<st1:Person=
Name=20
        w:st=3D"on">se</st1:PersonName>s, but I <st1:PersonName=20
        w:st=3D"on">se</st1:PersonName>e this as very&nbsp;different to=20
        the&nbsp;bulk ack currently described which es<st1:PersonName=20
        w:st=3D"on">se</st1:PersonName>natially carries in bulk all of the=
=20
        individal acks.&nbsp;The bulking mechanism is quite clear in saying=
 that=20
        each ANCP message is&nbsp;bundled header and all, and acted upon=20
        individually by the recipient, and whether it's a request or an ack=
 is=20
        <st1:PersonName w:st=3D"on">se</st1:PersonName>condary. I'm sure yo=
u'll=20
        agree that this is undesirable overhead and complexity for what it'=
s=20
        worth, also in view of the fact that "something" on the recipient s=
ide=20
        would need to decide what ack/nack goes into a bulk=20
        respon<st1:PersonName w:st=3D"on">se</st1:PersonName> and what does=
n't.=20
        </SPAN></FONT><o:p></o:p></P></DIV>
        <DIV>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPA=
N=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Having =
a=20
        cumulatitive ack is an all thogether different thing, which I=20
        would&nbsp;support, and it should not involve the "bulking" of each=
=20
        indivdual ack, and is an item that&nbsp;for which&nbsp;proposals ar=
e=20
        welcome.</SPAN></FONT><FONT face=3DArial size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"><o:p></o:p></SPAN></F=
ONT></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3D#993366 size=3D2><S=
PAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: Arial">[[SW]=
]=20
        Sorry, I should have been clearer. Bulking adds an overall header f=
or=20
        the individual messages being bulked. If all the messages succeed, =
we=20
        can define the behavior to <st1:PersonName=20
        w:st=3D"on">se</st1:PersonName>nd a single ACK (NOT a bulk ACK=20
        compo<st1:PersonName w:st=3D"on">se</st1:PersonName>d of individual=
=20
        sub-messages carrying ACK) with the transaction-ID of the main head=
er=20
        reflected back in the ACK. &nbsp;This provides an elegant way to ad=
dress=20
        cumulative ACK. This is not defined in the draft today (<st1:Person=
Name=20
        w:st=3D"on">se</st1:PersonName>e &#8220;if needed&#8221; above), bu=
t is easily=20
        provided by bulking, and can be added if we=20
        agree.<o:p></o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3D#993366 size=3D2><S=
PAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: Arial">Far a=
s=20
        request message is concerned, having individual messages (with thei=
r own=20
        header) in the request reduces complexity, provides a way to bulk=20
        messages of different types if needed. It allows each sub-message t=
o be=20
        individually NACK&#8217;d where required. Bulking in such a way all=
ows the=20
        flexibility of treating individual sub-messages as completely=20
        independent or related.</SPAN></FONT><FONT face=3DArial color=3Dbla=
ck=20
        size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">&nbsp;<=
/SPAN></FONT><o:p></o:p></P>
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=
=20
        style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPA=
N=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Woj#2&g=
t; The=20
        above, in principle is fine, BUT it is far removed from the current=
=20
        bulking mechanism. The order would be to have a proposal regarding=
=20
        this&nbsp;on its own right.&nbsp;</SPAN></FONT><FONT face=3DArial=20
        color=3Dnavy size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p></o=
:p></SPAN></FONT></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=
=20
        style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p>&nb=
sp;</o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><B><FONT face=3DArial color=3Dnavy size=3D2><S=
PAN=20
        style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: navy; FONT-FAMI=
LY: Arial">[[SW2]]=20
        It can easily be extended and doesn&#8217;t need to be done right a=
way.=20
        Rehashing (new proposal) when you have the basis for in the draft i=
s not=20
        justifiable.</SPAN></FONT></B><FONT face=3DArial color=3Dnavy size=
=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p></o=
:p></SPAN></FONT></P></DIV>
        <DIV>
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=
=20
        style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
        <DIV>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=
=20
        style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">2. Bulki=
ng also=20
        provides a nice solution if one&nbsp;ever needed to atomically rece=
ive=20
        and process *distinct* ANCP message types.&nbsp;</SPAN></FONT><FONT=
=20
        face=3DArial color=3Dblack size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">&nbsp;<=
/SPAN></FONT><FONT=20
        face=3DArial color=3Dnavy size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p></o=
:p></SPAN></FONT></P>
        <P class=3DMsoNormal><B><I><FONT face=3DArial color=3Dnavy size=3D2=
><SPAN=20
        style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: navy; FONT-STYL=
E: italic; FONT-FAMILY: Arial"><o:p>&nbsp;</o:p></SPAN></FONT></I></B></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPA=
N=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Woj&gt;=
&nbsp;There=20
        appears to be no such thing; </SPAN></FONT><FONT face=3DArial color=
=3Dnavy=20
        size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p></o=
:p></SPAN></FONT></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3D#993366 size=3D2><S=
PAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: Arial">[[SW]=
]=20
        Today, but as you mentioned in another thread, we need to design th=
e=20
        protocol to be generic in anticipation of such=20
        requirements.</SPAN></FONT><FONT face=3DArial color=3Dblack size=3D=
2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">&nbsp;<=
/SPAN></FONT><o:p></o:p></P>
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=
=20
        style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPA=
N=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Woj#2&g=
t; What=20
        tentative requirements are you referring to, a&nbsp;relay?&nbsp;If=
=20
        so,&nbsp;bulking doesn't help there. This is also much different fr=
om a=20
        discussion about a generic TLV format that is to be u<st1:PersonNam=
e=20
        w:st=3D"on">se</st1:PersonName>d by the=20
        protocol.</SPAN></FONT><o:p></o:p></P>
        <P class=3DMsoNormal><B><I><FONT face=3DArial color=3Dnavy size=3D2=
><SPAN=20
        style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: navy; FONT-STYL=
E: italic; FONT-FAMILY: Arial"><o:p>&nbsp;</o:p></SPAN></FONT></I></B></P>
        <P class=3DMsoNormal><B><I><FONT face=3DArial color=3Dnavy size=3D2=
><SPAN=20
        style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: navy; FONT-STYL=
E: italic; FONT-FAMILY: Arial"><o:p>&nbsp;</o:p></SPAN></FONT></I></B></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPA=
N=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">in bulk=
ing,=20
        presumably the reciever would have to buffer all the way until the =
end=20
        of the bulk message, and then process each message individually. Th=
is=20
        <st1:PersonName w:st=3D"on">se</st1:PersonName>ems rather overweigh=
t when=20
        compared to simply <st1:PersonName w:st=3D"on">se</st1:PersonName>n=
ding=20
        each message again.</SPAN></FONT><FONT face=3DArial color=3Dnavy=20
        size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p></o=
:p></SPAN></FONT></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3D#993366 size=3D2><S=
PAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: Arial">[[SW]=
] Draft=20
        doesn&#8217;t impo<st1:PersonName w:st=3D"on">se</st1:PersonName> o=
n how much=20
        you bulk. If atomicity in handling of bulked messages is warranted =
by a=20
        u<st1:PersonName w:st=3D"on">se</st1:PersonName>-ca<st1:PersonName=
=20
        w:st=3D"on">se</st1:PersonName>, then yes you want to get the entir=
e=20
        message. If not, you could presumably process as you receive each=20
        complete sub-message within the bundle.</SPAN></FONT><FONT face=3DA=
rial=20
        color=3Dblack size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">&nbsp;<=
/SPAN></FONT><o:p></o:p></P>
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=
=20
        style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPA=
N=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Woj#2&g=
t;=20
        Adding a single bulk envelope and <st1:PersonName=20
        w:st=3D"on">se</st1:PersonName>nding inside it&nbsp;100 messages vs=
 2 bulk=20
        envelopes with 50 messages is also pretty pointless, and an=20
        exerci<st1:PersonName w:st=3D"on">se</st1:PersonName> in optimizing=
=20
        something that isn't needed in the first place: In each=20
        ca<st1:PersonName w:st=3D"on">se</st1:PersonName> you're still=20
        <st1:PersonName w:st=3D"on">se</st1:PersonName>nding 100 messages! =
The=20
        downside is that in either of the bulked messages ca<st1:PersonName=
=20
        w:st=3D"on">se</st1:PersonName> you generally will have to wait til=
l the=20
        full message is received. There are betterTCP access </SPAN></FONT>=
<FONT=20
        face=3DArial size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"><o:p></o:p></SPAN></F=
ONT></P>
        <P class=3DMsoNormal><B><I><FONT face=3DArial color=3Dnavy size=3D2=
><SPAN=20
        style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: navy; FONT-STYL=
E: italic; FONT-FAMILY: Arial"><o:p>&nbsp;</o:p></SPAN></FONT></I></B></P>
        <P class=3DMsoNormal><B><I><FONT face=3DArial color=3Dnavy size=3D2=
><SPAN=20
        style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: navy; FONT-STYL=
E: italic; FONT-FAMILY: Arial">&nbsp;</SPAN></FONT></I></B><B><FONT=20
        face=3DArial color=3Dnavy size=3D2><SPAN=20
        style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: navy; FONT-FAMI=
LY: Arial">[[SW2]]=20
        Sorry to repeat. If you need atomicity for the sub-messages in the=
=20
        bundle, then you need to wait. If not then you don&#8217;t have to.=
 This is=20
        providing you the flexibility, which you don&#8217;t easily have wi=
th=20
        individual messages (e.g atomic handling is hard to realize with=20
        individual messages).</SPAN></FONT></B><FONT face=3DArial color=3Dn=
avy=20
        size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p></o=
:p></SPAN></FONT></P></DIV>
        <DIV>
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=
=20
        style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
        <DIV>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=
=20
        style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">What is =
the=20
        downside of having it? It is&nbsp;negotiable as an optional=20
        capability.</SPAN></FONT><FONT face=3DArial color=3Dblack size=3D2>=
<SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">&nbsp;<=
/SPAN></FONT><o:p></o:p></P></DIV>
        <DIV>
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=
=20
        style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
        <DIV>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPA=
N=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Woj&gt;=
 A=20
        couple of reasons come to the fore; i) no body saw a good reason so=
 far=20
        to implement it/u<st1:PersonName w:st=3D"on">se</st1:PersonName> it=
 ii)=20
        it's added protocol "stuff" that has no clear benefit, does not rea=
lize=20
        any new u<st1:PersonName w:st=3D"on">se</st1:PersonName>-ca<st1:Per=
sonName=20
        w:st=3D"on">se</st1:PersonName>,&nbsp;does not optimize much, and i=
n fact=20
        as mentioned above it appears to rather have some downsides such as=
=20
        extra overhead, buffering and delay.</SPAN></FONT><B><I><FONT face=
=3DArial=20
        color=3Dnavy size=3D2><SPAN=20
        style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: navy; FONT-STYL=
E: italic; FONT-FAMILY: Arial"><o:p></o:p></SPAN></FONT></I></B></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=
=20
        style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p>&nb=
sp;</o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPA=
N=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Let's n=
ow have=20
        the axe fall...</SPAN></FONT><FONT face=3DArial color=3Dnavy size=
=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p></o=
:p></SPAN></FONT></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3D#993366 size=3D2><S=
PAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: Arial">[[SW]=
] Let=20
        us plea<st1:PersonName w:st=3D"on">se</st1:PersonName> not be dismi=
ssive=20
        towards something that has benefits (as outlined=20
        above).</SPAN></FONT><FONT face=3DArial color=3Dblack size=3D2><SPA=
N=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">&nbsp;<=
/SPAN></FONT><o:p></o:p></P>
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=
=20
        style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPA=
N=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Wo#2j&g=
t;=20
        &nbsp;With the exception of cumulative ack, which does de<st1:Perso=
nName=20
        w:st=3D"on">se</st1:PersonName>rve a standalone proposal to be put=
=20
        forward, neither me nor&nbsp;other members of the&nbsp;WG do&nbsp;a=
ppear=20
        to share the views regarding the purported benefits on bulking, nor=
 a=20
        desire to retain it in the spec.&nbsp;</SPAN></FONT><FONT face=3DAr=
ial=20
        color=3Dnavy size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p></o=
:p></SPAN></FONT></P>
        <P class=3DMsoNormal><B><FONT face=3DArial color=3Dnavy size=3D2><S=
PAN=20
        style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: navy; FONT-FAMI=
LY: Arial">[[SW2]]=20
        See above. This has been in the draft for a while, and I have not=20
        <st1:PersonName w:st=3D"on">se</st1:PersonName>en any technical arg=
uments=20
        from anyone el<st1:PersonName w:st=3D"on">se</st1:PersonName> on re=
moving=20
        it from the draft. I have clearly outlined the benefits above, and =
don&#8217;t=20
        <st1:PersonName w:st=3D"on">se</st1:PersonName>e convincing technic=
al=20
        reasons for this to go. </SPAN></FONT></B><FONT face=3DArial color=
=3Dnavy=20
        size=3D2><SPAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p></o=
:p></SPAN></FONT></P>
        <P class=3DMsoNormal><B><I><FONT face=3DArial color=3Dnavy size=3D2=
><SPAN=20
        style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: navy; FONT-STYL=
E: italic; FONT-FAMILY: Arial"><o:p>&nbsp;</o:p></SPAN></FONT></I></B></P>
        <P class=3DMsoNormal><B><I><FONT face=3DArial color=3Dnavy size=3D2=
><SPAN=20
        style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: navy; FONT-STYL=
E: italic; FONT-FAMILY: Arial"><o:p>&nbsp;</o:p></SPAN></FONT></I></B></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPA=
N=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Sorry, =
it just=20
        needs to go.</SPAN></FONT><o:p></o:p></P>
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=
=20
        style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><B><FONT face=3DArial color=3Dnavy size=3D2><S=
PAN=20
        style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; COLOR: navy; FONT-FAMI=
LY: Arial">[[SW2]]=20
        Is this with your chair hat on or as an individual WG member?=20
        <o:p></o:p></SPAN></FONT></B></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=
=20
        style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p>&nb=
sp;</o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPA=
N=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Cheers,=
</SPAN></FONT><o:p></o:p></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblack size=3D2><SPA=
N=20
        style=3D"FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: Arial">Woj.</S=
PAN></FONT><o:p></o:p></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><SPAN=
=20
        style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial"><o:p>&nb=
sp;</o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3D#993366 size=3D2><S=
PAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: Arial">Cheer=
s<o:p></o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3D#993366 size=3D2><S=
PAN=20
        style=3D"FONT-SIZE: 10pt; COLOR: #993366; FONT-FAMILY: Arial">-Sanj=
ay<o:p></o:p></SPAN></FONT></P>
        <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=
=20
        style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p>&nb=
sp;</o:p></SPAN></FONT></P></DIV>
        <DIV>
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=
=20
        style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></DIV>
        <DIV>
        <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=
=20
        style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P></DIV>
        <BLOCKQUOTE=20
        style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP:=
 medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: 5pt 0in 5pt 3=
.75pt; BORDER-LEFT: blue 1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: medi=
um none">
          <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><FONT face=3DT=
ahoma=20
          size=3D2><SPAN=20
          style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">-----Original=20
          Message-----<BR><B><SPAN style=3D"FONT-WEIGHT: bold">From:</SPAN>=
</B>=20
          Wojciech Dec (wdec) [mailto:wdec@cisco.com]<BR><B><SPAN=20
          style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> Tuesday, May 06, 200=
8 1:24=20
          PM<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Sanjay =
Wadhwa;=20
          Peter Arberg; ancp@ietf.org<BR><B><SPAN=20
          style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [ANCP] Bulk=20
          Transaction Message</SPAN></FONT><o:p></o:p></P>
          <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
          style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Sanjay,</SPAN></FON=
T><o:p></o:p></P>
          <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPA=
N=20
          style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
          <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
          style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">can you=20
          plea<st1:PersonName w:st=3D"on">se</st1:PersonName> pre<st1:Perso=
nName=20
          w:st=3D"on">se</st1:PersonName>nt to the WG and my<st1:PersonName=
=20
          w:st=3D"on">se</st1:PersonName>lf how bulk transaction capability=
 is=20
          u<st1:PersonName w:st=3D"on">se</st1:PersonName>ful in any way in=
 terms=20
          of scaling for example? And by the way, plea<st1:PersonName=20
          w:st=3D"on">se</st1:PersonName> treat this discussion is orthogon=
al to=20
          any other.</SPAN></FONT><o:p></o:p></P>
          <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPA=
N=20
          style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
          <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
          style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Cheers,</SPAN></FON=
T><o:p></o:p></P>
          <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
          style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Woj.</SPAN></FONT><=
o:p></o:p></P>
          <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPA=
N=20
          style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
          <BLOCKQUOTE=20
          style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TO=
P: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: 5pt 0in 5pt=
 3.75pt; BORDER-LEFT: black 1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: m=
edium none">
            <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><S=
PAN=20
            style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
            <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center" align=3Dcen=
ter><FONT=20
            face=3D"Times New Roman" size=3D3><SPAN style=3D"FONT-SIZE: 12p=
t">
            <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
            </SPAN></FONT></DIV>
            <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><B><FONT fac=
e=3DTahoma=20
            size=3D2><SPAN=20
            style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: Tahom=
a">From:</SPAN></FONT></B><FONT=20
            face=3DTahoma size=3D2><SPAN=20
            style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma"> Sanjay Wadhwa=20
            [mailto:swadhwa@juniper.net] <BR><B><SPAN=20
            style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> 06 May 2008=20
            19:08<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Wo=
jciech=20
            Dec (wdec); Peter Arberg; ancp@ietf.org<BR><B><SPAN=20
            style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> RE: [ANCP] Bulk=
=20
            Transaction Message</SPAN></FONT><o:p></o:p></P>
            <DIV>
            <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><=
SPAN=20
            style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">Woj<=
/SPAN></FONT><o:p></o:p></P></DIV>
            <DIV>
            <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><=
SPAN=20
            style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">&nbs=
p; It=20
            is a bad idea to remove bulk-transaction capability from the dr=
aft.=20
            On one hand you are trying to add "marginally u<st1:PersonName=
=20
            w:st=3D"on">se</st1:PersonName>ful" extensions (with TLVs), and=
 on the=20
            other hand you are arguing for removing u<st1:PersonName=20
            w:st=3D"on">se</st1:PersonName>ful abstractions which can help =
with=20
            scaling. If bulk-transaction capability needs to be augmented o=
r=20
            modified, then we should consider augmenting it, rather than=20
            removing it from the draft.</SPAN></FONT><o:p></o:p></P></DIV>
            <DIV>
            <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><S=
PAN=20
            style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P></=
DIV>
            <DIV>
            <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><=
SPAN=20
            style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">Chee=
rs</SPAN></FONT><o:p></o:p></P></DIV>
            <DIV>
            <P class=3DMsoNormal><FONT face=3DArial color=3Dblue size=3D2><=
SPAN=20
            style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Arial">-San=
jay</SPAN></FONT><o:p></o:p></P></DIV>
            <BLOCKQUOTE=20
            style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-=
TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: 5pt 0in 5=
pt 3.75pt; BORDER-LEFT: blue 1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: =
medium none">
              <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><FONT face=
=3DTahoma=20
              size=3D2><SPAN=20
              style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">-----Original=
=20
              Message-----<BR><B><SPAN=20
              style=3D"FONT-WEIGHT: bold">From:</SPAN></B> ancp-bounces@iet=
f.org=20
              [mailto:ancp-bounces@ietf.org]<B><SPAN=20
              style=3D"FONT-WEIGHT: bold">On Behalf Of </SPAN></B>Wojciech =
Dec=20
              (wdec)<BR><B><SPAN style=3D"FONT-WEIGHT: bold">Sent:</SPAN></=
B>=20
              Tuesday, May 06, 2008 12:42 PM<BR><B><SPAN=20
              style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Peter Arberg;=20
              ancp@ietf.org<BR><B><SPAN=20
              style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> Re: [ANCP] Bu=
lk=20
              Transaction Message</SPAN></FONT><o:p></o:p></P>
              <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
              style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Hi=20
              Folks,</SPAN></FONT><o:p></o:p></P>
              <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3>=
<SPAN=20
              style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
              <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
              style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">given that no=20
              discernable u<st1:PersonName w:st=3D"on">se</st1:PersonName> =
of Bulk=20
              messaging has been identified, nor&nbsp;there being a good re=
ason=20
              for it given the fact that ANCP is bound to the TCP transport=
 (or=20
              equivalent),&nbsp;I would like to propo<st1:PersonName=20
              w:st=3D"on">se</st1:PersonName> to remove all of the text rel=
ating=20
              to this capability and associated message from the protocol s=
pec=20
              draft.</SPAN></FONT><o:p></o:p></P>
              <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3>=
<SPAN=20
              style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></P>
              <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
              style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Regards,</SPAN>=
</FONT><o:p></o:p></P>
              <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
              style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Woj.</SPAN></FO=
NT><o:p></o:p></P>
              <BLOCKQUOTE=20
              style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDE=
R-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: 5pt 0in=
 5pt 3.75pt; BORDER-LEFT: black 1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTO=
M: medium none">
                <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D=
3><SPAN=20
                style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT></=
P>
                <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center"=20
                align=3Dcenter><FONT face=3D"Times New Roman" size=3D3><SPA=
N=20
                style=3D"FONT-SIZE: 12pt">
                <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
                </SPAN></FONT></DIV>
                <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><B><FONT=
=20
                face=3DTahoma size=3D2><SPAN=20
                style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: T=
ahoma">From:</SPAN></FONT></B><FONT=20
                face=3DTahoma size=3D2><SPAN=20
                style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">=20
                ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] <B><SP=
AN=20
                style=3D"FONT-WEIGHT: bold">On Behalf Of </SPAN></B>Wojciec=
h Dec=20
                (wdec)<BR><B><SPAN style=3D"FONT-WEIGHT: bold">Sent:</SPAN>=
</B> 20=20
                April 2008 15:18<BR><B><SPAN=20
                style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Peter Arberg;=20
                ancp@ietf.org<BR><B><SPAN=20
                style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> Re: [ANCP] =
Bulk=20
                Transaction Message</SPAN></FONT><o:p></o:p></P>
                <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
                style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Should also h=
ave=20
                added: Given that currently&nbsp;the bulk message does not=
=20
                appear to have had any practical&nbsp;adoption, having the =
DTeam=20
                adopt it/modify it, or possibly have it removed from the sp=
ec=20
                all together&nbsp;are all valid=20
                options.</SPAN></FONT><o:p></o:p></P>
                <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D=
3><SPAN=20
                style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT></=
P>
                <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
                style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">-Woj.</SPAN><=
/FONT><o:p></o:p></P>
                <BLOCKQUOTE=20
                style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BOR=
DER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: 5pt 0=
in 5pt 3.75pt; BORDER-LEFT: black 1.5pt solid; PADDING-TOP: 0in; BORDER-BOT=
TOM: medium none">
                  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=
=3D3><SPAN=20
                  style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FONT>=
</P>
                  <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center"=20
                  align=3Dcenter><FONT face=3D"Times New Roman" size=3D3><S=
PAN=20
                  style=3D"FONT-SIZE: 12pt">
                  <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D2>
                  </SPAN></FONT></DIV>
                  <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><B><FO=
NT=20
                  face=3DTahoma size=3D2><SPAN=20
                  style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY:=
 Tahoma">From:</SPAN></FONT></B><FONT=20
                  face=3DTahoma size=3D2><SPAN=20
                  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">=20
                  ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] <B><=
SPAN=20
                  style=3D"FONT-WEIGHT: bold">On Behalf Of </SPAN></B>Wojci=
ech Dec=20
                  (wdec)<BR><B><SPAN style=3D"FONT-WEIGHT: bold">Sent:</SPA=
N></B>=20
                  20 April 2008 14:39<BR><B><SPAN=20
                  style=3D"FONT-WEIGHT: bold">To:</SPAN></B> Peter Arberg;=
=20
                  ancp@ietf.org<BR><B><SPAN=20
                  style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> Re: [ANCP=
] Bulk=20
                  Transaction Message</SPAN></FONT><o:p></o:p></P>
                  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
                  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">It's all=20
                  simple:</SPAN></FONT><o:p></o:p></P>
                  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
                  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">-&nbsp;the =
Design=20
                  Team is looking at the possibility of using this=20
                  message</SPAN></FONT><o:p></o:p></P>
                  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
                  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">- the messa=
ge in=20
                  its current form does not appear to be terribly=20
                  u<st1:PersonName w:st=3D"on">se</st1:PersonName>ful, and =
could=20
                  be&nbsp;removed from the spec.</SPAN></FONT><o:p></o:p></=
P>
                  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=
=3D3><SPAN=20
                  style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT>=
</P>
                  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
                  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">-Woj.</SPAN=
></FONT><o:p></o:p></P>
                  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=
=3D3><SPAN=20
                  style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FONT>=
</P>
                  <BLOCKQUOTE=20
                  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; B=
ORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: 5pt=
 0in 5pt 3.75pt; BORDER-LEFT: black 1.5pt solid; PADDING-TOP: 0in; BORDER-B=
OTTOM: medium none">
                    <P class=3DMsoNormal><FONT face=3D"Times New Roman" siz=
e=3D3><SPAN=20
                    style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></FON=
T></P>
                    <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center"=20
                    align=3Dcenter><FONT face=3D"Times New Roman" size=3D3>=
<SPAN=20
                    style=3D"FONT-SIZE: 12pt">
                    <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=3D=
2>
                    </SPAN></FONT></DIV>
                    <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><B><=
FONT=20
                    face=3DTahoma size=3D2><SPAN=20
                    style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMIL=
Y: Tahoma">From:</SPAN></FONT></B><FONT=20
                    face=3DTahoma size=3D2><SPAN=20
                    style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">=20
                    ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org]=20
                    <B><SPAN style=3D"FONT-WEIGHT: bold">On Behalf Of=20
                    </SPAN></B>Peter Arberg<BR><B><SPAN=20
                    style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> 19 April 2=
008=20
                    03:07<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SPAN=
></B>=20
                    Wojciech Dec (wdec); ancp@ietf.org<BR><B><SPAN=20
                    style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> Re: [AN=
CP]=20
                    Bulk Transaction Message</SPAN></FONT><o:p></o:p></P>
                    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue si=
ze=3D2><SPAN=20
                    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Ari=
al">Hi=20
                    Woj,</SPAN></FONT><o:p></o:p></P>
                    <P class=3DMsoNormal><FONT face=3D"Times New Roman" siz=
e=3D3><SPAN=20
                    style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FON=
T></P>
                    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue si=
ze=3D2><SPAN=20
                    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Ari=
al">can=20
                    you give a little background to why you are looking for=
=20
                    vendor</SPAN></FONT><o:p></o:p></P>
                    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue si=
ze=3D2><SPAN=20
                    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Ari=
al">implementation=20
                    support for this specific capability &amp; message=20
                    ?</SPAN></FONT><o:p></o:p></P>
                    <P class=3DMsoNormal><FONT face=3D"Times New Roman" siz=
e=3D3><SPAN=20
                    style=3D"FONT-SIZE: 12pt">&nbsp;<o:p></o:p></SPAN></FON=
T></P>
                    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue si=
ze=3D2><SPAN=20
                    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Ari=
al">thanks,</SPAN></FONT><o:p></o:p></P>
                    <P class=3DMsoNormal><FONT face=3DArial color=3Dblue si=
ze=3D2><SPAN=20
                    style=3D"FONT-SIZE: 10pt; COLOR: blue; FONT-FAMILY: Ari=
al">Peter</SPAN></FONT><o:p></o:p></P>
                    <BLOCKQUOTE=20
                    style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in;=
 BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; MARGIN: 5=
pt 0in 5pt 3.75pt; BORDER-LEFT: blue 1.5pt solid; PADDING-TOP: 0in; BORDER-=
BOTTOM: medium none">
                      <P class=3DMsoNormal><FONT face=3D"Times New Roman"=20
                      size=3D3><SPAN=20
                      style=3D"FONT-SIZE: 12pt"><o:p>&nbsp;</o:p></SPAN></F=
ONT></P>
                      <DIV class=3DMsoNormal style=3D"TEXT-ALIGN: center"=20
                      align=3Dcenter><FONT face=3D"Times New Roman" size=3D=
3><SPAN=20
                      style=3D"FONT-SIZE: 12pt">
                      <HR tabIndex=3D-1 align=3Dcenter width=3D"100%" SIZE=
=3D2>
                      </SPAN></FONT></DIV>
                      <P class=3DMsoNormal style=3D"MARGIN-BOTTOM: 12pt"><B=
><FONT=20
                      face=3DTahoma size=3D2><SPAN=20
                      style=3D"FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAM=
ILY: Tahoma">From:</SPAN></FONT></B><FONT=20
                      face=3DTahoma size=3D2><SPAN=20
                      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">=20
                      ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org]=
=20
                      <B><SPAN style=3D"FONT-WEIGHT: bold">On Behalf Of=20
                      </SPAN></B>Wojciech Dec (wdec)<BR><B><SPAN=20
                      style=3D"FONT-WEIGHT: bold">Sent:</SPAN></B> 18. apri=
l 2008=20
                      08:04<BR><B><SPAN style=3D"FONT-WEIGHT: bold">To:</SP=
AN></B>=20
                      ancp@ietf.org<BR><B><SPAN=20
                      style=3D"FONT-WEIGHT: bold">Subject:</SPAN></B> [ANCP=
] Bulk=20
                      Transaction Message</SPAN></FONT><o:p></o:p></P>
                      <P><FONT face=3DArial size=3D2><SPAN lang=3DEN-GB=20
                      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"><!-- Co=
nverted from text/rtf format -->Hi=20
                      Folks,</SPAN></FONT><SPAN lang=3DEN-GB>=20
                      </SPAN><o:p></o:p></P>
                      <P><FONT face=3DArial size=3D2><SPAN lang=3DEN-GB=20
                      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Could y=
ou=20
                      plea<st1:PersonName w:st=3D"on">se</st1:PersonName> l=
et=20
                      me/us know if you currently have an implementation of=
 ANCP=20
                      that supports the Bulk Transaction Capability and=20
                      Message?</SPAN></FONT><o:p></o:p></P>
                      <P><FONT face=3DArial size=3D2><SPAN lang=3DEN-GB=20
                      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Thanks,=
</SPAN></FONT>=20
                      <BR><FONT face=3DArial size=3D2><SPAN lang=3DEN-GB=20
                      style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Woj.</S=
PAN></FONT><SPAN=20
                      lang=3DEN-GB>=20
                </SPAN><o:p></o:p></P></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOT=
E></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQ=
UOTE></BLOCKQUOTE></DIV></BLOCKQUOTE></BODY></HTML>

--_000_48C276B536524E478C659685995F6AA560439CC78BRBSJXadredbac_--

--===============1765829207==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1765829207==--


From ancp-bounces@ietf.org  Thu May  8 17:15:36 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 1A3303A6EAA;
	Thu,  8 May 2008 17:15:36 -0700 (PDT)
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 055903A67FE
	for <ancp@core3.amsl.com>; Thu,  8 May 2008 17:15:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.109
X-Spam-Level: *
X-Spam-Status: No, score=1.109 tagged_above=-999 required=5 tests=[AWL=1.294, 
	BAYES_40=-0.185]
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 bpx6GEAUSWsw for <ancp@core3.amsl.com>;
	Thu,  8 May 2008 17:15:29 -0700 (PDT)
Received: from prattle.redback.com (prattle.redback.com [155.53.12.9])
	by core3.amsl.com (Postfix) with ESMTP id 8AAB23A6ED8
	for <ancp@ietf.org>; Thu,  8 May 2008 17:15:29 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by prattle.redback.com (Postfix) with ESMTP id 14A93C2F0B4;
	Thu,  8 May 2008 17:15:28 -0700 (PDT)
Received: from prattle.redback.com ([127.0.0.1])
	by localhost (prattle [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
	id 07307-05; Thu,  8 May 2008 17:15:27 -0700 (PDT)
Received: from rbsjx.ad.redback.com (rbsjxh1.redback.com [155.53.14.105])
	by prattle.redback.com (Postfix) with ESMTP id 0521EC2F0B2;
	Thu,  8 May 2008 17:15:27 -0700 (PDT)
Received: from RBSJX.ad.redback.com ([155.53.14.103]) by
	rbsjxh1.ad.redback.com ([155.53.14.105]) with mapi;
	Thu, 8 May 2008 17:15:26 -0700
From: Peter Arberg <parberg@redback.com>
To: "Wojciech Dec (wdec)" <wdec@cisco.com>,
	Ole Helleberg Andersen <ole.helleberg.andersen@ericsson.com>,
	Sanjay Wadhwa <swadhwa@juniper.net>, Tina TSOU <tena@huawei.com>,
	Maglione Roberta <roberta.maglione@telecomitalia.it>
Date: Thu, 8 May 2008 17:15:23 -0700
Thread-Topic: [ANCP] question regarding  Labels in ANCP port up messages
Thread-Index: Aciqkn5nSPBPuwuySsamcvxF1uU6kQAZ9dQQAAE415AABe3TAABN80lQAA1w7OAAutMtAAAtn1MQAE7htiA=
Message-ID: <48C276B536524E478C659685995F6AA560439CC824@RBSJX.ad.redback.com>
References: <48C276B536524E478C659685995F6AA539DBBBE370@RBSJX.ad.redback.com><9BD5D7887235424FA97DFC223CAE3C280AB43A10@proton.jnpr.net><48C276B536524E478C659685995F6AA539DBBBE577@RBSJX.ad.redback.com><9BD5D7887235424FA97DFC223CAE3C28102EB5AA@proton.jnpr.net>
	<48C276B536524E478C659685995F6AA539DBBBEF99@RBSJX.ad.redback.com>
	<BAC301C0C1697C4EBDF97C805A273CBC9909C5@esealmw104.eemea.ericsson.se>
	<D9872168DBD43A41BD71FFC4713274D405043B12@xmb-ams-33b.emea.cisco.com>
In-Reply-To: <D9872168DBD43A41BD71FFC4713274D405043B12@xmb-ams-33b.emea.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-Virus-Scanned: by amavisd-new at redback.com
Cc: "ancp@ietf.org" <ancp@ietf.org>
Subject: Re: [ANCP] question regarding  Labels in ANCP port up messages
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org

Hi Woj,

I think your proposal goes hand in hand with my suggestion to document the
event message bit by bit instead of reference the RFC3292 or an expired old
gsmp-draft.

I will suggest we in the ANCP draft do a description in section
5.4.2 something in these lines:

The ANCP Event message with PORT UP message type (80) is used for
conveying DSL line attributes to the NAS, and is defined as follows:


0                   1                   2                   3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Vers  |  Sub  | Message Type  | Result|        Code           |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID  |            Transaction Identifier             |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I|      SubMessage Number      |           Length              |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                             Port                              |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                      Port Session Number                      |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                     Event Sequence Number                     |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|S|x|x|                                                       |
+-+-+-+-+                     Label                             |
|                                                               |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|x|x|x|x|x|x|x| Message Type  |   Tech Type   | Block Length  |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                                                               |
~                         Extension Value                       ~
|                                                               |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+


Version field is 1 byte, 4 bits for the major version and 4
bits for the sub-version, should be set to 3, and the sub field
should be set to 1.

Message Type is 1 byte, and can have the following values:
...

Result ...

Code ...

Partition ID ...

....


Label field is 8 bytes, should be set to 0 on transmit and ignored on receive.

....

So the idea is to document every single field in the event message,
and list what is the expected transmit value, and what should the
receiver do with the field.


I will actually suggest we remove the "label" name and just call the
unused field "reserved" and must be set to 0 on transmit and ignored on
receive.

If we simply call them "reserved" we always have the option to reuse them
in alater contribution / new version if theer ever should be a need to
use some bits in the event message header.


Also as another comment, I still think it will be beneficial if we
describe that the version number check should be per adjacency, so
we in the future can do a version change easy and allow the ANCP
implementation to have multiple adjacency with different versions of the
protocol, if we ever see a reason to increase the version number it
will give a much easier upgrade scenario.

cheers,
Peter


cheers,
Peter




________________________________

        From: Wojciech Dec (wdec) [mailto:wdec@cisco.com]
        Sent: 7. maj 2008 14:14
        To: Ole Helleberg Andersen; Peter Arberg; Sanjay Wadhwa; Tina TSOU; Maglione Roberta
        Cc: ancp@ietf.org
        Subject: RE: [ANCP] question regarding Labels in ANCP port up messages


        Hi All,

        it's with a certain amount of incredulity that I view the proposals on this thread for changing the version number of the protocol. Were such proposals to be accepted, by definition it would make most likely the ANCP draft incompatible with *all* current implementations, or at the very least introduce a compatibility mess in existing deployments short of a flag day change over, not to mention the issue of depreciating the old version.
        There really seems to be no reason to go through with a version change due to what may be attributed as a day 1 draft problem but *not* a day 1 implementation problem. Also, it is not the first time that the protocol spec draft has had some inaccuracies, and we've visited this aspect previously resulting in the following versioning strategy being laid out: http://www.ietf.org/mail-archive/web/ancp/current/msg00152.html . While the strategy states that an ANCP version change will not be considered due to "incompatibilities arising from implementations of pre-RFC drafts", neither does it state that the draft cannot change to reflect current implementations while keeping the version.

        Now, given that there seems to be some uneasiness (but thankfully not absolute) in the WG to come forward publicly with details of what is currently implemented, I have conducted a behind the scenes investigation of sorts, and present the summarized findings below:
        - There are 10 distinct implementations of ANCP
        - Out of these 9 either directly implement the label field format in as per section 5.3 of draft-gsmpv3-base-spec-08, or each is known to be compatible with at least 2 implementations that do so. By association, it seems reasonable to claim that all of these ANCP implementations use the draft-gsmpv3-base-spec-08 format. Also, all use version 3.1 as the protocol version, and the base protocol header also as per draft-gsmpv3-base-spec-08
        - One implementation is known to use the draft-ietf-ancp-protocol-02 format of the label field format, ie the rfc3292 format. This implementation is not known to be compatible with any of the others.

        Based on this, but not only, the obvious answer to the problem is *not* to do a version change, but rather fix the draft. Granted, this is a far from ideal situation for the one implementation affected, and it's a true shame that the problem wasn't spotted earlier. Like Peter I also wonder how any interop was achieved, but the fact that it is there is a significant one that should not be undone by hasty version changes. As such option 2 below is not one we'll be taking forward. Option 1 however also comes short as it does not quite follow the logic of simply documenting what is known to be interoperable in the WG draft. If specific implementations choose to realize knobs or other, fine, but this is not part of the protocol spec, and there is no such thing as "old label format". Please do consider the third option, ie fixing the draft to reflect what is already done.

        This fact in general highlights the problems we're having in carrying with the GSMPv3 (rfc3292) legacy, alongside adopted amendments from draft-gsmpv3-base-spec (this Label issue not being the only adopted item), alongside new protocol work. I trust that all of you agree that getting maximum clarity on all the legacy issues and dependencies in the protocol spec is in the WG's best interest, and that we are still some way off from that. As such I also expect the WG to support moves/proposals aimed at getting that clarity, with resolving this issue being not the first and not the last such move.

        Regards,
        Woj.





________________________________

                From: Ole Helleberg Andersen [mailto:ole.helleberg.andersen@ericsson.com]
                Sent: 06 May 2008 14:04
                To: Peter Arberg; Sanjay Wadhwa; Tina TSOU; Maglione Roberta; Wojciech Dec (wdec)
                Cc: ancp@ietf.org
                Subject: RE: [ANCP] question regarding Labels in ANCP port up messages


                Hi All,

                                I think the main issue is to ensure interoperability with existing implementations, and to allow for upgrading nodes that are already in service to a WG-draft compliant version. To do that in a manageable way we must allow for version negotiation per adjacency. We therefore need to change the WG-draft as suggested by Sanjay in his option 2.

                Concerning the encoding issue I prefer to make the WG-draft in line with existing implementations. However, if the WG decides to change it, differences in this encoding would also be solved by choosing Sanjay's option 2.

                Cheers,
                Ole

________________________________

                From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of Peter Arberg
                Sent: 2. maj 2008 20:52
                To: Sanjay Wadhwa; Tina TSOU; Maglione Roberta; Wojciech Dec (wdec)
                Cc: ancp@ietf.org
                Subject: Re: [ANCP] question regarding Labels in ANCP port up messages


                Hi Sanjay,

                yes apparently I missed your point in the last email, but I'm glad we agree something is needed
                to make existing ANCP implementations and the current draft to co-exist.

                I do not like your option 1) as if you need a config knob for interoperability, it is too easy to
                get into trouble.

                I think option 2) is the best way forward with the differences already identified, or we can
                continue to get a show of hands of ANCP implementations, and see if anyone is actually
                deployed based on the WG-draft.

                There is no beneficial reasons to base the event-message of RFC3292, it could as well be a message
                described bit by bit in the ANCP draft, and then we can keep the label space at 8 as many
                implementations alreday do.

                cheers,
                Peter





________________________________

                        From: Sanjay Wadhwa [mailto:swadhwa@juniper.net]
                        Sent: 2. maj 2008 05:35
                        To: Peter Arberg; Tina TSOU; Maglione Roberta; Wojciech Dec (wdec)
                        Cc: ancp@ietf.org
                        Subject: RE: [ANCP] question regarding Labels in ANCP port up messages



                        Peter

                         You missed my point below. The ANCP draft since becoming a WG draft does NOT refer to the old GSMP drafts. Any implementations based on this WG-draft are expected to be interoperable. You are pointing to pre-WG-draft versions of ANCP, and these were indeed based on expired GSMP drafts that evolved past RFC3292.

                        There is incompatibility between the current ANCP WG-draft and previous non-WG versions (TLV clash, label format..). As mentioned earlier it is prudent for older implementations to start supporting the WG-draft version as soon as possible.



                        For interoperability of WG-draft with the older pre-WG versions, I see the following options:



                        1. Versioning starts with the WG-draft i.e. WG-draft is version = 3, sub-version = 1. For any interop issues between older non-WG versions and the WG-draft, one needs to look at solving it within implementations (e.g. an AN that implements the WG-draft, could based on a configuration knob, generate a PORT-UP message with old label format the will be accepted by BNG implementing pre-WG versions of the draft).



                        2. Change the WG-draft (current draft) to use version = 3 and sub-version = 2. This is assuming there is no deployed implementation of current WG-draft that already uses 3.1 as the version, and also assuming the old pre-WG implementations use 3.1. There will be no backwards compatibility i.e. version 3.1 BNG will not work with version 3.2 AN (we will need to list this as caveat in the appendix section). AN and BNG will need to negotiate the same version in order for ANCP adjacency to come up. A BNG supporting both versions 3.1 and 3.2 could simultaneously become adjacent with one AN supporting 3.1 and another AN supporting 3.2. (i.e. version compatibility is per adjacency).

                        Also, major version number change (e.g. from 3 to 4) should only correspond to a major change in the protocol (e.g. different mechanism, different transport etc).



                        My vote would be to adopt option 2 above only if further changes to WG-draft happen that render it incompatible with the current WG-draft. Any interoperability issues with pre-WG versions could be handled via option 1.



                        Cheers

                        -Sanjay



                        ________________________________

                                                From: Peter Arberg [mailto:parberg@redback.com]
                        Sent: Wednesday, April 30, 2008 7:20 PM
                        To: Sanjay Wadhwa; Tina TSOU; Maglione Roberta; Wojciech Dec (wdec)
                        Cc: ancp@ietf.org
                        Subject: RE: [ANCP] question regarding Labels in ANCP port up messages



                        Sanjay,



                        What do you mean "why I reference an old draft"  ????????????



                        I'm surprised you even ask...  please take a look at YOUR own internet-draft that most

                        of the ANCP working implementations are based on, in case you do not have this old

                        internet-draft, I have attached it to the document.



                        If you look at the reference for this ancp-draft, you will see that in the reference section

                        you point to this old gsmp-draft...  Yes and I know this has been changed in the later

                        versions of the ANCP draft, but that do not change the fact that many of the implementations

                        today was developed when the attached draft was current.



                        I think a very good question is brought up here, and that is what is implemented and

                        running in networks today ?



                        My take on this is that when the reference was change from the old gsmp-draft to the older

                        RFC3292, apparently no one paid any attention to the fact the label definition in the event

                        message was different and not compatible.



                        What current implementations do today is an important factor in this discussion, and I think

                        it is time to come to realization that we might need a new version number for ANCP since

                        it continues to look like there is big holes open for interpretation. So if I did a ANCP

                        implementation there is bound to be interoperability issues with existing implementations

                        runnig.



                        cheers,

                        Peter









                                ________________________________

                                                                From: Sanjay Wadhwa [mailto:swadhwa@juniper.net]
                                Sent: 30. april 2008 14:42
                                To: Peter Arberg; Tina TSOU; Maglione Roberta; Wojciech Dec (wdec)
                                Cc: ancp@ietf.org
                                Subject: RE: [ANCP] question regarding Labels in ANCP port up messages

                                Peter
                                  The ANCP draft as it currently stands is based on RFC3292. It provides extensions and modifications to relevant constructs in RFC3292. There is no mention (implicit or explicit) of expired GSMP drafts in the ANCP draft. In order to implement the ANCP draft, I am not sure why one would look at the expired GSMP drafts. Do you see a reason to do this based on anything that you read in the ANCP draft? Bringing up reference to expired gsmp draft in this thread just adds to the confusion. For GSMPv3 objects in the messages (such as Label Type), one has to look at RFC3292 (this is clearly stated in the ANCP draft - section 2 and I am quoting it below) :

                                ANCP uses a subset of GSMPv3 messages to implement currently defined use-cases. These relevant GSMPv3 messages are identified in section 5. GSMPv3 procedures with suitable extensions, as used by ANCP, are described in sections 5.1, 5.2 and 5.3. GSMPv3 general extensions and GSMPv3 message specific extensions required by ANCP are described in sub-sections of 5.4. In addition to specifying extensions and modifications to relevant GSMP messages applicable to ANCP, this draft also defines the usage of these messages by ANCP, and indicates the values that ANCP should set for relevant fields in these GSMP messages. However, to understand the basic semantics of various fields in GSMP messages, the reader is referred to [4]. => RFC 3292.

                                What existing implementations currently do is an important but separate issue. These implementations for most part precede the current ANCP draft. It is fine to poll where these implementations diverge from the current draft. It is then upto the implementations (including the one that I am somewhat familiar with) to work towards compliance with the draft.

                                On the following points from  Woj:

                                Woj>2) The current version of the spec is not accurate, and does not reflect the fact that the known implementations follow the label field definition from draft-gsmpv3-base-spec.

                                It is not for the protocol draft to point out what current implementations do.  The best we can do is to further clarify in the draft that type and value fields of the Label object (defined in RFC3292) should be set to 0 in the port-up message (we already mention the lable object as a whole should be set to all 0s).

                                Woj> This would be a good thing for the WG to discuss. There most evidently is a fair amount of "dead wood" in the current spec, ie stuff that nobody yet implements or cares about.  In the former case, we could re-cast that material using the new notions/extensions, in the latter case simply chop it out.

                                I agree. We are based on GSMPv3 (RFC3292)  messages, and obviously not everything in these messages is leveraged by ANCP.  However, the sync rate and OAM uses-cases are implemented and in use (ideally we should leave these alone...i.e. no change beyond adding more clarity if needed). For anything new (such as multicast) we are defining new messages (no legacy).

                                -Sanjay

                                >-----Original Message-----
                                >From: Peter Arberg [mailto:parberg@redback.com <mailto:parberg@redback.com> ]
                                >Sent: Wednesday, April 30, 2008 3:56 PM
                                >To: Tina TSOU; Maglione Roberta; Sanjay Wadhwa; Wojciech Dec (wdec)
                                >Cc: ancp@ietf.org
                                >Subject: RE: [ANCP] question regarding Labels in ANCP port up messages
                                >
                                >
                                >Hi,
                                >
                                >some times I think it is amazing we ever got interoperability
                                >of ANCP :-)
                                >because looking at the label discussion is a very good example that the
                                >whole GSMP - ANCP reference have not worked very well.
                                >
                                >In the ANCP draft, section 5.4.2 the event message is shown like this:
                                >
                                >0                   1                   2                   3
                                >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
                                >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >| Vers  |  Sub  | Message Type  | Result|        Code           |
                                >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >| Partition ID  |            Transaction Identifier             |
                                >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >|I|      SubMessage Number      |           Length              |
                                >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >|                             Port                              |
                                >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >|                      Port Session Number                      |
                                >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >|                     Event Sequence Number                     |
                                >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >|x|S|x|x|                                                       |
                                >+-+-+-+-+                     Label                             |
                                >~                                                               ~
                                >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >|x|x|x|x|x|x|x|x| Message Type  |   Tech Type   | Block Length  |
                                >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >|                                                               |
                                >~                         Extension Value                       ~
                                >|                                                               |
                                >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >
                                >
                                >This is the exact same event message defined in
                                >draft-ietf-gsmp-v3-base-spec-08.txt  section 11.
                                >
                                >And in this gsmp-draft, section 5.1.3 the label space is defined
                                >as minimum 8 bytes if the length=0 and as such no value, and this
                                >is because the gsmp-draft has a new "label adaptaion" field.
                                >
                                >
                                >
                                >BUT in RFC3292 the event message is show in section 9, like this:
                                >
                                >0                   1                   2                   3
                                >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
                                >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >|    Version    | Message Type  |    Result     |     Code      |
                                >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >| Partition ID  |            Transaction Identifier             |
                                >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >|I|      SubMessage Number      |           Length              |
                                >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >|                             Port                              |
                                >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >|                      Port Session Number                      |
                                >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >|                     Event Sequence Number                     |
                                >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >|x|S|x|x|                                                       |
                                >+-+-+-+-+                     Label                             |
                                >~                                                               ~
                                >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >
                                >
                                >So a different Event Message picture/definition than what is shown
                                >in the ANCP draft, and in RFC3292 section 3.1.3 the label field
                                >is defined as 4 bytes if length=0 and as such no value.
                                >
                                >
                                >
                                >So I very much agree with Woj that we need this issue to be resolved,
                                >and proabably a show of hands what is actually done in different
                                >implementations, so we can nail down how the event message is
                                >suppose to look like in ANCP.
                                >
                                >
                                >I know at least 1 implementation which uses 8 bytes for the
                                >label field.
                                >
                                >
                                >cheers,
                                >Peter
                                >
                                >
                                >
                                >
                                >
                                >
                                >________________________________
                                >
                                >        From: ancp-bounces@ietf.org
                                >[mailto:ancp-bounces@ietf.org <mailto:ancp-bounces@ietf.org> ] On Behalf Of Tina TSOU
                                >        Sent: 30. april 2008 00:19
                                >        To: Maglione Roberta; Sanjay Wadhwa; Wojciech Dec (wdec)
                                >        Cc: ancp@ietf.org
                                >        Subject: Re: [ANCP] question regarding Labels in ANCP
                                >port up messages
                                >
                                >
                                >        Hi all,
                                >        It is clear to me that if Label Length is filled as 0,
                                >there is nothing to be filled into Label Value. The whole
                                >Label part is 4 bytes, not 8 bytes.
                                >
                                >        Cheers from the last working day before Labor's Day
                                >holidays in some countries:)
                                >
                                >        Tina
                                >
                                >                ----- Original Message -----
                                >                From: Wojciech Dec (wdec) <mailto:wdec@cisco.com <mailto:wdec@cisco.com> >
                                >                To: Sanjay Wadhwa <mailto:swadhwa@juniper.net <mailto:swadhwa@juniper.net> >
                                > ; Maglione Roberta <mailto:roberta.maglione@telecomitalia.it <mailto:roberta.maglione@telecomitalia.it> >
                                >                Cc: ancp@ietf.org
                                >                Sent: Wednesday, April 30, 2008 1:12 AM
                                >                Subject: Re: [ANCP] question regarding Labels
                                >in ANCP port up messages
                                >
                                >                Sanjay, All,
                                >
                                >                What is stated below runs counter to at least
                                >a handful of ANCP
                                >                implementations, all of which are known to be
                                >interoperable.
                                >                There are really two options:
                                >                1) The current version of the spec is correct,
                                >and the known
                                >                interoperable implementations do not follow it
                                >                2) The current version of the spec is not
                                >accurate, and does not reflect
                                >                the fact that the known implementations follow
                                >the label field
                                >                definition from draft-gsmpv3-base-spec.
                                >
                                >                I would like to ask you, as the lead editor of
                                >the spec, to work with
                                >                the WG in resolving what the problem is, and
                                >clearing up what the WG
                                >                spec says about and if 1) holds to be true,
                                >then proposing an
                                >                interoperability fix.
                                >
                                >                In either case, the issue highlights the fact
                                >that there is still
                                >                lingering confusion as to the dependencies
                                >ANCP has on rfc3292, or
                                >                draft-gsmpv3-base-spec, or both. It seems to
                                >be in the best interest of
                                >                all to address these.
                                >
                                >                Regards,
                                >                Woj.
                                >
                                >                > -----Original Message-----
                                >                > From: Sanjay Wadhwa [mailto:swadhwa@juniper.net <mailto:swadhwa@juniper.net> ]
                                >                > Sent: 29 April 2008 17:29
                                >                > To: Maglione Roberta
                                >                > Cc: Wojciech Dec (wdec); ancp@ietf.org;
                                >Philippe Champagne (pchamp)
                                >                > Subject: RE: question regarding Labels in
                                >ANCP port up messages
                                >                >
                                >                > Hi Maglione
                                >                >   Yes, the label format is as defined in RFC
                                >3292. The ANCP draft is
                                >                > based on RFC 3292 and proposes
                                >extensions/modifications where
                                >                > required.
                                >                > This is clearly stated upfront both in the
                                >abstract and in
                                >                > section 2. In
                                >                > section 5.4.2, it clearly  specifies the
                                >format of "port up" message
                                >                > (based on RFC 3292), and explicitly states
                                >the label field
                                >                > should be set
                                >                > to 0. Following is what the draft currently states:
                                >                >
                                >                >
                                >                > 5.4.2 Topology Discovery Extensions
                                >                >
                                >                > The GSMP Event message with PORT UP message
                                >type (80) is used for
                                >                > conveying DSL line attributes to the NAS.
                                >The version field should be
                                >                > set to 3, and the sub field should be set to
                                >1. The I and subMessage
                                >                > fields SHOULD be set to 1 to signify no
                                >fragmentation. The Port and
                                >                > Label fields should be set to 0.
                                >                >
                                >                >  0                   1                   2
                                >                3
                                >                >          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
                                >                >
                                >                >
                                >                >
                                >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >                >         | Vers  |  Sub  | Message Type  |
                                >Result|        Code
                                >                > |
                                >                >
                                >                >
                                >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >                >         | Partition ID  |
                                >Transaction Identifier
                                >                > |
                                >                >
                                >                >
                                >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >                >         |I|      SubMessage Number      |
                                >       Length
                                >                > |
                                >                >
                                >                >
                                >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >                >         |                             Port
                                >                > |
                                >                >
                                >                >
                                >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >                >         |                      Port Session Number
                                >                > |
                                >                >
                                >                >
                                >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >                >         |                     Event Sequence Number
                                >                > |
                                >                >
                                >                >
                                >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >                >         |x|S|x|x|
                                >                > |
                                >                >         +-+-+-+-+                     Label
                                >                > |
                                >                >         ~
                                >                > ~
                                >                >
                                >                >
                                >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >                >         |x|x|x|x|x|x|x|x| Message Type  |
                                >Tech Type   | Block Length
                                >                > |
                                >                >
                                >                >
                                >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >                >         |
                                >                > |
                                >                >         ~                         Extension Value
                                >                > ~
                                >                >         |
                                >                > |
                                >                >
                                >                >
                                >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >                >
                                >                > When we say the label field should be set to
                                >0, the intention
                                >                > is for the
                                >                > type and length fields in the label TLV to
                                >be set to 0. We can
                                >                > explicitly state this for clarity.
                                >                >
                                >                > -Sanjay
                                >                >
                                >                > >-----Original Message-----
                                >                > >From: Maglione Roberta
                                >[mailto:roberta.maglione@telecomitalia.it <mailto:roberta.maglione@telecomitalia.it> ]
                                >                > >Sent: Tuesday, April 29, 2008 8:06 AM
                                >                > >To: Sanjay Wadhwa
                                >                > >Cc: Wojciech Dec (wdec); ancp@ietf.org;
                                >pchamp@cisco.com
                                >                > >Subject: RE: question regarding Labels in
                                >ANCP port up messages
                                >                > >
                                >                > >
                                >                > >Hi Sanjay and All,
                                >                > >     I was reading the current ancp
                                >protocol draft in order to
                                >                > > understand which should be the correct
                                >format for the label
                                >                > >field in the ancp port Up message.
                                >                > >Actually as it was already pointed out in
                                >the alias the draft
                                >                > >in section 5.4.2 says "GSMP Event message
                                >with PORT UP message
                                >                > >type (80) is used"  thus I am assuming that
                                >the label in the
                                >                > >port UP message should follow the message
                                >format defined in
                                >                > >RFC 3292, section 3.1.3:
                                >                > >
                                >                > >    0                   1
                                >2                   3
                                >                > >    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
                                >                > >
                                >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >                > >   |x|S|x|x|       Label Type      |
                                >  Label Length         |
                                >                > >
                                >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >                > >   |
                                >                       |
                                >                > >   ~                          Label Value
                                >                       ~
                                >                > >   |
                                >                       |
                                >                > >
                                >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >                > >
                                >                > >but from what I have seen different
                                >implementations use
                                >                > >different format for label field: in
                                >particular several
                                >                > >implementations use  a label format that is
                                >similar to the one
                                >                > >specified in the expired draft
                                >draft-ietf-gsmp-v3-base-spec:
                                >                > >
                                >                > >     0                   1
                                > 2                   3
                                >                > >       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
                                >                > >
                                >                >
                                >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >                > >      |x|S|x|x|x|x|x|x|x|x|x|x|x|x|x|x|
                                >       Label
                                >                > Type         |
                                >                > >
                                >                >
                                >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >                > >      |    Label Adaptation           |
                                >     Label
                                >                > Length         |
                                >                > >
                                >                >
                                >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >                > >      |
                                >                >          |
                                >                > >      ~                          Label Value
                                >                >          ~
                                >                > >      |
                                >                >          |
                                >                > >
                                >                >
                                >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >                > >
                                >                > >
                                >                > >Even if ancp does not care about the label
                                >field, having this
                                >                > >field somehow not clearly specified in the
                                >current ancp draft
                                >                > >can easily lead to interoperability issues,
                                >thus I think it
                                >                > >would be very helpful if you and/or the
                                >other editors can
                                >                > >clarify what should be the correct format
                                >for the label field
                                >                > >to be used in the ancp Port Up message.
                                >                > >
                                >                > >Thanks and best regards,
                                >                > >Roberta
                                >                > >
                                >                > >________________________________________
                                >                > >From: Philippe Champagne (pchamp) [pchamp@cisco.com]
                                >                > >Sent: Thursday, April 24, 2008 7:14 PM
                                >                > >To: Sanjay Wadhwa
                                >                > >Cc: Maglione Roberta; Wojciech Dec (wdec);
                                >ancp@ietf.org
                                >                > >Subject: question regarding  Labels in ANCP
                                >port up messages
                                >                > >
                                >                > >Hi Sanjay
                                >                > >
                                >                > >In section 5.4.2 of the draft, we have:
                                >                > >
                                >                > >
                                >                > >         0                   1                   2
                                >                >         3
                                >                > >         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
                                >                > >
                                >                >
                                >>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >                > >        | Vers  |  Sub  | Message Type  |
                                >Result|        Code
                                >                > >         |
                                >                > >
                                >                >
                                >>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >                > >        | Partition ID  |
                                >Transaction Identifier
                                >                > >         |
                                >                > >
                                >                >
                                >>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >                > >        |I|      SubMessage Number      |
                                >        Length
                                >                > >         |
                                >                > >
                                >                >
                                >>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >                > >        |                             Port
                                >                > >         |
                                >                > >
                                >                >
                                >>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >                > >        |                      Port Session Number
                                >                > >         |
                                >                > >
                                >                >
                                >>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >                > >        |                     Event Sequence Number
                                >                > >         |
                                >                > >
                                >                >
                                >>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >                > >        |x|S|x|x|
                                >                > >         |
                                >                > >        +-+-+-+-+                     Label
                                >                > >         |
                                >                > >        ~
                                >                > >         ~
                                >                > >
                                >                >
                                >>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >                > >        |x|x|x|x|x|x|x|x| Message Type  |
                                >Tech Type   |
                                >                > >Block Length  |
                                >                > >
                                >                >
                                >>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >                > >        |
                                >                > >         |
                                >                > >        ~                         Extension Value
                                >                > >         ~
                                >                > >        |
                                >                > >         |
                                >                > >
                                >                >
                                >>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >                > >Where Label I suppose is taken from the RFC
                                >3292, section
                                >                > >3.1.3: (well, I'm guessing)
                                >                > >
                                >                > >   A summary of TLV labels supported in
                                >this version of the
                                >                > protocol is
                                >                > >   listed below:
                                >                > >
                                >                > >      TLV Label      Type       Section Title
                                >                > >      ---------      ----       -------------
                                >                > >      ATM Label      0x100      ATM TLV Labels
                                >                > >      FR Label       0x101      Frame Relay
                                >TLV Labels
                                >                > >      MPLS Gen Label 0x102      MPLS
                                >Generic TLV Labels
                                >                > >      FEC Label      0x103      FEC TLV Labels
                                >                > >
                                >                > >   All Labels will be designated as follow:
                                >                > >
                                >                > >    0                   1
                                >2                   3
                                >                > >    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
                                >                > >
                                >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >                > >   |x|S|x|x|       Label Type      |
                                >  Label Length         |
                                >                > >
                                >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >                > >   |
                                >                       |
                                >                > >   ~                          Label Value
                                >                       ~
                                >                > >   |
                                >                       |
                                >                > >
                                >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >                > >
                                >                > >      x: Reserved Flags.
                                >                > >         These are generally used by
                                >specific messages and will be
                                >                > >         defined in those messages.
                                >                > >
                                >                > >      S: Stacked Label Indicator
                                >                > >         Label Stacking is discussed below
                                >in section 3.1.3.5
                                >                > >
                                >                > >      Label Type
                                >                > >         A 12-bit field indicating the type
                                >of label.
                                >                > >
                                >                > >      Label Length
                                >                > >         A 16-bit field indicating the
                                >length of the Label
                                >                > Value field
                                >                > >         in bytes.
                                >                > >
                                >                > >      Label Value
                                >                > >         A variable length field that is an
                                >integer number of 32 bit
                                >                > >         words long.  The Label Value field
                                >is interpreted
                                >                > according to
                                >                > >         the Label Type as described in the
                                >following sections.
                                >                > >
                                >                > >
                                >                > >The draft is a bit obscure about this and
                                >since it doesn't
                                >                > >specify much, it can lead to
                                >misinterpretation for the unused
                                >                > >part. Moreover, it would appear that
                                >several implementations
                                >                > >currently use another format for the label
                                >field. Can you
                                >                > >explain?  I mean, how come what's in the
                                >current draft doesn't
                                >                > >match what's known to be implemented?
                                >                > >
                                >                > >I'm still wondering why we carried over
                                >pieces from GSMP that
                                >                > >we do not intend to use.
                                >                > >
                                >                > >I would recommend that if we are to keep
                                >them but not use
                                >                > >them, we should mention precisely how we
                                >intend not to use
                                >                > >them: that is how many 0 filled bytes this
                                >is expected to use
                                >                > >
                                >                > >The rfc 3292 doesn't cover the case where
                                >this field is not used.
                                >                > >
                                >                > >Can you shed some ligths on this?
                                >                > >
                                >                > >Thanks
                                >                > >Regards
                                >                > >Phil
                                >                > >
                                >                > >
                                >                > >
                                >                >
                                >>--------------------------------------------------------------------
                                >                > >
                                >                > >CONFIDENTIALITY NOTICE
                                >                > >
                                >                > >This message and its attachments are
                                >addressed solely to the
                                >                > >persons above and may contain confidential
                                >information. If you
                                >                > >have received the message in error, be
                                >informed that any use
                                >                > >of the content hereof is prohibited. Please
                                >return it
                                >                > >immediately to the sender and delete the
                                >message. Should you
                                >                > >have any questions, please contact us by replying to
                                >                > >webmaster@telecomitalia.it.
                                >                > >
                                >                > >        Thank you
                                >                > >
                                >                > >
                                >www.telecomitalia.it
                                >                > >
                                >                >
                                >>--------------------------------------------------------------------
                                >                > >
                                >                > >
                                >                >
                                >                _______________________________________________
                                >                ANCP mailing list
                                >                ANCP@ietf.org
                                >                https://www.ietf.org/mailman/listinfo/ancp <https://www.ietf.org/mailman/listinfo/ancp>
                                >
                                >

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


From ancp-bounces@ietf.org  Fri May  9 03:41:07 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id AABF33A6827;
	Fri,  9 May 2008 03:41:07 -0700 (PDT)
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 5E2DF3A6827
	for <ancp@core3.amsl.com>; Fri,  9 May 2008 03:41:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level: 
X-Spam-Status: No, score=x tagged_above=-999 required=5 tests=[]
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 cgyZl6wP-Kct for <ancp@core3.amsl.com>;
	Fri,  9 May 2008 03:41:05 -0700 (PDT)
Received: from maill.telecomitalia.it (maill.telecomitalia.it [217.169.121.52])
	by core3.amsl.com (Postfix) with ESMTP id 782053A681E
	for <ancp@ietf.org>; Fri,  9 May 2008 03:41:03 -0700 (PDT)
Received: from ptpxch009rm001.idc.cww.telecomitalia.it ([156.54.205.171]) by
	maill.telecomitalia.it with Microsoft SMTPSVC(6.0.3790.1830);
	Fri, 9 May 2008 12:38:25 +0200
Received: from grfhub702rm001.griffon.local ([10.19.3.9]) by
	ptpxch009rm001.idc.cww.telecomitalia.it with Microsoft
	SMTPSVC(6.0.3790.1830); Fri, 9 May 2008 12:38:23 +0200
Received: from GRFMBX702RM001.griffon.local ([10.19.3.19]) by
	grfhub702rm001.griffon.local ([10.19.3.9]) with mapi;
	Fri, 9 May 2008 12:38:18 +0200
Content-Class: urn:content-classes:message
Importance: normal
From: "Maglione Roberta" <roberta.maglione@telecomitalia.it>
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2992
To: "'Tina TSOU'" <tena@huawei.com>,
	"Peter Arberg" <parberg@redback.com>
Date: Fri, 9 May 2008 12:38:17 +0200
Thread-Topic: [ANCP] question regarding  Labels in ANCP port up messages
thread-index: AcixeKXJsPOYgqJNQzGfWojOQqd1mAARSnNA
Message-ID: <A1F769BC58A8B146B2EEA818EAE052A20121E824BD@GRFMBX702RM001.griffon.local>
References: <48C276B536524E478C659685995F6AA539DBBBE370@RBSJX.ad.redback.com>
	<9BD5D7887235424FA97DFC223CAE3C280AB43A10@proton.jnpr.net>
	<48C276B536524E478C659685995F6AA539DBBBE577@RBSJX.ad.redback.com>
	<9BD5D7887235424FA97DFC223CAE3C28102EB5AA@proton.jnpr.net>
	<48C276B536524E478C659685995F6AA539DBBBEF99@RBSJX.ad.redback.com>
	<BAC301C0C1697C4EBDF97C805A273CBC9909C5@esealmw104.eemea.ericsson.se>
	<D9872168DBD43A41BD71FFC4713274D405043B12@xmb-ams-33b.emea.cisco.com>
	<48C276B536524E478C659685995F6AA560439CC824@RBSJX.ad.redback.com>
	<004401c8b178$9ab53d60$ac4c460a@china.huawei.com>
In-Reply-To: <004401c8b178$9ab53d60$ac4c460a@china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-OriginalArrivalTime: 09 May 2008 10:38:23.0246 (UTC)
	FILETIME=[CE4402E0:01C8B1C0]
Cc: ancp@ietf.org
Subject: Re: [ANCP] question regarding  Labels in ANCP port up messages
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/pipermail/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>
Content-Type: multipart/mixed; boundary="===============1387474273=="
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1387474273==
Content-Transfer-Encoding: 7bit
Content-Class: urn:content-classes:message
Content-Language: en-US
Content-Type: multipart/alternative;
	boundary="_000_A1F769BC58A8B146B2EEA818EAE052A20121E824BDGRFMBX702RM00_"

This is a multi-part message in MIME format.

--_000_A1F769BC58A8B146B2EEA818EAE052A20121E824BDGRFMBX702RM00_
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Tina,
   you said that you support Peter's proposal on changing the unused =
field  from "label" to "reserved" , but you did not comment on the =
length of this field.
If my understanding is correct, Peter is also proposing to have a =
"reserved" field of 8 bytes:
"Label field is 8 bytes, should be set to 0 on transmit and ignored on =
receive."

what's your opinion on that?

Regards,
Roberta
________________________________
From: Tina TSOU [mailto:tena@huawei.com]
Sent: Friday, May 09, 2008 4:02 AM
To: Maglione Roberta; Sanjay Wadhwa; Ole Helleberg Andersen; Wojciech =
Dec (wdec); Peter Arberg
Cc: ancp@ietf.org
Subject: Re: [ANCP] question regarding Labels in ANCP port up messages

Dear Peter et al,
Comment in line.

B. R.
Tina
Messengers:
MSN: tinatsou6@hotmail.com<mailto:tinatsou6@hotmail.com>   Yahoo: =
tina_tsou    Skype: tinaTSOU    Jabber: =
tina@jabber.org<mailto:tina@jabber.org>    Google talk: =
tinatsou6@gmail.com<mailto:tinatsou6@gmail.com>
----- Original Message -----
From: Peter Arberg<mailto:parberg@redback.com>
To: Wojciech Dec (wdec)<mailto:wdec@cisco.com> ; Ole Helleberg =
Andersen<mailto:ole.helleberg.andersen@ericsson.com> ; Sanjay =
Wadhwa<mailto:swadhwa@juniper.net> ; Tina TSOU<mailto:tena@huawei.com> ; =
Maglione Roberta<mailto:roberta.maglione@telecomitalia.it>
Cc: ancp@ietf.org<mailto:ancp@ietf.org>
Sent: Friday, May 09, 2008 8:15 AM
Subject: RE: [ANCP] question regarding Labels in ANCP port up messages

Hi Woj,

I think your proposal goes hand in hand with my suggestion to document =
the
event message bit by bit instead of reference the RFC3292 or an expired =
old
gsmp-draft.

I will suggest we in the ANCP draft do a description in section
5.4.2 something in these lines:

The ANCP Event message with PORT UP message type (80) is used for
conveying DSL line attributes to the NAS, and is defined as follows:


0                   1                   2                   3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Vers  |  Sub  | Message Type  | Result|        Code           |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Partition ID  |            Transaction Identifier             |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I|      SubMessage Number      |           Length              |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                             Port                              |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                      Port Session Number                      |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                     Event Sequence Number                     |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|S|x|x|                                                       |
+-+-+-+-+                     Label                             |
|                                                               |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|x|x|x|x|x|x|x|x| Message Type  |   Tech Type   | Block Length  |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                                                               |
~                         Extension Value                       ~
|                                                               |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+


Version field is 1 byte, 4 bits for the major version and 4
bits for the sub-version, should be set to 3, and the sub field
should be set to 1.

Message Type is 1 byte, and can have the following values:
...

Result ...

Code ...

Partition ID ...

....


Label field is 8 bytes, should be set to 0 on transmit and ignored on =
receive.

....

So the idea is to document every single field in the event message,
and list what is the expected transmit value, and what should the
receiver do with the field.


I will actually suggest we remove the "label" name and just call the
unused field "reserved" and must be set to 0 on transmit and ignored on
receive.
[Tina: I really support Peter at this point.]

If we simply call them "reserved" we always have the option to reuse =
them
in alater contribution / new version if theer ever should be a need to
use some bits in the event message header.


Also as another comment, I still think it will be beneficial if we
describe that the version number check should be per adjacency, so
we in the future can do a version change easy and allow the ANCP
implementation to have multiple adjacency with different versions of the
protocol, if we ever see a reason to increase the version number it
will give a much easier upgrade scenario.

cheers,
Peter


cheers,
Peter




________________________________

        From: Wojciech Dec (wdec) [mailto:wdec@cisco.com]
        Sent: 7. maj 2008 14:14
        To: Ole Helleberg Andersen; Peter Arberg; Sanjay Wadhwa; Tina =
TSOU; Maglione Roberta
        Cc: ancp@ietf.org<mailto:ancp@ietf.org>
        Subject: RE: [ANCP] question regarding Labels in ANCP port up =
messages


        Hi All,

        it's with a certain amount of incredulity that I view the =
proposals on this thread for changing the version number of the =
protocol. Were such proposals to be accepted, by definition it would =
make most likely the ANCP draft incompatible with *all* current =
implementations, or at the very least introduce a compatibility mess in =
existing deployments short of a flag day change over, not to mention the =
issue of depreciating the old version.
        There really seems to be no reason to go through with a version =
change due to what may be attributed as a day 1 draft problem but *not* =
a day 1 implementation problem. Also, it is not the first time that the =
protocol spec draft has had some inaccuracies, and we've visited this =
aspect previously resulting in the following versioning strategy being =
laid out: =
http://www.ietf.org/mail-archive/web/ancp/current/msg00152.html . While =
the strategy states that an ANCP version change will not be considered =
due to "incompatibilities arising from implementations of pre-RFC =
drafts", neither does it state that the draft cannot change to reflect =
current implementations while keeping the version.

        Now, given that there seems to be some uneasiness (but =
thankfully not absolute) in the WG to come forward publicly with details =
of what is currently implemented, I have conducted a behind the scenes =
investigation of sorts, and present the summarized findings below:
        - There are 10 distinct implementations of ANCP
        - Out of these 9 either directly implement the label field =
format in as per section 5.3 of draft-gsmpv3-base-spec-08, or each is =
known to be compatible with at least 2 implementations that do so. By =
association, it seems reasonable to claim that all of these ANCP =
implementations use the draft-gsmpv3-base-spec-08 format. Also, all use =
version 3.1 as the protocol version, and the base protocol header also =
as per draft-gsmpv3-base-spec-08
        - One implementation is known to use the =
draft-ietf-ancp-protocol-02 format of the label field format, ie the =
rfc3292 format. This implementation is not known to be compatible with =
any of the others.

        Based on this, but not only, the obvious answer to the problem =
is *not* to do a version change, but rather fix the draft. Granted, this =
is a far from ideal situation for the one implementation affected, and =
it's a true shame that the problem wasn't spotted earlier. Like Peter I =
also wonder how any interop was achieved, but the fact that it is there =
is a significant one that should not be undone by hasty version changes. =
As such option 2 below is not one we'll be taking forward. Option 1 =
however also comes short as it does not quite follow the logic of simply =
documenting what is known to be interoperable in the WG draft. If =
specific implementations choose to realize knobs or other, fine, but =
this is not part of the protocol spec, and there is no such thing as =
"old label format". Please do consider the third option, ie fixing the =
draft to reflect what is already done.

        This fact in general highlights the problems we're having in =
carrying with the GSMPv3 (rfc3292) legacy, alongside adopted amendments =
from draft-gsmpv3-base-spec (this Label issue not being the only adopted =
item), alongside new protocol work. I trust that all of you agree that =
getting maximum clarity on all the legacy issues and dependencies in the =
protocol spec is in the WG's best interest, and that we are still some =
way off from that. As such I also expect the WG to support =
moves/proposals aimed at getting that clarity, with resolving this issue =
being not the first and not the last such move.

        Regards,
        Woj.





________________________________

                From: Ole Helleberg Andersen =
[mailto:ole.helleberg.andersen@ericsson.com]
                Sent: 06 May 2008 14:04
                To: Peter Arberg; Sanjay Wadhwa; Tina TSOU; Maglione =
Roberta; Wojciech Dec (wdec)
                Cc: ancp@ietf.org<mailto:ancp@ietf.org>
                Subject: RE: [ANCP] question regarding Labels in ANCP =
port up messages


                Hi All,

                                I think the main issue is to ensure =
interoperability with existing implementations, and to allow for =
upgrading nodes that are already in service to a WG-draft compliant =
version. To do that in a manageable way we must allow for version =
negotiation per adjacency. We therefore need to change the WG-draft as =
suggested by Sanjay in his option 2.

                Concerning the encoding issue I prefer to make the =
WG-draft in line with existing implementations. However, if the WG =
decides to change it, differences in this encoding would also be solved =
by choosing Sanjay's option 2.

                Cheers,
                Ole

________________________________

                From: =
ancp-bounces@ietf.org<mailto:ancp-bounces@ietf.org> =
[mailto:ancp-bounces@ietf.org] On Behalf Of Peter Arberg
                Sent: 2. maj 2008 20:52
                To: Sanjay Wadhwa; Tina TSOU; Maglione Roberta; Wojciech =
Dec (wdec)
                Cc: ancp@ietf.org<mailto:ancp@ietf.org>
                Subject: Re: [ANCP] question regarding Labels in ANCP =
port up messages


                Hi Sanjay,

                yes apparently I missed your point in the last email, =
but I'm glad we agree something is needed
                to make existing ANCP implementations and the current =
draft to co-exist.

                I do not like your option 1) as if you need a config =
knob for interoperability, it is too easy to
                get into trouble.

                I think option 2) is the best way forward with the =
differences already identified, or we can
                continue to get a show of hands of ANCP implementations, =
and see if anyone is actually
                deployed based on the WG-draft.

                There is no beneficial reasons to base the event-message =
of RFC3292, it could as well be a message
                described bit by bit in the ANCP draft, and then we can =
keep the label space at 8 as many
                implementations alreday do.

                cheers,
                Peter





________________________________

                        From: Sanjay Wadhwa [mailto:swadhwa@juniper.net]
                        Sent: 2. maj 2008 05:35
                        To: Peter Arberg; Tina TSOU; Maglione Roberta; =
Wojciech Dec (wdec)
                        Cc: ancp@ietf.org<mailto:ancp@ietf.org>
                        Subject: RE: [ANCP] question regarding Labels in =
ANCP port up messages



                        Peter

                         You missed my point below. The ANCP draft since =
becoming a WG draft does NOT refer to the old GSMP drafts. Any =
implementations based on this WG-draft are expected to be interoperable. =
You are pointing to pre-WG-draft versions of ANCP, and these were indeed =
based on expired GSMP drafts that evolved past RFC3292.

                        There is incompatibility between the current =
ANCP WG-draft and previous non-WG versions (TLV clash, label format..). =
As mentioned earlier it is prudent for older implementations to start =
supporting the WG-draft version as soon as possible.



                        For interoperability of WG-draft with the older =
pre-WG versions, I see the following options:



                        1. Versioning starts with the WG-draft i.e. =
WG-draft is version =3D 3, sub-version =3D 1. For any interop issues =
between older non-WG versions and the WG-draft, one needs to look at =
solving it within implementations (e.g. an AN that implements the =
WG-draft, could based on a configuration knob, generate a PORT-UP =
message with old label format the will be accepted by BNG implementing =
pre-WG versions of the draft).



                        2. Change the WG-draft (current draft) to use =
version =3D 3 and sub-version =3D 2. This is assuming there is no =
deployed implementation of current WG-draft that already uses 3.1 as the =
version, and also assuming the old pre-WG implementations use 3.1. There =
will be no backwards compatibility i.e. version 3.1 BNG will not work =
with version 3.2 AN (we will need to list this as caveat in the appendix =
section). AN and BNG will need to negotiate the same version in order =
for ANCP adjacency to come up. A BNG supporting both versions 3.1 and =
3.2 could simultaneously become adjacent with one AN supporting 3.1 and =
another AN supporting 3.2. (i.e. version compatibility is per =
adjacency).

                        Also, major version number change (e.g. from 3 =
to 4) should only correspond to a major change in the protocol (e.g. =
different mechanism, different transport etc).



                        My vote would be to adopt option 2 above only if =
further changes to WG-draft happen that render it incompatible with the =
current WG-draft. Any interoperability issues with pre-WG versions could =
be handled via option 1.



                        Cheers

                        -Sanjay



                        ________________________________

                                                From: Peter Arberg =
[mailto:parberg@redback.com]
                        Sent: Wednesday, April 30, 2008 7:20 PM
                        To: Sanjay Wadhwa; Tina TSOU; Maglione Roberta; =
Wojciech Dec (wdec)
                        Cc: ancp@ietf.org<mailto:ancp@ietf.org>
                        Subject: RE: [ANCP] question regarding Labels in =
ANCP port up messages



                        Sanjay,



                        What do you mean "why I reference an old draft"  =
????????????



                        I'm surprised you even ask...  please take a =
look at YOUR own internet-draft that most

                        of the ANCP working implementations are based =
on, in case you do not have this old

                        internet-draft, I have attached it to the =
document.



                        If you look at the reference for this =
ancp-draft, you will see that in the reference section

                        you point to this old gsmp-draft...  Yes and I =
know this has been changed in the later

                        versions of the ANCP draft, but that do not =
change the fact that many of the implementations

                        today was developed when the attached draft was =
current.



                        I think a very good question is brought up here, =
and that is what is implemented and

                        running in networks today ?



                        My take on this is that when the reference was =
change from the old gsmp-draft to the older

                        RFC3292, apparently no one paid any attention to =
the fact the label definition in the event

                        message was different and not compatible.



                        What current implementations do today is an =
important factor in this discussion, and I think

                        it is time to come to realization that we might =
need a new version number for ANCP since

                        it continues to look like there is big holes =
open for interpretation. So if I did a ANCP

                        implementation there is bound to be =
interoperability issues with existing implementations

                        runnig.



                        cheers,

                        Peter









                                ________________________________

                                                                From: =
Sanjay Wadhwa [mailto:swadhwa@juniper.net]
                                Sent: 30. april 2008 14:42
                                To: Peter Arberg; Tina TSOU; Maglione =
Roberta; Wojciech Dec (wdec)
                                Cc: ancp@ietf.org<mailto:ancp@ietf.org>
                                Subject: RE: [ANCP] question regarding =
Labels in ANCP port up messages

                                Peter
                                  The ANCP draft as it currently stands =
is based on RFC3292. It provides extensions and modifications to =
relevant constructs in RFC3292. There is no mention (implicit or =
explicit) of expired GSMP drafts in the ANCP draft. In order to =
implement the ANCP draft, I am not sure why one would look at the =
expired GSMP drafts. Do you see a reason to do this based on anything =
that you read in the ANCP draft? Bringing up reference to expired gsmp =
draft in this thread just adds to the confusion. For GSMPv3 objects in =
the messages (such as Label Type), one has to look at RFC3292 (this is =
clearly stated in the ANCP draft - section 2 and I am quoting it below) =
:

                                ANCP uses a subset of GSMPv3 messages to =
implement currently defined use-cases. These relevant GSMPv3 messages =
are identified in section 5. GSMPv3 procedures with suitable extensions, =
as used by ANCP, are described in sections 5.1, 5.2 and 5.3. GSMPv3 =
general extensions and GSMPv3 message specific extensions required by =
ANCP are described in sub-sections of 5.4. In addition to specifying =
extensions and modifications to relevant GSMP messages applicable to =
ANCP, this draft also defines the usage of these messages by ANCP, and =
indicates the values that ANCP should set for relevant fields in these =
GSMP messages. However, to understand the basic semantics of various =
fields in GSMP messages, the reader is referred to [4]. =3D> RFC 3292.

                                What existing implementations currently =
do is an important but separate issue. These implementations for most =
part precede the current ANCP draft. It is fine to poll where these =
implementations diverge from the current draft. It is then upto the =
implementations (including the one that I am somewhat familiar with) to =
work towards compliance with the draft.

                                On the following points from  Woj:

                                Woj>2) The current version of the spec =
is not accurate, and does not reflect the fact that the known =
implementations follow the label field definition from =
draft-gsmpv3-base-spec.

                                It is not for the protocol draft to =
point out what current implementations do.  The best we can do is to =
further clarify in the draft that type and value fields of the Label =
object (defined in RFC3292) should be set to 0 in the port-up message =
(we already mention the lable object as a whole should be set to all =
0s).

                                Woj> This would be a good thing for the =
WG to discuss. There most evidently is a fair amount of "dead wood" in =
the current spec, ie stuff that nobody yet implements or cares about.  =
In the former case, we could re-cast that material using the new =
notions/extensions, in the latter case simply chop it out.

                                I agree. We are based on GSMPv3 =
(RFC3292)  messages, and obviously not everything in these messages is =
leveraged by ANCP.  However, the sync rate and OAM uses-cases are =
implemented and in use (ideally we should leave these alone...i.e. no =
change beyond adding more clarity if needed). For anything new (such as =
multicast) we are defining new messages (no legacy).

                                -Sanjay

                                >-----Original Message-----
                                >From: Peter Arberg =
[mailto:parberg@redback.com <mailto:parberg@redback.com> ]
                                >Sent: Wednesday, April 30, 2008 3:56 PM
                                >To: Tina TSOU; Maglione Roberta; Sanjay =
Wadhwa; Wojciech Dec (wdec)
                                >Cc: ancp@ietf.org<mailto:ancp@ietf.org>
                                >Subject: RE: [ANCP] question regarding =
Labels in ANCP port up messages
                                >
                                >
                                >Hi,
                                >
                                >some times I think it is amazing we =
ever got interoperability
                                >of ANCP :-)
                                >because looking at the label discussion =
is a very good example that the
                                >whole GSMP - ANCP reference have not =
worked very well.
                                >
                                >In the ANCP draft, section 5.4.2 the =
event message is shown like this:
                                >
                                >0                   1                   =
2                   3
                                >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
                                =
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >| Vers  |  Sub  | Message Type  | =
Result|        Code           |
                                =
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >| Partition ID  |            =
Transaction Identifier             |
                                =
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >|I|      SubMessage Number      |       =
    Length              |
                                =
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >|                             Port      =
                        |
                                =
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >|                      Port Session =
Number                      |
                                =
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >|                     Event Sequence =
Number                     |
                                =
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >|x|S|x|x|                               =
                        |
                                >+-+-+-+-+                     Label     =
                        |
                                >~                                       =
                        ~
                                =
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >|x|x|x|x|x|x|x|x| Message Type  |   =
Tech Type   | Block Length  |
                                =
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >|                                       =
                        |
                                >~                         Extension =
Value                       ~
                                >|                                       =
                        |
                                =
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >
                                >
                                >This is the exact same event message =
defined in
                                >draft-ietf-gsmp-v3-base-spec-08.txt  =
section 11.
                                >
                                >And in this gsmp-draft, section 5.1.3 =
the label space is defined
                                >as minimum 8 bytes if the length=3D0 =
and as such no value, and this
                                >is because the gsmp-draft has a new =
"label adaptaion" field.
                                >
                                >
                                >
                                >BUT in RFC3292 the event message is =
show in section 9, like this:
                                >
                                >0                   1                   =
2                   3
                                >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
                                =
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >|    Version    | Message Type  |    =
Result     |     Code      |
                                =
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >| Partition ID  |            =
Transaction Identifier             |
                                =
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >|I|      SubMessage Number      |       =
    Length              |
                                =
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >|                             Port      =
                        |
                                =
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >|                      Port Session =
Number                      |
                                =
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >|                     Event Sequence =
Number                     |
                                =
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >|x|S|x|x|                               =
                        |
                                >+-+-+-+-+                     Label     =
                        |
                                >~                                       =
                        ~
                                =
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >
                                >
                                >So a different Event Message =
picture/definition than what is shown
                                >in the ANCP draft, and in RFC3292 =
section 3.1.3 the label field
                                >is defined as 4 bytes if length=3D0 and =
as such no value.
                                >
                                >
                                >
                                >So I very much agree with Woj that we =
need this issue to be resolved,
                                >and proabably a show of hands what is =
actually done in different
                                >implementations, so we can nail down =
how the event message is
                                >suppose to look like in ANCP.
                                >
                                >
                                >I know at least 1 implementation which =
uses 8 bytes for the
                                >label field.
                                >
                                >
                                >cheers,
                                >Peter
                                >
                                >
                                >
                                >
                                >
                                >
                                >________________________________
                                >
                                >        From: =
ancp-bounces@ietf.org<mailto:ancp-bounces@ietf.org>
                                >[mailto:ancp-bounces@ietf.org =
<mailto:ancp-bounces@ietf.org> ] On Behalf Of Tina TSOU
                                >        Sent: 30. april 2008 00:19
                                >        To: Maglione Roberta; Sanjay =
Wadhwa; Wojciech Dec (wdec)
                                >        Cc: =
ancp@ietf.org<mailto:ancp@ietf.org>
                                >        Subject: Re: [ANCP] question =
regarding Labels in ANCP
                                >port up messages
                                >
                                >
                                >        Hi all,
                                >        It is clear to me that if Label =
Length is filled as 0,
                                >there is nothing to be filled into =
Label Value. The whole
                                >Label part is 4 bytes, not 8 bytes.
                                >
                                >        Cheers from the last working =
day before Labor's Day
                                >holidays in some countries:)
                                >
                                >        Tina
                                >
                                >                ----- Original Message =
-----
                                >                From: Wojciech Dec =
(wdec) <mailto:wdec@cisco.com <mailto:wdec@cisco.com> >
                                >                To: Sanjay Wadhwa =
<mailto:swadhwa@juniper.net <mailto:swadhwa@juniper.net> >
                                > ; Maglione Roberta =
<mailto:roberta.maglione@telecomitalia.it =
<mailto:roberta.maglione@telecomitalia.it> >
                                >                Cc: =
ancp@ietf.org<mailto:ancp@ietf.org>
                                >                Sent: Wednesday, April =
30, 2008 1:12 AM
                                >                Subject: Re: [ANCP] =
question regarding Labels
                                >in ANCP port up messages
                                >
                                >                Sanjay, All,
                                >
                                >                What is stated below =
runs counter to at least
                                >a handful of ANCP
                                >                implementations, all of =
which are known to be
                                >interoperable.
                                >                There are really two =
options:
                                >                1) The current version =
of the spec is correct,
                                >and the known
                                >                interoperable =
implementations do not follow it
                                >                2) The current version =
of the spec is not
                                >accurate, and does not reflect
                                >                the fact that the known =
implementations follow
                                >the label field
                                >                definition from =
draft-gsmpv3-base-spec.
                                >
                                >                I would like to ask =
you, as the lead editor of
                                >the spec, to work with
                                >                the WG in resolving =
what the problem is, and
                                >clearing up what the WG
                                >                spec says about and if =
1) holds to be true,
                                >then proposing an
                                >                interoperability fix.
                                >
                                >                In either case, the =
issue highlights the fact
                                >that there is still
                                >                lingering confusion as =
to the dependencies
                                >ANCP has on rfc3292, or
                                >                draft-gsmpv3-base-spec, =
or both. It seems to
                                >be in the best interest of
                                >                all to address these.
                                >
                                >                Regards,
                                >                Woj.
                                >
                                >                > -----Original =
Message-----
                                >                > From: Sanjay Wadhwa =
[mailto:swadhwa@juniper.net <mailto:swadhwa@juniper.net> ]
                                >                > Sent: 29 April 2008 =
17:29
                                >                > To: Maglione Roberta
                                >                > Cc: Wojciech Dec =
(wdec); ancp@ietf.org<mailto:ancp@ietf.org>;
                                >Philippe Champagne (pchamp)
                                >                > Subject: RE: question =
regarding Labels in
                                >ANCP port up messages
                                >                >
                                >                > Hi Maglione
                                >                >   Yes, the label =
format is as defined in RFC
                                >3292. The ANCP draft is
                                >                > based on RFC 3292 and =
proposes
                                >extensions/modifications where
                                >                > required.
                                >                > This is clearly =
stated upfront both in the
                                >abstract and in
                                >                > section 2. In
                                >                > section 5.4.2, it =
clearly  specifies the
                                >format of "port up" message
                                >                > (based on RFC 3292), =
and explicitly states
                                >the label field
                                >                > should be set
                                >                > to 0. Following is =
what the draft currently states:
                                >                >
                                >                >
                                >                > 5.4.2 Topology =
Discovery Extensions
                                >                >
                                >                > The GSMP Event =
message with PORT UP message
                                >type (80) is used for
                                >                > conveying DSL line =
attributes to the NAS.
                                >The version field should be
                                >                > set to 3, and the sub =
field should be set to
                                >1. The I and subMessage
                                >                > fields SHOULD be set =
to 1 to signify no
                                >fragmentation. The Port and
                                >                > Label fields should =
be set to 0.
                                >                >
                                >                >  0                   =
1                   2
                                >                3
                                >                >          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
                                >                >
                                >                >
                                >                >
                                =
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >                >         | Vers  |  =
Sub  | Message Type  |
                                >Result|        Code
                                >                > |
                                >                >
                                >                >
                                =
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >                >         | Partition =
ID  |
                                >Transaction Identifier
                                >                > |
                                >                >
                                >                >
                                =
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >                >         |I|      =
SubMessage Number      |
                                >       Length
                                >                > |
                                >                >
                                >                >
                                =
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >                >         |             =
                Port
                                >                > |
                                >                >
                                >                >
                                =
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >                >         |             =
         Port Session Number
                                >                > |
                                >                >
                                >                >
                                =
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >                >         |             =
        Event Sequence Number
                                >                > |
                                >                >
                                >                >
                                =
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >                >         |x|S|x|x|
                                >                > |
                                >                >         +-+-+-+-+     =
                Label
                                >                > |
                                >                >         ~
                                >                > ~
                                >                >
                                >                >
                                =
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >                >         =
|x|x|x|x|x|x|x|x| Message Type  |
                                >Tech Type   | Block Length
                                >                > |
                                >                >
                                >                >
                                =
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >                >         |
                                >                > |
                                >                >         ~             =
            Extension Value
                                >                > ~
                                >                >         |
                                >                > |
                                >                >
                                >                >
                                =
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >                >
                                >                > When we say the label =
field should be set to
                                >0, the intention
                                >                > is for the
                                >                > type and length =
fields in the label TLV to
                                >be set to 0. We can
                                >                > explicitly state this =
for clarity.
                                >                >
                                >                > -Sanjay
                                >                >
                                >                > >-----Original =
Message-----
                                >                > >From: Maglione =
Roberta
                                =
>[mailto:roberta.maglione@telecomitalia.it =
<mailto:roberta.maglione@telecomitalia.it> ]
                                >                > >Sent: Tuesday, April =
29, 2008 8:06 AM
                                >                > >To: Sanjay Wadhwa
                                >                > >Cc: Wojciech Dec =
(wdec); ancp@ietf.org<mailto:ancp@ietf.org>;
                                >pchamp@cisco.com
                                >                > >Subject: RE: =
question regarding Labels in
                                >ANCP port up messages
                                >                > >
                                >                > >
                                >                > >Hi Sanjay and All,
                                >                > >     I was reading =
the current ancp
                                >protocol draft in order to
                                >                > > understand which =
should be the correct
                                >format for the label
                                >                > >field in the ancp =
port Up message.
                                >                > >Actually as it was =
already pointed out in
                                >the alias the draft
                                >                > >in section 5.4.2 =
says "GSMP Event message
                                >with PORT UP message
                                >                > >type (80) is used"  =
thus I am assuming that
                                >the label in the
                                >                > >port UP message =
should follow the message
                                >format defined in
                                >                > >RFC 3292, section =
3.1.3:
                                >                > >
                                >                > >    0                =
   1
                                >2                   3
                                >                > >    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
                                >                > >
                                =
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >                > >   |x|S|x|x|       =
Label Type      |
                                >  Label Length         |
                                >                > >
                                =
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >                > >   |
                                >                       |
                                >                > >   ~                 =
         Label Value
                                >                       ~
                                >                > >   |
                                >                       |
                                >                > >
                                =
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >                > >
                                >                > >but from what I have =
seen different
                                >implementations use
                                >                > >different format for =
label field: in
                                >particular several
                                >                > >implementations use  =
a label format that is
                                >similar to the one
                                >                > >specified in the =
expired draft
                                >draft-ietf-gsmp-v3-base-spec:
                                >                > >
                                >                > >     0               =
    1
                                > 2                   3
                                >                > >       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
                                >                > >
                                >                >
                                =
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >                > >      =
|x|S|x|x|x|x|x|x|x|x|x|x|x|x|x|x|
                                >       Label
                                >                > Type         |
                                >                > >
                                >                >
                                =
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >                > >      |    Label =
Adaptation           |
                                >     Label
                                >                > Length         |
                                >                > >
                                >                >
                                =
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >                > >      |
                                >                >          |
                                >                > >      ~              =
            Label Value
                                >                >          ~
                                >                > >      |
                                >                >          |
                                >                > >
                                >                >
                                =
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >                > >
                                >                > >
                                >                > >Even if ancp does =
not care about the label
                                >field, having this
                                >                > >field somehow not =
clearly specified in the
                                >current ancp draft
                                >                > >can easily lead to =
interoperability issues,
                                >thus I think it
                                >                > >would be very =
helpful if you and/or the
                                >other editors can
                                >                > >clarify what should =
be the correct format
                                >for the label field
                                >                > >to be used in the =
ancp Port Up message.
                                >                > >
                                >                > >Thanks and best =
regards,
                                >                > >Roberta
                                >                > >
                                >                > =
>________________________________________
                                >                > >From: Philippe =
Champagne (pchamp) [pchamp@cisco.com]
                                >                > >Sent: Thursday, =
April 24, 2008 7:14 PM
                                >                > >To: Sanjay Wadhwa
                                >                > >Cc: Maglione =
Roberta; Wojciech Dec (wdec);
                                >ancp@ietf.org
                                >                > >Subject: question =
regarding  Labels in ANCP
                                >port up messages
                                >                > >
                                >                > >Hi Sanjay
                                >                > >
                                >                > >In section 5.4.2 of =
the draft, we have:
                                >                > >
                                >                > >
                                >                > >         0           =
        1                   2
                                >                >         3
                                >                > >         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
                                >                > >
                                >                >
                                =
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >                > >        | Vers  |  =
Sub  | Message Type  |
                                >Result|        Code
                                >                > >         |
                                >                > >
                                >                >
                                =
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >                > >        | Partition =
ID  |
                                >Transaction Identifier
                                >                > >         |
                                >                > >
                                >                >
                                =
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >                > >        |I|      =
SubMessage Number      |
                                >        Length
                                >                > >         |
                                >                > >
                                >                >
                                =
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >                > >        |            =
                 Port
                                >                > >         |
                                >                > >
                                >                >
                                =
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >                > >        |            =
          Port Session Number
                                >                > >         |
                                >                > >
                                >                >
                                =
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >                > >        |            =
         Event Sequence Number
                                >                > >         |
                                >                > >
                                >                >
                                =
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >                > >        |x|S|x|x|
                                >                > >         |
                                >                > >        +-+-+-+-+    =
                 Label
                                >                > >         |
                                >                > >        ~
                                >                > >         ~
                                >                > >
                                >                >
                                =
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >                > >        =
|x|x|x|x|x|x|x|x| Message Type  |
                                >Tech Type   |
                                >                > >Block Length  |
                                >                > >
                                >                >
                                =
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >                > >        |
                                >                > >         |
                                >                > >        ~            =
             Extension Value
                                >                > >         ~
                                >                > >        |
                                >                > >         |
                                >                > >
                                >                >
                                =
>>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >                > >Where Label I =
suppose is taken from the RFC
                                >3292, section
                                >                > >3.1.3: (well, I'm =
guessing)
                                >                > >
                                >                > >   A summary of TLV =
labels supported in
                                >this version of the
                                >                > protocol is
                                >                > >   listed below:
                                >                > >
                                >                > >      TLV Label      =
Type       Section Title
                                >                > >      ---------      =
----       -------------
                                >                > >      ATM Label      =
0x100      ATM TLV Labels
                                >                > >      FR Label       =
0x101      Frame Relay
                                >TLV Labels
                                >                > >      MPLS Gen Label =
0x102      MPLS
                                >Generic TLV Labels
                                >                > >      FEC Label      =
0x103      FEC TLV Labels
                                >                > >
                                >                > >   All Labels will =
be designated as follow:
                                >                > >
                                >                > >    0                =
   1
                                >2                   3
                                >                > >    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
                                >                > >
                                =
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >                > >   |x|S|x|x|       =
Label Type      |
                                >  Label Length         |
                                >                > >
                                =
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >                > >   |
                                >                       |
                                >                > >   ~                 =
         Label Value
                                >                       ~
                                >                > >   |
                                >                       |
                                >                > >
                                =
>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                >                > >
                                >                > >      x: Reserved =
Flags.
                                >                > >         These are =
generally used by
                                >specific messages and will be
                                >                > >         defined in =
those messages.
                                >                > >
                                >                > >      S: Stacked =
Label Indicator
                                >                > >         Label =
Stacking is discussed below
                                >in section 3.1.3.5
                                >                > >
                                >                > >      Label Type
                                >                > >         A 12-bit =
field indicating the type
                                >of label.
                                >                > >
                                >                > >      Label Length
                                >                > >         A 16-bit =
field indicating the
                                >length of the Label
                                >                > Value field
                                >                > >         in bytes.
                                >                > >
                                >                > >      Label Value
                                >                > >         A variable =
length field that is an
                                >integer number of 32 bit
                                >                > >         words long. =
 The Label Value field
                                >is interpreted
                                >                > according to
                                >                > >         the Label =
Type as described in the
                                >following sections.
                                >                > >
                                >                > >
                                >                > >The draft is a bit =
obscure about this and
                                >since it doesn't
                                >                > >specify much, it can =
lead to
                                >misinterpretation for the unused
                                >                > >part. Moreover, it =
would appear that
                                >several implementations
                                >                > >currently use =
another format for the label
                                >field. Can you
                                >                > >explain?  I mean, =
how come what's in the
                                >current draft doesn't
                                >                > >match what's known =
to be implemented?
                                >                > >
                                >                > >I'm still wondering =
why we carried over
                                >pieces from GSMP that
                                >                > >we do not intend to =
use.
                                >                > >
                                >                > >I would recommend =
that if we are to keep
                                >them but not use
                                >                > >them, we should =
mention precisely how we
                                >intend not to use
                                >                > >them: that is how =
many 0 filled bytes this
                                >is expected to use
                                >                > >
                                >                > >The rfc 3292 doesn't =
cover the case where
                                >this field is not used.
                                >                > >
                                >                > >Can you shed some =
ligths on this?
                                >                > >
                                >                > >Thanks
                                >                > >Regards
                                >                > >Phil
                                >                > >
                                >                > >
                                >                > >
                                >                >
                                =
>>--------------------------------------------------------------------
                                >                > >
                                >                > >CONFIDENTIALITY =
NOTICE
                                >                > >
                                >                > >This message and its =
attachments are
                                >addressed solely to the
                                >                > >persons above and =
may contain confidential
                                >information. If you
                                >                > >have received the =
message in error, be
                                >informed that any use
                                >                > >of the content =
hereof is prohibited. Please
                                >return it
                                >                > >immediately to the =
sender and delete the
                                >message. Should you
                                >                > >have any questions, =
please contact us by replying to
                                >                > =
>webmaster@telecomitalia.it.
                                >                > >
                                >                > >        Thank you
                                >                > >
                                >                > >
                                >www.telecomitalia.it
                                >                > >
                                >                >
                                =
>>--------------------------------------------------------------------
                                >                > >
                                >                > >
                                >                >
                                >                =
_______________________________________________
                                >                ANCP mailing list
                                >                =
ANCP@ietf.org<mailto:ANCP@ietf.org>
                                >                =
https://www.ietf.org/mailman/listinfo/ancp =
<https://www.ietf.org/mailman/listinfo/ancp>
                                >
                                >
--------------------------------------------------------------------

CONFIDENTIALITY NOTICE

This message and its attachments are addressed solely to the persons =
above and may contain confidential information. If you have received the =
message in error, be informed that any use of the content hereof is =
prohibited. Please return it immediately to the sender and delete the =
message. Should you have any questions, please contact us by replying to =
webmaster@telecomitalia.it.

        Thank you

                                        www.telecomitalia.it

--------------------------------------------------------------------
                       =20

--_000_A1F769BC58A8B146B2EEA818EAE052A20121E824BDGRFMBX702RM00_
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
 namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" =
name=3D"PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"\@MS Mincho";
	panose-1:0 0 0 0 0 0 0 0 0 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;}
p
	{mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:"Times New Roman";}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:70.85pt 2.0cm 2.0cm 2.0cm;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body bgcolor=3Dwhite lang=3DIT link=3Dblue vlink=3Dblue>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Hi =
Tina,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>&nbsp;&nbsp; you =
said that
you support Peter&#8217;s proposal on changing the unused field =
&nbsp;from &#8220;label&#8221;
to &quot;reserved&quot; , but you did not comment on the length of this =
field. <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>If my =
understanding is correct,
Peter is also proposing to have a &#8220;reserved&#8221; field of 8 =
bytes:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
lang=3DEN-US
style=3D'font-size:12.0pt'>&#8220;Label field is 8 bytes, should be set =
to 0 on
transmit and ignored on receive.&#8221;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p>=
</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>what&#8217;s =
your opinion
on that? <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p>=
</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Regards,<o:p></o:=
p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Roberta<o:p></o:p=
></span></font></p>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span lang=3DEN-US style=3D'font-size:12.0pt'>

<hr size=3D3 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span lang=3DEN-US
style=3D'font-size:10.0pt;font-family:Tahoma;font-weight:bold'>From:</spa=
n></font></b><font
size=3D2 face=3DTahoma><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:Tahoma'>
Tina TSOU [mailto:tena@huawei.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Friday, May 09, =
2008 4:02 AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> Maglione Roberta; =
<st1:PersonName
w:st=3D"on">Sanjay Wadhwa</st1:PersonName>; Ole Helleberg Andersen; =
<st1:PersonName
w:st=3D"on">Wojciech Dec</st1:PersonName> (wdec); Peter Arberg<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b> ancp@ietf.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> Re: [ANCP] =
question
regarding Labels in ANCP port up messages</span></font><span =
lang=3DEN-US><o:p></o:p></span></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<div>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Dear Peter et al,</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Comment in line.</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>B. R.<br>
Tina<br>
Messengers: <br>
MSN: <a =
href=3D"mailto:tinatsou6@hotmail.com">tinatsou6@hotmail.com</a>&nbsp;&nbs=
p;
Yahoo: tina_tsou&nbsp;&nbsp;&nbsp; Skype: tinaTSOU&nbsp;&nbsp;&nbsp; =
Jabber: <a
href=3D"mailto:tina@jabber.org">tina@jabber.org</a>&nbsp;&nbsp;&nbsp; =
Google
talk: <a =
href=3D"mailto:tinatsou6@gmail.com">tinatsou6@gmail.com</a><o:p></o:p></s=
pan></font></p>

</div>

<blockquote style=3D'border:none;border-left:solid black =
1.5pt;padding:0cm 0cm 0cm 3.0pt;
margin-left:3.0pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5.0pt'>=


<div>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>----- Original Message ----- =
<o:p></o:p></span></font></p>

</div>

<div style=3D'font-color:black'>

<p class=3DMsoNormal style=3D'background:#E4E4E4'><b><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial;font-weight:bold'>From:</span=
></font></b><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'> <a
href=3D"mailto:parberg@redback.com" title=3D"parberg@redback.com">Peter =
Arberg</a> <o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><b><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial;font-weight:bold'>To:</span></font></b><font size=3D2
face=3DArial><span style=3D'font-size:10.0pt;font-family:Arial'> <a
href=3D"mailto:wdec@cisco.com" title=3D"wdec@cisco.com">Wojciech Dec =
(wdec)</a> ; <a
href=3D"mailto:ole.helleberg.andersen@ericsson.com"
title=3D"ole.helleberg.andersen@ericsson.com">Ole Helleberg Andersen</a> =
; <a
href=3D"mailto:swadhwa@juniper.net" title=3D"swadhwa@juniper.net">Sanjay =
Wadhwa</a>
; <a href=3D"mailto:tena@huawei.com" title=3D"tena@huawei.com">Tina =
TSOU</a> ; <a
href=3D"mailto:roberta.maglione@telecomitalia.it"
title=3D"roberta.maglione@telecomitalia.it">Maglione Roberta</a> =
<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><b><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial;font-weight:bold'>Cc:</span></font></b><font size=3D2
face=3DArial><span style=3D'font-size:10.0pt;font-family:Arial'> <a
href=3D"mailto:ancp@ietf.org" title=3D"ancp@ietf.org">ancp@ietf.org</a> =
<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><b><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial;font-weight:bold'>Sent:</span></font></b><font =
size=3D2
face=3DArial><span style=3D'font-size:10.0pt;font-family:Arial'> Friday, =
May 09,
2008 8:15 AM<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><b><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial;font-weight:bold'>Subject:</span></font></b><font =
size=3D2
face=3DArial><span style=3D'font-size:10.0pt;font-family:Arial'> RE: =
[ANCP]
question regarding Labels in ANCP port up =
messages<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>Hi Woj,<br>
<br>
I think your proposal goes hand in hand with my suggestion to document =
the<br>
event message bit by bit instead of reference the RFC3292 or an expired =
old<br>
gsmp-draft.<br>
<br>
I will suggest we in the ANCP draft do a description in section<br>
5.4.2 something in these lines:<br>
<br>
The ANCP Event message with PORT UP message type (80) is used for<br>
conveying DSL line attributes to the NAS, and is defined as follows:<br>
<br>
<br>
0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
3<br>
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<br>
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>
| Vers&nbsp; |&nbsp; Sub&nbsp; | Message Type&nbsp; |
Result|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Code&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>
| Partition ID&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Transaction
Identifier&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;
|<br>
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>
|I|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SubMessage
Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;
|<br>
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;
Port&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|<br>
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Port Session
Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|<br>
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Event Sequence
Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|<br>
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>
|x|S|x|x|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|<br>
+-+-+-+-+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;
|<br>
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;
|<br>
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>
|x|x|x|x|x|x|x|x| Message Type&nbsp; |&nbsp;&nbsp; Tech Type&nbsp;&nbsp; =
|
Block Length&nbsp; |<br>
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;
|<br>
~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Extension
Value&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
~<br>
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;
|<br>
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>
<br>
<br>
Version field is 1 byte, 4 bits for the major version and 4<br>
bits for the sub-version, should be set to 3, and the sub field<br>
should be set to 1.<br>
<br>
Message Type is 1 byte, and can have the following values:<br>
...<br>
<br>
Result ...<br>
<br>
Code ...<br>
<br>
Partition ID ...<br>
<br>
....<br>
<br>
<br>
Label field is 8 bytes, should be set to 0 on transmit and ignored on =
receive.<br>
<br>
....<br>
<br>
So the idea is to document every single field in the event message,<br>
and list what is the expected transmit value, and what should the<br>
receiver do with the field.<br>
<br>
<br>
I will actually suggest we remove the &quot;label&quot; name and just =
call the<br>
unused field &quot;reserved&quot; and must be set to 0 on transmit and =
ignored
on<br>
receive.<br>
</span></font><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial;color:blue'>[Tina: I really support Peter at this =
point.]</span></font><o:p></o:p></p>

</div>

</blockquote>

<blockquote style=3D'border:none;border-left:solid black =
1.5pt;padding:0cm 0cm 0cm 3.0pt;
margin-left:3.0pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5.0pt'>=


<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><br>
If we simply call them &quot;reserved&quot; we always have the option to =
reuse
them<br>
in alater contribution / new version if theer ever should be a need =
to<br>
use some bits in the event message header.<br>
<br>
<br>
Also as another comment, I still think it will be beneficial if we<br>
describe that the version number check should be per adjacency, so<br>
we in the future can do a version change easy and allow the ANCP<br>
implementation to have multiple adjacency with different versions of =
the<br>
protocol, if we ever see a reason to increase the version number it<br>
will give a much easier upgrade scenario.<br>
<br>
cheers,<br>
Peter<br>
<br>
<br>
cheers,<br>
Peter<br>
<br>
<br>
<br>
<br>
________________________________<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; From: <st1:PersonName =
w:st=3D"on">Wojciech
 Dec</st1:PersonName> (wdec) [mailto:wdec@cisco.com]<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Sent: 7. maj 2008 14:14<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; To: Ole Helleberg Andersen; =
Peter
Arberg; <st1:PersonName w:st=3D"on">Sanjay Wadhwa</st1:PersonName>; Tina =
TSOU;
Maglione Roberta<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Cc: <a =
href=3D"mailto:ancp@ietf.org">ancp@ietf.org</a><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Subject: RE: [ANCP] question
regarding Labels in ANCP port up messages<br>
<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Hi All,<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; it's with a certain amount of
incredulity that I view the proposals on this thread for changing the =
version
number of the protocol. Were such proposals to be accepted, by =
definition it
would make most likely the ANCP draft incompatible with *all* current
implementations, or at the very least introduce a compatibility mess in =
existing
deployments short of a flag day change over, not to mention the issue of
depreciating the old version.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; There really seems to be no =
reason
to go through with a version change due to what may be attributed as a =
day 1
draft problem but *not* a day 1 implementation problem. Also, it is not =
the
first time that the protocol spec draft has had some inaccuracies, and =
we've
visited this aspect previously resulting in the following versioning =
strategy
being laid out: <a
href=3D"http://www.ietf.org/mail-archive/web/ancp/current/msg00152.html">=
http://www.ietf.org/mail-archive/web/ancp/current/msg00152.html</a>
. While the strategy states that an ANCP version change will not be =
considered
due to &quot;incompatibilities arising from implementations of pre-RFC
drafts&quot;, neither does it state that the draft cannot change to =
reflect
current implementations while keeping the version.<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Now, given that there seems =
to be
some uneasiness (but thankfully not absolute) in the WG to come forward
publicly with details of what is currently implemented, I have conducted =
a
behind the scenes investigation of sorts, and present the summarized =
findings
below:<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - There are 10 distinct
implementations of ANCP<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - Out of these 9 either =
directly
implement the label field format in as per section 5.3 of
draft-gsmpv3-base-spec-08, or each is known to be compatible with at =
least 2
implementations that do so. By association, it seems reasonable to claim =
that
all of these ANCP implementations use the draft-gsmpv3-base-spec-08 =
format.
Also, all use version 3.1 as the protocol version, and the base protocol =
header
also as per draft-gsmpv3-base-spec-08<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - One implementation is known =
to use
the draft-ietf-ancp-protocol-02 format of the label field format, ie the
rfc3292 format. This implementation is not known to be compatible with =
any of
the others.<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Based on this, but not only, =
the
obvious answer to the problem is *not* to do a version change, but =
rather fix
the draft. Granted, this is a far from ideal situation for the one
implementation affected, and it's a true shame that the problem wasn't =
spotted
earlier. Like Peter I also wonder how any interop was achieved, but the =
fact
that it is there is a significant one that should not be undone by hasty
version changes. As such option 2 below is not one we'll be taking =
forward.
Option 1 however also comes short as it does not quite follow the logic =
of
simply documenting what is known to be interoperable in the WG draft. If
specific implementations choose to realize knobs or other, fine, but =
this is
not part of the protocol spec, and there is no such thing as &quot;old =
label
format&quot;. Please do consider the third option, ie fixing the draft =
to
reflect what is already done.<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; This fact in general =
highlights the
problems we're having in carrying with the GSMPv3 (rfc3292) legacy, =
alongside
adopted amendments from draft-gsmpv3-base-spec (this Label issue not =
being the
only adopted item), alongside new protocol work. I trust that all of you =
agree
that getting maximum clarity on all the legacy issues and dependencies =
in the
protocol spec is in the WG's best interest, and that we are still some =
way off
from that. As such I also expect the WG to support moves/proposals aimed =
at
getting that clarity, with resolving this issue being not the first and =
not the
last such move.<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Regards,<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Woj.<br>
<br>
<br>
<br>
<br>
<br>
________________________________<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;
From: Ole Helleberg Andersen =
[mailto:ole.helleberg.andersen@ericsson.com]<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;
Sent: 06 May 2008 14:04<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;
To: Peter Arberg; <st1:PersonName w:st=3D"on">Sanjay =
Wadhwa</st1:PersonName>;
Tina TSOU; Maglione Roberta; <st1:PersonName w:st=3D"on">Wojciech =
Dec</st1:PersonName>
(wdec)<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;
Cc: <a href=3D"mailto:ancp@ietf.org">ancp@ietf.org</a><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;
Subject: RE: [ANCP] question regarding Labels in ANCP port up =
messages<br>
<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;
Hi All,<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
I think the main issue is to ensure interoperability with existing =
implementations,
and to allow for upgrading nodes that are already in service to a =
WG-draft
compliant version. To do that in a manageable way we must allow for =
version
negotiation per adjacency. We therefore need to change the WG-draft as
suggested by Sanjay in his option 2.<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;
Concerning the encoding issue I prefer to make the WG-draft in line with
existing implementations. However, if the WG decides to change it, =
differences
in this encoding would also be solved by choosing Sanjay's option 2.<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;
Cheers,<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;
Ole<br>
<br>
________________________________<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;
From: <a href=3D"mailto:ancp-bounces@ietf.org">ancp-bounces@ietf.org</a>
[mailto:ancp-bounces@ietf.org] On Behalf Of Peter Arberg<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;
Sent: 2. maj 2008 20:52<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;
To: <st1:PersonName w:st=3D"on">Sanjay Wadhwa</st1:PersonName>; Tina =
TSOU;
Maglione Roberta; <st1:PersonName w:st=3D"on">Wojciech =
Dec</st1:PersonName>
(wdec)<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;
Cc: <a href=3D"mailto:ancp@ietf.org">ancp@ietf.org</a><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;
Subject: Re: [ANCP] question regarding Labels in ANCP port up =
messages<br>
<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;
Hi Sanjay,<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;
yes apparently I missed your point in the last email, but I'm glad we =
agree
something is needed<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;
to make existing ANCP implementations and the current draft to =
co-exist.<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;
I do not like your option 1) as if you need a config knob for =
interoperability,
it is too easy to<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;
get into trouble.<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;
I think option 2) is the best way forward with the differences already
identified, or we can<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;
continue to get a show of hands of ANCP implementations, and see if =
anyone is
actually<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;
deployed based on the WG-draft.<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;
There is no beneficial reasons to base the event-message of RFC3292, it =
could
as well be a message<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;
described bit by bit in the ANCP draft, and then we can keep the label =
space at
8 as many<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;
implementations alreday do.<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;
cheers,<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;
Peter<br>
<br>
<br>
<br>
<br>
<br>
________________________________<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
From: <st1:PersonName w:st=3D"on">Sanjay Wadhwa</st1:PersonName>
[mailto:swadhwa@juniper.net]<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Sent: 2. maj 2008 05:35<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
To: Peter Arberg; Tina TSOU; Maglione Roberta; <st1:PersonName =
w:st=3D"on">Wojciech
 Dec</st1:PersonName> (wdec)<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Cc: <a href=3D"mailto:ancp@ietf.org">ancp@ietf.org</a><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Subject: RE: [ANCP] question regarding Labels in ANCP port up =
messages<br>
<br>
<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Peter<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
You missed my point below. The ANCP draft since becoming a WG draft does =
NOT
refer to the old GSMP drafts. Any implementations based on this WG-draft =
are
expected to be interoperable. You are pointing to pre-WG-draft versions =
of
ANCP, and these were indeed based on expired GSMP drafts that evolved =
past
RFC3292.<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
There is incompatibility between the current ANCP WG-draft and previous =
non-WG
versions (TLV clash, label format..). As mentioned earlier it is prudent =
for
older implementations to start supporting the WG-draft version as soon =
as
possible.<br>
<br>
<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
For interoperability of WG-draft with the older pre-WG versions, I see =
the
following options:<br>
<br>
<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
1. Versioning starts with the WG-draft i.e. WG-draft is version =3D 3,
sub-version =3D 1. For any interop issues between older non-WG versions =
and the
WG-draft, one needs to look at solving it within implementations (e.g. =
an AN
that implements the WG-draft, could based on a configuration knob, =
generate a
PORT-UP message with old label format the will be accepted by BNG =
implementing
pre-WG versions of the draft).<br>
<br>
<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
2. Change the WG-draft (current draft) to use version =3D 3 and =
sub-version =3D 2.
This is assuming there is no deployed implementation of current WG-draft =
that
already uses 3.1 as the version, and also assuming the old pre-WG
implementations use 3.1. There will be no backwards compatibility i.e. =
version
3.1 BNG will not work with version 3.2 AN (we will need to list this as =
caveat
in the appendix section). AN and BNG will need to negotiate the same =
version in
order for ANCP adjacency to come up. A BNG supporting both versions 3.1 =
and 3.2
could simultaneously become adjacent with one AN supporting 3.1 and =
another AN
supporting 3.2. (i.e. version compatibility is per adjacency).<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Also, major version number change (e.g. from 3 to 4) should only =
correspond to
a major change in the protocol (e.g. different mechanism, different =
transport
etc).<br>
<br>
<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
My vote would be to adopt option 2 above only if further changes to =
WG-draft
happen that render it incompatible with the current WG-draft. Any
interoperability issues with pre-WG versions could be handled via option =
1.<br>
<br>
<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Cheers<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-Sanjay<br>
<br>
<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
________________________________<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
From: Peter Arberg [mailto:parberg@redback.com]<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Sent: Wednesday, April 30, 2008 7:20 PM<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
To: <st1:PersonName w:st=3D"on">Sanjay Wadhwa</st1:PersonName>; Tina =
TSOU;
Maglione Roberta; <st1:PersonName w:st=3D"on">Wojciech =
Dec</st1:PersonName>
(wdec)<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Cc: <a href=3D"mailto:ancp@ietf.org">ancp@ietf.org</a><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Subject: RE: [ANCP] question regarding Labels in ANCP port up =
messages<br>
<br>
<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Sanjay,<br>
<br>
<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
What do you mean &quot;why I reference an old draft&quot;&nbsp; =
????????????<br>
<br>
<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
I'm surprised you even ask...&nbsp; please take a look at YOUR own
internet-draft that most<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
of the ANCP working implementations are based on, in case you do not =
have this
old<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
internet-draft, I have attached it to the document.<br>
<br>
<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
If you look at the reference for this ancp-draft, you will see that in =
the
reference section<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
you point to this old gsmp-draft...&nbsp; Yes and I know this has been =
changed
in the later<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
versions of the ANCP draft, but that do not change the fact that many of =
the
implementations<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
today was developed when the attached draft was current.<br>
<br>
<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
I think a very good question is brought up here, and that is what is
implemented and<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
running in networks today ?<br>
<br>
<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
My take on this is that when the reference was change from the old =
gsmp-draft
to the older<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
RFC3292, apparently no one paid any attention to the fact the label =
definition
in the event<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
message was different and not compatible.<br>
<br>
<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
What current implementations do today is an important factor in this
discussion, and I think<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
it is time to come to realization that we might need a new version =
number for
ANCP since<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
it continues to look like there is big holes open for interpretation. So =
if I
did a ANCP<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
implementation there is bound to be interoperability issues with =
existing
implementations<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
runnig.<br>
<br>
<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
cheers,<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Peter<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
________________________________<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;
From: <st1:PersonName w:st=3D"on">Sanjay Wadhwa</st1:PersonName>
[mailto:swadhwa@juniper.net]<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Sent: 30. april 2008 14:42<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
To: Peter Arberg; Tina TSOU; Maglione Roberta; <st1:PersonName =
w:st=3D"on">Wojciech
 Dec</st1:PersonName> (wdec)<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Cc: <a href=3D"mailto:ancp@ietf.org">ancp@ietf.org</a><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Subject: RE: [ANCP] question regarding Labels in ANCP port up =
messages<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Peter<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
The ANCP draft as it currently stands is based on RFC3292. It provides
extensions and modifications to relevant constructs in RFC3292. There is =
no
mention (implicit or explicit) of expired GSMP drafts in the ANCP draft. =
In
order to implement the ANCP draft, I am not sure why one would look at =
the
expired GSMP drafts. Do you see a reason to do this based on anything =
that you
read in the ANCP draft? Bringing up reference to expired gsmp draft in =
this
thread just adds to the confusion. For GSMPv3 objects in the messages =
(such as
Label Type), one has to look at RFC3292 (this is clearly stated in the =
ANCP
draft - section 2 and I am quoting it below) :<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
ANCP uses a subset of GSMPv3 messages to implement currently defined =
use-cases.
These relevant GSMPv3 messages are identified in section 5. GSMPv3 =
procedures
with suitable extensions, as used by ANCP, are described in sections =
5.1, 5.2
and 5.3. GSMPv3 general extensions and GSMPv3 message specific =
extensions
required by ANCP are described in sub-sections of 5.4. In addition to
specifying extensions and modifications to relevant GSMP messages =
applicable to
ANCP, this draft also defines the usage of these messages by ANCP, and
indicates the values that ANCP should set for relevant fields in these =
GSMP
messages. However, to understand the basic semantics of various fields =
in GSMP
messages, the reader is referred to [4]. =3D&gt; RFC 3292.<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
What existing implementations currently do is an important but separate =
issue.
These implementations for most part precede the current ANCP draft. It =
is fine
to poll where these implementations diverge from the current draft. It =
is then
upto the implementations (including the one that I am somewhat familiar =
with)
to work towards compliance with the draft.<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
On the following points from&nbsp; Woj:<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Woj&gt;2) The current version of the spec is not accurate, and does not =
reflect
the fact that the known implementations follow the label field =
definition from
draft-gsmpv3-base-spec.<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
It is not for the protocol draft to point out what current =
implementations
do.&nbsp; The best we can do is to further clarify in the draft that =
type and
value fields of the Label object (defined in RFC3292) should be set to 0 =
in the
port-up message (we already mention the lable object as a whole should =
be set
to all 0s).<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Woj&gt; This would be a good thing for the WG to discuss. There most =
evidently
is a fair amount of &quot;dead wood&quot; in the current spec, ie stuff =
that
nobody yet implements or cares about.&nbsp; In the former case, we could
re-cast that material using the new notions/extensions, in the latter =
case
simply chop it out.<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
I agree. We are based on GSMPv3 (RFC3292)&nbsp; messages, and obviously =
not
everything in these messages is leveraged by ANCP.&nbsp; However, the =
sync rate
and OAM uses-cases are implemented and in use (ideally we should leave =
these
alone...i.e. no change beyond adding more clarity if needed). For =
anything new
(such as multicast) we are defining new messages (no legacy).<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
-Sanjay<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;-----Original Message-----<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;From: Peter Arberg [mailto:parberg@redback.com &lt;<a
href=3D"mailto:parberg@redback.com">mailto:parberg@redback.com</a>&gt; =
]<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;Sent: Wednesday, April 30, 2008 3:56 PM<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;To: Tina TSOU; Maglione Roberta; <st1:PersonName w:st=3D"on">Sanjay =
Wadhwa</st1:PersonName>;
<st1:PersonName w:st=3D"on">Wojciech Dec</st1:PersonName> (wdec)<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;Cc: <a href=3D"mailto:ancp@ietf.org">ancp@ietf.org</a><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;Subject: RE: [ANCP] question regarding Labels in ANCP port up =
messages<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;Hi,<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;some times I think it is amazing we ever got interoperability<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;of ANCP :-)<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;because looking at the label discussion is a very good example that =
the<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;whole GSMP - ANCP reference have not worked very well.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;In the ANCP draft, section 5.4.2 the event message is shown like =
this:<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
3<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;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<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;| Vers&nbsp; |&nbsp; Sub&nbsp; | Message Type&nbsp; | =
Result|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Code&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;| Partition ID&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Transaction
Identifier&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;
|<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;|I|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SubMessage =
Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;
|<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;
Port&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Port Session
Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Event Sequence
Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;|x|S|x|x|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;+-+-+-+-+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;
|<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;
~<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;|x|x|x|x|x|x|x|x| Message Type&nbsp; |&nbsp;&nbsp; Tech =
Type&nbsp;&nbsp; |
Block Length&nbsp; |<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;
|<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;
Extension
Value&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
~<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;
|<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;This is the exact same event message defined in<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;draft-ietf-gsmp-v3-base-spec-08.txt&nbsp; section 11.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;And in this gsmp-draft, section 5.1.3 the label space is defined<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;as minimum 8 bytes if the length=3D0 and as such no value, and =
this<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;is because the gsmp-draft has a new &quot;label adaptaion&quot; =
field.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;BUT in RFC3292 the event message is show in section 9, like =
this:<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
3<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;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<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;|&nbsp;&nbsp;&nbsp; Version&nbsp;&nbsp;&nbsp; | Message Type&nbsp;
|&nbsp;&nbsp;&nbsp; Result&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;
Code&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;| Partition ID&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Transaction
Identifier&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;
|<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;|I|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SubMessage =
Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;
|<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;
Port&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Port Session
Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Event Sequence
Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;|x|S|x|x|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;+-+-+-+-+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;
|<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;
~<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;So a different Event Message picture/definition than what is =
shown<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;in the ANCP draft, and in RFC3292 section 3.1.3 the label field<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;is defined as 4 bytes if length=3D0 and as such no value.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;So I very much agree with Woj that we need this issue to be =
resolved,<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;and proabably a show of hands what is actually done in different<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;implementations, so we can nail down how the event message is<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;suppose to look like in ANCP.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;I know at least 1 implementation which uses 8 bytes for the<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;label field.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;cheers,<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;Peter<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;________________________________<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; From: <a
href=3D"mailto:ancp-bounces@ietf.org">ancp-bounces@ietf.org</a><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;[mailto:ancp-bounces@ietf.org &lt;<a =
href=3D"mailto:ancp-bounces@ietf.org">mailto:ancp-bounces@ietf.org</a>&gt=
;
] On Behalf Of Tina TSOU<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Sent: 30. april 2008 =
00:19<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; To: Maglione Roberta; =
<st1:PersonName
w:st=3D"on">Sanjay Wadhwa</st1:PersonName>; <st1:PersonName =
w:st=3D"on">Wojciech
 Dec</st1:PersonName> (wdec)<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Cc: <a
href=3D"mailto:ancp@ietf.org">ancp@ietf.org</a><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Subject: Re: [ANCP] =
question
regarding Labels in ANCP<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;port up messages<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Hi all,<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; It is clear to me that if =
Label
Length is filled as 0,<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;there is nothing to be filled into Label Value. The whole<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;Label part is 4 bytes, not 8 bytes.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Cheers from the last =
working day
before Labor's Day<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;holidays in some countries:)<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Tina<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
----- Original Message -----<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
From: <st1:PersonName w:st=3D"on">Wojciech Dec</st1:PersonName> (wdec) =
&lt;<a
href=3D"mailto:wdec@cisco.com">mailto:wdec@cisco.com</a> &lt;<a
href=3D"mailto:wdec@cisco.com">mailto:wdec@cisco.com</a>&gt; &gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
To: <st1:PersonName w:st=3D"on">Sanjay Wadhwa</st1:PersonName> &lt;<a
href=3D"mailto:swadhwa@juniper.net">mailto:swadhwa@juniper.net</a> =
&lt;<a
href=3D"mailto:swadhwa@juniper.net">mailto:swadhwa@juniper.net</a>&gt; =
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt; ; Maglione Roberta &lt;<a =
href=3D"mailto:roberta.maglione@telecomitalia.it">mailto:roberta.maglione=
@telecomitalia.it</a>
&lt;<a =
href=3D"mailto:roberta.maglione@telecomitalia.it">mailto:roberta.maglione=
@telecomitalia.it</a>&gt;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
Cc: <a href=3D"mailto:ancp@ietf.org">ancp@ietf.org</a><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
Sent: Wednesday, April 30, 2008 1:12 AM<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
Subject: Re: [ANCP] question regarding Labels<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;in ANCP port up messages<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
Sanjay, All,<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
What is stated below runs counter to at least<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;a handful of ANCP<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
implementations, all of which are known to be<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;interoperable.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
There are really two options:<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
1) The current version of the spec is correct,<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;and the known<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
interoperable implementations do not follow it<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
2) The current version of the spec is not<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;accurate, and does not reflect<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
the fact that the known implementations follow<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;the label field<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
definition from draft-gsmpv3-base-spec.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
I would like to ask you, as the lead editor of<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;the spec, to work with<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
the WG in resolving what the problem is, and<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;clearing up what the WG<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
spec says about and if 1) holds to be true,<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;then proposing an<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
interoperability fix.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
In either case, the issue highlights the fact<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;that there is still<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
lingering confusion as to the dependencies<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;ANCP has on rfc3292, or<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
draft-gsmpv3-base-spec, or both. It seems to<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;be in the best interest of<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
all to address these.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
Regards,<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
Woj.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; -----Original Message-----<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; From: <st1:PersonName w:st=3D"on">Sanjay Wadhwa</st1:PersonName>
[mailto:swadhwa@juniper.net &lt;<a =
href=3D"mailto:swadhwa@juniper.net">mailto:swadhwa@juniper.net</a>&gt;
]<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; Sent: 29 April 2008 17:29<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; To: Maglione Roberta<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; Cc: <st1:PersonName w:st=3D"on">Wojciech Dec</st1:PersonName> =
(wdec); <a
href=3D"mailto:ancp@ietf.org">ancp@ietf.org</a>;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;Philippe Champagne (pchamp)<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; Subject: RE: question regarding Labels in<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;ANCP port up messages<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; Hi Maglione<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp; Yes, the label format is as defined in RFC<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;3292. The ANCP draft is<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; based on RFC 3292 and proposes<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;extensions/modifications where<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; required.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; This is clearly stated upfront both in the<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;abstract and in<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; section 2. In<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; section 5.4.2, it clearly&nbsp; specifies the<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;format of &quot;port up&quot; message<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; (based on RFC 3292), and explicitly states<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;the label field<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; should be set<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; to 0. Following is what the draft currently states:<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; 5.4.2 Topology Discovery Extensions<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; The GSMP Event message with PORT UP message<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;type (80) is used for<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; conveying DSL line attributes to the NAS.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;The version field should be<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; set to 3, and the sub field should be set to<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;1. The I and subMessage<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; fields SHOULD be set to 1 to signify no<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;fragmentation. The Port and<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; Label fields should be set to 0.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;
0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
2<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
3<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0 1 2 3 4 5 6 =
7 8 9
0 1 2 3 4 5 6 7<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;8 9 0 1 2 3 4 5<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; 6 7 8 9 0 1<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Vers&nbsp; =
|&nbsp;
Sub&nbsp; | Message Type&nbsp; |<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;Result|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Code<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; |<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Partition =
ID&nbsp; |<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;Transaction Identifier<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; |<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|I|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SubMessage
Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Length<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; |<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;
Port<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; |<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Port Session Number<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; |<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Event Sequence Number<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; |<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |x|S|x|x|<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; |<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+-+-+-+-+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Label<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; |<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ~<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; ~<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |x|x|x|x|x|x|x|x| =
Message
Type&nbsp; |<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;Tech Type&nbsp;&nbsp; | Block Length<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; |<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; |<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Extension Value<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; ~<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; |<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; When we say the label field should be set to<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;0, the intention<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; is for the<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; type and length fields in the label TLV to<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;be set to 0. We can<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; explicitly state this for clarity.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; -Sanjay<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;-----Original Message-----<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;From: Maglione Roberta<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;[mailto:<st1:PersonName =
w:st=3D"on">roberta.maglione@telecomitalia.it</st1:PersonName>
&lt;<a =
href=3D"mailto:roberta.maglione@telecomitalia.it">mailto:roberta.maglione=
@telecomitalia.it</a>&gt;
]<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;Sent: Tuesday, April 29, 2008 8:06 AM<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;To: <st1:PersonName w:st=3D"on">Sanjay =
Wadhwa</st1:PersonName><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;Cc: <st1:PersonName w:st=3D"on">Wojciech Dec</st1:PersonName> =
(wdec); <a
href=3D"mailto:ancp@ietf.org">ancp@ietf.org</a>;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;pchamp@cisco.com<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;Subject: RE: question regarding Labels in<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;ANCP port up messages<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;Hi Sanjay and All,<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp; I was reading the current ancp<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;protocol draft in order to<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt; understand which should be the correct<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;format for the label<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;field in the ancp port Up message.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;Actually as it was already pointed out in<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;the alias the draft<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;in section 5.4.2 says &quot;GSMP Event message<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;with PORT UP message<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;type (80) is used&quot;&nbsp; thus I am assuming that<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;the label in the<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;port UP message should follow the message<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;format defined in<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;RFC 3292, section 3.1.3:<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;
0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
1<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
3<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp; 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;0 1 2 3 4 5 6 7 8 9 0 1<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp; |x|S|x|x|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Label
Type&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp; Label Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp; |<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;
~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;
Label Value<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
~<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp; |<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;but from what I have seen different<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;implementations use<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;different format for label field: in<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;particular several<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;implementations use&nbsp; a label format that is<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;similar to the one<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;specified in the expired draft<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;draft-ietf-gsmp-v3-base-spec:<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;
0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
1<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt; =
2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
3<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0 1 2 3 4 5 6 7 8 9 0 1 2 =
3 4 5 6
7<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;8 9 0 1 2 3 4 5 6<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; 7 8 9 0 1<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|x|S|x|x|x|x|x|x|x|x|x|x|x|x|x|x|<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Label<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; Type&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp; Label
Adaptation&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp; Label<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;
Label Value<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ~<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;Even if ancp does not care about the label<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;field, having this<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;field somehow not clearly specified in the<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;current ancp draft<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;can easily lead to interoperability issues,<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;thus I think it<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;would be very helpful if you and/or the<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;other editors can<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;clarify what should be the correct format<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;for the label field<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;to be used in the ancp Port Up message.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;Thanks and best regards,<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;Roberta<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;________________________________________<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;From: Philippe Champagne (pchamp) [pchamp@cisco.com]<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;Sent: Thursday, April 24, 2008 7:14 PM<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;To: <st1:PersonName w:st=3D"on">Sanjay =
Wadhwa</st1:PersonName><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;Cc: Maglione Roberta; <st1:PersonName w:st=3D"on">Wojciech =
Dec</st1:PersonName>
(wdec);<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;ancp@ietf.org<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;Subject: question regarding&nbsp; Labels in ANCP<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;port up messages<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;Hi Sanjay<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;In section 5.4.2 of the draft, we have:<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
2<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 3<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0 1 2 3 4 5 6 =
7 8 9 0
1 2 3 4 5 6<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;7 8 9 0 1 2 3 4 5 6<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;7 8 9 0 1<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Vers&nbsp; |&nbsp;
Sub&nbsp; | Message Type&nbsp; |<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;Result|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Code<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Partition ID&nbsp; =
|<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;Transaction Identifier<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|I|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SubMessage =
Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Length<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;
Port<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Port Session Number<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Event Sequence Number<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |x|S|x|x|<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+-+-+-+-+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Label<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ~<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ~<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |x|x|x|x|x|x|x|x| =
Message
Type&nbsp; |<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;Tech Type&nbsp;&nbsp; |<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;Block Length&nbsp; |<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Extension Value<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ~<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;Where Label I suppose is taken from the RFC<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;3292, section<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;3.1.3: (well, I'm guessing)<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp; A summary of TLV labels supported in<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;this version of the<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; protocol is<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp; listed below:<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; TLV =
Label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Type&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Section Title<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
---------&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
----&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -------------<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ATM =
Label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
0x100&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ATM TLV Labels<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; FR
Label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
0x101&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Frame Relay<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;TLV Labels<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MPLS Gen Label
0x102&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MPLS<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;Generic TLV Labels<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; FEC =
Label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
0x103&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; FEC TLV Labels<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp; All Labels will be designated as follow:<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;
0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
1<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
3<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp; 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;0 1 2 3 4 5 6 7 8 9 0 1<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp; |x|S|x|x|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Label
Type&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp; Label Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp; |<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;
~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;
Label Value<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
~<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp; |<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
|<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<br>=

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; x: Reserved Flags.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; These are =
generally
used by<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;specific messages and will be<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; defined in =
those
messages.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; S: Stacked Label Indicator<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Label Stacking =
is
discussed below<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;in section 3.1.3.5<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Label Type<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A 12-bit field
indicating the type<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;of label.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Label Length<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A 16-bit field
indicating the<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;length of the Label<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; Value field<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; in bytes.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Label Value<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A variable =
length
field that is an<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;integer number of 32 bit<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; words =
long.&nbsp; The
Label Value field<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;is interpreted<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; according to<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the Label Type =
as
described in the<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;following sections.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;The draft is a bit obscure about this and<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;since it doesn't<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;specify much, it can lead to<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;misinterpretation for the unused<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;part. Moreover, it would appear that<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;several implementations<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;currently use another format for the label<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;field. Can you<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;explain?&nbsp; I mean, how come what's in the<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;current draft doesn't<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;match what's known to be implemented?<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;I'm still wondering why we carried over<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;pieces from GSMP that<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;we do not intend to use.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;I would recommend that if we are to keep<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;them but not use<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;them, we should mention precisely how we<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;intend not to use<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;them: that is how many 0 filled bytes this<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;is expected to use<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;The rfc 3292 doesn't cover the case where<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;this field is not used.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;Can you shed some ligths on this?<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;Thanks<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;Regards<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;Phil<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&gt;-----------------------------------------------------------------=
---<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;CONFIDENTIALITY NOTICE<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;This message and its attachments are<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;addressed solely to the<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;persons above and may contain confidential<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;information. If you<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;have received the message in error, be<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;informed that any use<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;of the content hereof is prohibited. Please<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;return it<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;immediately to the sender and delete the<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;message. Should you<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;have any questions, please contact us by replying to<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;webmaster@telecomitalia.it.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Thank you<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;www.telecomitalia.it<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&gt;-----------------------------------------------------------------=
---<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt; &gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
_______________________________________________<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
ANCP mailing list<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
<a href=3D"mailto:ANCP@ietf.org">ANCP@ietf.org</a><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;
<a =
href=3D"https://www.ietf.org/mailman/listinfo/ancp">https://www.ietf.org/=
mailman/listinfo/ancp</a>
&lt;<a =
href=3D"https://www.ietf.org/mailman/listinfo/ancp">https://www.ietf.org/=
mailman/listinfo/ancp</a>&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&gt;<o:p></o:p></span></font></p>

</div>

</blockquote>

</div>

<DIV><FONT size=3D2><FONT=20
face=3D"Courier =
New">--------------------------------------------------------------------=
<BR>CONFIDENTIALITY=20
NOTICE<BR>This message and its attachments are addressed solely to the=20
persons<BR>above and may contain confidential information. If you have=20
received<BR>the message in error, be informed that any use of the =
content=20
hereof<BR>is prohibited. Please return it immediately to the sender and=20
delete<BR>the message. Should you have any questions, please contact us=20
by<BR>replying to </FONT><A =
href=3D"mailto:webmaster@telecomitalia.it"><FONT=20
face=3D"Courier New">webmaster@telecomitalia.it</FONT></A><FONT=20
face=3D"Courier New">.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Thank=20
you<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;=20
</FONT><A href=3D"http://www.telecomitalia.it"><FONT=20
face=3D"Courier New">www.telecomitalia.it</FONT></A><BR><FONT=20
face=3D"Courier =
New">--------------------------------------------------------------------=
</FONT></FONT></DIV>
</body>

</html>

--_000_A1F769BC58A8B146B2EEA818EAE052A20121E824BDGRFMBX702RM00_--

--===============1387474273==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1387474273==--


From ancp-bounces@ietf.org  Fri May  9 09:00:03 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id CEF623A68B7;
	Fri,  9 May 2008 09:00:03 -0700 (PDT)
X-Original-To: ancp@ietf.org
Delivered-To: ancp@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id 3AB333A67FA; Fri,  9 May 2008 09:00:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20080509160001.3AB333A67FA@core3.amsl.com>
Date: Fri,  9 May 2008 09:00:01 -0700 (PDT)
Cc: ancp@ietf.org
Subject: [ANCP] I-D Action:draft-ietf-ancp-framework-06.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/pipermail/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>
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org


--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-06.txt
	Pages           : 47
	Date            : 2008-05-09

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 OSS systems.

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

Content-Type: text/plain
Content-ID: <2008-05-09085530.I-D@ietf.org>


--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--NextPart--


From ancp-bounces@ietf.org  Fri May  9 09:22:16 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 44D3B3A67CE;
	Fri,  9 May 2008 09:22:16 -0700 (PDT)
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 7CB6B3A67FA
	for <ancp@core3.amsl.com>; Fri,  9 May 2008 09:22:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level: 
X-Spam-Status: No, score=x tagged_above=-999 required=5 tests=[]
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 pg2DgCbJyAD8 for <ancp@core3.amsl.com>;
	Fri,  9 May 2008 09:22:13 -0700 (PDT)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [61.144.161.7])
	by core3.amsl.com (Postfix) with ESMTP id A795C3A67C1
	for <ancp@ietf.org>; Fri,  9 May 2008 09:22:11 -0700 (PDT)
Received: from huawei.com (szxga04-in [172.24.2.12])
	by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0K0K00IHAWAM49@szxga04-in.huawei.com> for
	ancp@ietf.org; Fri, 09 May 2008 10:01:34 +0800 (CST)
Received: from huawei.com ([172.24.1.24])
	by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0K0K009KOWALOS@szxga04-in.huawei.com> for
	ancp@ietf.org; Fri, 09 May 2008 10:01:34 +0800 (CST)
Received: from z24109b ([10.70.76.172])
	by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0K0K007RIWAI47@szxml04-in.huawei.com> for
	ancp@ietf.org; Fri, 09 May 2008 10:01:33 +0800 (CST)
Date: Fri, 09 May 2008 10:01:32 +0800
From: Tina TSOU <tena@huawei.com>
To: Maglione Roberta <roberta.maglione@telecomitalia.it>,
	Sanjay Wadhwa <swadhwa@juniper.net>,
	Ole Helleberg Andersen <ole.helleberg.andersen@ericsson.com>,
	"Wojciech Dec (wdec)" <wdec@cisco.com>, Peter Arberg <parberg@redback.com>
Message-id: <004401c8b178$9ab53d60$ac4c460a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
X-Priority: 3
X-MSMail-priority: Normal
References: <48C276B536524E478C659685995F6AA539DBBBE370@RBSJX.ad.redback.com>
	<9BD5D7887235424FA97DFC223CAE3C280AB43A10@proton.jnpr.net>
	<48C276B536524E478C659685995F6AA539DBBBE577@RBSJX.ad.redback.com>
	<9BD5D7887235424FA97DFC223CAE3C28102EB5AA@proton.jnpr.net>
	<48C276B536524E478C659685995F6AA539DBBBEF99@RBSJX.ad.redback.com>
	<BAC301C0C1697C4EBDF97C805A273CBC9909C5@esealmw104.eemea.ericsson.se>
	<D9872168DBD43A41BD71FFC4713274D405043B12@xmb-ams-33b.emea.cisco.com>
	<48C276B536524E478C659685995F6AA560439CC824@RBSJX.ad.redback.com>
Cc: ancp@ietf.org
Subject: Re: [ANCP] question regarding  Labels in ANCP port up messages
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/pipermail/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>
Content-Type: multipart/mixed; boundary="===============0835228569=="
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0835228569==
Content-type: multipart/alternative;
 boundary="Boundary_(ID_60WhkCpDe7hqTW27/agLbA)"

This is a multi-part message in MIME format.

--Boundary_(ID_60WhkCpDe7hqTW27/agLbA)
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT

Dear Peter et al,
Comment in line.

B. R.
Tina
Messengers: 
MSN: tinatsou6@hotmail.com   Yahoo: tina_tsou    Skype: tinaTSOU    Jabber: tina@jabber.org    Google talk: tinatsou6@gmail.com
  ----- Original Message ----- 
  From: Peter Arberg 
  To: Wojciech Dec (wdec) ; Ole Helleberg Andersen ; Sanjay Wadhwa ; Tina TSOU ; Maglione Roberta 
  Cc: ancp@ietf.org 
  Sent: Friday, May 09, 2008 8:15 AM
  Subject: RE: [ANCP] question regarding Labels in ANCP port up messages


  Hi Woj,

  I think your proposal goes hand in hand with my suggestion to document the
  event message bit by bit instead of reference the RFC3292 or an expired old
  gsmp-draft.

  I will suggest we in the ANCP draft do a description in section
  5.4.2 something in these lines:

  The ANCP Event message with PORT UP message type (80) is used for
  conveying DSL line attributes to the NAS, and is defined as follows:


  0                   1                   2                   3
  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
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  | Vers  |  Sub  | Message Type  | Result|        Code           |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  | Partition ID  |            Transaction Identifier             |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |I|      SubMessage Number      |           Length              |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |                             Port                              |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |                      Port Session Number                      |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |                     Event Sequence Number                     |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |x|S|x|x|                                                       |
  +-+-+-+-+                     Label                             |
  |                                                               |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |x|x|x|x|x|x|x|x| Message Type  |   Tech Type   | Block Length  |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |                                                               |
  ~                         Extension Value                       ~
  |                                                               |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+


  Version field is 1 byte, 4 bits for the major version and 4
  bits for the sub-version, should be set to 3, and the sub field
  should be set to 1.

  Message Type is 1 byte, and can have the following values:
  ...

  Result ...

  Code ...

  Partition ID ...

  ....


  Label field is 8 bytes, should be set to 0 on transmit and ignored on receive.

  ....

  So the idea is to document every single field in the event message,
  and list what is the expected transmit value, and what should the
  receiver do with the field.


  I will actually suggest we remove the "label" name and just call the
  unused field "reserved" and must be set to 0 on transmit and ignored on
  receive.
  [Tina: I really support Peter at this point.]

  If we simply call them "reserved" we always have the option to reuse them
  in alater contribution / new version if theer ever should be a need to
  use some bits in the event message header.


  Also as another comment, I still think it will be beneficial if we
  describe that the version number check should be per adjacency, so
  we in the future can do a version change easy and allow the ANCP
  implementation to have multiple adjacency with different versions of the
  protocol, if we ever see a reason to increase the version number it
  will give a much easier upgrade scenario.

  cheers,
  Peter


  cheers,
  Peter




  ________________________________

          From: Wojciech Dec (wdec) [mailto:wdec@cisco.com]
          Sent: 7. maj 2008 14:14
          To: Ole Helleberg Andersen; Peter Arberg; Sanjay Wadhwa; Tina TSOU; Maglione Roberta
          Cc: ancp@ietf.org
          Subject: RE: [ANCP] question regarding Labels in ANCP port up messages


          Hi All,

          it's with a certain amount of incredulity that I view the proposals on this thread for changing the version number of the protocol. Were such proposals to be accepted, by definition it would make most likely the ANCP draft incompatible with *all* current implementations, or at the very least introduce a compatibility mess in existing deployments short of a flag day change over, not to mention the issue of depreciating the old version.
          There really seems to be no reason to go through with a version change due to what may be attributed as a day 1 draft problem but *not* a day 1 implementation problem. Also, it is not the first time that the protocol spec draft has had some inaccuracies, and we've visited this aspect previously resulting in the following versioning strategy being laid out: http://www.ietf.org/mail-archive/web/ancp/current/msg00152.html . While the strategy states that an ANCP version change will not be considered due to "incompatibilities arising from implementations of pre-RFC drafts", neither does it state that the draft cannot change to reflect current implementations while keeping the version.

          Now, given that there seems to be some uneasiness (but thankfully not absolute) in the WG to come forward publicly with details of what is currently implemented, I have conducted a behind the scenes investigation of sorts, and present the summarized findings below:
          - There are 10 distinct implementations of ANCP
          - Out of these 9 either directly implement the label field format in as per section 5.3 of draft-gsmpv3-base-spec-08, or each is known to be compatible with at least 2 implementations that do so. By association, it seems reasonable to claim that all of these ANCP implementations use the draft-gsmpv3-base-spec-08 format. Also, all use version 3.1 as the protocol version, and the base protocol header also as per draft-gsmpv3-base-spec-08
          - One implementation is known to use the draft-ietf-ancp-protocol-02 format of the label field format, ie the rfc3292 format. This implementation is not known to be compatible with any of the others.

          Based on this, but not only, the obvious answer to the problem is *not* to do a version change, but rather fix the draft. Granted, this is a far from ideal situation for the one implementation affected, and it's a true shame that the problem wasn't spotted earlier. Like Peter I also wonder how any interop was achieved, but the fact that it is there is a significant one that should not be undone by hasty version changes. As such option 2 below is not one we'll be taking forward. Option 1 however also comes short as it does not quite follow the logic of simply documenting what is known to be interoperable in the WG draft. If specific implementations choose to realize knobs or other, fine, but this is not part of the protocol spec, and there is no such thing as "old label format". Please do consider the third option, ie fixing the draft to reflect what is already done.

          This fact in general highlights the problems we're having in carrying with the GSMPv3 (rfc3292) legacy, alongside adopted amendments from draft-gsmpv3-base-spec (this Label issue not being the only adopted item), alongside new protocol work. I trust that all of you agree that getting maximum clarity on all the legacy issues and dependencies in the protocol spec is in the WG's best interest, and that we are still some way off from that. As such I also expect the WG to support moves/proposals aimed at getting that clarity, with resolving this issue being not the first and not the last such move.

          Regards,
          Woj.





  ________________________________

                  From: Ole Helleberg Andersen [mailto:ole.helleberg.andersen@ericsson.com]
                  Sent: 06 May 2008 14:04
                  To: Peter Arberg; Sanjay Wadhwa; Tina TSOU; Maglione Roberta; Wojciech Dec (wdec)
                  Cc: ancp@ietf.org
                  Subject: RE: [ANCP] question regarding Labels in ANCP port up messages


                  Hi All,

                                  I think the main issue is to ensure interoperability with existing implementations, and to allow for upgrading nodes that are already in service to a WG-draft compliant version. To do that in a manageable way we must allow for version negotiation per adjacency. We therefore need to change the WG-draft as suggested by Sanjay in his option 2.

                  Concerning the encoding issue I prefer to make the WG-draft in line with existing implementations. However, if the WG decides to change it, differences in this encoding would also be solved by choosing Sanjay's option 2.

                  Cheers,
                  Ole

  ________________________________

                  From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of Peter Arberg
                  Sent: 2. maj 2008 20:52
                  To: Sanjay Wadhwa; Tina TSOU; Maglione Roberta; Wojciech Dec (wdec)
                  Cc: ancp@ietf.org
                  Subject: Re: [ANCP] question regarding Labels in ANCP port up messages


                  Hi Sanjay,

                  yes apparently I missed your point in the last email, but I'm glad we agree something is needed
                  to make existing ANCP implementations and the current draft to co-exist.

                  I do not like your option 1) as if you need a config knob for interoperability, it is too easy to
                  get into trouble.

                  I think option 2) is the best way forward with the differences already identified, or we can
                  continue to get a show of hands of ANCP implementations, and see if anyone is actually
                  deployed based on the WG-draft.

                  There is no beneficial reasons to base the event-message of RFC3292, it could as well be a message
                  described bit by bit in the ANCP draft, and then we can keep the label space at 8 as many
                  implementations alreday do.

                  cheers,
                  Peter





  ________________________________

                          From: Sanjay Wadhwa [mailto:swadhwa@juniper.net]
                          Sent: 2. maj 2008 05:35
                          To: Peter Arberg; Tina TSOU; Maglione Roberta; Wojciech Dec (wdec)
                          Cc: ancp@ietf.org
                          Subject: RE: [ANCP] question regarding Labels in ANCP port up messages



                          Peter

                           You missed my point below. The ANCP draft since becoming a WG draft does NOT refer to the old GSMP drafts. Any implementations based on this WG-draft are expected to be interoperable. You are pointing to pre-WG-draft versions of ANCP, and these were indeed based on expired GSMP drafts that evolved past RFC3292.

                          There is incompatibility between the current ANCP WG-draft and previous non-WG versions (TLV clash, label format..). As mentioned earlier it is prudent for older implementations to start supporting the WG-draft version as soon as possible.



                          For interoperability of WG-draft with the older pre-WG versions, I see the following options:



                          1. Versioning starts with the WG-draft i.e. WG-draft is version = 3, sub-version = 1. For any interop issues between older non-WG versions and the WG-draft, one needs to look at solving it within implementations (e.g. an AN that implements the WG-draft, could based on a configuration knob, generate a PORT-UP message with old label format the will be accepted by BNG implementing pre-WG versions of the draft).



                          2. Change the WG-draft (current draft) to use version = 3 and sub-version = 2. This is assuming there is no deployed implementation of current WG-draft that already uses 3.1 as the version, and also assuming the old pre-WG implementations use 3.1. There will be no backwards compatibility i.e. version 3.1 BNG will not work with version 3.2 AN (we will need to list this as caveat in the appendix section). AN and BNG will need to negotiate the same version in order for ANCP adjacency to come up. A BNG supporting both versions 3.1 and 3.2 could simultaneously become adjacent with one AN supporting 3.1 and another AN supporting 3.2. (i.e. version compatibility is per adjacency).

                          Also, major version number change (e.g. from 3 to 4) should only correspond to a major change in the protocol (e.g. different mechanism, different transport etc).



                          My vote would be to adopt option 2 above only if further changes to WG-draft happen that render it incompatible with the current WG-draft. Any interoperability issues with pre-WG versions could be handled via option 1.



                          Cheers

                          -Sanjay



                          ________________________________

                                                  From: Peter Arberg [mailto:parberg@redback.com]
                          Sent: Wednesday, April 30, 2008 7:20 PM
                          To: Sanjay Wadhwa; Tina TSOU; Maglione Roberta; Wojciech Dec (wdec)
                          Cc: ancp@ietf.org
                          Subject: RE: [ANCP] question regarding Labels in ANCP port up messages



                          Sanjay,



                          What do you mean "why I reference an old draft"  ????????????



                          I'm surprised you even ask...  please take a look at YOUR own internet-draft that most

                          of the ANCP working implementations are based on, in case you do not have this old

                          internet-draft, I have attached it to the document.



                          If you look at the reference for this ancp-draft, you will see that in the reference section

                          you point to this old gsmp-draft...  Yes and I know this has been changed in the later

                          versions of the ANCP draft, but that do not change the fact that many of the implementations

                          today was developed when the attached draft was current.



                          I think a very good question is brought up here, and that is what is implemented and

                          running in networks today ?



                          My take on this is that when the reference was change from the old gsmp-draft to the older

                          RFC3292, apparently no one paid any attention to the fact the label definition in the event

                          message was different and not compatible.



                          What current implementations do today is an important factor in this discussion, and I think

                          it is time to come to realization that we might need a new version number for ANCP since

                          it continues to look like there is big holes open for interpretation. So if I did a ANCP

                          implementation there is bound to be interoperability issues with existing implementations

                          runnig.



                          cheers,

                          Peter









                                  ________________________________

                                                                  From: Sanjay Wadhwa [mailto:swadhwa@juniper.net]
                                  Sent: 30. april 2008 14:42
                                  To: Peter Arberg; Tina TSOU; Maglione Roberta; Wojciech Dec (wdec)
                                  Cc: ancp@ietf.org
                                  Subject: RE: [ANCP] question regarding Labels in ANCP port up messages

                                  Peter
                                    The ANCP draft as it currently stands is based on RFC3292. It provides extensions and modifications to relevant constructs in RFC3292. There is no mention (implicit or explicit) of expired GSMP drafts in the ANCP draft. In order to implement the ANCP draft, I am not sure why one would look at the expired GSMP drafts. Do you see a reason to do this based on anything that you read in the ANCP draft? Bringing up reference to expired gsmp draft in this thread just adds to the confusion. For GSMPv3 objects in the messages (such as Label Type), one has to look at RFC3292 (this is clearly stated in the ANCP draft - section 2 and I am quoting it below) :

                                  ANCP uses a subset of GSMPv3 messages to implement currently defined use-cases. These relevant GSMPv3 messages are identified in section 5. GSMPv3 procedures with suitable extensions, as used by ANCP, are described in sections 5.1, 5.2 and 5.3. GSMPv3 general extensions and GSMPv3 message specific extensions required by ANCP are described in sub-sections of 5.4. In addition to specifying extensions and modifications to relevant GSMP messages applicable to ANCP, this draft also defines the usage of these messages by ANCP, and indicates the values that ANCP should set for relevant fields in these GSMP messages. However, to understand the basic semantics of various fields in GSMP messages, the reader is referred to [4]. => RFC 3292.

                                  What existing implementations currently do is an important but separate issue. These implementations for most part precede the current ANCP draft. It is fine to poll where these implementations diverge from the current draft. It is then upto the implementations (including the one that I am somewhat familiar with) to work towards compliance with the draft.

                                  On the following points from  Woj:

                                  Woj>2) The current version of the spec is not accurate, and does not reflect the fact that the known implementations follow the label field definition from draft-gsmpv3-base-spec.

                                  It is not for the protocol draft to point out what current implementations do.  The best we can do is to further clarify in the draft that type and value fields of the Label object (defined in RFC3292) should be set to 0 in the port-up message (we already mention the lable object as a whole should be set to all 0s).

                                  Woj> This would be a good thing for the WG to discuss. There most evidently is a fair amount of "dead wood" in the current spec, ie stuff that nobody yet implements or cares about.  In the former case, we could re-cast that material using the new notions/extensions, in the latter case simply chop it out.

                                  I agree. We are based on GSMPv3 (RFC3292)  messages, and obviously not everything in these messages is leveraged by ANCP.  However, the sync rate and OAM uses-cases are implemented and in use (ideally we should leave these alone...i.e. no change beyond adding more clarity if needed). For anything new (such as multicast) we are defining new messages (no legacy).

                                  -Sanjay

                                  >-----Original Message-----
                                  >From: Peter Arberg [mailto:parberg@redback.com <mailto:parberg@redback.com> ]
                                  >Sent: Wednesday, April 30, 2008 3:56 PM
                                  >To: Tina TSOU; Maglione Roberta; Sanjay Wadhwa; Wojciech Dec (wdec)
                                  >Cc: ancp@ietf.org
                                  >Subject: RE: [ANCP] question regarding Labels in ANCP port up messages
                                  >
                                  >
                                  >Hi,
                                  >
                                  >some times I think it is amazing we ever got interoperability
                                  >of ANCP :-)
                                  >because looking at the label discussion is a very good example that the
                                  >whole GSMP - ANCP reference have not worked very well.
                                  >
                                  >In the ANCP draft, section 5.4.2 the event message is shown like this:
                                  >
                                  >0                   1                   2                   3
                                  >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
                                  >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                  >| Vers  |  Sub  | Message Type  | Result|        Code           |
                                  >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                  >| Partition ID  |            Transaction Identifier             |
                                  >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                  >|I|      SubMessage Number      |           Length              |
                                  >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                  >|                             Port                              |
                                  >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                  >|                      Port Session Number                      |
                                  >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                  >|                     Event Sequence Number                     |
                                  >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                  >|x|S|x|x|                                                       |
                                  >+-+-+-+-+                     Label                             |
                                  >~                                                               ~
                                  >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                  >|x|x|x|x|x|x|x|x| Message Type  |   Tech Type   | Block Length  |
                                  >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                  >|                                                               |
                                  >~                         Extension Value                       ~
                                  >|                                                               |
                                  >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                  >
                                  >
                                  >This is the exact same event message defined in
                                  >draft-ietf-gsmp-v3-base-spec-08.txt  section 11.
                                  >
                                  >And in this gsmp-draft, section 5.1.3 the label space is defined
                                  >as minimum 8 bytes if the length=0 and as such no value, and this
                                  >is because the gsmp-draft has a new "label adaptaion" field.
                                  >
                                  >
                                  >
                                  >BUT in RFC3292 the event message is show in section 9, like this:
                                  >
                                  >0                   1                   2                   3
                                  >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
                                  >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                  >|    Version    | Message Type  |    Result     |     Code      |
                                  >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                  >| Partition ID  |            Transaction Identifier             |
                                  >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                  >|I|      SubMessage Number      |           Length              |
                                  >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                  >|                             Port                              |
                                  >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                  >|                      Port Session Number                      |
                                  >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                  >|                     Event Sequence Number                     |
                                  >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                  >|x|S|x|x|                                                       |
                                  >+-+-+-+-+                     Label                             |
                                  >~                                                               ~
                                  >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                  >
                                  >
                                  >So a different Event Message picture/definition than what is shown
                                  >in the ANCP draft, and in RFC3292 section 3.1.3 the label field
                                  >is defined as 4 bytes if length=0 and as such no value.
                                  >
                                  >
                                  >
                                  >So I very much agree with Woj that we need this issue to be resolved,
                                  >and proabably a show of hands what is actually done in different
                                  >implementations, so we can nail down how the event message is
                                  >suppose to look like in ANCP.
                                  >
                                  >
                                  >I know at least 1 implementation which uses 8 bytes for the
                                  >label field.
                                  >
                                  >
                                  >cheers,
                                  >Peter
                                  >
                                  >
                                  >
                                  >
                                  >
                                  >
                                  >________________________________
                                  >
                                  >        From: ancp-bounces@ietf.org
                                  >[mailto:ancp-bounces@ietf.org <mailto:ancp-bounces@ietf.org> ] On Behalf Of Tina TSOU
                                  >        Sent: 30. april 2008 00:19
                                  >        To: Maglione Roberta; Sanjay Wadhwa; Wojciech Dec (wdec)
                                  >        Cc: ancp@ietf.org
                                  >        Subject: Re: [ANCP] question regarding Labels in ANCP
                                  >port up messages
                                  >
                                  >
                                  >        Hi all,
                                  >        It is clear to me that if Label Length is filled as 0,
                                  >there is nothing to be filled into Label Value. The whole
                                  >Label part is 4 bytes, not 8 bytes.
                                  >
                                  >        Cheers from the last working day before Labor's Day
                                  >holidays in some countries:)
                                  >
                                  >        Tina
                                  >
                                  >                ----- Original Message -----
                                  >                From: Wojciech Dec (wdec) <mailto:wdec@cisco.com <mailto:wdec@cisco.com> >
                                  >                To: Sanjay Wadhwa <mailto:swadhwa@juniper.net <mailto:swadhwa@juniper.net> >
                                  > ; Maglione Roberta <mailto:roberta.maglione@telecomitalia.it <mailto:roberta.maglione@telecomitalia.it> >
                                  >                Cc: ancp@ietf.org
                                  >                Sent: Wednesday, April 30, 2008 1:12 AM
                                  >                Subject: Re: [ANCP] question regarding Labels
                                  >in ANCP port up messages
                                  >
                                  >                Sanjay, All,
                                  >
                                  >                What is stated below runs counter to at least
                                  >a handful of ANCP
                                  >                implementations, all of which are known to be
                                  >interoperable.
                                  >                There are really two options:
                                  >                1) The current version of the spec is correct,
                                  >and the known
                                  >                interoperable implementations do not follow it
                                  >                2) The current version of the spec is not
                                  >accurate, and does not reflect
                                  >                the fact that the known implementations follow
                                  >the label field
                                  >                definition from draft-gsmpv3-base-spec.
                                  >
                                  >                I would like to ask you, as the lead editor of
                                  >the spec, to work with
                                  >                the WG in resolving what the problem is, and
                                  >clearing up what the WG
                                  >                spec says about and if 1) holds to be true,
                                  >then proposing an
                                  >                interoperability fix.
                                  >
                                  >                In either case, the issue highlights the fact
                                  >that there is still
                                  >                lingering confusion as to the dependencies
                                  >ANCP has on rfc3292, or
                                  >                draft-gsmpv3-base-spec, or both. It seems to
                                  >be in the best interest of
                                  >                all to address these.
                                  >
                                  >                Regards,
                                  >                Woj.
                                  >
                                  >                > -----Original Message-----
                                  >                > From: Sanjay Wadhwa [mailto:swadhwa@juniper.net <mailto:swadhwa@juniper.net> ]
                                  >                > Sent: 29 April 2008 17:29
                                  >                > To: Maglione Roberta
                                  >                > Cc: Wojciech Dec (wdec); ancp@ietf.org;
                                  >Philippe Champagne (pchamp)
                                  >                > Subject: RE: question regarding Labels in
                                  >ANCP port up messages
                                  >                >
                                  >                > Hi Maglione
                                  >                >   Yes, the label format is as defined in RFC
                                  >3292. The ANCP draft is
                                  >                > based on RFC 3292 and proposes
                                  >extensions/modifications where
                                  >                > required.
                                  >                > This is clearly stated upfront both in the
                                  >abstract and in
                                  >                > section 2. In
                                  >                > section 5.4.2, it clearly  specifies the
                                  >format of "port up" message
                                  >                > (based on RFC 3292), and explicitly states
                                  >the label field
                                  >                > should be set
                                  >                > to 0. Following is what the draft currently states:
                                  >                >
                                  >                >
                                  >                > 5.4.2 Topology Discovery Extensions
                                  >                >
                                  >                > The GSMP Event message with PORT UP message
                                  >type (80) is used for
                                  >                > conveying DSL line attributes to the NAS.
                                  >The version field should be
                                  >                > set to 3, and the sub field should be set to
                                  >1. The I and subMessage
                                  >                > fields SHOULD be set to 1 to signify no
                                  >fragmentation. The Port and
                                  >                > Label fields should be set to 0.
                                  >                >
                                  >                >  0                   1                   2
                                  >                3
                                  >                >          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
                                  >                >
                                  >                >
                                  >                >
                                  >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                  >                >         | Vers  |  Sub  | Message Type  |
                                  >Result|        Code
                                  >                > |
                                  >                >
                                  >                >
                                  >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                  >                >         | Partition ID  |
                                  >Transaction Identifier
                                  >                > |
                                  >                >
                                  >                >
                                  >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                  >                >         |I|      SubMessage Number      |
                                  >       Length
                                  >                > |
                                  >                >
                                  >                >
                                  >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                  >                >         |                             Port
                                  >                > |
                                  >                >
                                  >                >
                                  >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                  >                >         |                      Port Session Number
                                  >                > |
                                  >                >
                                  >                >
                                  >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                  >                >         |                     Event Sequence Number
                                  >                > |
                                  >                >
                                  >                >
                                  >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                  >                >         |x|S|x|x|
                                  >                > |
                                  >                >         +-+-+-+-+                     Label
                                  >                > |
                                  >                >         ~
                                  >                > ~
                                  >                >
                                  >                >
                                  >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                  >                >         |x|x|x|x|x|x|x|x| Message Type  |
                                  >Tech Type   | Block Length
                                  >                > |
                                  >                >
                                  >                >
                                  >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                  >                >         |
                                  >                > |
                                  >                >         ~                         Extension Value
                                  >                > ~
                                  >                >         |
                                  >                > |
                                  >                >
                                  >                >
                                  >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                  >                >
                                  >                > When we say the label field should be set to
                                  >0, the intention
                                  >                > is for the
                                  >                > type and length fields in the label TLV to
                                  >be set to 0. We can
                                  >                > explicitly state this for clarity.
                                  >                >
                                  >                > -Sanjay
                                  >                >
                                  >                > >-----Original Message-----
                                  >                > >From: Maglione Roberta
                                  >[mailto:roberta.maglione@telecomitalia.it <mailto:roberta.maglione@telecomitalia.it> ]
                                  >                > >Sent: Tuesday, April 29, 2008 8:06 AM
                                  >                > >To: Sanjay Wadhwa
                                  >                > >Cc: Wojciech Dec (wdec); ancp@ietf.org;
                                  >pchamp@cisco.com
                                  >                > >Subject: RE: question regarding Labels in
                                  >ANCP port up messages
                                  >                > >
                                  >                > >
                                  >                > >Hi Sanjay and All,
                                  >                > >     I was reading the current ancp
                                  >protocol draft in order to
                                  >                > > understand which should be the correct
                                  >format for the label
                                  >                > >field in the ancp port Up message.
                                  >                > >Actually as it was already pointed out in
                                  >the alias the draft
                                  >                > >in section 5.4.2 says "GSMP Event message
                                  >with PORT UP message
                                  >                > >type (80) is used"  thus I am assuming that
                                  >the label in the
                                  >                > >port UP message should follow the message
                                  >format defined in
                                  >                > >RFC 3292, section 3.1.3:
                                  >                > >
                                  >                > >    0                   1
                                  >2                   3
                                  >                > >    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
                                  >                > >
                                  >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                  >                > >   |x|S|x|x|       Label Type      |
                                  >  Label Length         |
                                  >                > >
                                  >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                  >                > >   |
                                  >                       |
                                  >                > >   ~                          Label Value
                                  >                       ~
                                  >                > >   |
                                  >                       |
                                  >                > >
                                  >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                  >                > >
                                  >                > >but from what I have seen different
                                  >implementations use
                                  >                > >different format for label field: in
                                  >particular several
                                  >                > >implementations use  a label format that is
                                  >similar to the one
                                  >                > >specified in the expired draft
                                  >draft-ietf-gsmp-v3-base-spec:
                                  >                > >
                                  >                > >     0                   1
                                  > 2                   3
                                  >                > >       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
                                  >                > >
                                  >                >
                                  >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                  >                > >      |x|S|x|x|x|x|x|x|x|x|x|x|x|x|x|x|
                                  >       Label
                                  >                > Type         |
                                  >                > >
                                  >                >
                                  >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                  >                > >      |    Label Adaptation           |
                                  >     Label
                                  >                > Length         |
                                  >                > >
                                  >                >
                                  >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                  >                > >      |
                                  >                >          |
                                  >                > >      ~                          Label Value
                                  >                >          ~
                                  >                > >      |
                                  >                >          |
                                  >                > >
                                  >                >
                                  >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                  >                > >
                                  >                > >
                                  >                > >Even if ancp does not care about the label
                                  >field, having this
                                  >                > >field somehow not clearly specified in the
                                  >current ancp draft
                                  >                > >can easily lead to interoperability issues,
                                  >thus I think it
                                  >                > >would be very helpful if you and/or the
                                  >other editors can
                                  >                > >clarify what should be the correct format
                                  >for the label field
                                  >                > >to be used in the ancp Port Up message.
                                  >                > >
                                  >                > >Thanks and best regards,
                                  >                > >Roberta
                                  >                > >
                                  >                > >________________________________________
                                  >                > >From: Philippe Champagne (pchamp) [pchamp@cisco.com]
                                  >                > >Sent: Thursday, April 24, 2008 7:14 PM
                                  >                > >To: Sanjay Wadhwa
                                  >                > >Cc: Maglione Roberta; Wojciech Dec (wdec);
                                  >ancp@ietf.org
                                  >                > >Subject: question regarding  Labels in ANCP
                                  >port up messages
                                  >                > >
                                  >                > >Hi Sanjay
                                  >                > >
                                  >                > >In section 5.4.2 of the draft, we have:
                                  >                > >
                                  >                > >
                                  >                > >         0                   1                   2
                                  >                >         3
                                  >                > >         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
                                  >                > >
                                  >                >
                                  >>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                  >                > >        | Vers  |  Sub  | Message Type  |
                                  >Result|        Code
                                  >                > >         |
                                  >                > >
                                  >                >
                                  >>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                  >                > >        | Partition ID  |
                                  >Transaction Identifier
                                  >                > >         |
                                  >                > >
                                  >                >
                                  >>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                  >                > >        |I|      SubMessage Number      |
                                  >        Length
                                  >                > >         |
                                  >                > >
                                  >                >
                                  >>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                  >                > >        |                             Port
                                  >                > >         |
                                  >                > >
                                  >                >
                                  >>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                  >                > >        |                      Port Session Number
                                  >                > >         |
                                  >                > >
                                  >                >
                                  >>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                  >                > >        |                     Event Sequence Number
                                  >                > >         |
                                  >                > >
                                  >                >
                                  >>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                  >                > >        |x|S|x|x|
                                  >                > >         |
                                  >                > >        +-+-+-+-+                     Label
                                  >                > >         |
                                  >                > >        ~
                                  >                > >         ~
                                  >                > >
                                  >                >
                                  >>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                  >                > >        |x|x|x|x|x|x|x|x| Message Type  |
                                  >Tech Type   |
                                  >                > >Block Length  |
                                  >                > >
                                  >                >
                                  >>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                  >                > >        |
                                  >                > >         |
                                  >                > >        ~                         Extension Value
                                  >                > >         ~
                                  >                > >        |
                                  >                > >         |
                                  >                > >
                                  >                >
                                  >>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                  >                > >Where Label I suppose is taken from the RFC
                                  >3292, section
                                  >                > >3.1.3: (well, I'm guessing)
                                  >                > >
                                  >                > >   A summary of TLV labels supported in
                                  >this version of the
                                  >                > protocol is
                                  >                > >   listed below:
                                  >                > >
                                  >                > >      TLV Label      Type       Section Title
                                  >                > >      ---------      ----       -------------
                                  >                > >      ATM Label      0x100      ATM TLV Labels
                                  >                > >      FR Label       0x101      Frame Relay
                                  >TLV Labels
                                  >                > >      MPLS Gen Label 0x102      MPLS
                                  >Generic TLV Labels
                                  >                > >      FEC Label      0x103      FEC TLV Labels
                                  >                > >
                                  >                > >   All Labels will be designated as follow:
                                  >                > >
                                  >                > >    0                   1
                                  >2                   3
                                  >                > >    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
                                  >                > >
                                  >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                  >                > >   |x|S|x|x|       Label Type      |
                                  >  Label Length         |
                                  >                > >
                                  >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                  >                > >   |
                                  >                       |
                                  >                > >   ~                          Label Value
                                  >                       ~
                                  >                > >   |
                                  >                       |
                                  >                > >
                                  >+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                  >                > >
                                  >                > >      x: Reserved Flags.
                                  >                > >         These are generally used by
                                  >specific messages and will be
                                  >                > >         defined in those messages.
                                  >                > >
                                  >                > >      S: Stacked Label Indicator
                                  >                > >         Label Stacking is discussed below
                                  >in section 3.1.3.5
                                  >                > >
                                  >                > >      Label Type
                                  >                > >         A 12-bit field indicating the type
                                  >of label.
                                  >                > >
                                  >                > >      Label Length
                                  >                > >         A 16-bit field indicating the
                                  >length of the Label
                                  >                > Value field
                                  >                > >         in bytes.
                                  >                > >
                                  >                > >      Label Value
                                  >                > >         A variable length field that is an
                                  >integer number of 32 bit
                                  >                > >         words long.  The Label Value field
                                  >is interpreted
                                  >                > according to
                                  >                > >         the Label Type as described in the
                                  >following sections.
                                  >                > >
                                  >                > >
                                  >                > >The draft is a bit obscure about this and
                                  >since it doesn't
                                  >                > >specify much, it can lead to
                                  >misinterpretation for the unused
                                  >                > >part. Moreover, it would appear that
                                  >several implementations
                                  >                > >currently use another format for the label
                                  >field. Can you
                                  >                > >explain?  I mean, how come what's in the
                                  >current draft doesn't
                                  >                > >match what's known to be implemented?
                                  >                > >
                                  >                > >I'm still wondering why we carried over
                                  >pieces from GSMP that
                                  >                > >we do not intend to use.
                                  >                > >
                                  >                > >I would recommend that if we are to keep
                                  >them but not use
                                  >                > >them, we should mention precisely how we
                                  >intend not to use
                                  >                > >them: that is how many 0 filled bytes this
                                  >is expected to use
                                  >                > >
                                  >                > >The rfc 3292 doesn't cover the case where
                                  >this field is not used.
                                  >                > >
                                  >                > >Can you shed some ligths on this?
                                  >                > >
                                  >                > >Thanks
                                  >                > >Regards
                                  >                > >Phil
                                  >                > >
                                  >                > >
                                  >                > >
                                  >                >
                                  >>--------------------------------------------------------------------
                                  >                > >
                                  >                > >CONFIDENTIALITY NOTICE
                                  >                > >
                                  >                > >This message and its attachments are
                                  >addressed solely to the
                                  >                > >persons above and may contain confidential
                                  >information. If you
                                  >                > >have received the message in error, be
                                  >informed that any use
                                  >                > >of the content hereof is prohibited. Please
                                  >return it
                                  >                > >immediately to the sender and delete the
                                  >message. Should you
                                  >                > >have any questions, please contact us by replying to
                                  >                > >webmaster@telecomitalia.it.
                                  >                > >
                                  >                > >        Thank you
                                  >                > >
                                  >                > >
                                  >www.telecomitalia.it
                                  >                > >
                                  >                >
                                  >>--------------------------------------------------------------------
                                  >                > >
                                  >                > >
                                  >                >
                                  >                _______________________________________________
                                  >                ANCP mailing list
                                  >                ANCP@ietf.org
                                  >                https://www.ietf.org/mailman/listinfo/ancp <https://www.ietf.org/mailman/listinfo/ancp>
                                  >
                                  >

--Boundary_(ID_60WhkCpDe7hqTW27/agLbA)
Content-type: text/html; charset=iso-8859-1
Content-transfer-encoding: 7BIT

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2900.3243" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>Dear Peter et al,</FONT></DIV>
<DIV><FONT face=Arial size=2>Comment in line.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV>B. R.<BR>Tina<BR>Messengers: <BR>MSN: <A 
href="mailto:tinatsou6@hotmail.com">tinatsou6@hotmail.com</A>&nbsp;&nbsp; Yahoo: 
tina_tsou&nbsp;&nbsp;&nbsp; Skype: tinaTSOU&nbsp;&nbsp;&nbsp; Jabber: <A 
href="mailto:tina@jabber.org">tina@jabber.org</A>&nbsp;&nbsp;&nbsp; Google talk: 
<A href="mailto:tinatsou6@gmail.com">tinatsou6@gmail.com</A></DIV>
<BLOCKQUOTE 
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
  <DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV 
  style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B> 
  <A title=parberg@redback.com href="mailto:parberg@redback.com">Peter 
  Arberg</A> </DIV>
  <DIV style="FONT: 10pt arial"><B>To:</B> <A title=wdec@cisco.com 
  href="mailto:wdec@cisco.com">Wojciech Dec (wdec)</A> ; <A 
  title=ole.helleberg.andersen@ericsson.com 
  href="mailto:ole.helleberg.andersen@ericsson.com">Ole Helleberg Andersen</A> ; 
  <A title=swadhwa@juniper.net href="mailto:swadhwa@juniper.net">Sanjay 
  Wadhwa</A> ; <A title=tena@huawei.com href="mailto:tena@huawei.com">Tina 
  TSOU</A> ; <A title=roberta.maglione@telecomitalia.it 
  href="mailto:roberta.maglione@telecomitalia.it">Maglione Roberta</A> </DIV>
  <DIV style="FONT: 10pt arial"><B>Cc:</B> <A title=ancp@ietf.org 
  href="mailto:ancp@ietf.org">ancp@ietf.org</A> </DIV>
  <DIV style="FONT: 10pt arial"><B>Sent:</B> Friday, May 09, 2008 8:15 AM</DIV>
  <DIV style="FONT: 10pt arial"><B>Subject:</B> RE: [ANCP] question regarding 
  Labels in ANCP port up messages</DIV>
  <DIV><BR></DIV>
  <DIV>Hi Woj,<BR><BR>I think your proposal goes hand in hand with my suggestion 
  to document the<BR>event message bit by bit instead of reference the RFC3292 
  or an expired old<BR>gsmp-draft.<BR><BR>I will suggest we in the ANCP draft do 
  a description in section<BR>5.4.2 something in these lines:<BR><BR>The ANCP 
  Event message with PORT UP message type (80) is used for<BR>conveying DSL line 
  attributes to the NAS, and is defined as 
  follows:<BR><BR><BR>0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  3<BR>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<BR>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>| 
  Vers&nbsp; |&nbsp; Sub&nbsp; | Message Type&nbsp; | 
  Result|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Code&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |<BR>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>| 
  Partition ID&nbsp; 
  |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Transaction 
  Identifier&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |<BR>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>|I|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  SubMessage Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |<BR>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Port&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |<BR>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Port Session 
  Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |<BR>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Event Sequence 
  Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |<BR>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>|x|S|x|x|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |<BR>+-+-+-+-+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |<BR>|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |<BR>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>|x|x|x|x|x|x|x|x| 
  Message Type&nbsp; |&nbsp;&nbsp; Tech Type&nbsp;&nbsp; | Block Length&nbsp; 
  |<BR>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |<BR>~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Extension 
  Value&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  ~<BR>|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |<BR>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR><BR><BR>Version 
  field is 1 byte, 4 bits for the major version and 4<BR>bits for the 
  sub-version, should be set to 3, and the sub field<BR>should be set to 
  1.<BR><BR>Message Type is 1 byte, and can have the following 
  values:<BR>...<BR><BR>Result ...<BR><BR>Code ...<BR><BR>Partition ID 
  ...<BR><BR>....<BR><BR><BR>Label field is 8 bytes, should be set to 0 on 
  transmit and ignored on receive.<BR><BR>....<BR><BR>So the idea is to document 
  every single field in the event message,<BR>and list what is the expected 
  transmit value, and what should the<BR>receiver do with the 
  field.<BR><BR><BR>I will actually suggest we remove the "label" name and just 
  call the<BR>unused field "reserved" and must be set to 0 on transmit and 
  ignored on<BR>receive.<BR><FONT face=Arial color=#0000ff size=2>[Tina: I 
  really support Peter at this point.]</FONT></DIV><FONT face=Arial 
  size=2></FONT></BLOCKQUOTE>
<BLOCKQUOTE 
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
  <DIV><BR>If we simply call them "reserved" we always have the option to reuse 
  them<BR>in alater contribution / new version if theer ever should be a need 
  to<BR>use some bits in the event message header.<BR><BR><BR>Also as another 
  comment, I still think it will be beneficial if we<BR>describe that the 
  version number check should be per adjacency, so<BR>we in the future can do a 
  version change easy and allow the ANCP<BR>implementation to have multiple 
  adjacency with different versions of the<BR>protocol, if we ever see a reason 
  to increase the version number it<BR>will give a much easier upgrade 
  scenario.<BR><BR>cheers,<BR>Peter<BR><BR><BR>cheers,<BR>Peter<BR><BR><BR><BR><BR>________________________________<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  From: Wojciech Dec (wdec) 
  [mailto:wdec@cisco.com]<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Sent: 7. 
  maj 2008 14:14<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; To: Ole Helleberg 
  Andersen; Peter Arberg; Sanjay Wadhwa; Tina TSOU; Maglione 
  Roberta<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Cc: <A 
  href="mailto:ancp@ietf.org">ancp@ietf.org</A><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Subject: RE: [ANCP] question regarding Labels in ANCP port up 
  messages<BR><BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Hi 
  All,<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; it's with a certain 
  amount of incredulity that I view the proposals on this thread for changing 
  the version number of the protocol. Were such proposals to be accepted, by 
  definition it would make most likely the ANCP draft incompatible with *all* 
  current implementations, or at the very least introduce a compatibility mess 
  in existing deployments short of a flag day change over, not to mention the 
  issue of depreciating the old 
  version.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; There really seems to 
  be no reason to go through with a version change due to what may be attributed 
  as a day 1 draft problem but *not* a day 1 implementation problem. Also, it is 
  not the first time that the protocol spec draft has had some inaccuracies, and 
  we've visited this aspect previously resulting in the following versioning 
  strategy being laid out: <A 
  href="http://www.ietf.org/mail-archive/web/ancp/current/msg00152.html">http://www.ietf.org/mail-archive/web/ancp/current/msg00152.html</A> 
  . While the strategy states that an ANCP version change will not be considered 
  due to "incompatibilities arising from implementations of pre-RFC drafts", 
  neither does it state that the draft cannot change to reflect current 
  implementations while keeping the 
  version.<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Now, given that 
  there seems to be some uneasiness (but thankfully not absolute) in the WG to 
  come forward publicly with details of what is currently implemented, I have 
  conducted a behind the scenes investigation of sorts, and present the 
  summarized findings below:<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - 
  There are 10 distinct implementations of 
  ANCP<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - Out of these 9 either 
  directly implement the label field format in as per section 5.3 of 
  draft-gsmpv3-base-spec-08, or each is known to be compatible with at least 2 
  implementations that do so. By association, it seems reasonable to claim that 
  all of these ANCP implementations use the draft-gsmpv3-base-spec-08 format. 
  Also, all use version 3.1 as the protocol version, and the base protocol 
  header also as per 
  draft-gsmpv3-base-spec-08<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - One 
  implementation is known to use the draft-ietf-ancp-protocol-02 format of the 
  label field format, ie the rfc3292 format. This implementation is not known to 
  be compatible with any of the 
  others.<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Based on this, but 
  not only, the obvious answer to the problem is *not* to do a version change, 
  but rather fix the draft. Granted, this is a far from ideal situation for the 
  one implementation affected, and it's a true shame that the problem wasn't 
  spotted earlier. Like Peter I also wonder how any interop was achieved, but 
  the fact that it is there is a significant one that should not be undone by 
  hasty version changes. As such option 2 below is not one we'll be taking 
  forward. Option 1 however also comes short as it does not quite follow the 
  logic of simply documenting what is known to be interoperable in the WG draft. 
  If specific implementations choose to realize knobs or other, fine, but this 
  is not part of the protocol spec, and there is no such thing as "old label 
  format". Please do consider the third option, ie fixing the draft to reflect 
  what is already done.<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; This 
  fact in general highlights the problems we're having in carrying with the 
  GSMPv3 (rfc3292) legacy, alongside adopted amendments from 
  draft-gsmpv3-base-spec (this Label issue not being the only adopted item), 
  alongside new protocol work. I trust that all of you agree that getting 
  maximum clarity on all the legacy issues and dependencies in the protocol spec 
  is in the WG's best interest, and that we are still some way off from that. As 
  such I also expect the WG to support moves/proposals aimed at getting that 
  clarity, with resolving this issue being not the first and not the last such 
  move.<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Regards,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Woj.<BR><BR><BR><BR><BR><BR>________________________________<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  From: Ole Helleberg Andersen 
  [mailto:ole.helleberg.andersen@ericsson.com]<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Sent: 06 May 2008 
  14:04<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  To: Peter Arberg; Sanjay Wadhwa; Tina TSOU; Maglione Roberta; Wojciech Dec 
  (wdec)<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Cc: <A 
  href="mailto:ancp@ietf.org">ancp@ietf.org</A><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Subject: RE: [ANCP] question regarding Labels in ANCP port up 
  messages<BR><BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Hi 
  All,<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  I think the main issue is to ensure interoperability with existing 
  implementations, and to allow for upgrading nodes that are already in service 
  to a WG-draft compliant version. To do that in a manageable way we must allow 
  for version negotiation per adjacency. We therefore need to change the 
  WG-draft as suggested by Sanjay in his option 
  2.<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Concerning the encoding issue I prefer to make the WG-draft in line with 
  existing implementations. However, if the WG decides to change it, differences 
  in this encoding would also be solved by choosing Sanjay's option 
  2.<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Cheers,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Ole<BR><BR>________________________________<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  From: <A href="mailto:ancp-bounces@ietf.org">ancp-bounces@ietf.org</A> 
  [mailto:ancp-bounces@ietf.org] On Behalf Of Peter 
  Arberg<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Sent: 2. maj 2008 
  20:52<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  To: Sanjay Wadhwa; Tina TSOU; Maglione Roberta; Wojciech Dec 
  (wdec)<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Cc: <A 
  href="mailto:ancp@ietf.org">ancp@ietf.org</A><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Subject: Re: [ANCP] question regarding Labels in ANCP port up 
  messages<BR><BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Hi 
  Sanjay,<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  yes apparently I missed your point in the last email, but I'm glad we agree 
  something is 
  needed<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  to make existing ANCP implementations and the current draft to 
  co-exist.<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  I do not like your option 1) as if you need a config knob for 
  interoperability, it is too easy 
  to<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  get into 
  trouble.<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  I think option 2) is the best way forward with the differences already 
  identified, or we 
  can<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  continue to get a show of hands of ANCP implementations, and see if anyone is 
  actually<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  deployed based on the 
  WG-draft.<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  There is no beneficial reasons to base the event-message of RFC3292, it could 
  as well be a 
  message<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  described bit by bit in the ANCP draft, and then we can keep the label space 
  at 8 as 
  many<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  implementations alreday 
  do.<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  cheers,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Peter<BR><BR><BR><BR><BR><BR>________________________________<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  From: Sanjay Wadhwa 
  [mailto:swadhwa@juniper.net]<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Sent: 2. maj 2008 
  05:35<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  To: Peter Arberg; Tina TSOU; Maglione Roberta; Wojciech Dec 
  (wdec)<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Cc: <A 
  href="mailto:ancp@ietf.org">ancp@ietf.org</A><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Subject: RE: [ANCP] question regarding Labels in ANCP port up 
  messages<BR><BR><BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Peter<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  You missed my point below. The ANCP draft since becoming a WG draft does NOT 
  refer to the old GSMP drafts. Any implementations based on this WG-draft are 
  expected to be interoperable. You are pointing to pre-WG-draft versions of 
  ANCP, and these were indeed based on expired GSMP drafts that evolved past 
  RFC3292.<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  There is incompatibility between the current ANCP WG-draft and previous non-WG 
  versions (TLV clash, label format..). As mentioned earlier it is prudent for 
  older implementations to start supporting the WG-draft version as soon as 
  possible.<BR><BR><BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  For interoperability of WG-draft with the older pre-WG versions, I see the 
  following 
  options:<BR><BR><BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  1. Versioning starts with the WG-draft i.e. WG-draft is version = 3, 
  sub-version = 1. For any interop issues between older non-WG versions and the 
  WG-draft, one needs to look at solving it within implementations (e.g. an AN 
  that implements the WG-draft, could based on a configuration knob, generate a 
  PORT-UP message with old label format the will be accepted by BNG implementing 
  pre-WG versions of the 
  draft).<BR><BR><BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  2. Change the WG-draft (current draft) to use version = 3 and sub-version = 2. 
  This is assuming there is no deployed implementation of current WG-draft that 
  already uses 3.1 as the version, and also assuming the old pre-WG 
  implementations use 3.1. There will be no backwards compatibility i.e. version 
  3.1 BNG will not work with version 3.2 AN (we will need to list this as caveat 
  in the appendix section). AN and BNG will need to negotiate the same version 
  in order for ANCP adjacency to come up. A BNG supporting both versions 3.1 and 
  3.2 could simultaneously become adjacent with one AN supporting 3.1 and 
  another AN supporting 3.2. (i.e. version compatibility is per 
  adjacency).<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Also, major version number change (e.g. from 3 to 4) should only correspond to 
  a major change in the protocol (e.g. different mechanism, different transport 
  etc).<BR><BR><BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  My vote would be to adopt option 2 above only if further changes to WG-draft 
  happen that render it incompatible with the current WG-draft. Any 
  interoperability issues with pre-WG versions could be handled via option 
  1.<BR><BR><BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Cheers<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  -Sanjay<BR><BR><BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  ________________________________<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  From: Peter Arberg 
  [mailto:parberg@redback.com]<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Sent: Wednesday, April 30, 2008 7:20 
  PM<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  To: Sanjay Wadhwa; Tina TSOU; Maglione Roberta; Wojciech Dec 
  (wdec)<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Cc: <A 
  href="mailto:ancp@ietf.org">ancp@ietf.org</A><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Subject: RE: [ANCP] question regarding Labels in ANCP port up 
  messages<BR><BR><BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Sanjay,<BR><BR><BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  What do you mean "why I reference an old draft"&nbsp; 
  ????????????<BR><BR><BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  I'm surprised you even ask...&nbsp; please take a look at YOUR own 
  internet-draft that 
  most<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  of the ANCP working implementations are based on, in case you do not have this 
  old<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  internet-draft, I have attached it to the 
  document.<BR><BR><BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  If you look at the reference for this ancp-draft, you will see that in the 
  reference 
  section<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  you point to this old gsmp-draft...&nbsp; Yes and I know this has been changed 
  in the 
  later<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  versions of the ANCP draft, but that do not change the fact that many of the 
  implementations<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  today was developed when the attached draft was 
  current.<BR><BR><BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  I think a very good question is brought up here, and that is what is 
  implemented 
  and<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  running in networks today 
  ?<BR><BR><BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  My take on this is that when the reference was change from the old gsmp-draft 
  to the 
  older<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  RFC3292, apparently no one paid any attention to the fact the label definition 
  in the 
  event<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  message was different and not 
  compatible.<BR><BR><BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  What current implementations do today is an important factor in this 
  discussion, and I 
  think<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  it is time to come to realization that we might need a new version number for 
  ANCP 
  since<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  it continues to look like there is big holes open for interpretation. So if I 
  did a 
  ANCP<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  implementation there is bound to be interoperability issues with existing 
  implementations<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  runnig.<BR><BR><BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  cheers,<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Peter<BR><BR><BR><BR><BR><BR><BR><BR><BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  ________________________________<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  From: Sanjay Wadhwa 
  [mailto:swadhwa@juniper.net]<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Sent: 30. april 2008 
  14:42<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  To: Peter Arberg; Tina TSOU; Maglione Roberta; Wojciech Dec 
  (wdec)<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Cc: <A 
  href="mailto:ancp@ietf.org">ancp@ietf.org</A><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Subject: RE: [ANCP] question regarding Labels in ANCP port up 
  messages<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Peter<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  The ANCP draft as it currently stands is based on RFC3292. It provides 
  extensions and modifications to relevant constructs in RFC3292. There is no 
  mention (implicit or explicit) of expired GSMP drafts in the ANCP draft. In 
  order to implement the ANCP draft, I am not sure why one would look at the 
  expired GSMP drafts. Do you see a reason to do this based on anything that you 
  read in the ANCP draft? Bringing up reference to expired gsmp draft in this 
  thread just adds to the confusion. For GSMPv3 objects in the messages (such as 
  Label Type), one has to look at RFC3292 (this is clearly stated in the ANCP 
  draft - section 2 and I am quoting it below) 
  :<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  ANCP uses a subset of GSMPv3 messages to implement currently defined 
  use-cases. These relevant GSMPv3 messages are identified in section 5. GSMPv3 
  procedures with suitable extensions, as used by ANCP, are described in 
  sections 5.1, 5.2 and 5.3. GSMPv3 general extensions and GSMPv3 message 
  specific extensions required by ANCP are described in sub-sections of 5.4. In 
  addition to specifying extensions and modifications to relevant GSMP messages 
  applicable to ANCP, this draft also defines the usage of these messages by 
  ANCP, and indicates the values that ANCP should set for relevant fields in 
  these GSMP messages. However, to understand the basic semantics of various 
  fields in GSMP messages, the reader is referred to [4]. =&gt; RFC 
  3292.<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  What existing implementations currently do is an important but separate issue. 
  These implementations for most part precede the current ANCP draft. It is fine 
  to poll where these implementations diverge from the current draft. It is then 
  upto the implementations (including the one that I am somewhat familiar with) 
  to work towards compliance with the 
  draft.<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  On the following points from&nbsp; 
  Woj:<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Woj&gt;2) The current version of the spec is not accurate, and does not 
  reflect the fact that the known implementations follow the label field 
  definition from 
  draft-gsmpv3-base-spec.<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  It is not for the protocol draft to point out what current implementations 
  do.&nbsp; The best we can do is to further clarify in the draft that type and 
  value fields of the Label object (defined in RFC3292) should be set to 0 in 
  the port-up message (we already mention the lable object as a whole should be 
  set to all 
  0s).<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Woj&gt; This would be a good thing for the WG to discuss. There most evidently 
  is a fair amount of "dead wood" in the current spec, ie stuff that nobody yet 
  implements or cares about.&nbsp; In the former case, we could re-cast that 
  material using the new notions/extensions, in the latter case simply chop it 
  out.<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  I agree. We are based on GSMPv3 (RFC3292)&nbsp; messages, and obviously not 
  everything in these messages is leveraged by ANCP.&nbsp; However, the sync 
  rate and OAM uses-cases are implemented and in use (ideally we should leave 
  these alone...i.e. no change beyond adding more clarity if needed). For 
  anything new (such as multicast) we are defining new messages (no 
  legacy).<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  -Sanjay<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;-----Original 
  Message-----<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;From: Peter Arberg [mailto:parberg@redback.com &lt;<A 
  href="mailto:parberg@redback.com">mailto:parberg@redback.com</A>&gt; 
  ]<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;Sent: Wednesday, April 30, 2008 3:56 
  PM<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;To: Tina TSOU; Maglione Roberta; Sanjay Wadhwa; Wojciech Dec 
  (wdec)<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;Cc: <A 
  href="mailto:ancp@ietf.org">ancp@ietf.org</A><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;Subject: RE: [ANCP] question regarding Labels in ANCP port up 
  messages<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;Hi,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;some times I think it is amazing we ever got 
  interoperability<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;of ANCP 
  :-)<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;because looking at the label discussion is a very good example that 
  the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;whole GSMP - ANCP reference have not worked very 
  well.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;In the ANCP draft, section 5.4.2 the event message is shown like 
  this:<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  3<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;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<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;| Vers&nbsp; |&nbsp; Sub&nbsp; | Message Type&nbsp; | 
  Result|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Code&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;| Partition ID&nbsp; 
  |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Transaction 
  Identifier&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;|I|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SubMessage 
  Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Port&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Port Session 
  Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Event Sequence 
  Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;|x|S|x|x|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;+-+-+-+-+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  ~<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;|x|x|x|x|x|x|x|x| Message Type&nbsp; |&nbsp;&nbsp; Tech Type&nbsp;&nbsp; | 
  Block Length&nbsp; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Extension 
  Value&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  ~<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;This is the exact same event message defined 
  in<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;draft-ietf-gsmp-v3-base-spec-08.txt&nbsp; section 
  11.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;And in this gsmp-draft, section 5.1.3 the label space is 
  defined<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;as minimum 8 bytes if the length=0 and as such no value, and 
  this<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;is because the gsmp-draft has a new "label adaptaion" 
  field.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;BUT in RFC3292 the event message is show in section 9, like 
  this:<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  3<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;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<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;|&nbsp;&nbsp;&nbsp; Version&nbsp;&nbsp;&nbsp; | Message Type&nbsp; 
  |&nbsp;&nbsp;&nbsp; Result&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp; 
  Code&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;| Partition ID&nbsp; 
  |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Transaction 
  Identifier&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;|I|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SubMessage 
  Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Port&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Port Session 
  Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Event Sequence 
  Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;|x|S|x|x|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;+-+-+-+-+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  ~<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;So a different Event Message picture/definition than what is 
  shown<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;in the ANCP draft, and in RFC3292 section 3.1.3 the label 
  field<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;is defined as 4 bytes if length=0 and as such no 
  value.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;So I very much agree with Woj that we need this issue to be 
  resolved,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;and proabably a show of hands what is actually done in 
  different<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;implementations, so we can nail down how the event message 
  is<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;suppose to look like in 
  ANCP.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;I know at least 1 implementation which uses 8 bytes for 
  the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;label 
  field.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;cheers,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;Peter<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;________________________________<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; From: <A 
  href="mailto:ancp-bounces@ietf.org">ancp-bounces@ietf.org</A><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;[mailto:ancp-bounces@ietf.org &lt;<A 
  href="mailto:ancp-bounces@ietf.org">mailto:ancp-bounces@ietf.org</A>&gt; ] On 
  Behalf Of Tina 
  TSOU<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Sent: 30. april 2008 
  00:19<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; To: Maglione Roberta; Sanjay 
  Wadhwa; Wojciech Dec 
  (wdec)<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Cc: <A 
  href="mailto:ancp@ietf.org">ancp@ietf.org</A><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Subject: Re: [ANCP] question 
  regarding Labels in 
  ANCP<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;port up 
  messages<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Hi 
  all,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; It is clear to me that if Label 
  Length is filled as 
  0,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;there is nothing to be filled into Label Value. The 
  whole<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;Label part is 4 bytes, not 8 
  bytes.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Cheers from the last working 
  day before Labor's 
  Day<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;holidays in some 
  countries:)<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Tina<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  ----- Original Message 
  -----<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  From: Wojciech Dec (wdec) &lt;<A 
  href="mailto:wdec@cisco.com">mailto:wdec@cisco.com</A> &lt;<A 
  href="mailto:wdec@cisco.com">mailto:wdec@cisco.com</A>&gt; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  To: Sanjay Wadhwa &lt;<A 
  href="mailto:swadhwa@juniper.net">mailto:swadhwa@juniper.net</A> &lt;<A 
  href="mailto:swadhwa@juniper.net">mailto:swadhwa@juniper.net</A>&gt; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; ; Maglione Roberta &lt;<A 
  href="mailto:roberta.maglione@telecomitalia.it">mailto:roberta.maglione@telecomitalia.it</A> 
  &lt;<A 
  href="mailto:roberta.maglione@telecomitalia.it">mailto:roberta.maglione@telecomitalia.it</A>&gt; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Cc: <A 
  href="mailto:ancp@ietf.org">ancp@ietf.org</A><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Sent: Wednesday, April 30, 2008 1:12 
  AM<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Subject: Re: [ANCP] question regarding 
  Labels<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;in ANCP port up 
  messages<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Sanjay, 
  All,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  What is stated below runs counter to at 
  least<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;a handful of 
  ANCP<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  implementations, all of which are known to 
  be<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;interoperable.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  There are really two 
  options:<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  1) The current version of the spec is 
  correct,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;and the 
  known<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  interoperable implementations do not follow 
  it<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  2) The current version of the spec is 
  not<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;accurate, and does not 
  reflect<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  the fact that the known implementations 
  follow<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;the label 
  field<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  definition from 
  draft-gsmpv3-base-spec.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  I would like to ask you, as the lead editor 
  of<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;the spec, to work 
  with<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  the WG in resolving what the problem is, 
  and<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;clearing up what the 
  WG<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  spec says about and if 1) holds to be 
  true,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;then proposing 
  an<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  interoperability 
  fix.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  In either case, the issue highlights the 
  fact<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;that there is 
  still<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  lingering confusion as to the 
  dependencies<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;ANCP has on rfc3292, 
  or<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  draft-gsmpv3-base-spec, or both. It seems 
  to<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;be in the best interest 
  of<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  all to address 
  these.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Regards,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Woj.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; -----Original 
  Message-----<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; From: Sanjay Wadhwa [mailto:swadhwa@juniper.net &lt;<A 
  href="mailto:swadhwa@juniper.net">mailto:swadhwa@juniper.net</A>&gt; 
  ]<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; Sent: 29 April 2008 
  17:29<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; To: Maglione 
  Roberta<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; Cc: Wojciech Dec (wdec); <A 
  href="mailto:ancp@ietf.org">ancp@ietf.org</A>;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;Philippe Champagne 
  (pchamp)<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; Subject: RE: question regarding Labels 
  in<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;ANCP port up 
  messages<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; Hi 
  Maglione<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp; Yes, the label format is as defined in 
  RFC<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;3292. The ANCP draft 
  is<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; based on RFC 3292 and 
  proposes<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;extensions/modifications 
  where<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  required.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; This is clearly stated upfront both in 
  the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;abstract and 
  in<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; section 2. 
  In<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; section 5.4.2, it clearly&nbsp; specifies 
  the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;format of "port up" 
  message<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; (based on RFC 3292), and explicitly 
  states<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;the label 
  field<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; should be 
  set<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; to 0. Following is what the draft currently 
  states:<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 5.4.2 Topology Discovery 
  Extensions<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; The GSMP Event message with PORT UP 
  message<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;type (80) is used 
  for<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; conveying DSL line attributes to the 
  NAS.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;The version field should 
  be<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; set to 3, and the sub field should be set 
  to<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;1. The I and 
  subMessage<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; fields SHOULD be set to 1 to signify 
  no<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;fragmentation. The Port 
  and<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; Label fields should be set to 
  0.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp; 
  0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  2<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  3<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0 1 2 3 4 5 6 7 8 9 
  0 1 2 3 4 5 6 
  7<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;8 9 0 1 2 3 4 
  5<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 6 7 8 9 0 
  1<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Vers&nbsp; |&nbsp; 
  Sub&nbsp; | Message Type&nbsp; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;Result|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Code<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Partition ID&nbsp; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;Transaction 
  Identifier<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |I|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SubMessage 
  Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Length<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Port<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Port Session 
  Number<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Event Sequence 
  Number<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |x|S|x|x|<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  +-+-+-+-+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Label<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  ~<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  ~<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |x|x|x|x|x|x|x|x| Message 
  Type&nbsp; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;Tech Type&nbsp;&nbsp; | Block 
  Length<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  ~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Extension 
  Value<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  ~<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; When we say the label field should be set 
  to<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;0, the 
  intention<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; is for 
  the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; type and length fields in the label TLV 
  to<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;be set to 0. We 
  can<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; explicitly state this for 
  clarity.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  -Sanjay<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;-----Original 
  Message-----<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;From: Maglione 
  Roberta<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;[mailto:roberta.maglione@telecomitalia.it &lt;<A 
  href="mailto:roberta.maglione@telecomitalia.it">mailto:roberta.maglione@telecomitalia.it</A>&gt; 
  ]<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;Sent: Tuesday, April 29, 2008 8:06 
  AM<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;To: Sanjay 
  Wadhwa<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;Cc: Wojciech Dec (wdec); <A 
  href="mailto:ancp@ietf.org">ancp@ietf.org</A>;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;pchamp@cisco.com<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;Subject: RE: question regarding Labels 
  in<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;ANCP port up 
  messages<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;Hi Sanjay and 
  All,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp; I was reading the current 
  ancp<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;protocol draft in order 
  to<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt; understand which should be the 
  correct<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;format for the 
  label<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;field in the ancp port Up 
  message.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;Actually as it was already pointed out 
  in<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;the alias the 
  draft<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;in section 5.4.2 says "GSMP Event 
  message<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;with PORT UP 
  message<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;type (80) is used"&nbsp; thus I am assuming 
  that<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;the label in 
  the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;port UP message should follow the 
  message<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;format defined 
  in<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;RFC 3292, section 
  3.1.3:<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp;&nbsp; 
  0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  1<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  3<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp;&nbsp; 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 
  9<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;0 1 2 3 4 5 6 7 8 9 0 
  1<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp; |x|S|x|x|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Label 
  Type&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp; Label Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp; 
  ~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Label 
  Value<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  ~<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;but from what I have seen 
  different<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;implementations 
  use<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;different format for label field: 
  in<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;particular 
  several<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;implementations use&nbsp; a label format that 
  is<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;similar to the 
  one<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;specified in the expired 
  draft<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;draft-ietf-gsmp-v3-base-spec:<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp; 
  0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  1<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  3<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 
  6 
  7<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;8 9 0 1 2 3 4 5 
  6<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 7 8 9 0 
  1<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |x|S|x|x|x|x|x|x|x|x|x|x|x|x|x|x|<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Label<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; Type&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp; Label 
  Adaptation&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp; 
  Label<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  ~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Label 
  Value<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  ~<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;Even if ancp does not care about the 
  label<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;field, having 
  this<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;field somehow not clearly specified in 
  the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;current ancp 
  draft<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;can easily lead to interoperability 
  issues,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;thus I think 
  it<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;would be very helpful if you and/or 
  the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;other editors 
  can<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;clarify what should be the correct 
  format<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;for the label 
  field<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;to be used in the ancp Port Up 
  message.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;Thanks and best 
  regards,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;Roberta<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;________________________________________<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;From: Philippe Champagne (pchamp) 
  [pchamp@cisco.com]<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;Sent: Thursday, April 24, 2008 7:14 
  PM<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;To: Sanjay 
  Wadhwa<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;Cc: Maglione Roberta; Wojciech Dec 
  (wdec);<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;ancp@ietf.org<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;Subject: question regarding&nbsp; Labels in 
  ANCP<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;port up 
  messages<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;Hi 
  Sanjay<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;In section 5.4.2 of the draft, we 
  have:<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  2<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  3<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0 1 2 3 4 5 6 7 8 9 
  0 1 2 3 4 5 
  6<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;7 8 9 0 1 2 3 4 5 
  6<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;7 8 9 0 
  1<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Vers&nbsp; |&nbsp; 
  Sub&nbsp; | Message Type&nbsp; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;Result|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Code<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Partition ID&nbsp; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;Transaction 
  Identifier<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |I|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SubMessage 
  Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Length<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Port<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Port Session 
  Number<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Event Sequence 
  Number<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |x|S|x|x|<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  +-+-+-+-+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Label<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  ~<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  ~<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |x|x|x|x|x|x|x|x| Message 
  Type&nbsp; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;Tech Type&nbsp;&nbsp; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;Block Length&nbsp; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  ~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Extension 
  Value<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  ~<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;Where Label I suppose is taken from the 
  RFC<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;3292, 
  section<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;3.1.3: (well, I'm 
  guessing)<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp; A summary of TLV labels supported 
  in<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;this version of 
  the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; protocol 
  is<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp; listed 
  below:<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; TLV 
  Label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Type&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Section 
  Title<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  ---------&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  ----&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  -------------<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ATM 
  Label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0x100&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ATM 
  TLV 
  Labels<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; FR 
  Label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0x101&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Frame 
  Relay<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;TLV 
  Labels<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MPLS Gen Label 
  0x102&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  MPLS<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;Generic TLV 
  Labels<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; FEC 
  Label&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0x103&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; FEC 
  TLV 
  Labels<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp; All Labels will be designated as 
  follow:<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp;&nbsp; 
  0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  1<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  3<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp;&nbsp; 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 
  9<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;0 1 2 3 4 5 6 7 8 9 0 
  1<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp; |x|S|x|x|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Label 
  Type&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp; Label Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp; 
  ~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  Label 
  Value<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  ~<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; x: Reserved 
  Flags.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; These are generally 
  used 
  by<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;specific messages and will 
  be<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; defined in those 
  messages.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; S: Stacked Label 
  Indicator<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Label Stacking is 
  discussed 
  below<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;in section 
  3.1.3.5<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Label 
  Type<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A 12-bit field 
  indicating the 
  type<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;of 
  label.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Label 
  Length<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A 16-bit field 
  indicating 
  the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;length of the 
  Label<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; Value 
  field<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; in 
  bytes.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Label 
  Value<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A variable length 
  field that is 
  an<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;integer number of 32 
  bit<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; words long.&nbsp; 
  The Label Value 
  field<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;is 
  interpreted<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; according 
  to<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the Label Type as 
  described in 
  the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;following 
  sections.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;The draft is a bit obscure about this 
  and<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;since it 
  doesn't<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;specify much, it can lead 
  to<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;misinterpretation for the 
  unused<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;part. Moreover, it would appear 
  that<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;several 
  implementations<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;currently use another format for the 
  label<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;field. Can 
  you<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;explain?&nbsp; I mean, how come what's in 
  the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;current draft 
  doesn't<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;match what's known to be 
  implemented?<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;I'm still wondering why we carried 
  over<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;pieces from GSMP 
  that<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;we do not intend to 
  use.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;I would recommend that if we are to 
  keep<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;them but not 
  use<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;them, we should mention precisely how 
  we<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;intend not to 
  use<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;them: that is how many 0 filled bytes 
  this<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;is expected to 
  use<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;The rfc 3292 doesn't cover the case 
  where<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;this field is not 
  used.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;Can you shed some ligths on 
  this?<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;Thanks<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;Regards<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;Phil<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&gt;--------------------------------------------------------------------<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;CONFIDENTIALITY 
  NOTICE<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;This message and its attachments 
  are<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;addressed solely to 
  the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;persons above and may contain 
  confidential<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;information. If 
  you<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;have received the message in error, 
  be<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;informed that any 
  use<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;of the content hereof is prohibited. 
  Please<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;return 
  it<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;immediately to the sender and delete 
  the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;message. Should 
  you<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;have any questions, please contact us by replying 
  to<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;webmaster@telecomitalia.it.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Thank 
  you<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;www.telecomitalia.it<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&gt;--------------------------------------------------------------------<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  _______________________________________________<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  ANCP mailing 
  list<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  <A 
  href="mailto:ANCP@ietf.org">ANCP@ietf.org</A><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  <A 
  href="https://www.ietf.org/mailman/listinfo/ancp">https://www.ietf.org/mailman/listinfo/ancp</A> 
  &lt;<A 
  href="https://www.ietf.org/mailman/listinfo/ancp">https://www.ietf.org/mailman/listinfo/ancp</A>&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  &gt;<BR></DIV></BLOCKQUOTE></BODY></HTML>

--Boundary_(ID_60WhkCpDe7hqTW27/agLbA)--

--===============0835228569==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============0835228569==--


From ancp-bounces@ietf.org  Fri May 16 04:21:12 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 405E53A6B20;
	Fri, 16 May 2008 04:21:12 -0700 (PDT)
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 0FAE53A6B21
	for <ancp@core3.amsl.com>; Fri, 16 May 2008 04:21:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.757
X-Spam-Level: 
X-Spam-Status: No, score=-3.757 tagged_above=-999 required=5 tests=[AWL=2.110, 
	BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_73=0.6,
	RCVD_IN_DNSWL_MED=-4, SARE_UNSUB18=0.131]
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 hMANV17aZinf for <ancp@core3.amsl.com>;
	Fri, 16 May 2008 04:21:06 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id E93EB3A6B19
	for <ancp@ietf.org>; Fri, 16 May 2008 04:21:03 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,497,1204498800"; d="scan'208,217";a="9088049"
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 16 May 2008 13:20:57 +0200
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m4GBKvGD031694; 
	Fri, 16 May 2008 13:20:57 +0200
Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com
	[144.254.231.71])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m4GBKvof017130;
	Fri, 16 May 2008 11:20:57 GMT
Received: from xmb-ams-33b.cisco.com ([144.254.231.86]) by
	xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 16 May 2008 13:20:57 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 16 May 2008 13:20:54 +0200
Message-ID: <D9872168DBD43A41BD71FFC4713274D4051366B9@xmb-ams-33b.emea.cisco.com>
In-Reply-To: <CD6A16F9BCCBBC4CBF5271C5F06EC3BD046F66@BLR-EC-MBX07.wipro.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ANCP] ANCP Multicast Control Message
Thread-Index: Acij+5MzWijMyW8RTPSeLUilx/6xkAAkhiQjBK4fpLA=
References: <CD6A16F9BCCBBC4CBF5271C5F06EC3BD046F62@BLR-EC-MBX07.wipro.com><C432BBDA.7733B%einarnn@cisco.com>
	<20080421220043.GI175@cisco.com>
	<CD6A16F9BCCBBC4CBF5271C5F06EC3BD046F66@BLR-EC-MBX07.wipro.com>
From: "Wojciech Dec (wdec)" <wdec@cisco.com>
To: <vishwanathan.sundaram@wipro.com>,
	"Toerless Eckert (eckert)" <eckert@cisco.com>,
	"Einar Nilsen-Nygaard (einarnn)" <einarnn@cisco.com>
X-OriginalArrivalTime: 16 May 2008 11:20:57.0611 (UTC)
	FILETIME=[E9AD6DB0:01C8B746]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=74317; t=1210936857;
	x=1211800857; c=relaxed/simple; s=amsdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=wdec@cisco.com;
	z=From:=20=22Wojciech=20Dec=20(wdec)=22=20<wdec@cisco.com>
	|Subject:=20RE=3A=20[ANCP]=20ANCP=20Multicast=20Control=20M
	essage |Sender:=20;
	bh=J7Aw8yL4fmhvhQ4E0FUsLAQ8DiULhDiWrS2vyEZJh0M=;
	b=akWcJFq8EiTaXhCDCUI/pTaZ59opxbpzVaxlmHkdHtXCEQvBnNuWwBjFyK
	uJsJ2o8TcG5nOIVhazRRHq0sEf8MCsaCDnF/2goWHE7eQOfv7iDznI6NHNYi
	QtOmTPU2/M;
Authentication-Results: ams-dkim-2; header.From=wdec@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim2001 verified; ); 
Cc: ancp@ietf.org
Subject: Re: [ANCP] ANCP Multicast Control Message
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/pipermail/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>
Content-Type: multipart/mixed; boundary="===============0791629900=="
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0791629900==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8B746.E945ED88"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8B746.E945ED88
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Vish,
=20
adding the VLAN tag as a mandatory parameter seems undesirable. The use =
or otherwise of "multicast VLANs" is a local configuration issue on the =
AN which could be set to a default, or at best an optional parameter in =
the ANCP request message.

Regards,
Woj.

________________________________

	From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of =
vishwanathan.sundaram@wipro.com
	Sent: 22 April 2008 17:40
	To: Toerless Eckert (eckert); Einar Nilsen-Nygaard (einarnn)
	Cc: ancp@ietf.org
	Subject: Re: [ANCP] ANCP Multicast Control Message
=09
=09
	Comments
	a> It would be good to add Vlan tag as one of the parameters to the =
add/delete command, as this will indicate which VLAN should be used for =
multicasting. DSL TR 101,  discusses about the multicast flow being =
associated with a VLAN (Multicast-Vlan). In this case, the Access Node, =
needs to be informed about the VLAN ID on which a particular Multicast =
group is being associated by the NAS.
	=20
	Cheers
	Vish
	=20
	=20
=09
=09


________________________________

	From: Toerless Eckert [mailto:eckert@cisco.com]
	Sent: Mon 4/21/2008 6:00 PM
	To: Einar Nilsen-Nygaard
	Cc: Vishwanathan Somasundaram (WT01 - TES-Access Networks); =
wdec@cisco.com; ancp@ietf.org
	Subject: Re: [ANCP] ANCP Multicast Control Message
=09
=09

	Some comments:
=09
	a) Please change the name of the two 'Length' fields in the
	   control mesages sucht hat they can be differentiated easier from
	   another and specify what is counted in them, eg:
=09
	    Type=3DReplication-Control (0x01)|             Length            |
	                                                 ^^^^^^
	  =20
	   suggest to change to RC-Length, explanation "total number of bytes
	   of the following TLVs plus the replication control header".
=09
	    Type =3D CommandCode           |              Length               =
|
	                                                ^^^^^^
=09
	   suggest to change to CC-Length, explanation "total number of
	   this CommandCode TLV, counting this header and the following
	   multicast flow bytes".
=09
	b) Please try to avoid using the term "group" when referring to
	   an address which is either an ASM (Any Source Multicast) group
	   address (aka: a single multicast group address, IPv4 or IPv6)
	   or an SSM channel (aka: source and group address).
=09
	   I would stroingly suggest to only use the term "multicast flow"
	   or multicast flow address, or just "flow", and define that term
	   in the beginning of the document to be either an ASN group or
	   SSM channel.
=09
	   Otherwise there will be lots of confusions about whether or not
	   SSM is well supported by ANCP.
=09
	c) Do not refer to rfc2362. That RFC is obsolete and replaced by =
rfc4601.
	   I do not see a good reason to refer to any PIM spec anyhow, just
	   resolve the references used within the PIM-SM spec, eg:
=09
	   http://www.iana.org/assignments/address-family-numbers
=09
	   or the like.
=09
	d) To identify an actual SSM channel, it would be preferrable IMHO
	   to have an address family identifier for an SSM channel, aka:
	   an IP(v6/v6) source IP address followed by a group address. As
	   above IANA URL has nothing like this defined, i think there are
	   two choices:
=09
	   -> I) I'll check what effort it is to get that defined through IANA.
=09
	   -> II) we stick with the existing specification, which is to
	      have a separate field addrfamily/encoding/group and one
	      addrfamily/encoding/source, but then i would very much
	      like to see very explicit description in the protocol spec
	      what sequeneces of addfamily/encoding/addr (AEA) elements are =
valid,
	      and how they have to be interpreted:
=09
	      for add/delete commands:
	        -> MUST support a single AEA argument where the address
	           is an IPv4/IPv6 address that is a multicast group.
	           (ASM case).
=09
	        -> MUST support TWO AEA argument where the address of the
	           first AEA is an IPv4/IPv6 address which is a unicast
	           address, and the second AEA is an IPv4/IPv6 address which
	           is a multicast address. Aka: SSM case.
	    =20
	      In the example text i see two things i am questioning:
=09
	        I) The (S,G) channels are encoded first group and then source.
	           That IMHO is not preferrable. I would rather suggest like
	           written above to encode first source and then group.
	       =20
	        II) The text is suggesting to have eg: multiple group AEA
	            following an add/delete TLV. I have no strong opinion
	            whether or not that should be supported, but if we conclude
	            it should be supported, then that should explicitly be =
mentioned
	            in the text (see also below). And that description would
	            then of course have to detail a bit how a list of AEAs
	            with ASM groups and SSM channels is to be encoded.
	            Particularily this case makes it of course important
	            to either be very clear how an SSM channel is encoded
	            (source first or group first), or even better use a =
separate
	            Address-Familty identifier as suggested above.
=09
	e) I do not see any suggestion on the command reply. Is there
	   supposed to be some failure and/or success return codes ?
=09
	f) As far as return codes are concerned: I would like to see some
	   clearer statement about the suggested atomicity (if that's a
	   valid english word ;-) of the execution of multiple flows
	   within a single add/delete/modify TLV as well as the flows across
	   multiple TLVs within the same replication control message.
=09
	   -> What happens if any individual flow add/delete fails ? The
	      document right now only seems to imply that the execution of
	      the following add/deletes is simply not executed.  That by
	      itself would require the NAS to either query all state to figure
	      out what actually was executed or to simply try everything again.
=09
	      If we would add a return code like the following, that would
	      not be necessary:
	    =20
	        "Sorry, error: all flows up to byte XX into the packet where
	         performed well, and the following flow failed to be
	         addeded/deleted, and the rest was not even tried"
	    =20
	      I am not sure if this type of error return is the preferred
	      solution, but if we do not mandate something better, then
	      it probably should be done.
	 =20
	   -> A better solution would be to imply some form of atomicity,
	      eg: either at TLV or at replication control level. Meaning:
	      the AN tries to execute add/delete/modifies, but if anything =
fails,
	      then everything is undone. Or better: Nothing is applied by
	      the AN unless it can make sure everything will succeed.
=09
	g) Atomicity is a hard bargain for the control/forwarding plane
	   of a router/switch/DSLAM i think. If there is a bunch of =
add/delete/modify
	   and all of those should only be applied if all of them will =
succeed...
	   good luck getting that actually implemented correctly in the
	   forwarding plane of any AN.
=09
	   The thing i could see us asking to be done atomically is really
	   JUST a single flow-swap, aka: replace exactly one flow with
	   another flow.
=09
	   So ultimately, i think:
=09
	   -> For add/delete commands we ask for no atomicity and the error
	      code returned should somehow point to the first flow within
	      a packet that failed. And provide some additional error code
	      why (which we could define the values for later). And this
	      should allow us to have multiple flows as arguments to a
	      single add/delete to be more efficient.
	 =20
	   -> a modify should be called "swap", and should support only
	      exactly two flows as the argument. This swap should work
	      atomically, aka: the join would not be executed if the leave
	      could not be done, and the leave should of course not be
	      executed if the join would not work.
	 =20
	   -> So maybe overall the error return code would be
	    =20
	      command#, flow#, why
=09
	      where command# would be pointing to the command (numbered 1 t N)
	      within the recplication control command that failed,
	      flow# would be the flow (1..M) within that command (always 1 for
	      a swap, as we only allow a single flow there), and why would be
	      some eg: 8-bit error code where we could define values for that
	      would help diagnosis.
=09
=09
	h) The degree to which a platform is able to implement even this
	   most simple atomic swap is of course subject to implementation.
=09
	Cheers
	    Toerless
	    =20
	On Mon, Apr 21, 2008 at 09:47:06PM +0100, Einar Nilsen-Nygaard wrote:
	> Vish,
	>
	> I actually think that freedom in how a =B3swap=B2 operation would be =
implemented
	> in terms of the ordering of stopping the first multicast flow and =
starting
	> the second is not desirable. By specifying that the delete must come =
before
	> the add and that the operation should be terminated upon the first =
error,
	> the current specification gives us what should be deterministic =
behavior
	> between any and all conforming implementations.
	>
	> In contrast, the freedom to implement a swap operation via some form =
of
	> modify leaves the door open to multiple ways in which a modify =
request could
	> fail, making error recovery more troublesome and vendor-specific =
which I do
	> not see as at all desirable.
	>
	> Cheers,
	>
	> Einar
	>
	> On 21/04/2008 20:12, "vishwanathan.sundaram@wipro.com"
	> <vishwanathan.sundaram@wipro.com> scribbled:
	>
	> > Einar,
	> > Modify command would be usefull from Access box perspective, as the =
underlying
	> > implementation in AN's would have the freedom to design their swap =
operation,
	> > instead of always first deleting the existing group entry and =
adding another
	> > entry.
	> >=20
	> > Thanks
	> > Vish
	> >=20
	> >
	> >
	> > From: einarnn [mailto:einarnn@cisco.com]
	> > Sent: Sun 4/20/2008 11:12 AM
	> > To: Vishwanathan Somasundaram (WT01 - TES-Access Networks); =
wdec@cisco.com;
	> > ancp@ietf.org
	> > Subject: Re: [ANCP] ANCP Multicast Control Message
	> >
	> > Vish,
	> >
	> > Overloading the second byte of the command code to contain the =
number of
	> > =B3modifications=B2 doesn=B9t seem a good approach and the space =
saving per packet,
	> > which will probably be only 4 bytes most of the time, seems almost =
irrelevant.
	> > I think it would be better to keep the fields in the message for a =
single
	> > task.
	> >
	> > Treating a sequence of commands as an atomic operation, as detailed =
in the
	> > text, and implementing a swap via a delete follow by an add, should =
give ANs
	> > the freedom to implement what are, in effect, swap operations quite
	> > efficiently. In this context, I=B9m not sure what a =B3modify=B2 =
command code will
	> > really add?
	> >
	> > Cheers,
	> >
	> > Einar
	> >
	> > On 16/04/2008 15:41, "vishwanathan.sundaram@wipro.com"
	> > <vishwanathan.sundaram@wipro.com> wrote:
	> >
	> >> Hi Woj,
	> >> Currently, the command codes for replication control message are
	> >> 1. add (0x01)
	> >> 2. delete (0x02)
	> >> 3. delete all (0x04).
	> >>
	> >> Looking at the multicast Swap message format, which is used when =
the NAS
	> >> wants to switch from one group to another,can we not handle this =
situation by
	> >> having a message type Modify (0x08).
	> >> By using this message type we can mention the multicast group =
address which
	> >> needs to be swapped by new multicast group address.
	> >> Since the Command Code is 2 bytes, the second byte can be used to =
mention the
	> >> number of multicast groups that needs to be swapped.
	> >> This will allow, for multiple multicast group swaps. This will =
also reduce
	> >> the size of the packet. Since these messages intended only between =
the NAS
	> >> and AN, the introduction of modify command type gives further ease =
to the
	> >> Access boxes in implementing the swaps, which attributes to zap =
latency.
	> >>
	> >>      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
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	> >>      |        Type (0x88-0C)         |           Length            =
  |
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	> >>      | Vers  |  Sub  |MessageType=3D90 | Result|        Code       =
    |
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	> >>      | Partition ID  |            Transaction Identifier =3D 0001  =
    |
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	> >>      |I|      SubMessage Number      |           Length            =
  |
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	> >>      | 0x01 (Replication-Control)    |             Length          =
  |
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	> >>      | 0x01 (Access-Loop-Circuit-ID) |        Client-ID Length     =
  |
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	> >>      |                                                             =
  |
	> >>      ~                      Port Client-ID                         =
  ~
	> >>      |                                                             =
  |
	> >>     =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	> >>      | Type=3DCommandCode: Modify(0x08)|           Length
	> >> |
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	> >>      | AddrFamily 01 | EncType 0x0    |  Mcast group: 239.23.2.2   =
         |
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|
	> >>      | AddrFamily 01 | EncType 0x0    |  Mcast Source: 10.1.1.1
	> >> |
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|
	> >>       | AddrFamily 01 | EncType 0x0   |  New Mcast group: =
239.55.3.2   |
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|
	> >>      | AddrFamily 01 | EncType 0x0    |  New Mcast Source: =
10.1.1.1      |
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|
	> >>
	> >> Looking into the DSL TR 101, it also discusses about the multicast =
flow being
	> >> associated with a VLAN (Multicast-Vlan). In this case, the Access =
Node, needs
	> >> to be informed about the VLAN ID on which a particular Multicast =
group is
	> >> being associated by the NAS. Can this information also be added as =
part of
	> >> the TLV in message.
	> >>
	> >> Thanks
	> >> Vish
	> >>
	> >>
	> >> From: ancp-bounces@ietf.org on behalf of Wojciech Dec (wdec)
	> >> Sent: Mon 4/14/2008 11:00 AM
	> >> To: ancp@ietf.org
	> >> Subject: [ANCP] ANCP Multicast Control Message
	> >>
	> >>
	> >>
	> >> Hi All,
	> >>
	> >> As discussed during our recent IETF 71 meeting, our protocol =
design team
	> >> has forged ahead with prioritized list of problems to address, the =
first
	> >> of which was defining the ANCP message extensions for multicast =
control,
	> >> aka unsolicited multicast control. The DT is working on the =
response
	> >> message and also the solicited multicast control mode.
	> >> Below, we present the outcome of the work, which represents both a
	> >> design team consensus as well as a proposal for adoption into the =
ANCP
	> >> protocol spec, draft-ietf-ancp-protocol (some editorial work will =
be
	> >> still required). Please review the proposal and share your =
comments. We
	> >> will assume acceptance of the proposal in principle otherwise.
	> >>
	> >> Regards,
	> >> Woj & Matthew.
	> >>
	> >>
	> >> 2       Replication Control Message
	> >>
	> >>
	> >> This message is sent by the ANCP Server (NAS) to the ANCP Client =
(AN)
	> >> with a directive to either add (join) or delete (leave) a port to =
or
	> >> from a multicast flow. Its format is as follow:
	> >>       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
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	> >>      |Type=3DReplication-Control (0x01)|             Length        =
    |
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	> >>      | 0x01 (Access-Loop-Circuit-ID) |        Client-ID Length     =
  |
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	> >>      |                                                             =
  |
	> >>      ~                      Port Client-ID                         =
  ~
	> >>      |                                                             =
  |
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	> >>
	> >> Following the Port Client-ID information, one or more Command TLV
	> >> components can be included and the Access Node should process them =
in
	> >> the order in which they are listed. The Access Node (ANCP Client) =
should
	> >> threat all the commands as a single command block to be viewed as =
a
	> >> whole and bail out immediately when one of them fails.
	> >> The format of command TLV is as follow:
	> >>
	> >>       0                   1                   2                   =
3
	> >>       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
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	> >>      |  Type =3D CommandCode           |          Length           =
    |
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	> >>      | Addr Family   | Encoding Type |  Multicast Group Address    =
  |
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	> >>      | Addr Family   | Encoding Type |  Multicast Source Address   =
  |
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	> >>
	> >> Where CommandCode specifies the command and can be one of the =
following:
	> >>
	> >> 0x01  Add       Adds the specified multicast flow to the specified =
port
	> >> (join)
	> >> 0x02  Delete    Deletes the specified multicast flow (leave) on =
the
	> >> specified port.
	> >> 0x04  DeleteAll Deletes All multicast flow on the specified port =
(leave
	> >> all). No addresses are supplied.
	> >>
	> >> When we have more than one command, Deletes should always be =
listed
	> >> first. The unicast source address/mask follows the format defined =
in RFC
	> >> 2362 Section 4.1 case 1 which is duplicated here for quick review:
	> >>
	> >> Encoded-Unicast-address: Takes the following format:
	> >>
	> >>   0                   1                   2                   3
	> >>   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
	> >>  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	> >>  | Addr Family   | Encoding Type |     Unicast Address           |
	> >>  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	> >>
	> >>      Addr Family
	> >>            The address family of the `Unicast Address' field  of
	> >>            this address.
	> >>
	> >>           Here is the address family numbers assigned by IANA:
	> >>
	> >>  Number    Description
	> >>  --------  =
---------------------------------------------------------
	> >>       0    Reserved
	> >>       1    IP (IP version 4)
	> >>       2    IP6 (IP version 6)
	> >>       3    NSAP
	> >>       4    HDLC (8-bit multidrop)
	> >>       5    BBN 1822
	> >>       6    802 (includes all 802 media plus Ethernet "canonical =
format")
	> >>       7    E.163
	> >>       8    E.164 (SMDS, Frame Relay, ATM)
	> >>       9    F.69 (Telex)
	> >>      10    X.121 (X.25, Frame Relay)
	> >>      11    IPX
	> >>      12    Appletalk
	> >>      13    Decnet IV
	> >>      14    Banyan Vines
	> >>      15    E.164 with NSAP format subaddress
	> >>
	> >>      Encoding Type
	> >>           The type of encoding used within a specific Address
	> >>           Family.  The value `0' is reserved for this field,
	> >>           and represents the native encoding of the Address
	> >>           Family.
	> >>
	> >>      Unicast Address
	> >>           The unicast address as represented by the given
	> >>           Address Family and Encoding Type.
	> >>
	> >> Finally, although the length could be derived from the Addr Family =
and
	> >> the Encoding type, it is kept for future possible extension to =
this
	> >> command where other entry would be added to this command segment.
	> >> The equivalent of a swap command where the NAS would want to =
switch from
	> >> multicast group 239.23.2.2 to 239.55.3.2 will have the following =
format:
	> >>
	> >>       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
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	> >>      |        Type (0x88-0C)         |           Length            =
  |
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	> >>      | Vers  |  Sub  |MessageType=3D90 | Result|        Code       =
    |
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	> >>      | Partition ID  |            Transaction Identifier =3D 0001  =
    |
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	> >>      |I|      SubMessage Number      |           Length            =
  |
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	> >>      | 0x01 (Replication-Control)    |             Length          =
  |
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	> >>      | 0x01 (Access-Loop-Circuit-ID) |        Client-ID Length     =
  |
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	> >>      |                                                             =
  |
	> >>      ~                      Port Client-ID                         =
  ~
	> >>      |                                                             =
  |
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	> >>      | Type=3DCommandCode: Delete(0x02)|           Length          =
    |
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	> >>      | AddrFamily 01 | EncType 0x0   |  Mcast group: 239.23.2.2    =
  |
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|
	> >>      | AddrFamily 01 | EncType 0x0   |  Mcast Source: 10.1.1.1     =
  |
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|
	> >>      | Type=3DCommandCode: Add (0x01)  |           Length          =
    |
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	> >>      | AddrFamily 01 | EncType 0x0   |  Mcast group: 239.55.3.2    =
  |
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|
	> >>      | AddrFamily 01 | EncType 0x0   |  Mcast Source: 10.1.1.1     =
  |
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|
	> >>
	> >> Each command in the list is attributed an identification number =
based on
	> >> its occurrence in the message. In this case, the Delete command =
will be
	> >> attributed command number 1 while the Add will be attributed =
command
	> >> number 2. During the processing of these  commands, upon the first
	> >> failure of a command, the sequence is interrupted and an error =
message
	> >> (via Multicast Status Message) will be returned with the command =
number
	> >> identifying the command that failed.
	> >>
	> >> _______________________________________________
	> >> 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
	> >
	> >  Please do not print this email unless it is absolutely necessary.
	> >
	> >  The information contained in this electronic message and any =
attachments to
	> > this message are intended for the exclusive use of the addressee(s) =
and may
	> > contain proprietary, confidential or privileged information. If you =
are not
	> > the intended recipient, you should not disseminate, distribute or =
copy this
	> > e-mail. Please notify the sender immediately and destroy all copies =
of this
	> > message and any attachments.
	> >
	> > WARNING: Computer viruses can be transmitted via email. The =
recipient should
	> > check this email and any attachments for the presence of viruses. =
The company
	> > accepts no liability for any damage caused by any virus transmitted =
by this
	> > email.
	> >
	> > www.wipro.com
	> >
	> >
	> > --
	> > Einar Nilsen-Nygaard
	> > Technical Leader, Cisco
	> >
	> > Clothes make the man. Naked people have little or no influence on
	> > society. --Mark Twain
	> >
	>
=09
	> _______________________________________________
	> ANCP mailing list
	> ANCP@ietf.org
	> https://www.ietf.org/mailman/listinfo/ancp
=09
=09
	--
	---
	Toerless Eckert, eckert@cisco.com
	Cisco NSSTG Systems & Technology Architecture
	"The strategy is what you do, not what you write" - Wesley Clark
=09


------_=_NextPart_001_01C8B746.E945ED88
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML dir=3Dltr><HEAD><TITLE>Re: [ANCP] ANCP Multicast Control =
Message</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.3314" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D786361511-16052008><FONT =
face=3DArial=20
size=3D2>Hi Vish,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D786361511-16052008><FONT =
face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D786361511-16052008><FONT =
face=3DArial=20
size=3D2>adding the VLAN tag as a mandatory parameter seems undesirable. =
The use=20
or otherwise of "multicast VLANs" is a local configuration issue&nbsp;on =
the AN=20
which could be set to a default, or at best an optional parameter in the =
ANCP=20
request message.</FONT></SPAN><BR></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D786361511-16052008><FONT =
face=3DArial=20
size=3D2>Regards,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D786361511-16052008><FONT =
face=3DArial=20
size=3D2>Woj.</FONT></SPAN></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> ancp-bounces@ietf.org=20
  [mailto:ancp-bounces@ietf.org] <B>On Behalf Of=20
  </B>vishwanathan.sundaram@wipro.com<BR><B>Sent:</B> 22 April 2008=20
  17:40<BR><B>To:</B> Toerless Eckert (eckert); Einar Nilsen-Nygaard=20
  (einarnn)<BR><B>Cc:</B> ancp@ietf.org<BR><B>Subject:</B> Re: [ANCP] =
ANCP=20
  Multicast Control Message<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV id=3DidOWAReplyText87990 dir=3Dltr>
  <DIV dir=3Dltr><FONT face=3DArial size=3D2>Comments</FONT></DIV>
  <DIV dir=3Dltr><FONT face=3DArial size=3D2>a&gt; It would be good to =
add Vlan tag as=20
  one of the parameters to the add/delete command, as this will indicate =
which=20
  VLAN should be used for multicasting.&nbsp;DSL TR =
101,&nbsp;&nbsp;discusses=20
  about the multicast flow being associated with a VLAN =
(Multicast-Vlan). In=20
  this case, the Access Node, needs to be informed about the VLAN ID on =
which a=20
  particular Multicast group is being associated by the =
NAS.</FONT></DIV>
  <DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV dir=3Dltr><FONT face=3DArial size=3D2>Cheers</FONT></DIV>
  <DIV dir=3Dltr><FONT face=3DArial size=3D2>Vish</FONT></DIV>
  <DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT><FONT face=3DArial=20
  size=3D2></FONT>&nbsp;</DIV>
  <DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV><FONT =
face=3DArial=20
  size=3D2></FONT></DIV>
  <DIV dir=3Dltr><FONT face=3DArial size=3D2>
  <DIV dir=3Dltr><BR></FONT><BR></DIV>
  <DIV dir=3Dltr>
  <HR tabIndex=3D-1>
  </DIV>
  <DIV dir=3Dltr><FONT face=3DTahoma size=3D2><B>From:</B> Toerless =
Eckert=20
  [mailto:eckert@cisco.com]<BR><B>Sent:</B> Mon 4/21/2008 6:00 =
PM<BR><B>To:</B>=20
  Einar Nilsen-Nygaard<BR><B>Cc:</B> Vishwanathan Somasundaram (WT01 -=20
  TES-Access Networks); wdec@cisco.com; ancp@ietf.org<BR><B>Subject:</B> =
Re:=20
  [ANCP] ANCP Multicast Control Message<BR></FONT><BR></DIV></DIV>
  <DIV>
  <P><FONT size=3D2>Some comments:<BR><BR>a) Please change the name of =
the two=20
  'Length' fields in the<BR>&nbsp;&nbsp; control mesages sucht hat they =
can be=20
  differentiated easier from<BR>&nbsp;&nbsp; another and specify what is =
counted=20
  in them, eg:<BR><BR>&nbsp;&nbsp;&nbsp; Type=3DReplication-Control=20
  =
(0x01)|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;=20
  =
Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =

  =
|<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;=20
  ^^^^^^<BR>&nbsp;&nbsp;&nbsp;<BR>&nbsp;&nbsp; suggest to change to =
RC-Length,=20
  explanation "total number of bytes<BR>&nbsp;&nbsp; of the following =
TLVs plus=20
  the replication control header".<BR><BR>&nbsp;&nbsp;&nbsp; Type =3D=20
  =
CommandCode&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;=20
  =
Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;=20
  =
|<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  ^^^^^^<BR><BR>&nbsp;&nbsp; suggest to change to CC-Length, explanation =
"total=20
  number of<BR>&nbsp;&nbsp; this CommandCode TLV, counting this header =
and the=20
  following<BR>&nbsp;&nbsp; multicast flow bytes".<BR><BR>b) Please try =
to avoid=20
  using the term "group" when referring to<BR>&nbsp;&nbsp; an address =
which is=20
  either an ASM (Any Source Multicast) group<BR>&nbsp;&nbsp; address =
(aka: a=20
  single multicast group address, IPv4 or IPv6)<BR>&nbsp;&nbsp; or an =
SSM=20
  channel (aka: source and group address).<BR><BR>&nbsp;&nbsp; I would =
stroingly=20
  suggest to only use the term "multicast flow"<BR>&nbsp;&nbsp; or =
multicast=20
  flow address, or just "flow", and define that term<BR>&nbsp;&nbsp; in =
the=20
  beginning of the document to be either an ASN group or<BR>&nbsp;&nbsp; =
SSM=20
  channel.<BR><BR>&nbsp;&nbsp; Otherwise there will be lots of =
confusions about=20
  whether or not<BR>&nbsp;&nbsp; SSM is well supported by =
ANCP.<BR><BR>c) Do not=20
  refer to rfc2362. That RFC is obsolete and replaced by=20
  rfc4601.<BR>&nbsp;&nbsp; I do not see a good reason to refer to any =
PIM spec=20
  anyhow, just<BR>&nbsp;&nbsp; resolve the references used within the =
PIM-SM=20
  spec, eg:<BR><BR>&nbsp;&nbsp; <A=20
  =
href=3D"http://www.iana.org/assignments/address-family-numbers">http://ww=
w.iana.org/assignments/address-family-numbers</A><BR><BR>&nbsp;&nbsp;=20
  or the like.<BR><BR>d) To identify an actual SSM channel, it would be=20
  preferrable IMHO<BR>&nbsp;&nbsp; to have an address family identifier =
for an=20
  SSM channel, aka:<BR>&nbsp;&nbsp; an IP(v6/v6) source IP address =
followed by a=20
  group address. As<BR>&nbsp;&nbsp; above IANA URL has nothing like this =

  defined, i think there are<BR>&nbsp;&nbsp; two =
choices:<BR><BR>&nbsp;&nbsp;=20
  -&gt; I) I'll check what effort it is to get that defined through=20
  IANA.<BR><BR>&nbsp;&nbsp; -&gt; II) we stick with the existing =
specification,=20
  which is to<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; have a separate field=20
  addrfamily/encoding/group and one<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  addrfamily/encoding/source, but then i would very=20
  much<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; like to see very explicit =
description=20
  in the protocol spec<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; what sequeneces =
of=20
  addfamily/encoding/addr (AEA) elements are=20
  valid,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and how they have to be=20
  interpreted:<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; for add/delete=20
  commands:<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&gt; MUST =
support a=20
  single AEA argument where the=20
  =
address<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
is an=20
  IPv4/IPv6 address that is a multicast=20
  group.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
(ASM=20
  case).<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&gt; MUST =
support=20
  TWO AEA argument where the address of=20
  the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
first AEA=20
  is an IPv4/IPv6 address which is a=20
  =
unicast<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  address, and the second AEA is an IPv4/IPv6 address=20
  which<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
is a=20
  multicast address. Aka: SSM=20
  =
case.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 In=20
  the example text i see two things i am=20
  questioning:<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; I) The =
(S,G)=20
  channels are encoded first group and then=20
  =
source.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
That=20
  IMHO is not preferrable. I would rather suggest=20
  like<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
written=20
  above to encode first source and then=20
  =
group.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  II) The text is suggesting to have eg: multiple group=20
  =
AEA<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
=20
  following an add/delete TLV. I have no strong=20
  =
opinion<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
  whether or not that should be supported, but if we=20
  =
conclude<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;=20
  it should be supported, then that should explicitly be=20
  =
mentioned<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;=20
  in the text (see also below). And that description=20
  =
would<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;=20
  then of course have to detail a bit how a list of=20
  =
AEAs<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;=20
  with ASM groups and SSM channels is to be=20
  =
encoded.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;=20
  Particularily this case makes it of course=20
  =
important<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;=20
  to either be very clear how an SSM channel is=20
  =
encoded<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
  (source first or group first), or even better use a=20
  =
separate<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;=20
  Address-Familty identifier as suggested above.<BR><BR>e) I do not see =
any=20
  suggestion on the command reply. Is there<BR>&nbsp;&nbsp; supposed to =
be some=20
  failure and/or success return codes ?<BR><BR>f) As far as return codes =
are=20
  concerned: I would like to see some<BR>&nbsp;&nbsp; clearer statement =
about=20
  the suggested atomicity (if that's a<BR>&nbsp;&nbsp; valid english =
word ;-) of=20
  the execution of multiple flows<BR>&nbsp;&nbsp; within a single=20
  add/delete/modify TLV as well as the flows across<BR>&nbsp;&nbsp; =
multiple=20
  TLVs within the same replication control message.<BR><BR>&nbsp;&nbsp; =
-&gt;=20
  What happens if any individual flow add/delete fails ?=20
  The<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; document right now only seems to =
imply=20
  that the execution of<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the following=20
  add/deletes is simply not executed.&nbsp; That=20
  by<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; itself would require the NAS to =
either=20
  query all state to figure<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; out what =
actually=20
  was executed or to simply try everything=20
  again.<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; If we would add a return =
code=20
  like the following, that would<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; not =
be=20
  =
necessary:<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;=20
  "Sorry, error: all flows up to byte XX into the packet=20
  where<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; performed =
well, and=20
  the following flow failed to=20
  be<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
addeded/deleted, and=20
  the rest was not even=20
  =
tried"<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; I=20
  am not sure if this type of error return is the=20
  preferred<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; solution, but if we do not =
mandate=20
  something better, then<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; it probably =
should be=20
  done.<BR>&nbsp;&nbsp;<BR>&nbsp;&nbsp; -&gt; A better solution would be =
to=20
  imply some form of atomicity,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; eg: =
either at=20
  TLV or at replication control level.=20
  Meaning:<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the AN tries to execute=20
  add/delete/modifies, but if anything =
fails,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  then everything is undone. Or better: Nothing is applied=20
  by<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the AN unless it can make sure =
everything=20
  will succeed.<BR><BR>g) Atomicity is a hard bargain for the =
control/forwarding=20
  plane<BR>&nbsp;&nbsp; of a router/switch/DSLAM i think. If there is a =
bunch of=20
  add/delete/modify<BR>&nbsp;&nbsp; and all of those should only be =
applied if=20
  all of them will succeed...<BR>&nbsp;&nbsp; good luck getting that =
actually=20
  implemented correctly in the<BR>&nbsp;&nbsp; forwarding plane of any=20
  AN.<BR><BR>&nbsp;&nbsp; The thing i could see us asking to be done =
atomically=20
  is really<BR>&nbsp;&nbsp; JUST a single flow-swap, aka: replace =
exactly one=20
  flow with<BR>&nbsp;&nbsp; another flow.<BR><BR>&nbsp;&nbsp; So =
ultimately, i=20
  think:<BR><BR>&nbsp;&nbsp; -&gt; For add/delete commands we ask for no =

  atomicity and the error<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; code =
returned should=20
  somehow point to the first flow =
within<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a=20
  packet that failed. And provide some additional error=20
  code<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; why (which we could define the =
values=20
  for later). And this<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; should allow us =
to have=20
  multiple flows as arguments to a<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
single=20
  add/delete to be more efficient.<BR>&nbsp;&nbsp;<BR>&nbsp;&nbsp; -&gt; =
a=20
  modify should be called "swap", and should support=20
  only<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; exactly two flows as the =
argument. This=20
  swap should work<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; atomically, aka: =
the join=20
  would not be executed if the leave<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
could not=20
  be done, and the leave should of course not=20
  be<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; executed if the join would not=20
  work.<BR>&nbsp;&nbsp;<BR>&nbsp;&nbsp; -&gt; So maybe overall the error =
return=20
  code would=20
  be<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =

  command#, flow#, why<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; where =
command#=20
  would be pointing to the command (numbered 1 t=20
  N)<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; within the recplication control =
command=20
  that failed,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; flow# would be the flow =
(1..M)=20
  within that command (always 1 for<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a =
swap, as=20
  we only allow a single flow there), and why would=20
  be<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; some eg: 8-bit error code where =
we could=20
  define values for that<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; would help=20
  diagnosis.<BR><BR><BR>h) The degree to which a platform is able to =
implement=20
  even this<BR>&nbsp;&nbsp; most simple atomic swap is of course subject =
to=20
  implementation.<BR><BR>Cheers<BR>&nbsp;&nbsp;&nbsp;=20
  Toerless<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>On Mon, Apr 21, 2008 at=20
  09:47:06PM +0100, Einar Nilsen-Nygaard wrote:<BR>&gt; =
Vish,<BR>&gt;<BR>&gt; I=20
  actually think that freedom in how a =B3swap=B2 operation would be=20
  implemented<BR>&gt; in terms of the ordering of stopping the first =
multicast=20
  flow and starting<BR>&gt; the second is not desirable. By specifying =
that the=20
  delete must come before<BR>&gt; the add and that the operation should =
be=20
  terminated upon the first error,<BR>&gt; the current specification =
gives us=20
  what should be deterministic behavior<BR>&gt; between any and all =
conforming=20
  implementations.<BR>&gt;<BR>&gt; In contrast, the freedom to implement =
a swap=20
  operation via some form of<BR>&gt; modify leaves the door open to =
multiple=20
  ways in which a modify request could<BR>&gt; fail, making error =
recovery more=20
  troublesome and vendor-specific which I do<BR>&gt; not see as at all=20
  desirable.<BR>&gt;<BR>&gt; Cheers,<BR>&gt;<BR>&gt; =
Einar<BR>&gt;<BR>&gt; On=20
  21/04/2008 20:12, "vishwanathan.sundaram@wipro.com"<BR>&gt;=20
  &lt;vishwanathan.sundaram@wipro.com&gt; scribbled:<BR>&gt;<BR>&gt; =
&gt;=20
  Einar,<BR>&gt; &gt; Modify command would be usefull from Access box=20
  perspective, as the underlying<BR>&gt; &gt; implementation in AN's =
would have=20
  the freedom to design their swap operation,<BR>&gt; &gt; instead of =
always=20
  first deleting the existing group entry and adding another<BR>&gt; =
&gt;=20
  entry.<BR>&gt; &gt;&nbsp;<BR>&gt; &gt; Thanks<BR>&gt; &gt; =
Vish<BR>&gt;=20
  &gt;&nbsp;<BR>&gt; &gt;<BR>&gt; &gt;<BR>&gt; &gt; From: einarnn [<A=20
  =
href=3D"mailto:einarnn@cisco.com">mailto:einarnn@cisco.com</A>]<BR>&gt; =
&gt;=20
  Sent: Sun 4/20/2008 11:12 AM<BR>&gt; &gt; To: Vishwanathan =
Somasundaram (WT01=20
  - TES-Access Networks); wdec@cisco.com;<BR>&gt; &gt; =
ancp@ietf.org<BR>&gt;=20
  &gt; Subject: Re: [ANCP] ANCP Multicast Control Message<BR>&gt; =
&gt;<BR>&gt;=20
  &gt; Vish,<BR>&gt; &gt;<BR>&gt; &gt; Overloading the second byte of =
the=20
  command code to contain the number of<BR>&gt; &gt; =B3modifications=B2 =
doesn=B9t=20
  seem a good approach and the space saving per packet,<BR>&gt; &gt; =
which will=20
  probably be only 4 bytes most of the time, seems almost =
irrelevant.<BR>&gt;=20
  &gt; I think it would be better to keep the fields in the message for =
a=20
  single<BR>&gt; &gt; task.<BR>&gt; &gt;<BR>&gt; &gt; Treating a =
sequence of=20
  commands as an atomic operation, as detailed in the<BR>&gt; &gt; text, =
and=20
  implementing a swap via a delete follow by an add, should give =
ANs<BR>&gt;=20
  &gt; the freedom to implement what are, in effect, swap operations=20
  quite<BR>&gt; &gt; efficiently. In this context, I=B9m not sure what a =
=B3modify=B2=20
  command code will<BR>&gt; &gt; really add?<BR>&gt; &gt;<BR>&gt; &gt;=20
  Cheers,<BR>&gt; &gt;<BR>&gt; &gt; Einar<BR>&gt; &gt;<BR>&gt; &gt; On=20
  16/04/2008 15:41, "vishwanathan.sundaram@wipro.com"<BR>&gt; &gt;=20
  &lt;vishwanathan.sundaram@wipro.com&gt; wrote:<BR>&gt; &gt;<BR>&gt; =
&gt;&gt;=20
  Hi Woj,<BR>&gt; &gt;&gt; Currently, the command codes for replication =
control=20
  message are<BR>&gt; &gt;&gt; 1. add (0x01)<BR>&gt; &gt;&gt; 2. delete=20
  (0x02)<BR>&gt; &gt;&gt; 3. delete all (0x04).<BR>&gt; &gt;&gt;<BR>&gt; =

  &gt;&gt; Looking at the multicast Swap message format, which is used =
when the=20
  NAS<BR>&gt; &gt;&gt; wants to switch from one group to another,can we =
not=20
  handle this situation by<BR>&gt; &gt;&gt; having a message type Modify =

  (0x08).<BR>&gt; &gt;&gt; By using this message type we can mention the =

  multicast group address which<BR>&gt; &gt;&gt; needs to be swapped by =
new=20
  multicast group address.<BR>&gt; &gt;&gt; Since the Command Code is 2 =
bytes,=20
  the second byte can be used to mention the<BR>&gt; &gt;&gt; number of=20
  multicast groups that needs to be swapped.<BR>&gt; &gt;&gt; This will =
allow,=20
  for multiple multicast group swaps. This will also reduce<BR>&gt; =
&gt;&gt; the=20
  size of the packet. Since these messages intended only between the =
NAS<BR>&gt;=20
  &gt;&gt; and AN, the introduction of modify command type gives further =
ease to=20
  the<BR>&gt; &gt;&gt; Access boxes in implementing the swaps, which =
attributes=20
  to zap latency.<BR>&gt; &gt;&gt;<BR>&gt;=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 =
6 7 8 9=20
  0 1 2 3 4 5 6 7 8 9 0 1<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =

  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;=
=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Type=20
  (0x88-0C)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;=20
  |<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;=
=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Vers&nbsp; |&nbsp; Sub&nbsp;=20
  |MessageType=3D90 | Result|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Code&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|<BR>&gt;=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;=
=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Partition ID&nbsp;=20
  |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Transaction Identifier =3D 0001&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|<BR>&gt;=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;=
=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|I|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  SubMessage Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;=20
  |<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;=
=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | 0x01=20
  (Replication-Control)&nbsp;&nbsp;&nbsp;=20
  =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
=20
  =
Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =

  |<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;=
=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | 0x01 (Access-Loop-Circuit-ID) =

  |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Client-ID=20
  Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<BR>&gt;=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;=
=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;=20
  |<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Port=20
  =
Client-ID&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;=20
  ~<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;=20
  |<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;=
=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Type=3DCommandCode:=20
  =
Modify(0x08)|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
=20
  Length<BR>&gt; &gt;&gt; |<BR>&gt; =
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;=
=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | AddrFamily 01 | EncType=20
  0x0&nbsp;&nbsp;&nbsp; |&nbsp; Mcast group:=20
  =
239.23.2.2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;=20
  |<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|<BR>&gt;=
=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | AddrFamily 01 | EncType=20
  0x0&nbsp;&nbsp;&nbsp; |&nbsp; Mcast Source: 10.1.1.1<BR>&gt; &gt;&gt;=20
  |<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|<BR>&gt;=
=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | AddrFamily 01 | EncType =

  0x0&nbsp;&nbsp; |&nbsp; New Mcast group: 239.55.3.2&nbsp;&nbsp; =
|<BR>&gt;=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|<BR>&gt;=
=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | AddrFamily 01 | EncType=20
  0x0&nbsp;&nbsp;&nbsp; |&nbsp; New Mcast Source:=20
  10.1.1.1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<BR>&gt;=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|<BR>&gt;=
=20
  &gt;&gt;<BR>&gt; &gt;&gt; Looking into the DSL TR 101, it also =
discusses about=20
  the multicast flow being<BR>&gt; &gt;&gt; associated with a VLAN=20
  (Multicast-Vlan). In this case, the Access Node, needs<BR>&gt; =
&gt;&gt; to be=20
  informed about the VLAN ID on which a particular Multicast group =
is<BR>&gt;=20
  &gt;&gt; being associated by the NAS. Can this information also be =
added as=20
  part of<BR>&gt; &gt;&gt; the TLV in message.<BR>&gt; &gt;&gt;<BR>&gt; =
&gt;&gt;=20
  Thanks<BR>&gt; &gt;&gt; Vish<BR>&gt; &gt;&gt;<BR>&gt; &gt;&gt;<BR>&gt; =

  &gt;&gt; From: ancp-bounces@ietf.org on behalf of Wojciech Dec =
(wdec)<BR>&gt;=20
  &gt;&gt; Sent: Mon 4/14/2008 11:00 AM<BR>&gt; &gt;&gt; To:=20
  ancp@ietf.org<BR>&gt; &gt;&gt; Subject: [ANCP] ANCP Multicast Control=20
  Message<BR>&gt; &gt;&gt;<BR>&gt; &gt;&gt;<BR>&gt; &gt;&gt;<BR>&gt; =
&gt;&gt; Hi=20
  All,<BR>&gt; &gt;&gt;<BR>&gt; &gt;&gt; As discussed during our recent =
IETF 71=20
  meeting, our protocol design team<BR>&gt; &gt;&gt; has forged ahead =
with=20
  prioritized list of problems to address, the first<BR>&gt; &gt;&gt; of =
which=20
  was defining the ANCP message extensions for multicast =
control,<BR>&gt;=20
  &gt;&gt; aka unsolicited multicast control. The DT is working on the=20
  response<BR>&gt; &gt;&gt; message and also the solicited multicast =
control=20
  mode.<BR>&gt; &gt;&gt; Below, we present the outcome of the work, =
which=20
  represents both a<BR>&gt; &gt;&gt; design team consensus as well as a =
proposal=20
  for adoption into the ANCP<BR>&gt; &gt;&gt; protocol spec,=20
  draft-ietf-ancp-protocol (some editorial work will be<BR>&gt; &gt;&gt; =
still=20
  required). Please review the proposal and share your comments. =
We<BR>&gt;=20
  &gt;&gt; will assume acceptance of the proposal in principle=20
  otherwise.<BR>&gt; &gt;&gt;<BR>&gt; &gt;&gt; Regards,<BR>&gt; &gt;&gt; =
Woj=20
  &amp; Matthew.<BR>&gt; &gt;&gt;<BR>&gt; &gt;&gt;<BR>&gt; &gt;&gt;=20
  2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Replication Control =
Message<BR>&gt;=20
  &gt;&gt;<BR>&gt; &gt;&gt;<BR>&gt; &gt;&gt; This message is sent by the =
ANCP=20
  Server (NAS) to the ANCP Client (AN)<BR>&gt; &gt;&gt; with a directive =
to=20
  either add (join) or delete (leave) a port to or<BR>&gt; &gt;&gt; from =
a=20
  multicast flow. Its format is as follow:<BR>&gt;=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0 1 2 3 4 5 6 7 8 9 0 1 2 =
3 4 5 6=20
  7 8 9 0 1 2 3 4 5 6 7 8 9 0 1<BR>&gt; =
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;=
=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |Type=3DReplication-Control=20
  =
(0x01)|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;=20
  =
Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =

  |<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;=
=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | 0x01 (Access-Loop-Circuit-ID) =

  |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Client-ID=20
  Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<BR>&gt;=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;=
=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;=20
  |<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Port=20
  =
Client-ID&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;=20
  ~<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;=20
  |<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;=
=20
  &gt;&gt;<BR>&gt; &gt;&gt; Following the Port Client-ID information, =
one or=20
  more Command TLV<BR>&gt; &gt;&gt; components can be included and the =
Access=20
  Node should process them in<BR>&gt; &gt;&gt; the order in which they =
are=20
  listed. The Access Node (ANCP Client) should<BR>&gt; &gt;&gt; threat =
all the=20
  commands as a single command block to be viewed as a<BR>&gt; &gt;&gt; =
whole=20
  and bail out immediately when one of them fails.<BR>&gt; &gt;&gt; The =
format=20
  of command TLV is as follow:<BR>&gt; &gt;&gt;<BR>&gt;=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  3<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0 1 2 3 4 5 6 7 =
8 9 0 1=20
  2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1<BR>&gt;=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;=
=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp; Type =3D=20
  =
CommandCode&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;=20
  |<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;=
=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Addr Family&nbsp;&nbsp; | =
Encoding=20
  Type |&nbsp; Multicast Group Address&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|<BR>&gt;=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;=
=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Addr Family&nbsp;&nbsp; | =
Encoding=20
  Type |&nbsp; Multicast Source Address&nbsp;&nbsp;&nbsp;&nbsp; =
|<BR>&gt;=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;=
=20
  &gt;&gt;<BR>&gt; &gt;&gt; Where CommandCode specifies the command and =
can be=20
  one of the following:<BR>&gt; &gt;&gt;<BR>&gt; &gt;&gt; 0x01&nbsp;=20
  Add&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Adds the specified multicast =
flow to=20
  the specified port<BR>&gt; &gt;&gt; (join)<BR>&gt; &gt;&gt; 0x02&nbsp; =

  Delete&nbsp;&nbsp;&nbsp; Deletes the specified multicast flow (leave) =
on=20
  the<BR>&gt; &gt;&gt; specified port.<BR>&gt; &gt;&gt; 0x04&nbsp; =
DeleteAll=20
  Deletes All multicast flow on the specified port (leave<BR>&gt; =
&gt;&gt; all).=20
  No addresses are supplied.<BR>&gt; &gt;&gt;<BR>&gt; &gt;&gt; When we =
have more=20
  than one command, Deletes should always be listed<BR>&gt; &gt;&gt; =
first. The=20
  unicast source address/mask follows the format defined in RFC<BR>&gt; =
&gt;&gt;=20
  2362 Section 4.1 case 1 which is duplicated here for quick =
review:<BR>&gt;=20
  &gt;&gt;<BR>&gt; &gt;&gt; Encoded-Unicast-address: Takes the following =

  format:<BR>&gt; &gt;&gt;<BR>&gt; &gt;&gt;&nbsp;&nbsp;=20
  =
0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  3<BR>&gt; &gt;&gt;&nbsp;&nbsp; 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 =
0 1 2 3=20
  4 5 6 7 8 9 0 1<BR>&gt; &gt;&gt;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;=
=20
  &gt;&gt;&nbsp; | Addr Family&nbsp;&nbsp; | Encoding Type=20
  |&nbsp;&nbsp;&nbsp;&nbsp; Unicast=20
  Address&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|<BR>&gt;=20
  &gt;&gt;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;=
=20
  &gt;&gt;<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Addr =
Family<BR>&gt;=20
  =
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; The=20
  address family of the `Unicast Address' field&nbsp; of<BR>&gt;=20
  =
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;=20
  this address.<BR>&gt; &gt;&gt;<BR>&gt;=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Here is=20
  the address family numbers assigned by IANA:<BR>&gt; &gt;&gt;<BR>&gt;=20
  &gt;&gt;&nbsp; Number&nbsp;&nbsp;&nbsp; Description<BR>&gt; =
&gt;&gt;&nbsp;=20
  --------&nbsp;=20
  ---------------------------------------------------------<BR>&gt;=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp;=20
  Reserved<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  1&nbsp;&nbsp;&nbsp; IP (IP version 4)<BR>&gt;=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2&nbsp;&nbsp;&nbsp; IP6 =
(IP=20
  version 6)<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  3&nbsp;&nbsp;&nbsp; NSAP<BR>&gt; =
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  4&nbsp;&nbsp;&nbsp; HDLC (8-bit multidrop)<BR>&gt;=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 5&nbsp;&nbsp;&nbsp; BBN=20
  1822<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
6&nbsp;&nbsp;&nbsp;=20
  802 (includes all 802 media plus Ethernet "canonical format")<BR>&gt;=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 7&nbsp;&nbsp;&nbsp; =
E.163<BR>&gt;=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 8&nbsp;&nbsp;&nbsp; E.164 =
(SMDS,=20
  Frame Relay, ATM)<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =

  9&nbsp;&nbsp;&nbsp; F.69 (Telex)<BR>&gt;=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 10&nbsp;&nbsp;&nbsp; X.121 =
(X.25, Frame=20
  Relay)<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
11&nbsp;&nbsp;&nbsp;=20
  IPX<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
12&nbsp;&nbsp;&nbsp;=20
  Appletalk<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
13&nbsp;&nbsp;&nbsp;=20
  Decnet IV<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
14&nbsp;&nbsp;&nbsp;=20
  Banyan Vines<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  15&nbsp;&nbsp;&nbsp; E.164 with NSAP format subaddress<BR>&gt;=20
  &gt;&gt;<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Encoding =
Type<BR>&gt;=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
The type=20
  of encoding used within a specific Address<BR>&gt;=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Family.&nbsp; The value `0' is reserved for this field,<BR>&gt;=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
and=20
  represents the native encoding of the Address<BR>&gt;=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Family.<BR>&gt; &gt;&gt;<BR>&gt; =
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Unicast Address<BR>&gt;=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
The=20
  unicast address as represented by the given<BR>&gt;=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Address=20
  Family and Encoding Type.<BR>&gt; &gt;&gt;<BR>&gt; &gt;&gt; Finally, =
although=20
  the length could be derived from the Addr Family and<BR>&gt; &gt;&gt; =
the=20
  Encoding type, it is kept for future possible extension to =
this<BR>&gt;=20
  &gt;&gt; command where other entry would be added to this command=20
  segment.<BR>&gt; &gt;&gt; The equivalent of a swap command where the =
NAS would=20
  want to switch from<BR>&gt; &gt;&gt; multicast group 239.23.2.2 to =
239.55.3.2=20
  will have the following format:<BR>&gt; &gt;&gt;<BR>&gt;=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0 1 2 3 4 5 6 7 8 9 0 1 2 =
3 4 5 6=20
  7 8 9 0 1 2 3 4 5 6 7 8 9 0 1<BR>&gt; =
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;=
=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Type=20
  (0x88-0C)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;=20
  |<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;=
=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Vers&nbsp; |&nbsp; Sub&nbsp;=20
  |MessageType=3D90 | Result|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Code&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|<BR>&gt;=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;=
=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Partition ID&nbsp;=20
  |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Transaction Identifier =3D 0001&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|<BR>&gt;=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;=
=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|I|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  SubMessage Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;=20
  |<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;=
=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | 0x01=20
  (Replication-Control)&nbsp;&nbsp;&nbsp;=20
  =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
=20
  =
Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =

  |<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;=
=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | 0x01 (Access-Loop-Circuit-ID) =

  |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Client-ID=20
  Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<BR>&gt;=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;=
=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;=20
  |<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Port=20
  =
Client-ID&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;=20
  ~<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;=20
  |<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;=
=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Type=3DCommandCode:=20
  =
Delete(0x02)|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
=20
  =
Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;=20
  |<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;=
=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | AddrFamily 01 | EncType=20
  0x0&nbsp;&nbsp; |&nbsp; Mcast group: =
239.23.2.2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  |<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|<BR>&gt;=
=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | AddrFamily 01 | EncType=20
  0x0&nbsp;&nbsp; |&nbsp; Mcast Source:=20
  10.1.1.1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<BR>&gt;=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|<BR>&gt;=
=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Type=3DCommandCode: Add =
(0x01)&nbsp;=20
  |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;=20
  |<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;=
=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | AddrFamily 01 | EncType=20
  0x0&nbsp;&nbsp; |&nbsp; Mcast group: =
239.55.3.2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  |<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|<BR>&gt;=
=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | AddrFamily 01 | EncType=20
  0x0&nbsp;&nbsp; |&nbsp; Mcast Source:=20
  10.1.1.1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<BR>&gt;=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|<BR>&gt;=
=20
  &gt;&gt;<BR>&gt; &gt;&gt; Each command in the list is attributed an=20
  identification number based on<BR>&gt; &gt;&gt; its occurrence in the =
message.=20
  In this case, the Delete command will be<BR>&gt; &gt;&gt; attributed =
command=20
  number 1 while the Add will be attributed command<BR>&gt; &gt;&gt; =
number 2.=20
  During the processing of these&nbsp; commands, upon the first<BR>&gt; =
&gt;&gt;=20
  failure of a command, the sequence is interrupted and an error =
message<BR>&gt;=20
  &gt;&gt; (via Multicast Status Message) will be returned with the =
command=20
  number<BR>&gt; &gt;&gt; identifying the command that failed.<BR>&gt;=20
  &gt;&gt;<BR>&gt; &gt;&gt;=20
  _______________________________________________<BR>&gt; &gt;&gt; ANCP =
mailing=20
  list<BR>&gt; &gt;&gt; ANCP@ietf.org<BR>&gt; &gt;&gt; <A=20
  =
href=3D"https://www.ietf.org/mailman/listinfo/ancp">https://www.ietf.org/=
mailman/listinfo/ancp</A><BR>&gt;=20
  &gt;&gt;<BR>&gt; &gt;&gt;<BR>&gt; &gt;&gt;=20
  _______________________________________________<BR>&gt; &gt;&gt; ANCP =
mailing=20
  list<BR>&gt; &gt;&gt; ANCP@ietf.org<BR>&gt; &gt;&gt; <A=20
  =
href=3D"https://www.ietf.org/mailman/listinfo/ancp">https://www.ietf.org/=
mailman/listinfo/ancp</A><BR>&gt;=20
  &gt;<BR>&gt; &gt;&nbsp; Please do not print this email unless it is =
absolutely=20
  necessary.<BR>&gt; &gt;<BR>&gt; &gt;&nbsp; The information contained =
in this=20
  electronic message and any attachments to<BR>&gt; &gt; this message =
are=20
  intended for the exclusive use of the addressee(s) and may<BR>&gt; =
&gt;=20
  contain proprietary, confidential or privileged information. If you =
are=20
  not<BR>&gt; &gt; the intended recipient, you should not disseminate,=20
  distribute or copy this<BR>&gt; &gt; e-mail. Please notify the sender=20
  immediately and destroy all copies of this<BR>&gt; &gt; message and =
any=20
  attachments.<BR>&gt; &gt;<BR>&gt; &gt; WARNING: Computer viruses can =
be=20
  transmitted via email. The recipient should<BR>&gt; &gt; check this =
email and=20
  any attachments for the presence of viruses. The company<BR>&gt; &gt; =
accepts=20
  no liability for any damage caused by any virus transmitted by =
this<BR>&gt;=20
  &gt; email.<BR>&gt; &gt;<BR>&gt; &gt; www.wipro.com<BR>&gt; =
&gt;<BR>&gt;=20
  &gt;<BR>&gt; &gt; --<BR>&gt; &gt; Einar Nilsen-Nygaard<BR>&gt; &gt; =
Technical=20
  Leader, Cisco<BR>&gt; &gt;<BR>&gt; &gt; Clothes make the man. Naked =
people=20
  have little or no influence on<BR>&gt; &gt; society. --Mark =
Twain<BR>&gt;=20
  &gt;<BR>&gt;<BR><BR>&gt;=20
  _______________________________________________<BR>&gt; ANCP mailing=20
  list<BR>&gt; ANCP@ietf.org<BR>&gt; <A=20
  =
href=3D"https://www.ietf.org/mailman/listinfo/ancp">https://www.ietf.org/=
mailman/listinfo/ancp</A><BR><BR><BR>--<BR>---<BR>Toerless=20
  Eckert, eckert@cisco.com<BR>Cisco NSSTG Systems &amp; Technology=20
  Architecture<BR>"The strategy is what you do, not what you write" - =
Wesley=20
  Clark<BR></FONT></P></DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C8B746.E945ED88--

--===============0791629900==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============0791629900==--


From ancp-bounces@ietf.org  Fri May 16 06:33:38 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 6B7FD28C193;
	Fri, 16 May 2008 06:33:38 -0700 (PDT)
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 9158C3A67A5
	for <ancp@core3.amsl.com>; Fri, 16 May 2008 06:33:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.617
X-Spam-Level: 
X-Spam-Status: No, score=0.617 tagged_above=-999 required=5 tests=[AWL=2.135, 
	BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001,
	J_CHICKENPOX_73=0.6, SARE_UNSUB18=0.131]
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 p8ttpmAuzHee for <ancp@core3.amsl.com>;
	Fri, 16 May 2008 06:33:33 -0700 (PDT)
Received: from smail6.alcatel.fr (colt-na5.alcatel.fr [62.23.212.5])
	by core3.amsl.com (Postfix) with ESMTP id 47A2B28C0CF
	for <ancp@ietf.org>; Fri, 16 May 2008 06:33:25 -0700 (PDT)
Received: from FRVELSBHS04.ad2.ad.alcatel.com (frvelsbhs04.ad2.ad.alcatel.com
	[155.132.6.76])
	by smail6.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id m4GDXEfK008381; 
	Fri, 16 May 2008 15:33:14 +0200
Received: from FRVELSMBS22.ad2.ad.alcatel.com ([155.132.6.51]) by
	FRVELSBHS04.ad2.ad.alcatel.com with Microsoft
	SMTPSVC(6.0.3790.2499); Fri, 16 May 2008 15:33:14 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 16 May 2008 15:33:13 +0200
Message-ID: <7A6D4815C5E8F74988784FEBD50F2F1E01C237B6@FRVELSMBS22.ad2.ad.alcatel.com>
In-Reply-To: <D9872168DBD43A41BD71FFC4713274D4051366B9@xmb-ams-33b.emea.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ANCP] ANCP Multicast Control Message
Thread-Index: Acij+5MzWijMyW8RTPSeLUilx/6xkAAkhiQjBK4fpLAABK2RYA==
References: <CD6A16F9BCCBBC4CBF5271C5F06EC3BD046F62@BLR-EC-MBX07.wipro.com><C432BBDA.7733B%einarnn@cisco.com><20080421220043.GI175@cisco.com><CD6A16F9BCCBBC4CBF5271C5F06EC3BD046F66@BLR-EC-MBX07.wipro.com>
	<D9872168DBD43A41BD71FFC4713274D4051366B9@xmb-ams-33b.emea.cisco.com>
From: "DE CNODDER Stefaan" <stefaan.de_cnodder@alcatel-lucent.be>
To: "Wojciech Dec (wdec)" <wdec@cisco.com>,
	"VISHWANATHAN SOMASUNDARAM" <vishwanathan.sundaram@wipro.com>,
	"Toerless Eckert (eckert)" <eckert@cisco.com>,
	"Einar Nilsen-Nygaard (einarnn)" <einarnn@cisco.com>
X-OriginalArrivalTime: 16 May 2008 13:33:14.0331 (UTC)
	FILETIME=[6454CAB0:01C8B759]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.84
Cc: ancp@ietf.org
Subject: Re: [ANCP] ANCP Multicast Control Message
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/pipermail/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>
Content-Type: multipart/mixed; boundary="===============2066166416=="
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org

This is a multi-part message in MIME format.

--===============2066166416==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8B759.63F408A7"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8B759.63F408A7
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

=20
Hi Vish, Woj,
=20
I agree with Woj that the VLAN should be at most an optional parameter.  =
According to me, putting the multicast VLAN in the command message is =
also not correct because there can be quite a lot of commands send from =
the NAS to the AN and each message would always repeat this same =
information.  It looks better to me to configure the multicast VLAN at =
the level of the partition, that looks to be more than enough (if at all =
something is needed).  It is suffcient to me that the protocol is =
extensible enough to add it later when it is clear that there is a real =
need for it.
=20
regards,
Stefaan
=20
=20

________________________________

From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of =
Wojciech Dec (wdec)
Sent: vrijdag 16 mei 2008 13:21
To: VISHWANATHAN SOMASUNDARAM; Toerless Eckert (eckert); Einar =
Nilsen-Nygaard (einarnn)
Cc: ancp@ietf.org
Subject: Re: [ANCP] ANCP Multicast Control Message


Hi Vish,
=20
adding the VLAN tag as a mandatory parameter seems undesirable. The use =
or otherwise of "multicast VLANs" is a local configuration issue on the =
AN which could be set to a default, or at best an optional parameter in =
the ANCP request message.

Regards,
Woj.

________________________________

	From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On Behalf Of =
vishwanathan.sundaram@wipro.com
	Sent: 22 April 2008 17:40
	To: Toerless Eckert (eckert); Einar Nilsen-Nygaard (einarnn)
	Cc: ancp@ietf.org
	Subject: Re: [ANCP] ANCP Multicast Control Message
=09
=09
	Comments
	a> It would be good to add Vlan tag as one of the parameters to the =
add/delete command, as this will indicate which VLAN should be used for =
multicasting. DSL TR 101,  discusses about the multicast flow being =
associated with a VLAN (Multicast-Vlan). In this case, the Access Node, =
needs to be informed about the VLAN ID on which a particular Multicast =
group is being associated by the NAS.
	=20
	Cheers
	Vish
	=20
	=20
=09
=09


________________________________

	From: Toerless Eckert [mailto:eckert@cisco.com]
	Sent: Mon 4/21/2008 6:00 PM
	To: Einar Nilsen-Nygaard
	Cc: Vishwanathan Somasundaram (WT01 - TES-Access Networks); =
wdec@cisco.com; ancp@ietf.org
	Subject: Re: [ANCP] ANCP Multicast Control Message
=09
=09

	Some comments:
=09
	a) Please change the name of the two 'Length' fields in the
	   control mesages sucht hat they can be differentiated easier from
	   another and specify what is counted in them, eg:
=09
	    Type=3DReplication-Control (0x01)|             Length            |
	                                                 ^^^^^^
	  =20
	   suggest to change to RC-Length, explanation "total number of bytes
	   of the following TLVs plus the replication control header".
=09
	    Type =3D CommandCode           |              Length               =
|
	                                                ^^^^^^
=09
	   suggest to change to CC-Length, explanation "total number of
	   this CommandCode TLV, counting this header and the following
	   multicast flow bytes".
=09
	b) Please try to avoid using the term "group" when referring to
	   an address which is either an ASM (Any Source Multicast) group
	   address (aka: a single multicast group address, IPv4 or IPv6)
	   or an SSM channel (aka: source and group address).
=09
	   I would stroingly suggest to only use the term "multicast flow"
	   or multicast flow address, or just "flow", and define that term
	   in the beginning of the document to be either an ASN group or
	   SSM channel.
=09
	   Otherwise there will be lots of confusions about whether or not
	   SSM is well supported by ANCP.
=09
	c) Do not refer to rfc2362. That RFC is obsolete and replaced by =
rfc4601.
	   I do not see a good reason to refer to any PIM spec anyhow, just
	   resolve the references used within the PIM-SM spec, eg:
=09
	   http://www.iana.org/assignments/address-family-numbers
=09
	   or the like.
=09
	d) To identify an actual SSM channel, it would be preferrable IMHO
	   to have an address family identifier for an SSM channel, aka:
	   an IP(v6/v6) source IP address followed by a group address. As
	   above IANA URL has nothing like this defined, i think there are
	   two choices:
=09
	   -> I) I'll check what effort it is to get that defined through IANA.
=09
	   -> II) we stick with the existing specification, which is to
	      have a separate field addrfamily/encoding/group and one
	      addrfamily/encoding/source, but then i would very much
	      like to see very explicit description in the protocol spec
	      what sequeneces of addfamily/encoding/addr (AEA) elements are =
valid,
	      and how they have to be interpreted:
=09
	      for add/delete commands:
	        -> MUST support a single AEA argument where the address
	           is an IPv4/IPv6 address that is a multicast group.
	           (ASM case).
=09
	        -> MUST support TWO AEA argument where the address of the
	           first AEA is an IPv4/IPv6 address which is a unicast
	           address, and the second AEA is an IPv4/IPv6 address which
	           is a multicast address. Aka: SSM case.
	    =20
	      In the example text i see two things i am questioning:
=09
	        I) The (S,G) channels are encoded first group and then source.
	           That IMHO is not preferrable. I would rather suggest like
	           written above to encode first source and then group.
	       =20
	        II) The text is suggesting to have eg: multiple group AEA
	            following an add/delete TLV. I have no strong opinion
	            whether or not that should be supported, but if we conclude
	            it should be supported, then that should explicitly be =
mentioned
	            in the text (see also below). And that description would
	            then of course have to detail a bit how a list of AEAs
	            with ASM groups and SSM channels is to be encoded.
	            Particularily this case makes it of course important
	            to either be very clear how an SSM channel is encoded
	            (source first or group first), or even better use a =
separate
	            Address-Familty identifier as suggested above.
=09
	e) I do not see any suggestion on the command reply. Is there
	   supposed to be some failure and/or success return codes ?
=09
	f) As far as return codes are concerned: I would like to see some
	   clearer statement about the suggested atomicity (if that's a
	   valid english word ;-) of the execution of multiple flows
	   within a single add/delete/modify TLV as well as the flows across
	   multiple TLVs within the same replication control message.
=09
	   -> What happens if any individual flow add/delete fails ? The
	      document right now only seems to imply that the execution of
	      the following add/deletes is simply not executed.  That by
	      itself would require the NAS to either query all state to figure
	      out what actually was executed or to simply try everything again.
=09
	      If we would add a return code like the following, that would
	      not be necessary:
	    =20
	        "Sorry, error: all flows up to byte XX into the packet where
	         performed well, and the following flow failed to be
	         addeded/deleted, and the rest was not even tried"
	    =20
	      I am not sure if this type of error return is the preferred
	      solution, but if we do not mandate something better, then
	      it probably should be done.
	 =20
	   -> A better solution would be to imply some form of atomicity,
	      eg: either at TLV or at replication control level. Meaning:
	      the AN tries to execute add/delete/modifies, but if anything =
fails,
	      then everything is undone. Or better: Nothing is applied by
	      the AN unless it can make sure everything will succeed.
=09
	g) Atomicity is a hard bargain for the control/forwarding plane
	   of a router/switch/DSLAM i think. If there is a bunch of =
add/delete/modify
	   and all of those should only be applied if all of them will =
succeed...
	   good luck getting that actually implemented correctly in the
	   forwarding plane of any AN.
=09
	   The thing i could see us asking to be done atomically is really
	   JUST a single flow-swap, aka: replace exactly one flow with
	   another flow.
=09
	   So ultimately, i think:
=09
	   -> For add/delete commands we ask for no atomicity and the error
	      code returned should somehow point to the first flow within
	      a packet that failed. And provide some additional error code
	      why (which we could define the values for later). And this
	      should allow us to have multiple flows as arguments to a
	      single add/delete to be more efficient.
	 =20
	   -> a modify should be called "swap", and should support only
	      exactly two flows as the argument. This swap should work
	      atomically, aka: the join would not be executed if the leave
	      could not be done, and the leave should of course not be
	      executed if the join would not work.
	 =20
	   -> So maybe overall the error return code would be
	    =20
	      command#, flow#, why
=09
	      where command# would be pointing to the command (numbered 1 t N)
	      within the recplication control command that failed,
	      flow# would be the flow (1..M) within that command (always 1 for
	      a swap, as we only allow a single flow there), and why would be
	      some eg: 8-bit error code where we could define values for that
	      would help diagnosis.
=09
=09
	h) The degree to which a platform is able to implement even this
	   most simple atomic swap is of course subject to implementation.
=09
	Cheers
	    Toerless
	    =20
	On Mon, Apr 21, 2008 at 09:47:06PM +0100, Einar Nilsen-Nygaard wrote:
	> Vish,
	>
	> I actually think that freedom in how a =B3swap=B2 operation would be =
implemented
	> in terms of the ordering of stopping the first multicast flow and =
starting
	> the second is not desirable. By specifying that the delete must come =
before
	> the add and that the operation should be terminated upon the first =
error,
	> the current specification gives us what should be deterministic =
behavior
	> between any and all conforming implementations.
	>
	> In contrast, the freedom to implement a swap operation via some form =
of
	> modify leaves the door open to multiple ways in which a modify =
request could
	> fail, making error recovery more troublesome and vendor-specific =
which I do
	> not see as at all desirable.
	>
	> Cheers,
	>
	> Einar
	>
	> On 21/04/2008 20:12, "vishwanathan.sundaram@wipro.com"
	> <vishwanathan.sundaram@wipro.com> scribbled:
	>
	> > Einar,
	> > Modify command would be usefull from Access box perspective, as the =
underlying
	> > implementation in AN's would have the freedom to design their swap =
operation,
	> > instead of always first deleting the existing group entry and =
adding another
	> > entry.
	> >=20
	> > Thanks
	> > Vish
	> >=20
	> >
	> >
	> > From: einarnn [mailto:einarnn@cisco.com]
	> > Sent: Sun 4/20/2008 11:12 AM
	> > To: Vishwanathan Somasundaram (WT01 - TES-Access Networks); =
wdec@cisco.com;
	> > ancp@ietf.org
	> > Subject: Re: [ANCP] ANCP Multicast Control Message
	> >
	> > Vish,
	> >
	> > Overloading the second byte of the command code to contain the =
number of
	> > =B3modifications=B2 doesn=B9t seem a good approach and the space =
saving per packet,
	> > which will probably be only 4 bytes most of the time, seems almost =
irrelevant.
	> > I think it would be better to keep the fields in the message for a =
single
	> > task.
	> >
	> > Treating a sequence of commands as an atomic operation, as detailed =
in the
	> > text, and implementing a swap via a delete follow by an add, should =
give ANs
	> > the freedom to implement what are, in effect, swap operations quite
	> > efficiently. In this context, I=B9m not sure what a =B3modify=B2 =
command code will
	> > really add?
	> >
	> > Cheers,
	> >
	> > Einar
	> >
	> > On 16/04/2008 15:41, "vishwanathan.sundaram@wipro.com"
	> > <vishwanathan.sundaram@wipro.com> wrote:
	> >
	> >> Hi Woj,
	> >> Currently, the command codes for replication control message are
	> >> 1. add (0x01)
	> >> 2. delete (0x02)
	> >> 3. delete all (0x04).
	> >>
	> >> Looking at the multicast Swap message format, which is used when =
the NAS
	> >> wants to switch from one group to another,can we not handle this =
situation by
	> >> having a message type Modify (0x08).
	> >> By using this message type we can mention the multicast group =
address which
	> >> needs to be swapped by new multicast group address.
	> >> Since the Command Code is 2 bytes, the second byte can be used to =
mention the
	> >> number of multicast groups that needs to be swapped.
	> >> This will allow, for multiple multicast group swaps. This will =
also reduce
	> >> the size of the packet. Since these messages intended only between =
the NAS
	> >> and AN, the introduction of modify command type gives further ease =
to the
	> >> Access boxes in implementing the swaps, which attributes to zap =
latency.
	> >>
	> >>      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
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	> >>      |        Type (0x88-0C)         |           Length            =
  |
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	> >>      | Vers  |  Sub  |MessageType=3D90 | Result|        Code       =
    |
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	> >>      | Partition ID  |            Transaction Identifier =3D 0001  =
    |
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	> >>      |I|      SubMessage Number      |           Length            =
  |
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	> >>      | 0x01 (Replication-Control)    |             Length          =
  |
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	> >>      | 0x01 (Access-Loop-Circuit-ID) |        Client-ID Length     =
  |
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	> >>      |                                                             =
  |
	> >>      ~                      Port Client-ID                         =
  ~
	> >>      |                                                             =
  |
	> >>     =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	> >>      | Type=3DCommandCode: Modify(0x08)|           Length
	> >> |
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	> >>      | AddrFamily 01 | EncType 0x0    |  Mcast group: 239.23.2.2   =
         |
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|
	> >>      | AddrFamily 01 | EncType 0x0    |  Mcast Source: 10.1.1.1
	> >> |
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|
	> >>       | AddrFamily 01 | EncType 0x0   |  New Mcast group: =
239.55.3.2   |
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|
	> >>      | AddrFamily 01 | EncType 0x0    |  New Mcast Source: =
10.1.1.1      |
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|
	> >>
	> >> Looking into the DSL TR 101, it also discusses about the multicast =
flow being
	> >> associated with a VLAN (Multicast-Vlan). In this case, the Access =
Node, needs
	> >> to be informed about the VLAN ID on which a particular Multicast =
group is
	> >> being associated by the NAS. Can this information also be added as =
part of
	> >> the TLV in message.
	> >>
	> >> Thanks
	> >> Vish
	> >>
	> >>
	> >> From: ancp-bounces@ietf.org on behalf of Wojciech Dec (wdec)
	> >> Sent: Mon 4/14/2008 11:00 AM
	> >> To: ancp@ietf.org
	> >> Subject: [ANCP] ANCP Multicast Control Message
	> >>
	> >>
	> >>
	> >> Hi All,
	> >>
	> >> As discussed during our recent IETF 71 meeting, our protocol =
design team
	> >> has forged ahead with prioritized list of problems to address, the =
first
	> >> of which was defining the ANCP message extensions for multicast =
control,
	> >> aka unsolicited multicast control. The DT is working on the =
response
	> >> message and also the solicited multicast control mode.
	> >> Below, we present the outcome of the work, which represents both a
	> >> design team consensus as well as a proposal for adoption into the =
ANCP
	> >> protocol spec, draft-ietf-ancp-protocol (some editorial work will =
be
	> >> still required). Please review the proposal and share your =
comments. We
	> >> will assume acceptance of the proposal in principle otherwise.
	> >>
	> >> Regards,
	> >> Woj & Matthew.
	> >>
	> >>
	> >> 2       Replication Control Message
	> >>
	> >>
	> >> This message is sent by the ANCP Server (NAS) to the ANCP Client =
(AN)
	> >> with a directive to either add (join) or delete (leave) a port to =
or
	> >> from a multicast flow. Its format is as follow:
	> >>       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
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	> >>      |Type=3DReplication-Control (0x01)|             Length        =
    |
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	> >>      | 0x01 (Access-Loop-Circuit-ID) |        Client-ID Length     =
  |
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	> >>      |                                                             =
  |
	> >>      ~                      Port Client-ID                         =
  ~
	> >>      |                                                             =
  |
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	> >>
	> >> Following the Port Client-ID information, one or more Command TLV
	> >> components can be included and the Access Node should process them =
in
	> >> the order in which they are listed. The Access Node (ANCP Client) =
should
	> >> threat all the commands as a single command block to be viewed as =
a
	> >> whole and bail out immediately when one of them fails.
	> >> The format of command TLV is as follow:
	> >>
	> >>       0                   1                   2                   =
3
	> >>       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
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	> >>      |  Type =3D CommandCode           |          Length           =
    |
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	> >>      | Addr Family   | Encoding Type |  Multicast Group Address    =
  |
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	> >>      | Addr Family   | Encoding Type |  Multicast Source Address   =
  |
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	> >>
	> >> Where CommandCode specifies the command and can be one of the =
following:
	> >>
	> >> 0x01  Add       Adds the specified multicast flow to the specified =
port
	> >> (join)
	> >> 0x02  Delete    Deletes the specified multicast flow (leave) on =
the
	> >> specified port.
	> >> 0x04  DeleteAll Deletes All multicast flow on the specified port =
(leave
	> >> all). No addresses are supplied.
	> >>
	> >> When we have more than one command, Deletes should always be =
listed
	> >> first. The unicast source address/mask follows the format defined =
in RFC
	> >> 2362 Section 4.1 case 1 which is duplicated here for quick review:
	> >>
	> >> Encoded-Unicast-address: Takes the following format:
	> >>
	> >>   0                   1                   2                   3
	> >>   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
	> >>  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	> >>  | Addr Family   | Encoding Type |     Unicast Address           |
	> >>  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	> >>
	> >>      Addr Family
	> >>            The address family of the `Unicast Address' field  of
	> >>            this address.
	> >>
	> >>           Here is the address family numbers assigned by IANA:
	> >>
	> >>  Number    Description
	> >>  --------  =
---------------------------------------------------------
	> >>       0    Reserved
	> >>       1    IP (IP version 4)
	> >>       2    IP6 (IP version 6)
	> >>       3    NSAP
	> >>       4    HDLC (8-bit multidrop)
	> >>       5    BBN 1822
	> >>       6    802 (includes all 802 media plus Ethernet "canonical =
format")
	> >>       7    E.163
	> >>       8    E.164 (SMDS, Frame Relay, ATM)
	> >>       9    F.69 (Telex)
	> >>      10    X.121 (X.25, Frame Relay)
	> >>      11    IPX
	> >>      12    Appletalk
	> >>      13    Decnet IV
	> >>      14    Banyan Vines
	> >>      15    E.164 with NSAP format subaddress
	> >>
	> >>      Encoding Type
	> >>           The type of encoding used within a specific Address
	> >>           Family.  The value `0' is reserved for this field,
	> >>           and represents the native encoding of the Address
	> >>           Family.
	> >>
	> >>      Unicast Address
	> >>           The unicast address as represented by the given
	> >>           Address Family and Encoding Type.
	> >>
	> >> Finally, although the length could be derived from the Addr Family =
and
	> >> the Encoding type, it is kept for future possible extension to =
this
	> >> command where other entry would be added to this command segment.
	> >> The equivalent of a swap command where the NAS would want to =
switch from
	> >> multicast group 239.23.2.2 to 239.55.3.2 will have the following =
format:
	> >>
	> >>       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
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	> >>      |        Type (0x88-0C)         |           Length            =
  |
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	> >>      | Vers  |  Sub  |MessageType=3D90 | Result|        Code       =
    |
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	> >>      | Partition ID  |            Transaction Identifier =3D 0001  =
    |
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	> >>      |I|      SubMessage Number      |           Length            =
  |
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	> >>      | 0x01 (Replication-Control)    |             Length          =
  |
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	> >>      | 0x01 (Access-Loop-Circuit-ID) |        Client-ID Length     =
  |
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	> >>      |                                                             =
  |
	> >>      ~                      Port Client-ID                         =
  ~
	> >>      |                                                             =
  |
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	> >>      | Type=3DCommandCode: Delete(0x02)|           Length          =
    |
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	> >>      | AddrFamily 01 | EncType 0x0   |  Mcast group: 239.23.2.2    =
  |
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|
	> >>      | AddrFamily 01 | EncType 0x0   |  Mcast Source: 10.1.1.1     =
  |
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|
	> >>      | Type=3DCommandCode: Add (0x01)  |           Length          =
    |
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	> >>      | AddrFamily 01 | EncType 0x0   |  Mcast group: 239.55.3.2    =
  |
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|
	> >>      | AddrFamily 01 | EncType 0x0   |  Mcast Source: 10.1.1.1     =
  |
	> >>      =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|
	> >>
	> >> Each command in the list is attributed an identification number =
based on
	> >> its occurrence in the message. In this case, the Delete command =
will be
	> >> attributed command number 1 while the Add will be attributed =
command
	> >> number 2. During the processing of these  commands, upon the first
	> >> failure of a command, the sequence is interrupted and an error =
message
	> >> (via Multicast Status Message) will be returned with the command =
number
	> >> identifying the command that failed.
	> >>
	> >> _______________________________________________
	> >> 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
	> >
	> >  Please do not print this email unless it is absolutely necessary.
	> >
	> >  The information contained in this electronic message and any =
attachments to
	> > this message are intended for the exclusive use of the addressee(s) =
and may
	> > contain proprietary, confidential or privileged information. If you =
are not
	> > the intended recipient, you should not disseminate, distribute or =
copy this
	> > e-mail. Please notify the sender immediately and destroy all copies =
of this
	> > message and any attachments.
	> >
	> > WARNING: Computer viruses can be transmitted via email. The =
recipient should
	> > check this email and any attachments for the presence of viruses. =
The company
	> > accepts no liability for any damage caused by any virus transmitted =
by this
	> > email.
	> >
	> > www.wipro.com
	> >
	> >
	> > --
	> > Einar Nilsen-Nygaard
	> > Technical Leader, Cisco
	> >
	> > Clothes make the man. Naked people have little or no influence on
	> > society. --Mark Twain
	> >
	>
=09
	> _______________________________________________
	> ANCP mailing list
	> ANCP@ietf.org
	> https://www.ietf.org/mailman/listinfo/ancp
=09
=09
	--
	---
	Toerless Eckert, eckert@cisco.com
	Cisco NSSTG Systems & Technology Architecture
	"The strategy is what you do, not what you write" - Wesley Clark
=09


------_=_NextPart_001_01C8B759.63F408A7
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML dir=3Dltr><HEAD><TITLE>Re: [ANCP] ANCP Multicast Control =
Message</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.3314" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D393332913-16052008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Hi Vish, Woj,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D393332913-16052008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D393332913-16052008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>I agree with Woj that the VLAN should be at =
most an=20
optional parameter.&nbsp; According to me, putting the multicast VLAN in =
the=20
command message is also not correct because there can be quite a lot of =
commands=20
send from the NAS to the AN and each message would always repeat this =
same=20
information.&nbsp; It looks better to me to configure the multicast VLAN =
at the=20
level of the partition, that looks to be more than enough (if at all =
something=20
is needed).&nbsp; It is suffcient to me that the protocol is extensible =
enough=20
to add it later when it is clear that there is a real need for=20
it.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D393332913-16052008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D393332913-16052008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>regards,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D393332913-16052008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Stefaan</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D393332913-16052008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D393332913-16052008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> ancp-bounces@ietf.org=20
[mailto:ancp-bounces@ietf.org] <B>On Behalf Of </B>Wojciech Dec=20
(wdec)<BR><B>Sent:</B> vrijdag 16 mei 2008 13:21<BR><B>To:</B> =
VISHWANATHAN=20
SOMASUNDARAM; Toerless Eckert (eckert); Einar Nilsen-Nygaard=20
(einarnn)<BR><B>Cc:</B> ancp@ietf.org<BR><B>Subject:</B> Re: [ANCP] ANCP =

Multicast Control Message<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D786361511-16052008><FONT =
face=3DArial=20
size=3D2>Hi Vish,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D786361511-16052008><FONT =
face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D786361511-16052008><FONT =
face=3DArial=20
size=3D2>adding the VLAN tag as a mandatory parameter seems undesirable. =
The use=20
or otherwise of "multicast VLANs" is a local configuration issue&nbsp;on =
the AN=20
which could be set to a default, or at best an optional parameter in the =
ANCP=20
request message.</FONT></SPAN><BR></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D786361511-16052008><FONT =
face=3DArial=20
size=3D2>Regards,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D786361511-16052008><FONT =
face=3DArial=20
size=3D2>Woj.</FONT></SPAN></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> ancp-bounces@ietf.org=20
  [mailto:ancp-bounces@ietf.org] <B>On Behalf Of=20
  </B>vishwanathan.sundaram@wipro.com<BR><B>Sent:</B> 22 April 2008=20
  17:40<BR><B>To:</B> Toerless Eckert (eckert); Einar Nilsen-Nygaard=20
  (einarnn)<BR><B>Cc:</B> ancp@ietf.org<BR><B>Subject:</B> Re: [ANCP] =
ANCP=20
  Multicast Control Message<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV id=3DidOWAReplyText87990 dir=3Dltr>
  <DIV dir=3Dltr><FONT face=3DArial size=3D2>Comments</FONT></DIV>
  <DIV dir=3Dltr><FONT face=3DArial size=3D2>a&gt; It would be good to =
add Vlan tag as=20
  one of the parameters to the add/delete command, as this will indicate =
which=20
  VLAN should be used for multicasting.&nbsp;DSL TR =
101,&nbsp;&nbsp;discusses=20
  about the multicast flow being associated with a VLAN =
(Multicast-Vlan). In=20
  this case, the Access Node, needs to be informed about the VLAN ID on =
which a=20
  particular Multicast group is being associated by the =
NAS.</FONT></DIV>
  <DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
  <DIV dir=3Dltr><FONT face=3DArial size=3D2>Cheers</FONT></DIV>
  <DIV dir=3Dltr><FONT face=3DArial size=3D2>Vish</FONT></DIV>
  <DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT><FONT face=3DArial=20
  size=3D2></FONT>&nbsp;</DIV>
  <DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV><FONT =
face=3DArial=20
  size=3D2></FONT></DIV>
  <DIV dir=3Dltr><FONT face=3DArial size=3D2>
  <DIV dir=3Dltr><BR></FONT><BR></DIV>
  <DIV dir=3Dltr>
  <HR tabIndex=3D-1>
  </DIV>
  <DIV dir=3Dltr><FONT face=3DTahoma size=3D2><B>From:</B> Toerless =
Eckert=20
  [mailto:eckert@cisco.com]<BR><B>Sent:</B> Mon 4/21/2008 6:00 =
PM<BR><B>To:</B>=20
  Einar Nilsen-Nygaard<BR><B>Cc:</B> Vishwanathan Somasundaram (WT01 -=20
  TES-Access Networks); wdec@cisco.com; ancp@ietf.org<BR><B>Subject:</B> =
Re:=20
  [ANCP] ANCP Multicast Control Message<BR></FONT><BR></DIV></DIV>
  <DIV>
  <P><FONT size=3D2>Some comments:<BR><BR>a) Please change the name of =
the two=20
  'Length' fields in the<BR>&nbsp;&nbsp; control mesages sucht hat they =
can be=20
  differentiated easier from<BR>&nbsp;&nbsp; another and specify what is =
counted=20
  in them, eg:<BR><BR>&nbsp;&nbsp;&nbsp; Type=3DReplication-Control=20
  =
(0x01)|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;=20
  =
Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =

  =
|<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;=20
  ^^^^^^<BR>&nbsp;&nbsp;&nbsp;<BR>&nbsp;&nbsp; suggest to change to =
RC-Length,=20
  explanation "total number of bytes<BR>&nbsp;&nbsp; of the following =
TLVs plus=20
  the replication control header".<BR><BR>&nbsp;&nbsp;&nbsp; Type =3D=20
  =
CommandCode&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;=20
  =
Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;=20
  =
|<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  ^^^^^^<BR><BR>&nbsp;&nbsp; suggest to change to CC-Length, explanation =
"total=20
  number of<BR>&nbsp;&nbsp; this CommandCode TLV, counting this header =
and the=20
  following<BR>&nbsp;&nbsp; multicast flow bytes".<BR><BR>b) Please try =
to avoid=20
  using the term "group" when referring to<BR>&nbsp;&nbsp; an address =
which is=20
  either an ASM (Any Source Multicast) group<BR>&nbsp;&nbsp; address =
(aka: a=20
  single multicast group address, IPv4 or IPv6)<BR>&nbsp;&nbsp; or an =
SSM=20
  channel (aka: source and group address).<BR><BR>&nbsp;&nbsp; I would =
stroingly=20
  suggest to only use the term "multicast flow"<BR>&nbsp;&nbsp; or =
multicast=20
  flow address, or just "flow", and define that term<BR>&nbsp;&nbsp; in =
the=20
  beginning of the document to be either an ASN group or<BR>&nbsp;&nbsp; =
SSM=20
  channel.<BR><BR>&nbsp;&nbsp; Otherwise there will be lots of =
confusions about=20
  whether or not<BR>&nbsp;&nbsp; SSM is well supported by =
ANCP.<BR><BR>c) Do not=20
  refer to rfc2362. That RFC is obsolete and replaced by=20
  rfc4601.<BR>&nbsp;&nbsp; I do not see a good reason to refer to any =
PIM spec=20
  anyhow, just<BR>&nbsp;&nbsp; resolve the references used within the =
PIM-SM=20
  spec, eg:<BR><BR>&nbsp;&nbsp; <A=20
  =
href=3D"http://www.iana.org/assignments/address-family-numbers">http://ww=
w.iana.org/assignments/address-family-numbers</A><BR><BR>&nbsp;&nbsp;=20
  or the like.<BR><BR>d) To identify an actual SSM channel, it would be=20
  preferrable IMHO<BR>&nbsp;&nbsp; to have an address family identifier =
for an=20
  SSM channel, aka:<BR>&nbsp;&nbsp; an IP(v6/v6) source IP address =
followed by a=20
  group address. As<BR>&nbsp;&nbsp; above IANA URL has nothing like this =

  defined, i think there are<BR>&nbsp;&nbsp; two =
choices:<BR><BR>&nbsp;&nbsp;=20
  -&gt; I) I'll check what effort it is to get that defined through=20
  IANA.<BR><BR>&nbsp;&nbsp; -&gt; II) we stick with the existing =
specification,=20
  which is to<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; have a separate field=20
  addrfamily/encoding/group and one<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  addrfamily/encoding/source, but then i would very=20
  much<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; like to see very explicit =
description=20
  in the protocol spec<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; what sequeneces =
of=20
  addfamily/encoding/addr (AEA) elements are=20
  valid,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and how they have to be=20
  interpreted:<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; for add/delete=20
  commands:<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&gt; MUST =
support a=20
  single AEA argument where the=20
  =
address<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
is an=20
  IPv4/IPv6 address that is a multicast=20
  group.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
(ASM=20
  case).<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -&gt; MUST =
support=20
  TWO AEA argument where the address of=20
  the<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
first AEA=20
  is an IPv4/IPv6 address which is a=20
  =
unicast<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  address, and the second AEA is an IPv4/IPv6 address=20
  which<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
is a=20
  multicast address. Aka: SSM=20
  =
case.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 In=20
  the example text i see two things i am=20
  questioning:<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; I) The =
(S,G)=20
  channels are encoded first group and then=20
  =
source.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
That=20
  IMHO is not preferrable. I would rather suggest=20
  like<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
written=20
  above to encode first source and then=20
  =
group.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  II) The text is suggesting to have eg: multiple group=20
  =
AEA<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
=20
  following an add/delete TLV. I have no strong=20
  =
opinion<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
  whether or not that should be supported, but if we=20
  =
conclude<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;=20
  it should be supported, then that should explicitly be=20
  =
mentioned<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;=20
  in the text (see also below). And that description=20
  =
would<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;=20
  then of course have to detail a bit how a list of=20
  =
AEAs<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;=20
  with ASM groups and SSM channels is to be=20
  =
encoded.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;=20
  Particularily this case makes it of course=20
  =
important<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;=20
  to either be very clear how an SSM channel is=20
  =
encoded<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;=20
  (source first or group first), or even better use a=20
  =
separate<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;=20
  Address-Familty identifier as suggested above.<BR><BR>e) I do not see =
any=20
  suggestion on the command reply. Is there<BR>&nbsp;&nbsp; supposed to =
be some=20
  failure and/or success return codes ?<BR><BR>f) As far as return codes =
are=20
  concerned: I would like to see some<BR>&nbsp;&nbsp; clearer statement =
about=20
  the suggested atomicity (if that's a<BR>&nbsp;&nbsp; valid english =
word ;-) of=20
  the execution of multiple flows<BR>&nbsp;&nbsp; within a single=20
  add/delete/modify TLV as well as the flows across<BR>&nbsp;&nbsp; =
multiple=20
  TLVs within the same replication control message.<BR><BR>&nbsp;&nbsp; =
-&gt;=20
  What happens if any individual flow add/delete fails ?=20
  The<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; document right now only seems to =
imply=20
  that the execution of<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the following=20
  add/deletes is simply not executed.&nbsp; That=20
  by<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; itself would require the NAS to =
either=20
  query all state to figure<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; out what =
actually=20
  was executed or to simply try everything=20
  again.<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; If we would add a return =
code=20
  like the following, that would<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; not =
be=20
  =
necessary:<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;=20
  "Sorry, error: all flows up to byte XX into the packet=20
  where<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; performed =
well, and=20
  the following flow failed to=20
  be<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
addeded/deleted, and=20
  the rest was not even=20
  =
tried"<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; I=20
  am not sure if this type of error return is the=20
  preferred<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; solution, but if we do not =
mandate=20
  something better, then<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; it probably =
should be=20
  done.<BR>&nbsp;&nbsp;<BR>&nbsp;&nbsp; -&gt; A better solution would be =
to=20
  imply some form of atomicity,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; eg: =
either at=20
  TLV or at replication control level.=20
  Meaning:<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the AN tries to execute=20
  add/delete/modifies, but if anything =
fails,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  then everything is undone. Or better: Nothing is applied=20
  by<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the AN unless it can make sure =
everything=20
  will succeed.<BR><BR>g) Atomicity is a hard bargain for the =
control/forwarding=20
  plane<BR>&nbsp;&nbsp; of a router/switch/DSLAM i think. If there is a =
bunch of=20
  add/delete/modify<BR>&nbsp;&nbsp; and all of those should only be =
applied if=20
  all of them will succeed...<BR>&nbsp;&nbsp; good luck getting that =
actually=20
  implemented correctly in the<BR>&nbsp;&nbsp; forwarding plane of any=20
  AN.<BR><BR>&nbsp;&nbsp; The thing i could see us asking to be done =
atomically=20
  is really<BR>&nbsp;&nbsp; JUST a single flow-swap, aka: replace =
exactly one=20
  flow with<BR>&nbsp;&nbsp; another flow.<BR><BR>&nbsp;&nbsp; So =
ultimately, i=20
  think:<BR><BR>&nbsp;&nbsp; -&gt; For add/delete commands we ask for no =

  atomicity and the error<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; code =
returned should=20
  somehow point to the first flow =
within<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a=20
  packet that failed. And provide some additional error=20
  code<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; why (which we could define the =
values=20
  for later). And this<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; should allow us =
to have=20
  multiple flows as arguments to a<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
single=20
  add/delete to be more efficient.<BR>&nbsp;&nbsp;<BR>&nbsp;&nbsp; -&gt; =
a=20
  modify should be called "swap", and should support=20
  only<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; exactly two flows as the =
argument. This=20
  swap should work<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; atomically, aka: =
the join=20
  would not be executed if the leave<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
could not=20
  be done, and the leave should of course not=20
  be<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; executed if the join would not=20
  work.<BR>&nbsp;&nbsp;<BR>&nbsp;&nbsp; -&gt; So maybe overall the error =
return=20
  code would=20
  be<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =

  command#, flow#, why<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; where =
command#=20
  would be pointing to the command (numbered 1 t=20
  N)<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; within the recplication control =
command=20
  that failed,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; flow# would be the flow =
(1..M)=20
  within that command (always 1 for<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a =
swap, as=20
  we only allow a single flow there), and why would=20
  be<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; some eg: 8-bit error code where =
we could=20
  define values for that<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; would help=20
  diagnosis.<BR><BR><BR>h) The degree to which a platform is able to =
implement=20
  even this<BR>&nbsp;&nbsp; most simple atomic swap is of course subject =
to=20
  implementation.<BR><BR>Cheers<BR>&nbsp;&nbsp;&nbsp;=20
  Toerless<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>On Mon, Apr 21, 2008 at=20
  09:47:06PM +0100, Einar Nilsen-Nygaard wrote:<BR>&gt; =
Vish,<BR>&gt;<BR>&gt; I=20
  actually think that freedom in how a =B3swap=B2 operation would be=20
  implemented<BR>&gt; in terms of the ordering of stopping the first =
multicast=20
  flow and starting<BR>&gt; the second is not desirable. By specifying =
that the=20
  delete must come before<BR>&gt; the add and that the operation should =
be=20
  terminated upon the first error,<BR>&gt; the current specification =
gives us=20
  what should be deterministic behavior<BR>&gt; between any and all =
conforming=20
  implementations.<BR>&gt;<BR>&gt; In contrast, the freedom to implement =
a swap=20
  operation via some form of<BR>&gt; modify leaves the door open to =
multiple=20
  ways in which a modify request could<BR>&gt; fail, making error =
recovery more=20
  troublesome and vendor-specific which I do<BR>&gt; not see as at all=20
  desirable.<BR>&gt;<BR>&gt; Cheers,<BR>&gt;<BR>&gt; =
Einar<BR>&gt;<BR>&gt; On=20
  21/04/2008 20:12, "vishwanathan.sundaram@wipro.com"<BR>&gt;=20
  &lt;vishwanathan.sundaram@wipro.com&gt; scribbled:<BR>&gt;<BR>&gt; =
&gt;=20
  Einar,<BR>&gt; &gt; Modify command would be usefull from Access box=20
  perspective, as the underlying<BR>&gt; &gt; implementation in AN's =
would have=20
  the freedom to design their swap operation,<BR>&gt; &gt; instead of =
always=20
  first deleting the existing group entry and adding another<BR>&gt; =
&gt;=20
  entry.<BR>&gt; &gt;&nbsp;<BR>&gt; &gt; Thanks<BR>&gt; &gt; =
Vish<BR>&gt;=20
  &gt;&nbsp;<BR>&gt; &gt;<BR>&gt; &gt;<BR>&gt; &gt; From: einarnn [<A=20
  =
href=3D"mailto:einarnn@cisco.com">mailto:einarnn@cisco.com</A>]<BR>&gt; =
&gt;=20
  Sent: Sun 4/20/2008 11:12 AM<BR>&gt; &gt; To: Vishwanathan =
Somasundaram (WT01=20
  - TES-Access Networks); wdec@cisco.com;<BR>&gt; &gt; =
ancp@ietf.org<BR>&gt;=20
  &gt; Subject: Re: [ANCP] ANCP Multicast Control Message<BR>&gt; =
&gt;<BR>&gt;=20
  &gt; Vish,<BR>&gt; &gt;<BR>&gt; &gt; Overloading the second byte of =
the=20
  command code to contain the number of<BR>&gt; &gt; =B3modifications=B2 =
doesn=B9t=20
  seem a good approach and the space saving per packet,<BR>&gt; &gt; =
which will=20
  probably be only 4 bytes most of the time, seems almost =
irrelevant.<BR>&gt;=20
  &gt; I think it would be better to keep the fields in the message for =
a=20
  single<BR>&gt; &gt; task.<BR>&gt; &gt;<BR>&gt; &gt; Treating a =
sequence of=20
  commands as an atomic operation, as detailed in the<BR>&gt; &gt; text, =
and=20
  implementing a swap via a delete follow by an add, should give =
ANs<BR>&gt;=20
  &gt; the freedom to implement what are, in effect, swap operations=20
  quite<BR>&gt; &gt; efficiently. In this context, I=B9m not sure what a =
=B3modify=B2=20
  command code will<BR>&gt; &gt; really add?<BR>&gt; &gt;<BR>&gt; &gt;=20
  Cheers,<BR>&gt; &gt;<BR>&gt; &gt; Einar<BR>&gt; &gt;<BR>&gt; &gt; On=20
  16/04/2008 15:41, "vishwanathan.sundaram@wipro.com"<BR>&gt; &gt;=20
  &lt;vishwanathan.sundaram@wipro.com&gt; wrote:<BR>&gt; &gt;<BR>&gt; =
&gt;&gt;=20
  Hi Woj,<BR>&gt; &gt;&gt; Currently, the command codes for replication =
control=20
  message are<BR>&gt; &gt;&gt; 1. add (0x01)<BR>&gt; &gt;&gt; 2. delete=20
  (0x02)<BR>&gt; &gt;&gt; 3. delete all (0x04).<BR>&gt; &gt;&gt;<BR>&gt; =

  &gt;&gt; Looking at the multicast Swap message format, which is used =
when the=20
  NAS<BR>&gt; &gt;&gt; wants to switch from one group to another,can we =
not=20
  handle this situation by<BR>&gt; &gt;&gt; having a message type Modify =

  (0x08).<BR>&gt; &gt;&gt; By using this message type we can mention the =

  multicast group address which<BR>&gt; &gt;&gt; needs to be swapped by =
new=20
  multicast group address.<BR>&gt; &gt;&gt; Since the Command Code is 2 =
bytes,=20
  the second byte can be used to mention the<BR>&gt; &gt;&gt; number of=20
  multicast groups that needs to be swapped.<BR>&gt; &gt;&gt; This will =
allow,=20
  for multiple multicast group swaps. This will also reduce<BR>&gt; =
&gt;&gt; the=20
  size of the packet. Since these messages intended only between the =
NAS<BR>&gt;=20
  &gt;&gt; and AN, the introduction of modify command type gives further =
ease to=20
  the<BR>&gt; &gt;&gt; Access boxes in implementing the swaps, which =
attributes=20
  to zap latency.<BR>&gt; &gt;&gt;<BR>&gt;=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 =
6 7 8 9=20
  0 1 2 3 4 5 6 7 8 9 0 1<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =

  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;=
=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Type=20
  (0x88-0C)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;=20
  |<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;=
=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Vers&nbsp; |&nbsp; Sub&nbsp;=20
  |MessageType=3D90 | Result|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Code&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|<BR>&gt;=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;=
=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Partition ID&nbsp;=20
  |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Transaction Identifier =3D 0001&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|<BR>&gt;=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;=
=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|I|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  SubMessage Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;=20
  |<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;=
=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | 0x01=20
  (Replication-Control)&nbsp;&nbsp;&nbsp;=20
  =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
=20
  =
Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =

  |<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;=
=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | 0x01 (Access-Loop-Circuit-ID) =

  |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Client-ID=20
  Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<BR>&gt;=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;=
=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;=20
  |<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Port=20
  =
Client-ID&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;=20
  ~<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;=20
  |<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;=
=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Type=3DCommandCode:=20
  =
Modify(0x08)|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
=20
  Length<BR>&gt; &gt;&gt; |<BR>&gt; =
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;=
=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | AddrFamily 01 | EncType=20
  0x0&nbsp;&nbsp;&nbsp; |&nbsp; Mcast group:=20
  =
239.23.2.2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;=20
  |<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|<BR>&gt;=
=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | AddrFamily 01 | EncType=20
  0x0&nbsp;&nbsp;&nbsp; |&nbsp; Mcast Source: 10.1.1.1<BR>&gt; &gt;&gt;=20
  |<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|<BR>&gt;=
=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | AddrFamily 01 | EncType =

  0x0&nbsp;&nbsp; |&nbsp; New Mcast group: 239.55.3.2&nbsp;&nbsp; =
|<BR>&gt;=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|<BR>&gt;=
=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | AddrFamily 01 | EncType=20
  0x0&nbsp;&nbsp;&nbsp; |&nbsp; New Mcast Source:=20
  10.1.1.1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<BR>&gt;=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|<BR>&gt;=
=20
  &gt;&gt;<BR>&gt; &gt;&gt; Looking into the DSL TR 101, it also =
discusses about=20
  the multicast flow being<BR>&gt; &gt;&gt; associated with a VLAN=20
  (Multicast-Vlan). In this case, the Access Node, needs<BR>&gt; =
&gt;&gt; to be=20
  informed about the VLAN ID on which a particular Multicast group =
is<BR>&gt;=20
  &gt;&gt; being associated by the NAS. Can this information also be =
added as=20
  part of<BR>&gt; &gt;&gt; the TLV in message.<BR>&gt; &gt;&gt;<BR>&gt; =
&gt;&gt;=20
  Thanks<BR>&gt; &gt;&gt; Vish<BR>&gt; &gt;&gt;<BR>&gt; &gt;&gt;<BR>&gt; =

  &gt;&gt; From: ancp-bounces@ietf.org on behalf of Wojciech Dec =
(wdec)<BR>&gt;=20
  &gt;&gt; Sent: Mon 4/14/2008 11:00 AM<BR>&gt; &gt;&gt; To:=20
  ancp@ietf.org<BR>&gt; &gt;&gt; Subject: [ANCP] ANCP Multicast Control=20
  Message<BR>&gt; &gt;&gt;<BR>&gt; &gt;&gt;<BR>&gt; &gt;&gt;<BR>&gt; =
&gt;&gt; Hi=20
  All,<BR>&gt; &gt;&gt;<BR>&gt; &gt;&gt; As discussed during our recent =
IETF 71=20
  meeting, our protocol design team<BR>&gt; &gt;&gt; has forged ahead =
with=20
  prioritized list of problems to address, the first<BR>&gt; &gt;&gt; of =
which=20
  was defining the ANCP message extensions for multicast =
control,<BR>&gt;=20
  &gt;&gt; aka unsolicited multicast control. The DT is working on the=20
  response<BR>&gt; &gt;&gt; message and also the solicited multicast =
control=20
  mode.<BR>&gt; &gt;&gt; Below, we present the outcome of the work, =
which=20
  represents both a<BR>&gt; &gt;&gt; design team consensus as well as a =
proposal=20
  for adoption into the ANCP<BR>&gt; &gt;&gt; protocol spec,=20
  draft-ietf-ancp-protocol (some editorial work will be<BR>&gt; &gt;&gt; =
still=20
  required). Please review the proposal and share your comments. =
We<BR>&gt;=20
  &gt;&gt; will assume acceptance of the proposal in principle=20
  otherwise.<BR>&gt; &gt;&gt;<BR>&gt; &gt;&gt; Regards,<BR>&gt; &gt;&gt; =
Woj=20
  &amp; Matthew.<BR>&gt; &gt;&gt;<BR>&gt; &gt;&gt;<BR>&gt; &gt;&gt;=20
  2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Replication Control =
Message<BR>&gt;=20
  &gt;&gt;<BR>&gt; &gt;&gt;<BR>&gt; &gt;&gt; This message is sent by the =
ANCP=20
  Server (NAS) to the ANCP Client (AN)<BR>&gt; &gt;&gt; with a directive =
to=20
  either add (join) or delete (leave) a port to or<BR>&gt; &gt;&gt; from =
a=20
  multicast flow. Its format is as follow:<BR>&gt;=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0 1 2 3 4 5 6 7 8 9 0 1 2 =
3 4 5 6=20
  7 8 9 0 1 2 3 4 5 6 7 8 9 0 1<BR>&gt; =
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;=
=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |Type=3DReplication-Control=20
  =
(0x01)|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;=20
  =
Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =

  |<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;=
=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | 0x01 (Access-Loop-Circuit-ID) =

  |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Client-ID=20
  Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<BR>&gt;=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;=
=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;=20
  |<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Port=20
  =
Client-ID&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;=20
  ~<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;=20
  |<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;=
=20
  &gt;&gt;<BR>&gt; &gt;&gt; Following the Port Client-ID information, =
one or=20
  more Command TLV<BR>&gt; &gt;&gt; components can be included and the =
Access=20
  Node should process them in<BR>&gt; &gt;&gt; the order in which they =
are=20
  listed. The Access Node (ANCP Client) should<BR>&gt; &gt;&gt; threat =
all the=20
  commands as a single command block to be viewed as a<BR>&gt; &gt;&gt; =
whole=20
  and bail out immediately when one of them fails.<BR>&gt; &gt;&gt; The =
format=20
  of command TLV is as follow:<BR>&gt; &gt;&gt;<BR>&gt;=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  3<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0 1 2 3 4 5 6 7 =
8 9 0 1=20
  2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1<BR>&gt;=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;=
=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp; Type =3D=20
  =
CommandCode&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;=20
  |<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;=
=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Addr Family&nbsp;&nbsp; | =
Encoding=20
  Type |&nbsp; Multicast Group Address&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|<BR>&gt;=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;=
=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Addr Family&nbsp;&nbsp; | =
Encoding=20
  Type |&nbsp; Multicast Source Address&nbsp;&nbsp;&nbsp;&nbsp; =
|<BR>&gt;=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;=
=20
  &gt;&gt;<BR>&gt; &gt;&gt; Where CommandCode specifies the command and =
can be=20
  one of the following:<BR>&gt; &gt;&gt;<BR>&gt; &gt;&gt; 0x01&nbsp;=20
  Add&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Adds the specified multicast =
flow to=20
  the specified port<BR>&gt; &gt;&gt; (join)<BR>&gt; &gt;&gt; 0x02&nbsp; =

  Delete&nbsp;&nbsp;&nbsp; Deletes the specified multicast flow (leave) =
on=20
  the<BR>&gt; &gt;&gt; specified port.<BR>&gt; &gt;&gt; 0x04&nbsp; =
DeleteAll=20
  Deletes All multicast flow on the specified port (leave<BR>&gt; =
&gt;&gt; all).=20
  No addresses are supplied.<BR>&gt; &gt;&gt;<BR>&gt; &gt;&gt; When we =
have more=20
  than one command, Deletes should always be listed<BR>&gt; &gt;&gt; =
first. The=20
  unicast source address/mask follows the format defined in RFC<BR>&gt; =
&gt;&gt;=20
  2362 Section 4.1 case 1 which is duplicated here for quick =
review:<BR>&gt;=20
  &gt;&gt;<BR>&gt; &gt;&gt; Encoded-Unicast-address: Takes the following =

  format:<BR>&gt; &gt;&gt;<BR>&gt; &gt;&gt;&nbsp;&nbsp;=20
  =
0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  3<BR>&gt; &gt;&gt;&nbsp;&nbsp; 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 =
0 1 2 3=20
  4 5 6 7 8 9 0 1<BR>&gt; &gt;&gt;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;=
=20
  &gt;&gt;&nbsp; | Addr Family&nbsp;&nbsp; | Encoding Type=20
  |&nbsp;&nbsp;&nbsp;&nbsp; Unicast=20
  Address&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|<BR>&gt;=20
  &gt;&gt;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;=
=20
  &gt;&gt;<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Addr =
Family<BR>&gt;=20
  =
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; The=20
  address family of the `Unicast Address' field&nbsp; of<BR>&gt;=20
  =
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;=20
  this address.<BR>&gt; &gt;&gt;<BR>&gt;=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Here is=20
  the address family numbers assigned by IANA:<BR>&gt; &gt;&gt;<BR>&gt;=20
  &gt;&gt;&nbsp; Number&nbsp;&nbsp;&nbsp; Description<BR>&gt; =
&gt;&gt;&nbsp;=20
  --------&nbsp;=20
  ---------------------------------------------------------<BR>&gt;=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp;=20
  Reserved<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  1&nbsp;&nbsp;&nbsp; IP (IP version 4)<BR>&gt;=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2&nbsp;&nbsp;&nbsp; IP6 =
(IP=20
  version 6)<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  3&nbsp;&nbsp;&nbsp; NSAP<BR>&gt; =
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  4&nbsp;&nbsp;&nbsp; HDLC (8-bit multidrop)<BR>&gt;=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 5&nbsp;&nbsp;&nbsp; BBN=20
  1822<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
6&nbsp;&nbsp;&nbsp;=20
  802 (includes all 802 media plus Ethernet "canonical format")<BR>&gt;=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 7&nbsp;&nbsp;&nbsp; =
E.163<BR>&gt;=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 8&nbsp;&nbsp;&nbsp; E.164 =
(SMDS,=20
  Frame Relay, ATM)<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =

  9&nbsp;&nbsp;&nbsp; F.69 (Telex)<BR>&gt;=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 10&nbsp;&nbsp;&nbsp; X.121 =
(X.25, Frame=20
  Relay)<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
11&nbsp;&nbsp;&nbsp;=20
  IPX<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
12&nbsp;&nbsp;&nbsp;=20
  Appletalk<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
13&nbsp;&nbsp;&nbsp;=20
  Decnet IV<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
14&nbsp;&nbsp;&nbsp;=20
  Banyan Vines<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  15&nbsp;&nbsp;&nbsp; E.164 with NSAP format subaddress<BR>&gt;=20
  &gt;&gt;<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Encoding =
Type<BR>&gt;=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
The type=20
  of encoding used within a specific Address<BR>&gt;=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Family.&nbsp; The value `0' is reserved for this field,<BR>&gt;=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
and=20
  represents the native encoding of the Address<BR>&gt;=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Family.<BR>&gt; &gt;&gt;<BR>&gt; =
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Unicast Address<BR>&gt;=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
The=20
  unicast address as represented by the given<BR>&gt;=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Address=20
  Family and Encoding Type.<BR>&gt; &gt;&gt;<BR>&gt; &gt;&gt; Finally, =
although=20
  the length could be derived from the Addr Family and<BR>&gt; &gt;&gt; =
the=20
  Encoding type, it is kept for future possible extension to =
this<BR>&gt;=20
  &gt;&gt; command where other entry would be added to this command=20
  segment.<BR>&gt; &gt;&gt; The equivalent of a swap command where the =
NAS would=20
  want to switch from<BR>&gt; &gt;&gt; multicast group 239.23.2.2 to =
239.55.3.2=20
  will have the following format:<BR>&gt; &gt;&gt;<BR>&gt;=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0 1 2 3 4 5 6 7 8 9 0 1 2 =
3 4 5 6=20
  7 8 9 0 1 2 3 4 5 6 7 8 9 0 1<BR>&gt; =
&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;=
=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Type=20
  (0x88-0C)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;=20
  |<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;=
=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Vers&nbsp; |&nbsp; Sub&nbsp;=20
  |MessageType=3D90 | Result|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Code&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|<BR>&gt;=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;=
=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Partition ID&nbsp;=20
  |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Transaction Identifier =3D 0001&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|<BR>&gt;=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;=
=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|I|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  SubMessage Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;=20
  |<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;=
=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | 0x01=20
  (Replication-Control)&nbsp;&nbsp;&nbsp;=20
  =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
=20
  =
Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =

  |<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;=
=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | 0x01 (Access-Loop-Circuit-ID) =

  |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Client-ID=20
  Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<BR>&gt;=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;=
=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;=20
  |<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
~&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  Port=20
  =
Client-ID&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;=20
  ~<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;=20
  |<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;=
=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Type=3DCommandCode:=20
  =
Delete(0x02)|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
=20
  =
Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;=20
  |<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;=
=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | AddrFamily 01 | EncType=20
  0x0&nbsp;&nbsp; |&nbsp; Mcast group: =
239.23.2.2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  |<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|<BR>&gt;=
=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | AddrFamily 01 | EncType=20
  0x0&nbsp;&nbsp; |&nbsp; Mcast Source:=20
  10.1.1.1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<BR>&gt;=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|<BR>&gt;=
=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Type=3DCommandCode: Add =
(0x01)&nbsp;=20
  |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;=20
  |<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>&gt;=
=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | AddrFamily 01 | EncType=20
  0x0&nbsp;&nbsp; |&nbsp; Mcast group: =
239.55.3.2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  |<BR>&gt; &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|<BR>&gt;=
=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | AddrFamily 01 | EncType=20
  0x0&nbsp;&nbsp; |&nbsp; Mcast Source:=20
  10.1.1.1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<BR>&gt;=20
  &gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
  =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-|<BR>&gt;=
=20
  &gt;&gt;<BR>&gt; &gt;&gt; Each command in the list is attributed an=20
  identification number based on<BR>&gt; &gt;&gt; its occurrence in the =
message.=20
  In this case, the Delete command will be<BR>&gt; &gt;&gt; attributed =
command=20
  number 1 while the Add will be attributed command<BR>&gt; &gt;&gt; =
number 2.=20
  During the processing of these&nbsp; commands, upon the first<BR>&gt; =
&gt;&gt;=20
  failure of a command, the sequence is interrupted and an error =
message<BR>&gt;=20
  &gt;&gt; (via Multicast Status Message) will be returned with the =
command=20
  number<BR>&gt; &gt;&gt; identifying the command that failed.<BR>&gt;=20
  &gt;&gt;<BR>&gt; &gt;&gt;=20
  _______________________________________________<BR>&gt; &gt;&gt; ANCP =
mailing=20
  list<BR>&gt; &gt;&gt; ANCP@ietf.org<BR>&gt; &gt;&gt; <A=20
  =
href=3D"https://www.ietf.org/mailman/listinfo/ancp">https://www.ietf.org/=
mailman/listinfo/ancp</A><BR>&gt;=20
  &gt;&gt;<BR>&gt; &gt;&gt;<BR>&gt; &gt;&gt;=20
  _______________________________________________<BR>&gt; &gt;&gt; ANCP =
mailing=20
  list<BR>&gt; &gt;&gt; ANCP@ietf.org<BR>&gt; &gt;&gt; <A=20
  =
href=3D"https://www.ietf.org/mailman/listinfo/ancp">https://www.ietf.org/=
mailman/listinfo/ancp</A><BR>&gt;=20
  &gt;<BR>&gt; &gt;&nbsp; Please do not print this email unless it is =
absolutely=20
  necessary.<BR>&gt; &gt;<BR>&gt; &gt;&nbsp; The information contained =
in this=20
  electronic message and any attachments to<BR>&gt; &gt; this message =
are=20
  intended for the exclusive use of the addressee(s) and may<BR>&gt; =
&gt;=20
  contain proprietary, confidential or privileged information. If you =
are=20
  not<BR>&gt; &gt; the intended recipient, you should not disseminate,=20
  distribute or copy this<BR>&gt; &gt; e-mail. Please notify the sender=20
  immediately and destroy all copies of this<BR>&gt; &gt; message and =
any=20
  attachments.<BR>&gt; &gt;<BR>&gt; &gt; WARNING: Computer viruses can =
be=20
  transmitted via email. The recipient should<BR>&gt; &gt; check this =
email and=20
  any attachments for the presence of viruses. The company<BR>&gt; &gt; =
accepts=20
  no liability for any damage caused by any virus transmitted by =
this<BR>&gt;=20
  &gt; email.<BR>&gt; &gt;<BR>&gt; &gt; www.wipro.com<BR>&gt; =
&gt;<BR>&gt;=20
  &gt;<BR>&gt; &gt; --<BR>&gt; &gt; Einar Nilsen-Nygaard<BR>&gt; &gt; =
Technical=20
  Leader, Cisco<BR>&gt; &gt;<BR>&gt; &gt; Clothes make the man. Naked =
people=20
  have little or no influence on<BR>&gt; &gt; society. --Mark =
Twain<BR>&gt;=20
  &gt;<BR>&gt;<BR><BR>&gt;=20
  _______________________________________________<BR>&gt; ANCP mailing=20
  list<BR>&gt; ANCP@ietf.org<BR>&gt; <A=20
  =
href=3D"https://www.ietf.org/mailman/listinfo/ancp">https://www.ietf.org/=
mailman/listinfo/ancp</A><BR><BR><BR>--<BR>---<BR>Toerless=20
  Eckert, eckert@cisco.com<BR>Cisco NSSTG Systems &amp; Technology=20
  Architecture<BR>"The strategy is what you do, not what you write" - =
Wesley=20
  Clark<BR></FONT></P></DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C8B759.63F408A7--

--===============2066166416==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============2066166416==--


From ancp-bounces@ietf.org  Thu May 22 12:24:59 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id B46593A6A43;
	Thu, 22 May 2008 12:24:59 -0700 (PDT)
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 AC6B13A69FD
	for <ancp@core3.amsl.com>; Thu, 22 May 2008 12:23:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 spFUVVDyZal1 for <ancp@core3.amsl.com>;
	Thu, 22 May 2008 12:23:39 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149])
	by core3.amsl.com (Postfix) with ESMTP id 930E63A68D2
	for <ancp@ietf.org>; Thu, 22 May 2008 12:23:39 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,526,1204520400"; 
   d="scan'208";a="9063410"
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 22 May 2008 15:23:39 -0400
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m4MJNd9o030515
	for <ancp@ietf.org>; Thu, 22 May 2008 15:23:39 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id m4MJNdId002551
	for <ancp@ietf.org>; Thu, 22 May 2008 19:23:39 GMT
Received: from xmb-rtp-214.amer.cisco.com ([64.102.31.75]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 22 May 2008 15:23:38 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 22 May 2008 15:23:38 -0400
Message-ID: <B572D44B3E633C458552EA782C13BE3404A34CC8@xmb-rtp-214.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Adjacency timer
Thread-Index: Aci8PRAa/3IC9tapRTaTNB02UW1umQABBpRw
From: "Vitali Vinokour (vvinokou)" <vvinokou@cisco.com>
To: <ancp@ietf.org>
X-OriginalArrivalTime: 22 May 2008 19:23:39.0047 (UTC)
	FILETIME=[56845B70:01C8BC41]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=725; t=1211484219; x=1212348219;
	c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=vvinokou@cisco.com;
	z=From:=20=22Vitali=20Vinokour=20(vvinokou)=22=20<vvinokou@c
	isco.com> |Subject:=20Adjacency=20timer |Sender:=20
	|To:=20<ancp@ietf.org>;
	bh=mrHeGCtvkr+Y0W21TkBo8axP2xba6WPgDRoXjTe5/pU=;
	b=k54MYrWxOLnEh4ccdpOtWils2WA9q8+v6JQKDQk6NBi3aw+eKp5iBahNJu
	9NCjUFSS5dU5OOfaJGlH1la7FGu6pDIbS1ko/1e5NnTP8l+ryn5/1RZjkxL5
	2z3SimKZF0;
Authentication-Results: rtp-dkim-1; header.From=vvinokou@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
Subject: [ANCP] Adjacency timer
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org

Hello,

GSMP rfc specifies that "The Timer field is used to inform the receiver
of the timer value used in the adjacency protocol of the sender.  The
timer specifies the nominal time between periodic adjacency protocol
messages.  It is a constant for the duration of a GSMP session."

However, Timer field is present in all adjacency protocol messages. Is
the receiver expected to cache the remote timer value from the very
first SYN and ignore Timer field in all subsequent messages? Or is the
expected behavior to match the Timer field in each message to the
initial value and consider invalid all messages whith mismatching
values?  Neither GSMP rfc nor ANCP draft specify the behavior.

Thanks,
Vitali 
_______________________________________________
ANCP mailing list
ANCP@ietf.org
https://www.ietf.org/mailman/listinfo/ancp


From ancp-bounces@ietf.org  Fri May 30 00:07:26 2008
Return-Path: <ancp-bounces@ietf.org>
X-Original-To: ancp-archive@optimus.ietf.org
Delivered-To: ietfarch-ancp-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id C124B3A6844;
	Fri, 30 May 2008 00:07:26 -0700 (PDT)
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 CC6003A6B52
	for <ancp@core3.amsl.com>; Fri, 30 May 2008 00:07:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.184
X-Spam-Level: 
X-Spam-Status: No, score=-4.184 tagged_above=-999 required=5
	tests=[BAYES_40=-0.185, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 LvgaiZlVIq7f for <ancp@core3.amsl.com>;
	Fri, 30 May 2008 00:07:24 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by core3.amsl.com (Postfix) with ESMTP id 6DA203A67DA
	for <ancp@ietf.org>; Fri, 30 May 2008 00:07:23 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,565,1204498800"; d="scan'208,217";a="10293411"
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 30 May 2008 09:07:21 +0200
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m4U77LoA022890
	for <ancp@ietf.org>; Fri, 30 May 2008 09:07:21 +0200
Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com
	[144.254.231.71])
	by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m4U77Lfc003812
	for <ancp@ietf.org>; Fri, 30 May 2008 07:07:21 GMT
Received: from xmb-ams-33b.cisco.com ([144.254.231.86]) by
	xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 30 May 2008 09:07:21 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 30 May 2008 09:07:17 +0200
Message-ID: <D9872168DBD43A41BD71FFC4713274D4052062ED@xmb-ams-33b.emea.cisco.com>
In-Reply-To: <D9872168DBD43A41BD71FFC4713274D404F5DDC9@xmb-ams-33b.emea.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [ANCP] ANCP message length field
Thread-Index: AcikfcgluibF+DjWTfupYAEgs2PQXQAFCpLwB0Ul7CA=
References: <D9872168DBD43A41BD71FFC4713274D404F5DC52@xmb-ams-33b.emea.cisco.com>
	<D9872168DBD43A41BD71FFC4713274D404F5DDC9@xmb-ams-33b.emea.cisco.com>
From: "Wojciech Dec (wdec)" <wdec@cisco.com>
To: <ancp@ietf.org>
X-OriginalArrivalTime: 30 May 2008 07:07:21.0378 (UTC)
	FILETIME=[CDE10820:01C8C223]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=14928; t=1212131241;
	x=1212995241; c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=wdec@cisco.com;
	z=From:=20=22Wojciech=20Dec=20(wdec)=22=20<wdec@cisco.com>
	|Subject:=20RE=3A=20[ANCP]=20ANCP=20message=20length=20fiel d
	|Sender:=20; bh=6LoAnTN+DzBKyrwkKpvbMp6Hlr8s+Xfffi8pIiC/R+Q=;
	b=fZOhW8sLUrm7aBtVmo8hMtjYIi8NgFG5ICxbYpkcRGUazVwRXX1cs6H/r+
	ZWlwO9ktTbaReprGC1saB2t5N07bHnjG7+XglThnKEgMiY717QgxjhCLOggR
	ClUpO1pqn0;
Authentication-Results: ams-dkim-1; header.From=wdec@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
Subject: Re: [ANCP] ANCP message length field
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/pipermail/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>
Content-Type: multipart/mixed; boundary="===============1673412189=="
Sender: ancp-bounces@ietf.org
Errors-To: ancp-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1673412189==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8C223.CDBC72DD"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8C223.CDBC72DD
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Folks,
=20
any comments, or preferences regarding the proposals? Since one of the
two identical Length fields is redundant, we have some options on
dealing with them...=20
=20
-Woj.


________________________________

	From: ancp-bounces@ietf.org [mailto:ancp-bounces@ietf.org] On
Behalf Of Wojciech Dec (wdec)
	Sent: 22 April 2008 18:09
	To: ancp@ietf.org
	Subject: Re: [ANCP] ANCP message length field
=09
=09
	Adding one note regarding the options for carrying PDUs
exceeding 64kb. Using other GSMP derived notions in proposal options 2a
and 2b it would be possible to set a "result" field flag to indicate the
continuation of a fregmented PDU, with the transaction identifier
allowing the possibility to stitch back together such a message. An
implementation would however have to pay close attention to this flag,
and the fact that overall legth of the message would be the sum of two
(or more) length fields.


________________________________

		From: ancp-bounces@ietf.org
[mailto:ancp-bounces@ietf.org] On Behalf Of Wojciech Dec (wdec)
		Sent: 22 April 2008 15:36
		To: ancp@ietf.org
		Subject: [ANCP] ANCP message length field
	=09
	=09

		Hi Folks,=20

		As part of our GSMP legacy we've inherited some base
protocol header fields that, for lack of a better word, are largely
useless for ANCP. An example of such a field are the dual message Length
field deriving from rfc3292 and rfc3293, both of which in ANCP carry the
same value (it's not at all clear why rfc3293 needed such a field, but
that's a different story). This is shown in more detail below in the
form of an ANCP header:


		      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=20
=09
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=20
		     |        Type (0x88-0C)         |           Length
|=20
=09
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=20
		     | Vers  |  Sub  |MessageType    | Result|
Code           |=20
=09
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=20
		     | Partition ID  |            Transaction Identifier
|=20
=09
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=20
		     |I|      SubMessage Number      |           Length
|=20
=09
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=20

		RFC 3293 defines the first "Length" field to be:
This 2-byte unsigned integer indicates the total length of the=20
		      GSMP message only.  It does not include the 4-byte
TLV header.=20


		RFC 3292 defines the second "Length" field to be: Length
of the GSMP message including its header fields and=20
		         defined GSMP message body.  The length of
additional data=20
		         appended to the end of the standard message
SHOULD be included=20
		         in the Length field.=20

		It's thus quite clear that the two fields, in ANCP's
case, carry the same value and it appears reasonable to think of
possible changes:.

		Proposal 1.=20
		The "additional data" possibility is to be dropped.
There appears to be no reason to transmit non ANCP data in ANCP.=20

		Proposal 2 - Option a.=20
		Re-define the Sub-message Number and Length fields to
convey really a Sub-message Number and Sub-Message Length, and allow
multiple commands to be bundled under the same transaction header, which
appears interesting in the perspective of multicast control, and line
configuration use-cases. Backwards compatibility with existing
implementations could be maintained since currently all ANCP's
applications set the I flag to "0". Implementations supporting this
change, would most likely be required to send the so-far commonly
implemented Port-up/down and OAM "legacy" messages with the I flag set
to "1".

		Proposal 2 Option b.=20
		Instead of using the Sub-message number and 2nd Length
fields, we define these to be reserved fields of no use in ANCP.=20

		Proposal 2 Option c.=20
		Define the 1st Length field to be reserved fields of no
use in ANCP, using instead only the Sub Message and Length fields to
stitch together ANCP messages that go over 64kb boundary.

		Proposal 2 Option d=20
		Continue using both fields as today, but refine the
Sub-message and Length field to allow for messages over 64kb.=20

		I solicit the WG's feedback regarding these proposed
changes.=20

		Regards,=20
		Woj.=20


------_=_NextPart_001_01C8C223.CDBC72DD
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>ANCP message length field</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3314" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D917401016-29052008><FONT =
face=3DArial=20
size=3D2>Hi Folks,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D917401016-29052008><FONT =
face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D917401016-29052008><FONT =
face=3DArial=20
size=3D2>any comments, or preferences regarding the proposals? Since one =
of the=20
two&nbsp;identical Length fields is redundant, we have some options on =
dealing=20
with them... </FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN =
class=3D917401016-29052008></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN =
class=3D917401016-29052008></SPAN><SPAN=20
class=3D917401016-29052008><FONT face=3DArial =
size=3D2>-Woj.</FONT></SPAN></DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> ancp-bounces@ietf.org=20
  [mailto:ancp-bounces@ietf.org] <B>On Behalf Of </B>Wojciech Dec=20
  (wdec)<BR><B>Sent:</B> 22 April 2008 18:09<BR><B>To:</B>=20
  ancp@ietf.org<BR><B>Subject:</B> Re: [ANCP] ANCP message length=20
  field<BR></FONT><BR></DIV>
  <DIV></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D487120016-22042008><FONT =
face=3DArial=20
  size=3D2>Adding one note regarding&nbsp;the options for carrying PDUs =
exceeding=20
  64kb. Using other&nbsp;GSMP derived notions in proposal options 2a and =
2b it=20
  would be possible to&nbsp;set a "result" field flag to indicate the=20
  continuation of a fregmented PDU, with the transaction identifier =
allowing the=20
  possibility to stitch back together such a message. An implementation =
would=20
  however have to pay close attention to this flag, and the fact that =
overall=20
  legth of the message would be the sum of two (or more) length=20
  fields.</FONT></SPAN></DIV><BR>
  <BLOCKQUOTE dir=3Dltr=20
  style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px =
solid; MARGIN-RIGHT: 0px">
    <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft>
    <HR tabIndex=3D-1>
    <FONT face=3DTahoma size=3D2><B>From:</B> ancp-bounces@ietf.org=20
    [mailto:ancp-bounces@ietf.org] <B>On Behalf Of </B>Wojciech Dec=20
    (wdec)<BR><B>Sent:</B> 22 April 2008 15:36<BR><B>To:</B>=20
    ancp@ietf.org<BR><B>Subject:</B> [ANCP] ANCP message length=20
    field<BR></FONT><BR></DIV>
    <DIV></DIV><!-- Converted from text/rtf format -->
    <P><SPAN lang=3Den-gb><FONT face=3DArial size=3D2>Hi =
Folks,</FONT></SPAN> </P>
    <P><SPAN lang=3Den-gb><FONT face=3DArial size=3D2>As part of our =
GSMP legacy we've=20
    inherited some base protocol header fields that, for lack of a =
better word,=20
    are largely useless for ANCP. An example of such a field are the =
dual=20
    message Length field deriving from rfc3292 and rfc3293, both of =
which in=20
    ANCP carry the same value (it's not at all clear why rfc3293 needed =
such a=20
    field, but that's a different story). This is shown in more detail =
below in=20
    the form of an ANCP header:</FONT></SPAN></P><BR>
    <P><SPAN lang=3Den-gb><FONT face=3D"Courier New"=20
    size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0 1 2 3 4 5 6 7 8 9 0 1 2 3 =
4 5 6 7 8=20
    9 0 1 2 3 4 5 6 7 8 9 0 1</FONT></SPAN> <BR><SPAN lang=3Den-gb><FONT =

    face=3D"Courier New" size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+</FONT><=
/SPAN>=20
    <BR><SPAN lang=3Den-gb><FONT face=3D"Courier New"=20
    size=3D2>&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Type (0x88-0C)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;=20
    |</FONT></SPAN> <BR><SPAN lang=3Den-gb><FONT face=3D"Courier New"=20
    size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;=20
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=20
    </FONT></SPAN><BR><SPAN lang=3Den-gb><FONT face=3D"Courier New"=20
    size=3D2>&nbsp;&nbsp;&nbsp;&nbsp; | Vers&nbsp; |&nbsp; Sub&nbsp;=20
    |MessageType&nbsp;&nbsp;&nbsp; |=20
    Result|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Code&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |=20
    </FONT></SPAN><BR><SPAN lang=3Den-gb><FONT face=3D"Courier New"=20
    size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;=20
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=20
    </FONT></SPAN><BR><SPAN lang=3Den-gb><FONT face=3D"Courier New"=20
    size=3D2>&nbsp;&nbsp;&nbsp;&nbsp; | Partition ID&nbsp;=20
    |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    Transaction=20
    =
Identifier&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;=20
    | </FONT></SPAN><BR><SPAN lang=3Den-gb><FONT face=3D"Courier New"=20
    size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;=20
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=20
    </FONT></SPAN><BR><SPAN lang=3Den-gb><FONT face=3D"Courier New"=20
    size=3D2>&nbsp;&nbsp;&nbsp;&nbsp; |I|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
SubMessage=20
    Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    =
Length&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;=20
    | </FONT></SPAN><BR><SPAN lang=3Den-gb><FONT face=3D"Courier New"=20
    size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;=20
    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+=20
    </FONT></SPAN></P>
    <P><SPAN lang=3Den-gb><FONT face=3DArial size=3D2>RFC 3293 defines =
the first=20
    "Length" field to be:</FONT></SPAN><SPAN lang=3Den-us> <FONT=20
    face=3D"Courier New" size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; This =
2-byte=20
    unsigned integer indicates the total length of the</FONT></SPAN> =
<BR><SPAN=20
    lang=3Den-us><FONT face=3D"Courier New" =
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
    GSMP message only.&nbsp; It does not include the 4-byte TLV=20
    header.</FONT></SPAN> </P><BR>
    <P><SPAN lang=3Den-us><FONT face=3DArial size=3D2>RFC 3292 defines =
the second=20
    "Length" field to be: Length of the GSMP message including its =
header fields=20
    and</FONT></SPAN> <BR><SPAN lang=3Den-us><FONT face=3DArial=20
    size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; defined =
GSMP message=20
    body.&nbsp; The length of additional data</FONT></SPAN> <BR><SPAN=20
    lang=3Den-us><FONT face=3DArial=20
    size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; appended =
to the end=20
    of the standard message SHOULD be included</FONT></SPAN> <BR><SPAN=20
    lang=3Den-us><FONT face=3DArial=20
    size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; in the =
Length=20
    field.</FONT></SPAN> </P>
    <P><SPAN lang=3Den-us><FONT face=3DArial size=3D2>It's thus quite =
clear that the=20
    two fields, in ANCP's case, carry the same value and it appears =
reasonable=20
    to think of possible changes:.</FONT></SPAN></P>
    <P><SPAN lang=3Den-us><FONT face=3DArial size=3D2>Proposal 1.=20
    </FONT></SPAN><BR><SPAN lang=3Den-us><FONT face=3DArial size=3D2>The =
"additional=20
    data" possibility is to be dropped. There appears to be no reason to =

    transmit non ANCP data in ANCP.</FONT></SPAN> </P>
    <P><SPAN lang=3Den-us><FONT face=3DArial size=3D2>Proposal 2 - =
Option=20
    a.</FONT></SPAN> <BR><SPAN lang=3Den-us><FONT face=3DArial =
size=3D2>Re-define the=20
    Sub-message Number and Length fields to convey really a Sub-message =
Number=20
    and Sub-Message Length, and allow multiple commands to be bundled =
under the=20
    same transaction header, which appears interesting in the =
perspective of=20
    multicast control, and line configuration use-cases. Backwards =
compatibility=20
    with existing implementations could be maintained since currently =
all ANCP's=20
    applications set the I flag to "0". Implementations supporting this =
change,=20
    would most likely be required to send the so-far commonly =
implemented=20
    Port-up/down and OAM "legacy" messages with the I flag set to=20
    "1".</FONT></SPAN></P>
    <P><SPAN lang=3Den-us><FONT face=3DArial size=3D2>Proposal 2 Option=20
    b.</FONT></SPAN> <BR><SPAN lang=3Den-us><FONT face=3DArial =
size=3D2>Instead of=20
    using the Sub-message number and 2nd Length fields, we define these =
to be=20
    reserved fields of no use in ANCP.</FONT></SPAN> </P>
    <P><SPAN lang=3Den-us><FONT face=3DArial size=3D2>Proposal 2 Option=20
    c.</FONT></SPAN> <BR><SPAN lang=3Den-us><FONT face=3DArial =
size=3D2>Define the 1st=20
    Length field to be reserved fields of no use in ANCP, using instead =
only the=20
    Sub Message and Length fields to stitch together ANCP messages that =
go over=20
    64kb boundary.</FONT></SPAN></P>
    <P><SPAN lang=3Den-us><FONT face=3DArial size=3D2>Proposal 2 Option=20
    d</FONT></SPAN> <BR><SPAN lang=3Den-us><FONT face=3DArial =
size=3D2>Continue using=20
    both fields as today, but refine the Sub-message and Length field to =
allow=20
    for messages over 64kb.</FONT></SPAN> </P>
    <P><SPAN lang=3Den-us><FONT face=3DArial size=3D2>I solicit the WG's =
feedback=20
    regarding these proposed changes.</FONT></SPAN> </P>
    <P><SPAN lang=3Den-us><FONT face=3DArial =
size=3D2>Regards,</FONT></SPAN> <BR><SPAN=20
    lang=3Den-us><FONT face=3DArial size=3D2>Woj.</FONT></SPAN>=20
</P></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C8C223.CDBC72DD--

--===============1673412189==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1673412189==--


