[Status] Overlay-Underlay correlation use-case discussion for STATUS

"Frank Brockners (fbrockne)" <fbrockne@cisco.com> Mon, 29 July 2013 07:01 UTC

Return-Path: <fbrockne@cisco.com>
X-Original-To: status@ietfa.amsl.com
Delivered-To: status@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 460B021F95BD for <status@ietfa.amsl.com>; Mon, 29 Jul 2013 00:01:46 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ILOF3n-maQV3 for <status@ietfa.amsl.com>; Mon, 29 Jul 2013 00:01:45 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id BDAB621F9E0B for <status@ietf.org>; Mon, 29 Jul 2013 00:01:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=627439; q=dns/txt; s=iport; t=1375081300; x=1376290900; h=from:to:cc:subject:date:message-id:mime-version; bh=mNvDwjCfFdLtsJ4E90NygUFq7nBXawFC35t2MlJBoqk=; b=fZAwxO3RCTYKazQu7vmciEhD4nedsqH2ekjbYGJt5JmRBoUvLExp48IP 2hwNuyVFBq5VO9LcxVs2NQDBzTXYBHyWx04jwHqLw6dVSdiALqYR+26p+ 64W7rSMFS+j751E+PF4cdd25lXN6BURKQjV9qYAd1Plp8PtGBNDaiVq+c 8=;
X-Files: ietf-status_overlay-underlay_28jul2013.pdf : 454497
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApwEABMS9lGtJV2Y/2dsb2JhbADDZnQ
X-IronPort-AV: E=Sophos; i="4.89,767,1367971200"; d="pdf'?scan'208,217"; a="240473879"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-1.cisco.com with ESMTP; 29 Jul 2013 07:01:16 +0000
Received: from xhc-aln-x10.cisco.com (xhc-aln-x10.cisco.com [173.36.12.84]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r6T71Fj3000781 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 29 Jul 2013 07:01:15 GMT
Received: from xmb-aln-x06.cisco.com ([169.254.1.78]) by xhc-aln-x10.cisco.com ([173.36.12.84]) with mapi id 14.02.0318.004; Mon, 29 Jul 2013 02:01:14 -0500
From: "Frank Brockners (fbrockne)" <fbrockne@cisco.com>
To: "status@ietf.org" <status@ietf.org>
Thread-Topic: Overlay-Underlay correlation use-case discussion for STATUS
Thread-Index: Ac6MKUxQVocAY4j7RrW3wol3yGtSsg==
Date: Mon, 29 Jul 2013 07:01:14 +0000
Message-ID: <B3C8C1D36EDE59418C7AC4D5523B208A22EB54BA@xmb-aln-x06.cisco.com>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.61.72.236]
Content-Type: multipart/mixed; boundary="_004_B3C8C1D36EDE59418C7AC4D5523B208A22EB54BAxmbalnx06ciscoc_"
MIME-Version: 1.0
Cc: "Fabio Maino (fmaino)" <fmaino@cisco.com>, "Darrel Lewis (darlewis)" <darlewis@cisco.com>, "Alvaro Retana (aretana)" <aretana@cisco.com>, "Shwetha Bhandari (shwethab)" <shwethab@cisco.com>, "John G.Scudder" <jgs@juniper.net>
Subject: [Status] Overlay-Underlay correlation use-case discussion for STATUS
X-BeenThere: status@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Stacked Tunnels for Source Routing \(STATUS\)." <status.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/status>, <mailto:status-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/status>
List-Post: <mailto:status@ietf.org>
List-Help: <mailto:status-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/status>, <mailto:status-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Jul 2013 07:01:46 -0000

Folks,



similar to John Brzozowski, we were also hoping to get some time on the agenda to discuss use-cases related to overlay-underlay correlation at the STATUS BoF - unfortunately we seem to share fate with John. We also thought that it would be useful to share the slides at least - see attached.



If interested, you might also want to have a look at http://www.ietf.org/id/draft-brockners-lisp-sr-00.txt - which discusses how the combination of LISP and Segment-Routing with IPv6 transport could be used in this context. The I-D describes extensions to LISP to enable a LISP mapping system to communicate a list of segment identifiers to the encapsulating router for purposes of traffic steering in the underlay or request the transport network to record the list of segments (nodal segments or adjacency segments) a particular packet or set of packets traverses in the transport network.



Looking forward to the discussions at the BoF.


Thanks, Frank