Re: [CCAMP] Poll on ODUFlex-related encoding

Lou Berger <lberger@labn.net> Tue, 05 February 2013 22:39 UTC

Return-Path: <lberger@labn.net>
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 EAEA121F8915 for <ccamp@ietfa.amsl.com>; Tue, 5 Feb 2013 14:39:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.701
X-Spam-Level:
X-Spam-Status: No, score=-101.701 tagged_above=-999 required=5 tests=[AWL=0.898, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OR87ApObjSHq for <ccamp@ietfa.amsl.com>; Tue, 5 Feb 2013 14:39:10 -0800 (PST)
Received: from oproxy11-pub.bluehost.com (oproxy11-pub.bluehost.com [173.254.64.10]) by ietfa.amsl.com (Postfix) with SMTP id 0CDDF21F890D for <ccamp@ietf.org>; Tue, 5 Feb 2013 14:39:09 -0800 (PST)
Received: (qmail 24512 invoked by uid 0); 5 Feb 2013 22:38:42 -0000
Received: from unknown (HELO box313.bluehost.com) (69.89.31.113) by oproxy11.bluehost.com with SMTP; 5 Feb 2013 22:38:42 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References:Subject:CC:To:MIME-Version:From:Date:Message-ID; bh=J3tIb3jnP2CmLyEnPJR3szIm3Qz9VFjEe94nr6tkxa8=; b=af0siqLDo7Tj4icS1LrMMU/r6Vg93nZcrTvXeG5SrWMv9vdWoNxShovzR+m22nRhNn4SCoA/RqDfHVQjPj/I67ATy2rB2g0plx1M7HRII4c78gBd9hMNToChUWWxIaG5;
Received: from box313.bluehost.com ([69.89.31.113]:46095 helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.80) (envelope-from <lberger@labn.net>) id 1U2rA2-0000pm-IC; Tue, 05 Feb 2013 15:38:42 -0700
Message-ID: <511189F0.8030709@labn.net>
Date: Tue, 05 Feb 2013 17:38:40 -0500
From: Lou Berger <lberger@labn.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: John E Drake <jdrake@juniper.net>
References: <F82A4B6D50F9464B8EBA55651F541CF83585B3CE@SZXEML552-MBX.china.huawei.com> <B6585D85A128FD47857D0FD58D8120D3B3CCD0@xmb-rcd-x14.cisco.com> <0182DEA5604B3A44A2EE61F3EE3ED69E145055F2@BL2PRD0510MB349.namprd05.prod.outlook.com>
In-Reply-To: <0182DEA5604B3A44A2EE61F3EE3ED69E145055F2@BL2PRD0510MB349.namprd05.prod.outlook.com>
X-Enigmail-Version: 1.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.net}
Cc: CCAMP <ccamp@ietf.org>, "draft-ietf-ccamp-gmpls-ospf-g709v3@tools.ietf.org" <draft-ietf-ccamp-gmpls-ospf-g709v3@tools.ietf.org>, "draft-ietf-ccamp-gmpls-signaling-g709v3@tools.ietf.org" <draft-ietf-ccamp-gmpls-signaling-g709v3@tools.ietf.org>
Subject: Re: [CCAMP] Poll on ODUFlex-related encoding
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: Tue, 05 Feb 2013 22:39:11 -0000

John,

See question in-line below.

On 2/5/2013 2:19 PM, John E Drake wrote:
> Snipped, comment inline
> 
> Irrespectively Yours,
> 
> John
> 
>>>    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
>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>  |  Signal Type  |       N       |        Reserved       |
>>>  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>  |              NVC           |      Multiplier (MT)     |
>>>  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>  |                      Bit_Rate                       |
>>>  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>
>> I just wonder are we not better off keeping Tolerance field in
>> signaling and adding a statement in v7 that this field is hardcoded to
>> 100ppm.
>>
>> This has advantage of interworking with earlier draft implementations
>> and is also flexible for various (future/ unknown) client signal types.
>> I.e., we use the same encoding as defined thus far in the document
>> (copying from
>> v6):
>>
>>       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
>>      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>      |  Signal Type  |       N       |           Tolerance           |
>>      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>      |              NVC              |        Multiplier (MT)        |
>>      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>      |                            Bit_Rate                           |
>>      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>
>> And state that Tolerance MUST be set to 100 ppm.
> 
> 
> JD: This is a very good idea.  

Great.  Thanks for being clear on which option you support.

> 'Per [G.874.1/2011] (or whatever is
> the correct reference) Tolerance MUST be set to 100 ppm.'
> 

Is this correct (always 100ppm)?  Fatai/Sergio referred to table 7-2 in
G709 which has 20ppm for most signal types and 100ppm for others.  And
it seems there is some text that got dropped in the latest rev of
G.874.1 (from and earlier amendment).

In your role as ITU-T SG15 liaison manager, can you either figure out
what the right text & reference should be or propose a liaison that we
can send asking the ITU-T for whatever information we need to close this
issue/document?

Thanks,
Lou

>  
>>
>>
>> Thanks
>>
>> Regards...Zafar
>>
>>> <snip>
>>
>> _______________________________________________
>> CCAMP mailing list
>> CCAMP@ietf.org
>> https://www.ietf.org/mailman/listinfo/ccamp
> 
> 
> 
> 
> 
>