[v6ops] Late addition to V6OPS agenda: segment routing for IPv6?
"Eric Vyncke (evyncke)" <evyncke@cisco.com> Thu, 10 July 2014 15:06 UTC
Return-Path: <evyncke@cisco.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DEBB21A0659 for <v6ops@ietfa.amsl.com>; Thu, 10 Jul 2014 08:06:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.151
X-Spam-Level:
X-Spam-Status: No, score=-15.151 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pCu_5eDX3XX0 for <v6ops@ietfa.amsl.com>; Thu, 10 Jul 2014 08:06:41 -0700 (PDT)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AED941A0AAB for <v6ops@ietf.org>; Thu, 10 Jul 2014 08:06:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3336; q=dns/txt; s=iport; t=1405004813; x=1406214413; h=from:to:cc:subject:date:message-id:mime-version; bh=4Tq4zzHup6Qa8n+MolkQBFtF15Rz1kISRZj352BEqdg=; b=OkiqD66jVmQe0p9F3BT+LHFCgOE3WVNrfF48XrD3YNpwm/K6FeWznz9a RitiDPz3vq4bvOKtzgTaTcbZACGsRlYyhfAPahIlRKMFzhWFEjA0UCch2 7asOHGuU+87NoXpRuVg+VoSpkWwUmlT74bgdPJTVYq8dqquZP5f7fW6+m o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag4FAPOqvlOtJA2L/2dsb2JhbABZgkdHgSzGboENFnWECnkSAQwOZhcQBA6IR8gNF49EhEoFih6QYpQVg0OCMA
X-IronPort-AV: E=Sophos; i="5.01,638,1400025600"; d="scan'208,217"; a="59793380"
Received: from alln-core-6.cisco.com ([173.36.13.139]) by alln-iport-8.cisco.com with ESMTP; 10 Jul 2014 15:06:52 +0000
Received: from xhc-aln-x07.cisco.com (xhc-aln-x07.cisco.com [173.36.12.81]) by alln-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id s6AF6d2o023512 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <v6ops@ietf.org>; Thu, 10 Jul 2014 15:06:39 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.120]) by xhc-aln-x07.cisco.com ([173.36.12.81]) with mapi id 14.03.0123.003; Thu, 10 Jul 2014 10:06:39 -0500
From: "Eric Vyncke (evyncke)" <evyncke@cisco.com>
To: IPv6 Ops WG <v6ops@ietf.org>
Thread-Topic: Late addition to V6OPS agenda: segment routing for IPv6?
Thread-Index: AQHPnFCMLc7lfw+FYEqYrOVbl/Eiyw==
Date: Thu, 10 Jul 2014 15:06:38 +0000
Message-ID: <CFE4789D.20A1D%evyncke@cisco.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.4.3.140616
x-originating-ip: [10.55.185.72]
Content-Type: multipart/alternative; boundary="_000_CFE4789D20A1Devynckeciscocom_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/HD1pb3uClJlWiAds-dtZyvhdoRQ
Cc: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
Subject: [v6ops] Late addition to V6OPS agenda: segment routing for IPv6?
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Jul 2014 15:06:46 -0000
Fred and Joel, You may be aware of segment routing whose architecture and MPLS version are discussed in the SPRING WG. But, there is also an IPv6 version discussed in 6MAN: * draft-previdi-6man-segment-routing-header * draft-vyncke-6man-segment-routing-security-00 It is about a modified routing extension header to allow mainly for traffic engineering and or replace a MPLS LDP core by a native IPv6 one. Hence, there is a major (we hope) operational impact. Stefano (in cc) and I understand that we are late in the process to get a slot in V6OPS, but, if you could get us a 10-minute slot on Monday AM or Tuesday PM, then we could present what are the goals & architecture of segment routing for IPv6 (which really leverages IPv6, hence perhaps 'the killing app' for IPv6 :-)) Thanks in advance and see you in Toronto -éric
- [v6ops] Late addition to V6OPS agenda: segment ro… Eric Vyncke (evyncke)