Re: [CCAMP] 答复: R: OSPF OTN considerations post IETF 82 (Issue 1/2)

Lou Berger <lberger@labn.net> Tue, 20 December 2011 23:24 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 5BC9D11E808A for <ccamp@ietfa.amsl.com>; Tue, 20 Dec 2011 15:24:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -94.49
X-Spam-Level:
X-Spam-Status: No, score=-94.49 tagged_above=-999 required=5 tests=[AWL=0.480, BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, IP_NOT_FRIENDLY=0.334, MIME_8BIT_HEADER=0.3, MIME_CHARSET_FARAWAY=2.45, SARE_SUB_ENC_GB2312=1.345, USER_IN_WHITELIST=-100]
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 wlvDrPXWXQdB for <ccamp@ietfa.amsl.com>; Tue, 20 Dec 2011 15:24:10 -0800 (PST)
Received: from oproxy3-pub.bluehost.com (oproxy3-pub.bluehost.com [69.89.21.8]) by ietfa.amsl.com (Postfix) with SMTP id 95D7011E8089 for <ccamp@ietf.org>; Tue, 20 Dec 2011 15:24:10 -0800 (PST)
Received: (qmail 20917 invoked by uid 0); 20 Dec 2011 23:23:49 -0000
Received: from unknown (HELO box313.bluehost.com) (69.89.31.113) by oproxy3.bluehost.com with SMTP; 20 Dec 2011 23:23:49 -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=Bb4iSBHiKGJb64LKJZGIvYl+M4juCkuSowqer7BrUKU=; b=Gzowb4AY9Ra2XHwhpf9DFsAJqf4n4EHBz5Qk28Vynoo+TdTBHVBMQqYAQb/h3Fs24OauLsjkVSsObF0eZ55YSgthQ+ox8UchVLmK/g3RI0jtPFzAxDqgr2u6aLMYz56D;
Received: from box313.bluehost.com ([69.89.31.113] helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.76) (envelope-from <lberger@labn.net>) id 1Rd92C-00050g-QW; Tue, 20 Dec 2011 16:23:49 -0700
Message-ID: <4EF11904.30708@labn.net>
Date: Tue, 20 Dec 2011 18:23:48 -0500
From: Lou Berger <lberger@labn.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: John E Drake <jdrake@juniper.net>
References: <B5630A95D803744A81C51AD4040A6DAA2293E672A9@ESESSCMS0360.eemea.ericsson.se> <F050945A8D8E9A44A71039532BA344D81918795F@FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com> <F82A4B6D50F9464B8EBA55651F541CF825CB0593@SZXEML520-MBX.china.huawei.com> <4EDE3E19.6010303@orange.com> <F82A4B6D50F9464B8EBA55651F541CF825CC18AB@SZXEML520-MBS.china.huawei.com> <4EF0A18F.4080000@orange.com> <5E893DB832F57341992548CDBB333163A54B517AFD@EMBX01-HQ.jnpr.net> <F050945A8D8E9A44A71039532BA344D819BA8E25@FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com> <5E893DB832F57341992548CDBB333163A54B517B62@EMBX01-HQ.jnpr.net> <5292FFA96EC22A4386067E9DBCC0CD2B010A0998FB37@EX-NAP.tellabs-west.tellabsinc.net> <4EF0B788.7020700@labn.net> <5E893DB832F57341992548CDBB333163A54B517BE2@EMBX01-HQ.jnpr.net> <4EF0C99B.4020505@labn.net> <5E893DB832F57341992548CDBB333163A54B517E4F@EMBX01-HQ.jnpr.net> <4EF0EE83.3060601@labn.net> <5E893DB832F57341992548CDBB333163A54B518072@EMBX01-HQ.jnpr.net>
In-Reply-To: <5E893DB832F57341992548CDBB333163A54B518072@EMBX01-HQ.jnpr.net>
X-Enigmail-Version: 1.0.1
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: 8bit
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>
Subject: Re: [CCAMP] =?gb2312?b?tPC4tDogIFI6ICBPU1BGIE9UTiBjb25zaWRlcmF0aW9u?= =?gb2312?b?cyBwb3N0IElFVEYgODIgKElzc3VlIDEvMik=?=
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, 20 Dec 2011 23:24:11 -0000

John,
	As you probably know, each time we have new technology or a
