From nobody Mon Feb 2 08:52:50 2015 Return-Path: X-Original-To: spring@ietfa.amsl.com Delivered-To: spring@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 85A711A1AFB; Mon, 2 Feb 2015 08:52:47 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -14.511 X-Spam-Level: X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 t0555i1CK30M; Mon, 2 Feb 2015 08:52:45 -0800 (PST) Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ADAB31A03A2; Mon, 2 Feb 2015 08:52:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4195; q=dns/txt; s=iport; t=1422895965; x=1424105565; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=Waccd02ug5DbuwFppkDFI/kcI4qstmEILFHFJzBsNBk=; b=fo2lz9cWyN6CEvl5ZSh+ehVvFMMIMZJA4wYbhGkawrjvpecWw+WMQujP d1i2O36NfDg2OZmLsebFG+JaTp2Q7IqOVVmUEhqieawjUeYWkzCQrVdtr 6j/uLUOSY38zZmRHFFHa2DWeRhpP1HegsieQVJnl68iTwElagZVz+Cg0T 8=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A0DoBAA2qs9U/xbLJq1bg1hZgwHBXQqFcQKBYQEBAQEBfYQNAQEEAQEBIA8BBTYKEQsYAgIFFgsCAgkDAgECARUwBgEMBgIBAYgpDcBIlWoBAQEBAQEBAQEBAQEBAQEBAQEWBIEhjl6CaIFBAQSFS5Jjhj2MHyKCAhyBUT0xgkIBAQE X-IronPort-AV: E=Sophos;i="5.09,507,1418083200"; d="scan'208";a="335998441" Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP; 02 Feb 2015 16:52:42 +0000 Received: from [10.148.128.133] ([10.148.128.133]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id t12GqfaM007253; Mon, 2 Feb 2015 16:52:42 GMT Message-ID: <54CFAB4F.9060306@cisco.com> Date: Mon, 02 Feb 2015 17:52:31 +0100 From: Peter Psenak User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: "Anil Kumar S N (VRP Network BL)" , OSPF WG List , "spring@ietf.org" References: <327562D94EA7BF428CD805F338C31EF02B70A76D@nkgeml512-mbx.china.huawei.com> In-Reply-To: <327562D94EA7BF428CD805F338C31EF02B70A76D@nkgeml512-mbx.china.huawei.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Archived-At: Subject: Re: [spring] [OSPF] draft-psenak-ospf-segment-routing-extensions-05 X-BeenThere: spring@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "Stacked Tunnels for Source Routing \(STATUS\)." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Feb 2015 16:52:47 -0000 Anil, Adj-SID is a link attribute. Link is identified the same way as it is identified in the Router LSA - link-type, link-id, link-data. for unnumbered link: link-type = 1 link-id = Neighboring router's Router ID link-data = interface's ifIndex So if RTA wants to use a particular link between RTB and RTC, it needs to know the ifIndex of that link and pick the link based on that. regards, Peter On 2/2/15 15:39 , Anil Kumar S N (VRP Network BL) wrote: > Hi All, > > I have a question on Adjacency Segment Identifier: > > How will RTA indentify and map adj-labels originated by RTB (having > unnumbered point-to-point connections b/w RTB and RTC) among labels to > which link ? > > Router ID > > 1.1.1.1 2.2.2.2 3.3.3.3 > > +-------+ P2p Links 1-5 +-------+   > > | +-------------+----+ | > > | | | | > > +-------+ | +------------------+ | > > | | | | | | > > | RTA +----------+ RTB +------------------+ RTC | > > | | | | | | > > +-------+ | +------------------+ | > > | | | | > > | +------------------+ | > > | | | | > > +-------+ +-------+ > > Router vertex 2.2.2.2 > > LinkType LinkId LinkData Metric IfIndex IfType > > P2P 1.1.1.1 11.0.0.112 100 0 NULL > >> Connected to Nbr vertex 1.1.1.1 > > P2P 3.3.3.3 12.0.0.112 100 0 NULL > >> Connected to Nbr vertex 3.3.3.3 > > P2P 3.3.3.3 13.0.0.112 100 0 NULL > >> Connected to Nbr vertex 3.3.3.3 > > P2P 3.3.3.3 14.0.0.112 100 0 NULL > >> Connected to Nbr vertex 3.3.3.3 > > P2P 3.3.3.3 15.0.0.112 100 0 NULL > >> Connected to Nbr vertex 3.3.3.3 > > P2P 3.3.3.3 16.0.0.112 100 0 NULL > >> Connected to Nbr vertex 3.3.3.3 > > Quick Reference RFC 2328 A.4.2 Router-LSAs [Link Type] > > Type > A quick description of the router link. One of the following. > Note that host routes are classified as links to stub networks > with network mask of 0xffffffff. > > Type Description > __________________________________________________ > 1 Point-to-point connection to another router > 2 Connection to a transit network > 3 Connection to a stub network > 4 Virtual link > > Link ID > Identifies the object that this router link connects to. Value > depends on the link's Type. When connecting to an object that > also originates an LSA (i.e., another router or a transit > network) the Link ID is equal to the neighboring LSA's Link > State ID. This provides the key for looking up the neighboring > LSA in the link state database during the routing table > calculation. See Section 12.2 <#Title_12.2>for more details. > > Type Link ID > ______________________________________ > 1 Neighboring router's Router ID > 2 IP address of Designated Router > 3 IP network/subnet number > 4 Neighboring router's Router ID > > > Link Data > Value again depends on the link's Type field. For connections to > stub networks, Link Data specifies the network's IP address > mask. For unnumbered point-to-point connections, it specifies > the interface's MIB-II [Ref8] <#BibRef_Ref8>ifIndex value. For the other > link > types it specifies the router interface's IP address. This > latter piece of information is needed during the routing table > build process, when calculating the IP address of the next hop. > See Section 16.1.1 <#Title_16.1.1>for more details. > > With Regards > > Anil S N > > > > _______________________________________________ > OSPF mailing list > OSPF@ietf.org > https://www.ietf.org/mailman/listinfo/ospf > From nobody Mon Feb 2 12:12:41 2015 Return-Path: X-Original-To: spring@ietfa.amsl.com Delivered-To: spring@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E37F1A1A25; Mon, 2 Feb 2015 06:39:46 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.81 X-Spam-Level: X-Spam-Status: No, score=-2.81 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 r2ZN__8d88Kh; Mon, 2 Feb 2015 06:39:42 -0800 (PST) Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BC2A11A039A; Mon, 2 Feb 2015 06:39:41 -0800 (PST) Received: from 172.18.7.190 (EHLO lhreml406-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BRZ84629; Mon, 02 Feb 2015 14:39:40 +0000 (GMT) Received: from nkgeml409-hub.china.huawei.com (10.98.56.40) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 2 Feb 2015 14:39:39 +0000 Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.106]) by nkgeml409-hub.china.huawei.com ([10.98.56.40]) with mapi id 14.03.0158.001; Mon, 2 Feb 2015 22:39:34 +0800 From: "Anil Kumar S N (VRP Network BL)" To: OSPF WG List , "spring@ietf.org" Thread-Topic: [spring] [OSPF] draft-psenak-ospf-segment-routing-extensions-05 Thread-Index: AdA+9g8H8gNLSnlaSY2XryzB6a6VsQ== Date: Mon, 2 Feb 2015 14:39:34 +0000 Message-ID: <327562D94EA7BF428CD805F338C31EF02B70A76D@nkgeml512-mbx.china.huawei.com> Accept-Language: en-US, zh-CN Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.18.152.169] Content-Type: multipart/alternative; boundary="_000_327562D94EA7BF428CD805F338C31EF02B70A76Dnkgeml512mbxchi_" MIME-Version: 1.0 X-CFilter-Loop: Reflected Archived-At: X-Mailman-Approved-At: Mon, 02 Feb 2015 12:12:39 -0800 Subject: [spring] [OSPF] draft-psenak-ospf-segment-routing-extensions-05 X-BeenThere: spring@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "Stacked Tunnels for Source Routing \(STATUS\)." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Feb 2015 14:39:46 -0000 --_000_327562D94EA7BF428CD805F338C31EF02B70A76Dnkgeml512mbxchi_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi All, I have a question on Adjacency Segment Identifier: How will RTA indentify and map adj-labels originated by RTB (having unnumbe= red point-to-point connections b/w RTB and RTC) among labels to which link = ? Router ID 1.1.1.1 2.2.2.2 3.3.3.3 +-------+ P2p Links 1-5 +-------+ ? | +-------------+----+ | | | | | +-------+ | +------------------+ | | | | | | | | RTA +----------+ RTB +------------------+ RTC | | | | | | | +-------+ | +------------------+ | | | | | | +------------------+ | | | | | +-------+ +-------+ Router vertex 2.2.2.2 LinkType LinkId LinkData Metric IfIndex IfType P2P 1.1.1.1 11.0.0.112 100 0 NULL >> = Connected to Nbr vertex 1.1.1.1 P2P 3.3.3.3 12.0.0.112 100 0 NULL >> = Connected to Nbr vertex 3.3.3.3 P2P 3.3.3.3 13.0.0.112 100 0 NULL >> = Connected to Nbr vertex 3.3.3.3 P2P 3.3.3.3 14.0.0.112 100 0 NULL >> = Connected to Nbr vertex 3.3.3.3 P2P 3.3.3.3 15.0.0.112 100 0 NULL >> = Connected to Nbr vertex 3.3.3.3 P2P 3.3.3.3 16.0.0.112 100 0 NULL >> = Connected to Nbr vertex 3.3.3.3 Quick Reference RFC 2328 A.4.2 Router-LSAs [Link Type] Type A quick description of the router link. One of the following. Note that host routes are classified as links to stub networks with network mask of 0xffffffff. Type Description __________________________________________________ 1 Point-to-point connection to another router 2 Connection to a transit network 3 Connection to a stub network 4 Virtual link Link ID Identifies the object that this router link connects to. Value depends on the link's Type. When connecting to an object that also originates an LSA (i.e., another router or a transit network) the Link ID is equal to the neighboring LSA's Link State ID. This provides the key for looking up the neighboring LSA in the link state database during the routing table calculation. See Section 12.2 for more details. Type Link ID ______________________________________ 1 Neighboring router's Router ID 2 IP address of Designated Router 3 IP network/subnet number 4 Neighboring router's Router ID Link Data Value again depends on the link's Type field. For connections to stub networks, Link Data specifies the network's IP address mask. For unnumbered point-to-point connections, it specifies the interface's MIB-II [Ref8] ifIndex value. For the other link types it specifies the router interface's IP address. This latter piece of information is needed during the routing table build process, when calculating the IP address of the next hop. See Section 16.1.1 for more details. With Regards Anil S N --_000_327562D94EA7BF428CD805F338C31EF02B70A76Dnkgeml512mbxchi_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

= Hi All,

=  

=      I have a question on Adjacency Segment Identifier:=

How will RTA indentify and map adj-labels orig= inated by RTB (having unnumbered point-to-point connections b/= w RTB and RTC) among labels to which link ?

=  

= Router ID

= 1.1.1.1            2= .2.2.2            &n= bsp;        3.3.3.3

=  

=             &nb= sp;      +-------+  P2p Links 1-5&nbs= p;  +-------+        &= nbsp;           

=             &nb= sp;      |       = 3;-------------+----+       | &n= bsp;            = ;     

=             &nb= sp;      |      = ; |            =       |       | = ;            &n= bsp;     

= +-------+          |&n= bsp;      +------------------+  =      |        &= nbsp;          

= |       |      =     |       |   = ;            &n= bsp;  |       |    &= nbsp;           &nbs= p;  

= |  RTA  +----------+  RTB  +---------------= ---+  RTC  |        &= nbsp;          

= |       |      =     |       |   = ;             &= nbsp; |       |    &= nbsp;           &nbs= p;  

= +-------+          |&n= bsp;      +------------------+  =      |        &= nbsp;          

=             &nb= sp;      |      = ; |            =       |       | = ;            &n= bsp;     

=             &nb= sp;      |      = ; +------------------+       | &= nbsp;           &nbs= p;     

=             &nb= sp;      |      = ; |            =       |       | = ;            &n= bsp;     

=             &nb= sp;      +-------+   &= nbsp;           &nbs= p;  +-------+ 

=  

=  

= Router vertex 2.2.2.2

= LinkType  LinkId         = LinkData        Metric  IfIndex&nb= sp; IfType

= P2P       1.1.1.1     &nb= sp;   11.0.0.112      100 &nbs= p;   0        NULL   = ;      >> Connected to Nbr vertex 1.1.1= .1

= P2P       3.3.3.3     &nb= sp;   12.0.0.112      100 &nbs= p;   0        NULL   = ;      >> Connected to Nbr vertex 3.3.3= .3

= P2P       3.3.3.3     &nb= sp;   13.0.0.112      100 &nbs= p;   0        NULL   = ;      >> Connected to Nbr vertex 3.3.3= .3

= P2P       3.3.3.3     &nb= sp;   14.0.0.112      100 &nbs= p;   0        NULL   = ;      >> Connected to Nbr vertex 3.3.3= .3

= P2P       3.3.3.3     &nb= sp;   15.0.0.112      100 &nbs= p;   0        NULL   = ;      >> Connected to Nbr vertex 3.3.3= .3

= P2P       3.3.3.3     &nb= sp;   16.0.0.112      100 &nbs= p;   0        NULL   = ;      >> Connected to Nbr vertex 3.3.3= .3

=  

=  

= Quick Reference RFC 2328 A.4.2 Router-LSAs [Link Type]

=  

Type
A quick description of the router link. One of the following.
Note that host routes are classified as links to stub networks
with network mask of 0xffffffff.

Type Description
__________________________________________________
1 Point-to-point connection to another router
2 Connection to a transit network
3 Connection to a stub network
4 Virtual link

Link ID
Identifies the object that this router link connects to. Value
depends on the link's Type. When connecting to an object that
also originates an LSA (i.e., another router or a transit
network) the Link ID is equal to the neighboring LSA's Link
State ID. This provides the key for looking up the neighboring
LSA in the link state database during the routing table
calculation. See = Section 12.2 for more details.<= /o:p>

 

Type Link ID
______________________________________
1 Neighboring router's Router ID
2 IP address of Designated Router
3 IP network/subnet number
4 Neighboring router's Router ID


Link Data
Value again depends on the link's Type field. For connections to
stub networks, Link Data specifies the network's IP address
mask. For unnumbered point-to-point connections, it specifies
the interface's MIB-II [Ref8] ifIndex value. For the ot= her link
types it specifies the router interface's IP address. This
latter piece of information is needed during the routing table
build process, when calculating the IP address of the next hop.
See <= a href=3D"#Title_16.1.1">Section 16.1.1 for more details.

=  

=  

= With Regards

= Anil S N           &= nbsp;     

--_000_327562D94EA7BF428CD805F338C31EF02B70A76Dnkgeml512mbxchi_-- From nobody Fri Feb 6 03:35:27 2015 Return-Path: X-Original-To: spring@ietfa.amsl.com Delivered-To: spring@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69E371A0334; Fri, 6 Feb 2015 03:35:24 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 ALL9O4VPSI2M; Fri, 6 Feb 2015 03:35:21 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id DFA9F1A00FA; Fri, 6 Feb 2015 03:35:21 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: X-Test-IDTracker: no X-IETF-IDTracker: 5.10.2 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20150206113521.25610.85618.idtracker@ietfa.amsl.com> Date: Fri, 06 Feb 2015 03:35:21 -0800 Archived-At: Cc: spring@ietf.org Subject: [spring] I-D Action: draft-ietf-spring-segment-routing-01.txt X-BeenThere: spring@ietf.org X-Mailman-Version: 2.1.15 List-Id: "Stacked Tunnels for Source Routing \(STATUS\)." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Feb 2015 11:35:24 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Source Packet Routing in Networking Working Group of the IETF. Title : Segment Routing Architecture Authors : Clarence Filsfils Stefano Previdi Ahmed Bashandy Bruno Decraene Stephane Litkowski Martin Horneffer Rob Shakir Jeff Tantsura Edward Crabbe Filename : draft-ietf-spring-segment-routing-01.txt Pages : 19 Date : 2015-02-06 Abstract: Segment Routing (SR) leverages the source routing paradigm. A node steers a packet through an ordered list of instructions, called segments. A segment can represent any instruction, topological or service-based. A segment can have a local semantic to an SR node or global within an SR domain. SR allows to enforce a flow through any topological path and service chain while maintaining per-flow state only at the ingress node to the SR domain. Segment Routing can be directly applied to the MPLS architecture with no change on the forwarding plane. A segment is encoded as an MPLS label. An ordered list of segments is encoded as a stack of labels. The segment to process is on the top of the stack. Upon completion of a segment, the related label is popped from the stack. Segment Routing can be applied to the IPv6 architecture, with a new type of routing extension header. A segment is encoded as an IPv6 address. An ordered list of segments is encoded as an ordered list of IPv6 addresses in the routing extension header. The segment to process is indicated by a pointer in the routing extension header. Upon completion of a segment, the pointer is incremented. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-spring-segment-routing/ There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-spring-segment-routing-01 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=draft-ietf-spring-segment-routing-01 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Fri Feb 6 03:38:04 2015 Return-Path: X-Original-To: spring@ietfa.amsl.com Delivered-To: spring@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E6581A034C for ; Fri, 6 Feb 2015 03:38:00 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -14.511 X-Spam-Level: X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 80e-_DRg5_Tm for ; Fri, 6 Feb 2015 03:37:58 -0800 (PST) Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 10EDA1A0267 for ; Fri, 6 Feb 2015 03:37:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2438; q=dns/txt; s=iport; t=1423222678; x=1424432278; h=from:to:subject:date:message-id:references:content-id: content-transfer-encoding:mime-version; bh=dCjBtw8UdmCyTeprvOj3Cr3IXAtcKCbAS3tmm1dvk4c=; b=T/tlnIZ9c0z4jNuosVu7vcLmDg52nakb+H5WwHK2jjQ8Q/JebTgRqUGR hU0f3T7+KR81YhNz6Ckb3KBtAQnaB9kV2k7hP1F+2soKHSY1QxkqNDWTO 4XWrjggsdSLG6XSZADRhd1jPFtoZ2Y1cGvgfBgPVOClm50lWAYstNSqzU A=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A0A6BgAup9RU/4ENJK1agwZSVQUEwDaCKIVvAoEcQwEBAQEBfYQMAQEBAwE6PQcLAgEaAwIfEDIXBAIIAgQBEgmIHAgIBdUTAQEBAQEBAQMBAQEBAQEBAQEZkAWDEIETBY8ag1CFXIEXNoJNjlIig25vAYFDfgEBAQ X-IronPort-AV: E=Sophos;i="5.09,529,1418083200"; d="scan'208";a="121168396" Received: from alln-core-9.cisco.com ([173.36.13.129]) by alln-iport-5.cisco.com with ESMTP; 06 Feb 2015 11:37:57 +0000 Received: from xhc-aln-x01.cisco.com (xhc-aln-x01.cisco.com [173.36.12.75]) by alln-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id t16BbvdX018353 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 6 Feb 2015 11:37:57 GMT Received: from xmb-rcd-x01.cisco.com ([169.254.1.238]) by xhc-aln-x01.cisco.com ([173.36.12.75]) with mapi id 14.03.0195.001; Fri, 6 Feb 2015 05:37:56 -0600 From: "Stefano Previdi (sprevidi)" To: "spring@ietf.org" , "Andrew G. Malis" Thread-Topic: New Version Notification for draft-ietf-spring-segment-routing-01.txt Thread-Index: AQHQQgEBn052VTxDAUeC69qlyfb+hg== Date: Fri, 6 Feb 2015 11:37:56 +0000 Message-ID: <35616C1A-E688-42BA-87FC-B5E692E2B340@cisco.com> References: <20150206113522.25610.28949.idtracker@ietfa.amsl.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.61.88.220] Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: Subject: [spring] Fwd: New Version Notification for draft-ietf-spring-segment-routing-01.txt X-BeenThere: spring@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "Stacked Tunnels for Source Routing \(STATUS\)." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Feb 2015 11:38:00 -0000 this version aims to address comments form Andrew. Thanks. s. Begin forwarded message: > From: > Subject: New Version Notification for draft-ietf-spring-segment-routing-0= 1.txt >=20 > A new version of I-D, draft-ietf-spring-segment-routing-01.txt > has been successfully submitted by Stefano Previdi and posted to the > IETF repository. >=20 > Name: draft-ietf-spring-segment-routing > Revision: 01 > Title: Segment Routing Architecture > Document date: 2015-02-05 > Group: spring > Pages: 19 > URL: http://www.ietf.org/internet-drafts/draft-ietf-spring-seg= ment-routing-01.txt > Status: https://datatracker.ietf.org/doc/draft-ietf-spring-segmen= t-routing/ > Htmlized: http://tools.ietf.org/html/draft-ietf-spring-segment-rout= ing-01 > Diff: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-spring-segm= ent-routing-01 >=20 > Abstract: > Segment Routing (SR) leverages the source routing paradigm. A node > steers a packet through an ordered list of instructions, called > segments. A segment can represent any instruction, topological or > service-based. A segment can have a local semantic to an SR node or > global within an SR domain. SR allows to enforce a flow through any > topological path and service chain while maintaining per-flow state > only at the ingress node to the SR domain. >=20 > Segment Routing can be directly applied to the MPLS architecture with > no change on the forwarding plane. A segment is encoded as an MPLS > label. An ordered list of segments is encoded as a stack of labels. > The segment to process is on the top of the stack. Upon completion > of a segment, the related label is popped from the stack. >=20 > Segment Routing can be applied to the IPv6 architecture, with a new > type of routing extension header. A segment is encoded as an IPv6 > address. An ordered list of segments is encoded as an ordered list > of IPv6 addresses in the routing extension header. The segment to > process is indicated by a pointer in the routing extension header. > Upon completion of a segment, the pointer is incremented. >=20 >=20 >=20 >=20 >=20 > Please note that it may take a couple of minutes from the time of submiss= ion > until the htmlized version and diff are available at tools.ietf.org. >=20 > The IETF Secretariat >=20 From nobody Fri Feb 6 04:04:10 2015 Return-Path: X-Original-To: spring@ietfa.amsl.com Delivered-To: spring@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D16BC1A0263 for ; Fri, 6 Feb 2015 04:04:06 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.902 X-Spam-Level: X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 SzaY1Te_Khug for ; Fri, 6 Feb 2015 04:04:04 -0800 (PST) Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1bon0722.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::1:722]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1CBA61A01BA for ; Fri, 6 Feb 2015 04:04:04 -0800 (PST) Received: from hannes-mba.local (66.129.239.13) by BLUPR05MB436.namprd05.prod.outlook.com (10.141.27.152) with Microsoft SMTP Server (TLS) id 15.1.75.20; Fri, 6 Feb 2015 12:03:41 +0000 Received: from hannes-mba.local (localhost [IPv6:::1]) by hannes-mba.local (Postfix) with ESMTP id 521BBE12A60; Fri, 6 Feb 2015 12:56:14 +0100 (CET) Date: Fri, 6 Feb 2015 12:56:14 +0100 From: Hannes Gredler To: Message-ID: <20150206115614.GA5179@hannes-mba.local> References: <20150206113521.25610.85618.idtracker@ietfa.amsl.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <20150206113521.25610.85618.idtracker@ietfa.amsl.com> User-Agent: Mutt/1.5.23 (2014-03-12) X-Originating-IP: [66.129.239.13] X-ClientProxiedBy: CY1PR09CA0028.namprd09.prod.outlook.com (25.160.223.38) To BLUPR05MB436.namprd05.prod.outlook.com (10.141.27.152) Authentication-Results: cisco.com; dkim=none (message not signed) header.d=none; X-Microsoft-Antispam: UriScan:; X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:BLUPR05MB436; X-Exchange-Antispam-Report-Test: UriScan:; X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(601004); SRVR:BLUPR05MB436; X-Forefront-PRVS: 047999FF16 X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(6009001)(24454002)(377424004)(77156002)(62966003)(50466002)(76506005)(92566002)(15975445007)(23726002)(40100003)(2950100001)(77096005)(1720100001)(47776003)(110136001)(2351001)(33656002)(46102003)(50986999)(122386002)(19580405001)(54356999)(46406003)(98436002)(83506001)(19580395003)(122856001)(76176999)(87976001)(86362001)(97756001)(66066001)(230783001)(579124003); DIR:OUT; SFP:1102; SCL:1; SRVR:BLUPR05MB436; H:hannes-mba.local; FPR:; SPF:None; MLV:sfv; LANG:en; X-Exchange-Antispam-Report-CFA-Test: BCL:0;PCL:0;RULEID:;SRVR:BLUPR05MB436; X-OriginatorOrg: juniper.net X-MS-Exchange-CrossTenant-OriginalArrivalTime: 06 Feb 2015 12:03:41.6082 (UTC) X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR05MB436 Archived-At: Cc: spring@ietf.org Subject: Re: [spring] I-D Action: draft-ietf-spring-segment-routing-01.txt X-BeenThere: spring@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "Stacked Tunnels for Source Routing \(STATUS\)." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Feb 2015 12:04:07 -0000 hi stefano, is 'SRDB' a typo ? - if not could you addd a definition/reference what are the 'SRDB Maintenance rules', please ? thanks, /hannes --- 3.6.1. Mapping Server A Remote-Binding SID S advertised by the mapping server M for remote prefix R attached to non-SR-capable node N signals the same information as if N had advertised S as a Prefix-SID. Further details are described in the SR/LDP interworking procedures ([I-D.filsfils-spring-segment-routing-ldp-interop]. The segment allocation and SRDB Maintenance rules are the same as ^^^^^^^^^^^^^^^^ those defined for Prefix-SID. 3.6.2. Tunnel Headend The segment allocation and SRDB Maintenance rules are the same as ^^^^^^^^^^^^^^^^ those defined for Adj-SID. A tunnel attached to a head-end H acts as an adjacency attached to H. --- On Fri, Feb 06, 2015 at 03:35:21AM -0800, internet-drafts@ietf.org wrote: | | A New Internet-Draft is available from the on-line Internet-Drafts directories. | This draft is a work item of the Source Packet Routing in Networking Working Group of the IETF. | | Title : Segment Routing Architecture | Authors : Clarence Filsfils | Stefano Previdi | Ahmed Bashandy | Bruno Decraene | Stephane Litkowski | Martin Horneffer | Rob Shakir | Jeff Tantsura | Edward Crabbe | Filename : draft-ietf-spring-segment-routing-01.txt | Pages : 19 | Date : 2015-02-06 | | Abstract: | Segment Routing (SR) leverages the source routing paradigm. A node | steers a packet through an ordered list of instructions, called | segments. A segment can represent any instruction, topological or | service-based. A segment can have a local semantic to an SR node or | global within an SR domain. SR allows to enforce a flow through any | topological path and service chain while maintaining per-flow state | only at the ingress node to the SR domain. | | Segment Routing can be directly applied to the MPLS architecture with | no change on the forwarding plane. A segment is encoded as an MPLS | label. An ordered list of segments is encoded as a stack of labels. | The segment to process is on the top of the stack. Upon completion | of a segment, the related label is popped from the stack. | | Segment Routing can be applied to the IPv6 architecture, with a new | type of routing extension header. A segment is encoded as an IPv6 | address. An ordered list of segments is encoded as an ordered list | of IPv6 addresses in the routing extension header. The segment to | process is indicated by a pointer in the routing extension header. | Upon completion of a segment, the pointer is incremented. | | | | The IETF datatracker status page for this draft is: | https://datatracker.ietf.org/doc/draft-ietf-spring-segment-routing/ | | There's also a htmlized version available at: | http://tools.ietf.org/html/draft-ietf-spring-segment-routing-01 | | A diff from the previous version is available at: | http://www.ietf.org/rfcdiff?url2=draft-ietf-spring-segment-routing-01 | | | Please note that it may take a couple of minutes from the time of submission | until the htmlized version and diff are available at tools.ietf.org. | | Internet-Drafts are also available by anonymous FTP at: | ftp://ftp.ietf.org/internet-drafts/ | | _______________________________________________ | spring mailing list | spring@ietf.org | https://www.ietf.org/mailman/listinfo/spring From nobody Fri Feb 6 04:24:14 2015 Return-Path: X-Original-To: spring@ietfa.amsl.com Delivered-To: spring@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3437B1A035F for ; Fri, 6 Feb 2015 04:24:10 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -14.511 X-Spam-Level: X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 du6MnUOfqSB6 for ; Fri, 6 Feb 2015 04:24:07 -0800 (PST) Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C16CA1A0263 for ; Fri, 6 Feb 2015 04:24:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4219; q=dns/txt; s=iport; t=1423225446; x=1424435046; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=S6+y3psdkQCxvMvjSXMt3khQaF1M5BC0E9E3CjZbYls=; b=e/d/PbgJiRWFKQKtkGe/erH5VqlJX6Lwt8KoBjChJfcdFlllx33mUc+1 lsLLjqkfTmHx3RhYmSG1uUdCExdwrAkQGQyFjcf7zMzwbFd09etMxzwqE R5weS1PWQ48Cf9bWH4LGJUNR9cUe7iYMlecFJd16T7tmRSkfTzHjoKjDk U=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Aj0GAH6x1FStJA2J/2dsb2JhbABagwZSVQUEwDaCHAqFJ0oCgRxDAQEBAQF9hAwBAQEDAQEBATc0CwULAgEIEgYeECcLFw4CBA4FCYgcCAgF1QsBAQEBAQEBAQEBAQEBAQEBAQEBAQEXj0UzB4MWgRMFjxqDUIVcgRc2gk2OUiKCAhyBUG+BRH4BAQE X-IronPort-AV: E=Sophos;i="5.09,529,1418083200"; d="scan'208";a="390883433" Received: from alln-core-4.cisco.com ([173.36.13.137]) by rcdn-iport-9.cisco.com with ESMTP; 06 Feb 2015 12:24:05 +0000 Received: from xhc-aln-x10.cisco.com (xhc-aln-x10.cisco.com [173.36.12.84]) by alln-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id t16CO5EE032298 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 6 Feb 2015 12:24:05 GMT Received: from xmb-rcd-x01.cisco.com ([169.254.1.238]) by xhc-aln-x10.cisco.com ([173.36.12.84]) with mapi id 14.03.0195.001; Fri, 6 Feb 2015 06:24:05 -0600 From: "Stefano Previdi (sprevidi)" To: Hannes Gredler Thread-Topic: [spring] I-D Action: draft-ietf-spring-segment-routing-01.txt Thread-Index: AQHQQgEHzNc2sN6F2ke2aOrZWFbJYZzj6GMAgAAHxYA= Date: Fri, 6 Feb 2015 12:24:04 +0000 Message-ID: References: <20150206113521.25610.85618.idtracker@ietfa.amsl.com> <20150206115614.GA5179@hannes-mba.local> In-Reply-To: <20150206115614.GA5179@hannes-mba.local> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.61.88.220] Content-Type: text/plain; charset="us-ascii" Content-ID: <64930B05A8A40847BC5F0E84F30671AA@emea.cisco.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: Cc: "" Subject: Re: [spring] I-D Action: draft-ietf-spring-segment-routing-01.txt X-BeenThere: spring@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "Stacked Tunnels for Source Routing \(STATUS\)." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Feb 2015 12:24:10 -0000 On Feb 6, 2015, at 12:56 PM, Hannes Gredler wrote: > hi stefano, >=20 > is 'SRDB' a typo ? yes. I'll fix it. Thanks. s. > - if not could you addd a definition/reference > what are the 'SRDB Maintenance rules', please ? >=20 > thanks, >=20 > /hannes >=20 > --- > 3.6.1. Mapping Server >=20 > A Remote-Binding SID S advertised by the mapping server M for remote > prefix R attached to non-SR-capable node N signals the same > information as if N had advertised S as a Prefix-SID. Further > details are described in the SR/LDP interworking procedures > ([I-D.filsfils-spring-segment-routing-ldp-interop]. >=20 > The segment allocation and SRDB Maintenance rules are the same as > ^^^^^^^^^^^^^^^^ > those defined for Prefix-SID. >=20 > 3.6.2. Tunnel Headend >=20 > The segment allocation and SRDB Maintenance rules are the same as > ^^^^^^^^^^^^^^^^ > those defined for Adj-SID. A tunnel attached to a head-end H acts as > an adjacency attached to H. >=20 > --- >=20 >=20 > On Fri, Feb 06, 2015 at 03:35:21AM -0800, internet-drafts@ietf.org wrote: > |=20 > | A New Internet-Draft is available from the on-line Internet-Drafts dire= ctories. > | This draft is a work item of the Source Packet Routing in Networking W= orking Group of the IETF. > |=20 > | Title : Segment Routing Architecture > | Authors : Clarence Filsfils > | Stefano Previdi > | Ahmed Bashandy > | Bruno Decraene > | Stephane Litkowski > | Martin Horneffer > | Rob Shakir > | Jeff Tantsura > | Edward Crabbe > | Filename : draft-ietf-spring-segment-routing-01.txt > | Pages : 19 > | Date : 2015-02-06 > |=20 > | Abstract: > | Segment Routing (SR) leverages the source routing paradigm. A node > | steers a packet through an ordered list of instructions, called > | segments. A segment can represent any instruction, topological or > | service-based. A segment can have a local semantic to an SR node or > | global within an SR domain. SR allows to enforce a flow through any > | topological path and service chain while maintaining per-flow state > | only at the ingress node to the SR domain. > |=20 > | Segment Routing can be directly applied to the MPLS architecture wit= h > | no change on the forwarding plane. A segment is encoded as an MPLS > | label. An ordered list of segments is encoded as a stack of labels. > | The segment to process is on the top of the stack. Upon completion > | of a segment, the related label is popped from the stack. > |=20 > | Segment Routing can be applied to the IPv6 architecture, with a new > | type of routing extension header. A segment is encoded as an IPv6 > | address. An ordered list of segments is encoded as an ordered list > | of IPv6 addresses in the routing extension header. The segment to > | process is indicated by a pointer in the routing extension header. > | Upon completion of a segment, the pointer is incremented. > |=20 > |=20 > |=20 > | The IETF datatracker status page for this draft is: > | https://datatracker.ietf.org/doc/draft-ietf-spring-segment-routing/ > |=20 > | There's also a htmlized version available at: > | http://tools.ietf.org/html/draft-ietf-spring-segment-routing-01 > |=20 > | A diff from the previous version is available at: > | http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-spring-segment-routing-01 > |=20 > |=20 > | Please note that it may take a couple of minutes from the time of submi= ssion > | until the htmlized version and diff are available at tools.ietf.org. > |=20 > | Internet-Drafts are also available by anonymous FTP at: > | ftp://ftp.ietf.org/internet-drafts/ > |=20 > | _______________________________________________ > | spring mailing list > | spring@ietf.org > | https://www.ietf.org/mailman/listinfo/spring From nobody Fri Feb 6 11:13:06 2015 Return-Path: X-Original-To: spring@ietfa.amsl.com Delivered-To: spring@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 810141A1A1D for ; Fri, 6 Feb 2015 11:13:02 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 ior7EB5G3Ssd for ; Fri, 6 Feb 2015 11:13:00 -0800 (PST) Received: from mail-qa0-x236.google.com (mail-qa0-x236.google.com [IPv6:2607:f8b0:400d:c00::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0B4811A1A06 for ; Fri, 6 Feb 2015 11:13:00 -0800 (PST) Received: by mail-qa0-f54.google.com with SMTP id w8so12349619qac.13 for ; Fri, 06 Feb 2015 11:12:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=Dg4b4nZ0IZQIXbShu1V/hUP6LVA9ElaT4v1nqcFaxx4=; b=LPPDNFj9iVsO6J3TikoRymvJlm4sT9ylL8stemKyLS70qHf1Lx/czgIOz7QHKdDD8q oUuDUTtOBpSpKUdACbsP5e3UKvNd9+iBrRgcJleF5VtTcnPQAKCKK9wLh2Jnb5Ltqif4 mS7jtbisPJlTiV9T4PrkEuiIZHon96mbpzV3p6LBrAzj9Nf9Z5x8fp0OTsOaHojZzNpP TobzymDp8SWLvRcPGi4ORdJUknXaM8jmJ36ocBAdyy4k8wk9GxJUzUE8+6BKTw/ixYgU KyMKPicPyqvh1TlnSYyqHLXqRVLvK7UiaT4FhOPQ1rxNIrD9uHh25Kkt86vL/ireQqfv FJTA== X-Received: by 10.140.101.119 with SMTP id t110mr11106484qge.9.1423249979168; Fri, 06 Feb 2015 11:12:59 -0800 (PST) MIME-Version: 1.0 Received: by 10.140.96.200 with HTTP; Fri, 6 Feb 2015 11:12:39 -0800 (PST) In-Reply-To: <35616C1A-E688-42BA-87FC-B5E692E2B340@cisco.com> References: <20150206113522.25610.28949.idtracker@ietfa.amsl.com> <35616C1A-E688-42BA-87FC-B5E692E2B340@cisco.com> From: "Andrew G. Malis" Date: Fri, 6 Feb 2015 14:12:39 -0500 Message-ID: To: "Stefano Previdi (sprevidi)" Content-Type: multipart/alternative; boundary=001a11c16e5e6f5e7d050e703594 Archived-At: Cc: "spring@ietf.org" Subject: Re: [spring] New Version Notification for draft-ietf-spring-segment-routing-01.txt X-BeenThere: spring@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "Stacked Tunnels for Source Routing \(STATUS\)." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Feb 2015 19:13:02 -0000 --001a11c16e5e6f5e7d050e703594 Content-Type: text/plain; charset=UTF-8 Stefano, Thanks, much appreciated. Cheers, Andy On Fri, Feb 6, 2015 at 6:37 AM, Stefano Previdi (sprevidi) < sprevidi@cisco.com> wrote: > this version aims to address comments form Andrew. > > Thanks. > s. > > > Begin forwarded message: > > > From: > > Subject: New Version Notification for > draft-ietf-spring-segment-routing-01.txt > > > > A new version of I-D, draft-ietf-spring-segment-routing-01.txt > > has been successfully submitted by Stefano Previdi and posted to the > > IETF repository. > > > > Name: draft-ietf-spring-segment-routing > > Revision: 01 > > Title: Segment Routing Architecture > > Document date: 2015-02-05 > > Group: spring > > Pages: 19 > > URL: > http://www.ietf.org/internet-drafts/draft-ietf-spring-segment-routing-01.txt > > Status: > https://datatracker.ietf.org/doc/draft-ietf-spring-segment-routing/ > > Htmlized: > http://tools.ietf.org/html/draft-ietf-spring-segment-routing-01 > > Diff: > http://www.ietf.org/rfcdiff?url2=draft-ietf-spring-segment-routing-01 > > > > Abstract: > > Segment Routing (SR) leverages the source routing paradigm. A node > > steers a packet through an ordered list of instructions, called > > segments. A segment can represent any instruction, topological or > > service-based. A segment can have a local semantic to an SR node or > > global within an SR domain. SR allows to enforce a flow through any > > topological path and service chain while maintaining per-flow state > > only at the ingress node to the SR domain. > > > > Segment Routing can be directly applied to the MPLS architecture with > > no change on the forwarding plane. A segment is encoded as an MPLS > > label. An ordered list of segments is encoded as a stack of labels. > > The segment to process is on the top of the stack. Upon completion > > of a segment, the related label is popped from the stack. > > > > Segment Routing can be applied to the IPv6 architecture, with a new > > type of routing extension header. A segment is encoded as an IPv6 > > address. An ordered list of segments is encoded as an ordered list > > of IPv6 addresses in the routing extension header. The segment to > > process is indicated by a pointer in the routing extension header. > > Upon completion of a segment, the pointer is incremented. > > > > > > > > > > > > Please note that it may take a couple of minutes from the time of > submission > > until the htmlized version and diff are available at tools.ietf.org. > > > > The IETF Secretariat > > > > --001a11c16e5e6f5e7d050e703594 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Stefano,

