Re: [CCAMP] WG draft-ietf-ccamp-rwa-wson-encode-13 - Suggested modification on processing capabilities encodings
"PELOSO, PIERRE (PIERRE)" <pierre.peloso@alcatel-lucent.com> Wed, 28 March 2012 06:39 UTC
Return-Path: <pierre.peloso@alcatel-lucent.com>
X-Original-To: ccamp@ietfa.amsl.com
Delivered-To: ccamp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1D1C21F8793 for <ccamp@ietfa.amsl.com>; Tue, 27 Mar 2012 23:39:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.797
X-Spam-Level:
X-Spam-Status: No, score=-9.797 tagged_above=-999 required=5 tests=[AWL=0.452, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4densfZEWSpn for <ccamp@ietfa.amsl.com>; Tue, 27 Mar 2012 23:39:10 -0700 (PDT)
Received: from smail6.alcatel.fr (smail6.alcatel.fr [64.208.49.42]) by ietfa.amsl.com (Postfix) with ESMTP id CB62421F8792 for <ccamp@ietf.org>; Tue, 27 Mar 2012 23:39:09 -0700 (PDT)
Received: from FRMRSSXCHHUB03.dc-m.alcatel-lucent.com (FRMRSSXCHHUB03.dc-m.alcatel-lucent.com [135.120.45.63]) by smail6.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id q2S6d4wn026398 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 28 Mar 2012 08:39:06 +0200
Received: from FRMRSSXCHMBSA1.dc-m.alcatel-lucent.com ([135.120.45.34]) by FRMRSSXCHHUB03.dc-m.alcatel-lucent.com ([135.120.45.63]) with mapi; Wed, 28 Mar 2012 08:39:04 +0200
From: "PELOSO, PIERRE (PIERRE)" <pierre.peloso@alcatel-lucent.com>
To: Lou Berger <lberger@labn.net>
Date: Wed, 28 Mar 2012 08:39:02 +0200
Thread-Topic: [CCAMP] WG draft-ietf-ccamp-rwa-wson-encode-13 - Suggested modification on processing capabilities encodings
Thread-Index: Ac0MZFVTlv3Iapq9TAy4FIAQhA2HxQAR5wPg
Message-ID: <CCBFBB7025DF984494DEC3285C05815212FA9F570E@FRMRSSXCHMBSA1.dc-m.alcatel-lucent.com>
References: <CCBFBB7025DF984494DEC3285C058152129C035AB0@FRMRSSXCHMBSA1.dc-m.alcatel-lucent.com> <4F723744.2040403@labn.net>
In-Reply-To: <4F723744.2040403@labn.net>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: fr-FR, en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.69 on 155.132.188.84
Cc: "ccamp@ietf.org" <ccamp@ietf.org>
Subject: Re: [CCAMP] WG draft-ietf-ccamp-rwa-wson-encode-13 - Suggested modification on processing capabilities encodings
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Mar 2012 06:39:11 -0000
Lou, I am happy helping the readability of the suggested changes. See below Regards, Pierre Section 5.6: Processing Capabilites sub-sub-TLV UNCHANGED: This sub-sub-TLV contains a list of resource block processing capabilities. Type := Processing Capabilities List Value := A list of Processing Capabilities Fields OLD: The processing capability list sub-TLV is a list of WSON network element (NE) that can perform signal processing functions including: 1. Number of Resources within the block 2. Regeneration capability 3. Fault and performance monitoring 4. Vendor Specific capability NEW: The processing capability list sub-sub-TLV is a list of capabilites that can be achieved through the refered resources: 1. Regeneration capability 2. Fault and performance monitoring 3. Vendor Specific capability UNCHANGED: Note that the code points for Fault and performance monitoring and vendor specific capability are subject to further study. 5.6.1. Processing Capabilities Field The processing capability field is then given by: 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Processing Cap ID | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Possible additional capability parameters depending upon | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ : the processing ID : +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ OLD: When the processing Cap ID is "number of resources" the format is simply: 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Processing Cap ID | Length = 8 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Number of resources per block | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ NEW: [erased old content] UNCHANGED: When the processing Cap ID is "regeneration capability", the following additional capability parameters are provided in the sub- TLV: 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | T | C | Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Where T bit indicates the type of regenerator: T=0: Reserved T=1: 1R Regenerator T=2: 2R Regenerator T=3: 3R Regenerator Where C bit indicates the capability of regenerator: C=0: Reserved C=1: Fixed Regeneration Point C=2: Selective Regeneration Point Note that when the capability of regenerator is indicated to be Selective Regeneration Pools, regeneration pool properties such as ingress and egress restrictions and availability need to be specified. This encoding is to be determined in the later revision. -----Message d'origine----- De : Lou Berger [mailto:lberger@labn.net] Envoyé : mardi 27 mars 2012 23:55 À : PELOSO, PIERRE (PIERRE) Cc : ccamp@ietf.org Objet : Re: [CCAMP] WG draft-ietf-ccamp-rwa-wson-encode-13 - Suggested modification on processing capabilities encodings Pierre, I think all would find it helpful if you use the RFC editor's standard approach to proposing text changes, i.e.: Please send the changes in this format: Section # (or indicate Global) OLD: old text NEW: new text Much thanks, Lou On 3/27/2012 9:29 PM, PELOSO, PIERRE (PIERRE) wrote: > Hi Young and Greg, > > Please find a proposed modification to paragraph 5.6 of the draft that > simplifies the Resource Block Information TLV. > This modification consists in removing the number of resources > infromation from the Resource Block Information. > I believe (and I'm not the only one) that it is is simpler to part the > description of resources from the number of devices that comply to the > resource description (namely here the resource block info sub-TLV). > This gives more simplicity and avoids all the possible interpretations > provided in my email related both to the info and encoding drafts. > > regards, > > Pierre > > > 5.6 Processing Capabilites sub-sub-TLV > > This sub-sub-TLV contains a list of resource block processing > capabilities. > > Type := Processing Capabilities List > > Value := A list of Processing Capabilities Fields > > The processing capability list sub-sub-TLV is a list of capabilites > that can be achieved through the targetted resource: > > 1. Regeneration capability > > 2. Fault and performance monitoring > > 3. Vendor Specific capability > > Note that the code points for Fault and performance monitoring and > vendor specific capability are subject to further study. > > 5.6.1. Processing Capabilities Field > > The processing capability field is then given by: > > 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 > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | Processing Cap ID | Length | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | Possible additional capability parameters depending upon | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > : the processing ID : > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > > > When the processing Cap ID is "regeneration capability", the > following additional capability parameters are provided in the sub- > TLV: > > 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 > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | Regen Cap | Length = 8 | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | T | C | Reserved | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > > > Where T bit indicates the type of regenerator: > > T=0: Reserved > > T=1: 1R Regenerator > > T=2: 2R Regenerator > > T=3: 3R Regenerator > > Where C bit indicates the capability of regenerator: > > C=0: Reserved > > C=1: Fixed Regeneration Point > > C=2: Selective Regeneration Point > > Note that when the capability of regenerator is indicated to be > Selective Regeneration Pools, regeneration pool properties such as > ingress and egress restrictions and availability need to be > specified. This encoding is to be determined in the later revision. > > > > _______________________________________________ > CCAMP mailing list > CCAMP@ietf.org > https://www.ietf.org/mailman/listinfo/ccamp
- [CCAMP] WG draft-ietf-ccamp-rwa-wson-encode-13 - … PELOSO, PIERRE (PIERRE)
- Re: [CCAMP] WG draft-ietf-ccamp-rwa-wson-encode-1… Lou Berger
- Re: [CCAMP] WG draft-ietf-ccamp-rwa-wson-encode-1… PELOSO, PIERRE (PIERRE)
- Re: [CCAMP] WG draft-ietf-ccamp-rwa-wson-encode-1… Leeyoung