change/evolution in a technology the folks involved in the technology
come up with a fairly technology-specific solution to their problem.
Part of the WG process has always been looking at the technology
specific extensions and figuring out what, if any, impact the
technlogy-specific extensions should have on the common portion of
GMPLS.  Prior to OTNv3, this can most recently be seen in both the
ethernet and WSON WG work.  In these cases, WG participants triggered
generalization of the proposed mechanisms.  This was even the case for
Ethernet, where I was on the other side as an author and the WG prompted
taking one document and making it 3.  IMO, as both a WG participant and
co-chair (yes, this time I'm making a statement as a Chair!), this
process is consistent, and required, by both the CCAMP's charter and WG
procedural precedent.   It is also exactly what we, the co-chairs, said
in our OTN discussion at IETF-78. (We mentioned defining new common
mechanisms as part of the solution refinement stage.)

In this case the OTN documents are not proposing a new mechanism, but
rather using a technology-specific approach.  Furthermore, in our
discussions you proposed modifying/deprecating documented usage /
meaning of SC Type.  I still see this as fitting within 'defining new
common mechanisms as part of the solution refinement stage.'

As you also may recall, the usage of SC type has come up multiple times
since it was introduced (perhaps by Yakov?).  I think (again as
participant and chair) it would be good to close this issue once and for
all.

See below for specific responses (as a WG participant).

On 12/20/2011 4:37 PM, John E Drake wrote:
> Lou,
> 
> I don't see any inconsistency between the two statements.  Nobody
> uses PSC 1-4 so we don't have to touch it and the SDH/SONET model,
> which we are re-using, is already consistent with base GMPLS - what
> is advertised for an interface is a single switching type, the types
> of client signals it supports, and its available bandwidth.
> 
> How does the existence of this draft, which will have no new
> information, help the chairs gauge rough consensus on this issue in
> the WG, 

It depends on which issue you are talking about.  If talking about the
general issue as discussed above, I hope it will close it for the future.

If talking about my (individual, not chair) proposal of using multiple
SC types for OTNv3, I don't think it immediately does.  What it will do
is provide context for that proposal.  In the interim, I recommend (as a
WG participant, not chair) tabling discussion on my proposal until we
know which way the general issue is resolved.

> especially since rough consensus seems to already exist?
> (I.e., the editors, authors, and contributors of the OTN routing
> draft would seem to represent a substantial portion of the WG.)

Well if the WG used this as the sole measure, consensus could have been
declared in Maastrict.

Lou

PS I've noted where I'm speaking as an individual WG participant and
where I'm expressing opinions as a Co-chair as this message contains both.

> 
> Thanks,
> 
> John 
> 
>> -----Original Message-----
>> From: Lou Berger [mailto:lberger@labn.net]
>> Sent: Tuesday, December 20, 2011 12:22 PM
>> To: John E Drake
>> Cc: Sadler, Jonathan B.; BELOTTI, SERGIO (SERGIO); CCAMP
>> Subject: Re: [CCAMP] 答复: R: OSPF OTN considerations post IETF 82
>> (Issue 1/2)
>>
>>
>> On 12/20/2011 2:02 PM, John E Drake wrote:
>>>>> In an earlier message I asked if you were interested in putting a
>> draft
>>>>> together to document your proposed change to the base GMPLS specs.
>>> [
>>> [JD]  There are no changes to the base GMPLS specs.  We are not
>> changing the base definition of PSC 1-4 and what we are defining is
>> completely consistent with SDH/SONET.
>>>
>>
>> John,
>> 	In an earlier message you said:
>>
>> On 11/30/2011 5:23 PM, John E Drake wrote:
>>> Yes, I think that's fair.
>>>
>>>>> -----Original Message-----
>>>>> From: Lou Berger [mailto:lberger@labn.net]
>>>>> Sent: Wednesday, November 30, 2011 1:51 PM
>>>>> To: John E Drake
>>>>> Cc: Daniele Ceccarelli; CCAMP
>>>>> Subject: Re: [CCAMP] OSPF OTN considerations post IETF 82 (Issue
>> 1/2)
>>>>>
>>>>> So you're basically arguing that SC shouldn't be used to indicate
>>>>> different levels of hierarchy, i.e., usage (b) in my earlier
>> message,
>>>>> and that the definition of PSC-1 -> n was flawed.  Right?
>>>>>
>>>>> Which then reduces the meaning of SC to simply and indicator of
>> label
>>>>> type and ISCD format indicator.
>>>>>
>>>>> Is this your position?
>>>>>
>>
>> Deprecating PSC1-4 and making SC Type just an indicator of label and
>> ISCD format will be covered in the draft. The draft wouldn't say
>> anything specifically about OTN.
>>
>> Lou
>>
>>
>>
>