Thanks, much appreciated.

Cheers,
Andy

On Fri, Feb 6, 2015 at 6:37 AM, Stefa= no Previdi (sprevidi) <sprevidi@cisco.com> wrote:
this version aims to address comments form Andrew.=

Thanks.
s.


Begin forwarded message:

> From: <internet-drafts@= ietf.org>
> Subject: New Version Notification for draft-ietf-spring-segment-routin= g-01.txt
>
> A new version of I-D, draft-ietf-spring-segment-routing-01.txt
> has been successfully submitted by Stefano Previdi and posted to the > IETF repository.
>
> Name:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0draft-ietf-spring-segment-routi= ng
> Revision:=C2=A0 =C2=A0 =C2=A001
> Title:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Segment = Routing Architecture
> Document date:=C2=A0 =C2=A0 =C2=A0 =C2=A0 2015-02-05
> Group:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 spring > Pages:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 19
> URL:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 http://www.ietf.org/internet-drafts/draft-ietf-spring-segment-routi= ng-01.txt
> Status:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0https:= //datatracker.ietf.org/doc/draft-ietf-spring-segment-routing/
> Htmlized:=C2=A0 =C2=A0 =C2=A0 =C2=A0http://tools.ie= tf.org/html/draft-ietf-spring-segment-routing-01
> Diff:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-spring-segment-routing-01<= /a>
>
> Abstract:
>=C2=A0 =C2=A0Segment Routing (SR) leverages the source routing paradigm= .=C2=A0 A node
>=C2=A0 =C2=A0steers a packet through an ordered list of instructions, c= alled
>=C2=A0 =C2=A0segments.=C2=A0 A segment can represent any instruction, t= opological or
>=C2=A0 =C2=A0service-based.=C2=A0 A segment can have a local semantic t= o an SR node or
>=C2=A0 =C2=A0global within an SR domain.=C2=A0 SR allows to enforce a f= low through any
>=C2=A0 =C2=A0topological path and service chain while maintaining per-f= low state
>=C2=A0 =C2=A0only at the ingress node to the SR domain.
>
>=C2=A0 =C2=A0Segment Routing can be directly applied to the MPLS archit= ecture with
>=C2=A0 =C2=A0no change on the forwarding plane.=C2=A0 A segment is enco= ded as an MPLS
>=C2=A0 =C2=A0label.=C2=A0 An ordered list of segments is encoded as a s= tack of labels.
>=C2=A0 =C2=A0The segment to process is on the top of the stack.=C2=A0 U= pon completion
>=C2=A0 =C2=A0of a segment, the related label is popped from the stack.<= br> >
>=C2=A0 =C2=A0Segment Routing can be applied to the IPv6 architecture, w= ith a new
>=C2=A0 =C2=A0type of routing extension header.=C2=A0 A segment is encod= ed as an IPv6
>=C2=A0 =C2=A0address.=C2=A0 An ordered list of segments is encoded as a= n ordered list
>=C2=A0 =C2=A0of IPv6 addresses in the routing extension header.=C2=A0 T= he segment to
>=C2=A0 =C2=A0process is indicated by a pointer in the routing extension= header.
>=C2=A0 =C2=A0Upon completion of a segment, the pointer is incremented.<= br> >
>
>
>
>
> Please note that it may take a couple of minutes from the time of subm= ission
> until the htmlized version and diff are available at tools.ietf.org.
>
> The IETF Secretariat
>


