Re: [CCAMP] Next steps on overlay

Daniele Ceccarelli <daniele.ceccarelli@ericsson.com> Mon, 28 January 2013 16:29 UTC

Return-Path: <daniele.ceccarelli@ericsson.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 63C7921F87D3 for <ccamp@ietfa.amsl.com>; Mon, 28 Jan 2013 08:29:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.198
X-Spam-Level:
X-Spam-Status: No, score=-5.198 tagged_above=-999 required=5 tests=[AWL=0.450, BAYES_00=-2.599, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4]
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 I8Dlh3t9mC4c for <ccamp@ietfa.amsl.com>; Mon, 28 Jan 2013 08:29:42 -0800 (PST)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id A742221F87C4 for <ccamp@ietf.org>; Mon, 28 Jan 2013 08:29:41 -0800 (PST)
X-AuditID: c1b4fb25-b7f366d000004d10-7f-5106a7743900
Received: from ESESSHC022.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id 03.8F.19728.477A6015; Mon, 28 Jan 2013 17:29:40 +0100 (CET)
Received: from ESESSMB301.ericsson.se ([169.254.1.40]) by ESESSHC022.ericsson.se ([153.88.183.84]) with mapi id 14.02.0318.004; Mon, 28 Jan 2013 17:29:40 +0100
From: Daniele Ceccarelli <daniele.ceccarelli@ericsson.com>
To: "BRUNGARD, DEBORAH A" <db3546@att.com>, "ccamp@ietf.org" <ccamp@ietf.org>
Thread-Topic: Next steps on overlay
Thread-Index: Ac36bemQNHMdz+KeTBOfZZLP6sIh3gC+XFww
Date: Mon, 28 Jan 2013 16:29:39 +0000
Message-ID: <4A1562797D64E44993C5CBF38CF1BE48074083@ESESSMB301.ericsson.se>
References: <F64C10EAA68C8044B33656FA214632C8258164@MISOUT7MSGUSR9O.ITServices.sbc.com>
In-Reply-To: <F64C10EAA68C8044B33656FA214632C8258164@MISOUT7MSGUSR9O.ITServices.sbc.com>
Accept-Language: it-IT, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.16]
Content-Type: multipart/alternative; boundary="_000_4A1562797D64E44993C5CBF38CF1BE48074083ESESSMB301ericsso_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrGLMWRmVeSWpSXmKPExsUyM+JvrW7JcrZAg42tphZP5txgsbjc1c3u wOTxsn8Oo8eSJT+ZApiiuGxSUnMyy1KL9O0SuDIW3PrIXPAmuOL/0onMDYyLPboYOTkkBEwk vqxcww5hi0lcuLeerYuRi0NI4BCjxMv9J5kgnMWMEpO/TmPtYuTgYBOwknhyyAfEFBHwlZg6 nQnEFBZQkjgxMxdkjIiAssSPrUuZIWwjiaYzb8HGswioSvxpvscKYvMKeEss39DCAmILCYRL 7H34AayeUyBC4sCndrAaRgFZiQm7FzGC2MwC4hK3nsxngjhTQGLJnvPMELaoxMvH/1ghbEWJ nWfbmSHq8yU2PrrHCLFLUOLkzCcsExhFZiEZNQtJ2SwkZRBxPYkbU6ewQdjaEssWvmaGsHUl Zvw7xIIsvoCRfRUje25iZk56udEmRmDcHNzyW3UH451zIocYpTlYlMR5w10vBAgJpCeWpGan phakFsUXleakFh9iZOLglGpgXDp9caQ9R01cvh2/f7oYu36mzdQ5R46cYYqMS2IpUDoeIHqx dIZdYc7ch6uOdBg+/bst3E9HINpJKVxkrcnbmR3f3ql43NrwK6yNZ5la84uZDNcPbTcJE4uS 5ex4HrLPu/2Nsm+QZHKQinzrpqVmq6NWvDi/Mb3r4SerecE/vy1IbticYsmjxFKckWioxVxU nAgAv1t242kCAAA=
Subject: Re: [CCAMP] Next steps on overlay
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: Mon, 28 Jan 2013 16:29:44 -0000

Deborah, all,

agree that it's time to sum up.

As agreed in Atlanta draft-many-ccamp-gmpls-overlay-model<http://tools.ietf.org/id/draft-many-ccamp-gmpls-overlay-model-01.txt> will be updated in the next days so to reflect the discussions of the last months on the list and will try to reflect all the topics where there is no consensus and, if available, list all the proposed alternatives.

Basically:

- The overall doc will reflect my latest summary (v2) including the following comments basically from Lou and Igor.
- The terminology part will be based at the time being on VPNs (but open to be modified if needed)
- Use cases: will try to cover the ones in the E-NNI and L1VPN drafts. If more of them are needed please contact me.
- Description of the different advertisement models and service models. Basically we are defining a general topology service model so that existing VPN service models are particular cases of it.
- Relationship with MLN/MRN: the overlay interfaces does not necessarily need to be placed on a link between different technology domains (e.g. IP and WSON) but could be placed also withing the same NE between two layer of the same technology (e.g. an OTN deployment where the ODU3 layer is managed as a provided network providing connectivity between ODU2s which form the client network).

In addition, wrt latest discussion on Additional Overlay Protocol Extensions i think that's meat for the second document on the advertisement, where for each of them we need to say which info is needed AND NOT HOW IT ENCODED OR TRANSPORTED. This final part will be addressed in the third document dedicated to protocol extensions (this was the agreement in Atlanta and i think there is no reason to move from that).

It is definitely too early to move to doc #3 but we could start working on #2. Most of its content, wrt the Virtual Links advertisement model (former E-NNI) has already been widely explained by Igor and Lou, which seem to disagree on HOW to carry the info but not on WHICH of them are needed.

BR
Daniele


________________________________
From: ccamp-bounces@ietf.org [mailto:ccamp-bounces@ietf.org] On Behalf Of BRUNGARD, DEBORAH A
Sent: giovedì 24 gennaio 2013 21.04
To: ccamp@ietf.org
Subject: [CCAMP] Next steps on overlay

CCAMP,

There's been quite a bit of discussion on the list, we'd like to see progress on this topic. Perhaps we've reached the point where it's time to update/author drafts to reflect current positions. This can either be done in one document or in multiple (authors' choice).

We also note that multiple viewpoints on how overlays may be deployed/operated have been discussed. We suggest that documenting these use cases, including data plane and control plane relationships/boundaries, would be helpful.

Thanks,
Deborah and Lou
CCAMP Chairs