--001a11c16e5e6f5e7d050e703594-- From nobody Thu Feb 12 10:40:28 2015 Return-Path: X-Original-To: spring@ietfa.amsl.com Delivered-To: spring@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E31B31A00A8; Thu, 12 Feb 2015 10:40:23 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -104.201 X-Spam-Level: X-Spam-Status: No, score=-104.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 jYKvcLH8lgex; Thu, 12 Feb 2015 10:40:21 -0800 (PST) Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DD4121A1AE5; Thu, 12 Feb 2015 10:40:17 -0800 (PST) X-AuditID: c6180641-f79916d00000623a-c1-54dc93b747d9 Received: from EUSAAHC008.ericsson.se (Unknown_Domain [147.117.188.96]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id 2B.73.25146.7B39CD45; Thu, 12 Feb 2015 12:51:19 +0100 (CET) Received: from EUSAAMB103.ericsson.se ([147.117.188.120]) by EUSAAHC008.ericsson.se ([147.117.188.96]) with mapi id 14.03.0210.002; Thu, 12 Feb 2015 13:40:16 -0500 From: Gregory Mirsky To: "mpls@ietf.org" , "rtg-bfd@ietf.org" , "spring@ietf.org" Thread-Topic: New Version Notification for draft-mirsky-mpls-bfd-directed-02.txt Thread-Index: AQHQRvHNwCfJMiQTLEK8YUR7hkvUlJztVp0w Date: Thu, 12 Feb 2015 18:40:15 +0000 Message-ID: <7347100B5761DC41A166AC17F22DF1121B900074@eusaamb103.ericsson.se> References: <20150212182905.4209.86980.idtracker@ietfa.amsl.com> In-Reply-To: <20150212182905.4209.86980.idtracker@ietfa.amsl.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [147.117.188.10] Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrELMWRmVeSWpSXmKPExsUyuXRPgu72yXdCDA6vl7K4tXQlq8XnP9sY LY5f+M3owOyxZMlPpgDGKC6blNSczLLUIn27BK6MO4+OsxVsEa1ofnOdqYHxjUgXIyeHhICJ RN/cyawQtpjEhXvr2boYuTiEBI4wSiw68J0dwlnOKLG6YxsjSBWbgJHEi4097CC2iEChxOd9 11hAbGGBQInD174yQcSDJE5d+MQIYRtJPD84jw3EZhFQlfjQ8oK5i5GDg1fAV2LWWVGQsJCA g8SlqUvBRnIKOErsnH2cGcRmBDro+6k1YCOZBcQlbj2ZzwRxqIDEkj3nmSFsUYmXj/9BPaAk MWnpOVaQ8cwCmhLrd+lDtCpKTOl+CDaeV0BQ4uTMJywTGEVnIZk6C6FjFpKOWUg6FjCyrGLk KC1OLctNNzLcxAiMhGMSbI47GBd8sjzEKMDBqMTD++He7RAh1sSy4srcQ4zSHCxK4rxlVw6G CAmkJ5akZqemFqQWxReV5qQWH2Jk4uCUamBsiwmZ8Dzum/szQ18xtsBivyknT39bxGv523h3 /8eFH9v+/XLJ72q3cZ9hLrFOniv9Z4FAw/GPYt8iDuoy+lmfYZv4wV+od9XBVVylqo3tHkWK a1+vnu6iH/zr9K8D1yyv6GaVCtaF/TlUMTVAz0lDe23/ntbg3abR4ufMn36Lm6x1oePrBwYl luKMREMt5qLiRADR0u7XZQIAAA== Archived-At: Subject: [spring] FW: New Version Notification for draft-mirsky-mpls-bfd-directed-02.txt X-BeenThere: spring@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "Stacked Tunnels for Source Routing \(STATUS\)." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Feb 2015 18:40:24 -0000 RGVhciBBbGwsDQphdXRob3JzIG9mIHR3byBkcmFmdHMsIGRyYWZ0LWNoZW4tbXBscy1iZmQtZW5o YW5jZW1lbnQgYW5kIGRyYWZ0LW1pcnNreS1tcGxzLWJmZC1kaXJlY3RlZCwgZGVjaWRlZCB0byB3 b3JrIHRvZ2V0aGVyIG9uIHRoZSBwcm9ibGVtcyByZWxhdGVkIHRvIGNvbnRyb2xsaW5nIHJldmVy c2UgcGF0aCBvZiBhIEJGRCBzZXNzaW9uLiBUaGlzIGlzIG5ldyB2ZXJzaW9uIG9mIG91ciBqb2lu dCBlZmZvcnRzIHRvIG1vdmUgdGhlIHdvcmsgZnVydGhlci4gV2UgbmVlZCB5b3VyIGhlbHAgYnkg c2hhcmluZyB5b3VyIGNvbW1lbnRzLCBzdWdnZXN0aW9ucyBiZWZvcmUgdGhlIG1lZXRpbmcgaW4g RGFsbGFzIG9uIHRoZXNlIG1haWxpbmcgbGlzdHMuDQoNCglSZWdhcmRzLA0KCQlHcmVnDQoNCi0t LS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBpbnRlcm5ldC1kcmFmdHNAaWV0Zi5vcmcg W21haWx0bzppbnRlcm5ldC1kcmFmdHNAaWV0Zi5vcmddIA0KU2VudDogVGh1cnNkYXksIEZlYnJ1 YXJ5IDEyLCAyMDE1IDEwOjI5IEFNDQpUbzogTWFjaCBDaGVuOyBHcmVnb3J5IE1pcnNreTsgSmVm ZiBUYW50c3VyYTsgR3JlZ29yeSBNaXJza3k7IEplZmYgVGFudHN1cmE7IE1hY2ggQ2hlbiAoR3Vv eWkpOyBJbHlhIFZhcmxhc2hraW47IElseWEgVmFybGFzaGtpbg0KU3ViamVjdDogTmV3IFZlcnNp b24gTm90aWZpY2F0aW9uIGZvciBkcmFmdC1taXJza3ktbXBscy1iZmQtZGlyZWN0ZWQtMDIudHh0 DQoNCg0KQSBuZXcgdmVyc2lvbiBvZiBJLUQsIGRyYWZ0LW1pcnNreS1tcGxzLWJmZC1kaXJlY3Rl ZC0wMi50eHQNCmhhcyBiZWVuIHN1Y2Nlc3NmdWxseSBzdWJtaXR0ZWQgYnkgR3JlZyBNaXJza3kg YW5kIHBvc3RlZCB0byB0aGUgSUVURiByZXBvc2l0b3J5Lg0KDQpOYW1lOgkJZHJhZnQtbWlyc2t5 LW1wbHMtYmZkLWRpcmVjdGVkDQpSZXZpc2lvbjoJMDINClRpdGxlOgkJQmlkaXJlY3Rpb25hbCBG b3J3YXJkaW5nIERldGVjdGlvbiAoQkZEKSBEaXJlY3RlZCBSZXR1cm4gUGF0aA0KRG9jdW1lbnQg ZGF0ZToJMjAxNS0wMi0xMg0KR3JvdXA6CQlJbmRpdmlkdWFsIFN1Ym1pc3Npb24NClBhZ2VzOgkJ MTANClVSTDogICAgICAgICAgICBodHRwOi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy9k cmFmdC1taXJza3ktbXBscy1iZmQtZGlyZWN0ZWQtMDIudHh0DQpTdGF0dXM6ICAgICAgICAgaHR0 cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtbWlyc2t5LW1wbHMtYmZkLWRpcmVj dGVkLw0KSHRtbGl6ZWQ6ICAgICAgIGh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LW1p cnNreS1tcGxzLWJmZC1kaXJlY3RlZC0wMg0KRGlmZjogICAgICAgICAgIGh0dHA6Ly93d3cuaWV0 Zi5vcmcvcmZjZGlmZj91cmwyPWRyYWZ0LW1pcnNreS1tcGxzLWJmZC1kaXJlY3RlZC0wMg0KDQpB YnN0cmFjdDoNCiAgIEJpZGlyZWN0aW9uYWwgRm9yd2FyZGluZyBEZXRlY3Rpb24gKEJGRCkgaXMg ZXhwZWN0ZWQgdG8gbW9uaXRvciBiaS0NCiAgIGRpcmVjdGlvbmFsIHBhdGhzLiAgV2hlbiBhIEJG RCBzZXNzaW9uIG1vbml0b3JzIGluIGl0cyBmb3J3YXJkDQogICBkaXJlY3Rpb24gYW4gZXhwbGlj aXRseSByb3V0ZWQgcGF0aCB0aGVyZSBpcyBhIG5lZWQgdG8gYmUgYWJsZSB0bw0KICAgZGlyZWN0 IGZhci1lbmQgQkZEIHBlZXIgdG8gdXNlIHNwZWNpZmljIHBhdGggYXMgcmV2ZXJzZSBkaXJlY3Rp b24gb2YNCiAgIHRoZSBCRkQgc2Vzc2lvbi4NCg0KICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIA0K DQoNClBsZWFzZSBub3RlIHRoYXQgaXQgbWF5IHRha2UgYSBjb3VwbGUgb2YgbWludXRlcyBmcm9t IHRoZSB0aW1lIG9mIHN1Ym1pc3Npb24gdW50aWwgdGhlIGh0bWxpemVkIHZlcnNpb24gYW5kIGRp ZmYgYXJlIGF2YWlsYWJsZSBhdCB0b29scy5pZXRmLm9yZy4NCg0KVGhlIElFVEYgU2VjcmV0YXJp YXQNCg0K From nobody Tue Feb 24 08:16:36 2015 Return-Path: X-Original-To: spring@ietfa.amsl.com Delivered-To: spring@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A3741A1B34 for ; Tue, 24 Feb 2015 08:16:34 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.999 X-Spam-Level: X-Spam-Status: No, score=-101.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 DG0E4Q639eeJ for ; Tue, 24 Feb 2015 08:16:33 -0800 (PST) Received: from mail-oi0-x22a.google.com (mail-oi0-x22a.google.com [IPv6:2607:f8b0:4003:c06::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1A54E1A1A25 for ; Tue, 24 Feb 2015 08:16:33 -0800 (PST) Received: by mail-oi0-f42.google.com with SMTP id h136so20122275oig.1 for ; Tue, 24 Feb 2015 08:16:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=hjeR3/uQophhmdknso2rFzzB6ik82wWfbWOgCV93pSw=; b=V67pNAML5qSUyhYFuXFm4uDPG71vQHR52sIp+NhA28P3w551HRgrWV/1bOBeJ7kprO +5TAd2YoU5cOKFmfvd+ivwc4RZFR6F97uj3p/Xef2zEvFuygYPZL0jHqViwL1ZH4WXAR YPR1saMLIKh41E29pOjR31rv6cisAYzZyfqf7R35R8e/KLXUlI5RL/aue1Ak+Jt+7W2x kMFvrVuxFE1VTZ4IYii9LjOge9Lp34RjQty8wUGQzD57mW/dvmizVT8JLXEEJTrwlzgG dyGNw8nFUZC+Lat0K01R79y9fDm0JjQKIeJkeXwkaopT4w46MdO2lW2501L+tRm35Sl7 IjMw== MIME-Version: 1.0 X-Received: by 10.202.102.158 with SMTP id m30mr11156445oik.22.1424794592464; Tue, 24 Feb 2015 08:16:32 -0800 (PST) Received: by 10.60.94.20 with HTTP; Tue, 24 Feb 2015 08:16:28 -0800 (PST) Date: Tue, 24 Feb 2015 11:16:28 -0500 Message-ID: From: Alia Atlas To: "spring@ietf.org" Content-Type: multipart/alternative; boundary=001a114098ec8fd45d050fd7d7e5 Archived-At: Cc: Bruno Decraene Subject: [spring] SPRING chairs X-BeenThere: spring@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "Stacked Tunnels for Source Routing \(STATUS\)." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Feb 2015 16:16:34 -0000 --001a114098ec8fd45d050fd7d7e5 Content-Type: text/plain; charset=UTF-8 Hi SPRING, >From Weds evening of IETF-92, Alvaro will be serving as Routing AD so it isn't appropriate for him to continue to chair a WG in the Routing Area. Thus, Alvaro is stepping down as co-chair of SPRING. I really appreciate the hard work that Alvaro has done as SPRING co-chair. I have consulted with Alvaro, Deborah, Adrian, and John Scudder, and have decided to appoint Bruno DeCraene to serve in this role. Bruno will be busy ramping up. I expect the handover to be finished in Dallas. Bruno can be reached at . Thanks, Alia --001a114098ec8fd45d050fd7d7e5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi SPRING,

From Weds evening of IETF-92, Alvaro will be servi= ng as Routing AD so it isn't appropriate for him to continue to chair a= WG in the Routing Area.=C2=A0 Thus, Alvaro is stepping down as co-chair of= SPRING.=C2=A0 I really appreciate the hard work that Alvaro has done as SP= RING co-chair.

<= div style=3D"font-size:12.8000001907349px">I have consulted with Alvaro, De= borah, Adrian, and John Scudder, and have decided to appoint Bruno DeCraene= to serve in this role.=C2=A0 Bruno will be busy ramping up.=C2=A0 I expect= the handover to be finished in Dallas.

Bruno c= an be reached at=C2=A0<brun= o.decraene@orange.com>.

Thanks,
Alia
--001a114098ec8fd45d050fd7d7e5-- From nobody Thu Feb 26 06:03:01 2015 Return-Path: X-Original-To: spring@ietfa.amsl.com Delivered-To: spring@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3EFBE1A0123 for ; Thu, 26 Feb 2015 06:02:59 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.901 X-Spam-Level: X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 NTELEjzGOLYM for ; Thu, 26 Feb 2015 06:02:57 -0800 (PST) Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1on0777.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::777]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6C8911A0154 for ; Thu, 26 Feb 2015 06:02:56 -0800 (PST) Received: from BY1PR0501MB1240.namprd05.prod.outlook.com (25.160.200.139) by BY1PR0501MB1239.namprd05.prod.outlook.com (25.160.200.13) with Microsoft SMTP Server (TLS) id 15.1.93.16; Thu, 26 Feb 2015 14:02:38 +0000 Received: from BY1PR0501MB1240.namprd05.prod.outlook.com ([25.160.200.139]) by BY1PR0501MB1240.namprd05.prod.outlook.com ([25.160.200.139]) with mapi id 15.01.0093.004; Thu, 26 Feb 2015 14:02:38 +0000 From: Pushpasis Sarkar To: Alia Atlas , "spring@ietf.org" Thread-Topic: [spring] SPRING chairs Thread-Index: AQHQUPIFSOoSXu4+5E6VWRaTJbMIng== Date: Thu, 26 Feb 2015 14:02:38 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.4.8.150116 x-originating-ip: [116.197.184.10] authentication-results: spf=none (sender IP is ) smtp.mailfrom=psarkar@juniper.net; x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:BY1PR0501MB1239; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:; x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:; SRVR:BY1PR0501MB1239; x-forefront-prvs: 0499DAF22A x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(189002)(377454003)(164054003)(199003)(50986999)(54356999)(2900100001)(105586002)(76176999)(46102003)(2656002)(68736005)(87936001)(106116001)(102836002)(2950100001)(2501003)(99286002)(106356001)(62966003)(77156002)(92566002)(36756003)(122556002)(83506001)(40100003)(5880100001)(19580405001)(97736003)(19580395003)(101416001)(16236675004)(64706001)(66066001)(86362001); DIR:OUT; SFP:1102; SCL:1; SRVR:BY1PR0501MB1239; H:BY1PR0501MB1240.namprd05.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts) Content-Type: multipart/alternative; boundary="_000_D113B50221173psarkarjunipernet_" MIME-Version: 1.0 X-OriginatorOrg: juniper.net X-MS-Exchange-CrossTenant-originalarrivaltime: 26 Feb 2015 14:02:38.2368 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4 X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY1PR0501MB1239 Archived-At: Cc: Bruno Decraene Subject: Re: [spring] SPRING chairs X-BeenThere: spring@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "Stacked Tunnels for Source Routing \(STATUS\)." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Feb 2015 14:02:59 -0000 --_000_D113B50221173psarkarjunipernet_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Bruno, Many many congratulations to you for the new role!!! Regards -Pushpasis From: Alia Atlas > Date: Tuesday, February 24, 2015 at 9:46 PM To: "spring@ietf.org" > Cc: Bruno Decraene > Subject: [spring] SPRING chairs Hi SPRING, >From Weds evening of IETF-92, Alvaro will be serving as Routing AD so it is= n't appropriate for him to continue to chair a WG in the Routing Area. Thu= s, Alvaro is stepping down as co-chair of SPRING. I really appreciate the = hard work that Alvaro has done as SPRING co-chair. I have consulted with Alvaro, Deborah, Adrian, and John Scudder, and have d= ecided to appoint Bruno DeCraene to serve in this role. Bruno will be busy= ramping up. I expect the handover to be finished in Dallas. Bruno can be reached at >. Thanks, Alia --_000_D113B50221173psarkarjunipernet_ Content-Type: text/html; charset="us-ascii" Content-ID: <1A90E393548D8D49B611949E96648F22@namprd05.prod.outlook.com> Content-Transfer-Encoding: quoted-printable
Hi Bruno,

Many many congratulations to you for the new role!!!

Regards
-Pushpasis

From: Alia Atlas <akatlas@gmail.com>
Date: Tuesday, February 24, 2015 at= 9:46 PM
To: "spring@ietf.org" <= spring@ietf.org>
Cc: Bruno Decraene <bruno.decraene@orange.com>
Subject: [spring] SPRING chairs

Hi SPRING,

From Weds evening of IETF-92, A= lvaro will be serving as Routing AD so it isn't appropriate for him to cont= inue to chair a WG in the Routing Area.  Thus, Alvaro is stepping down= as co-chair of SPRING.  I really appreciate the hard work that Alvaro has done as SPRING co-chair.

I have consulted with Alvaro, D= eborah, Adrian, and John Scudder, and have decided to appoint Bruno DeCraen= e to serve in this role.  Bruno will be busy ramping up.  I expec= t the handover to be finished in Dallas.

Bruno can be reached at &l= t;bruno.decraene@orange.com>.

Thanks,
Alia
 --_000_D113B50221173psarkarjunipernet_--