IETF Logo Mail Archive

Re: [Status] Summary of STATUS BOF and the next steps

"Carlos Pignataro (cpignata)" <cpignata@cisco.com> Tue, 03 September 2013 17:18 UTC

Return-Path: <cpignata@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 131AE21E804B for <status@ietfa.amsl.com>; Tue, 3 Sep 2013 10:18:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.549
X-Spam-Level:
X-Spam-Status: No, score=-110.549 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 dhbVXHvVtz+v for <status@ietfa.amsl.com>; Tue, 3 Sep 2013 10:18:01 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id 7C26111E80F8 for <status@ietf.org>; Tue, 3 Sep 2013 10:18:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3245; q=dns/txt; s=iport; t=1378228681; x=1379438281; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=C1UiX8q01VdKsdJ+86Pb1ganwdbpohjCcQpbPIQjXcs=; b=ShJN7hHJ4YDbVI+kCornRwrMuWwx9LVTwUl/i7yIkm9mE2spDTNug3Qz VNcCBUVY7T6h6x1JZvkB7ZbtNhGA4CzPqqP7C4yRa0LqHN3WwuyLWBYiA mHrRaN2dbA1rAptojPOjZKURS/XXl6ktGRKl9cupdTGQYWgjxyk40Vj4e A=;
X-Files: signature.asc : 203
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhIFAOYYJlKtJXG+/2dsb2JhbABbgwc1UcB6gS4WdIIkAQEBAwEBAQFrCxACAQgVAwokJwslAgQOBQgGh24GDKxSjESPRTEHAoMbgQADkCOBLpgKgyCCKg
X-IronPort-AV: E=Sophos; i="4.89,1015,1367971200"; d="asc'?scan'208"; a="255042997"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by rcdn-iport-5.cisco.com with ESMTP; 03 Sep 2013 17:18:01 +0000
Received: from xhc-rcd-x13.cisco.com (xhc-rcd-x13.cisco.com [173.37.183.87]) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id r83HI0AP005499 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 3 Sep 2013 17:18:00 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.15]) by xhc-rcd-x13.cisco.com ([173.37.183.87]) with mapi id 14.02.0318.004; Tue, 3 Sep 2013 12:18:00 -0500
From: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
To: Mark Townsley <mark@townsley.net>
Thread-Topic: [Status] Summary of STATUS BOF and the next steps
Thread-Index: AQHOqLs9HivemM8DHkmVsz4P2sv2M5m0jP8AgAAIcAA=
Date: Tue, 03 Sep 2013 17:18:00 +0000
Message-ID: <95067C434CE250468B77282634C96ED325E8ECA6@xmb-aln-x02.cisco.com>
References: <20130903153538.BD19618C1B8@mercury.lcs.mit.edu> <C6190794-1904-4075-83B5-210AB4BB00AF@townsley.net>
In-Reply-To: <C6190794-1904-4075-83B5-210AB4BB00AF@townsley.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.117.115.54]
Content-Type: multipart/signed; boundary="Apple-Mail=_13E9F7E0-CD4F-4BC4-96E6-76F6925B88B6"; protocol="application/pgp-signature"; micalg="pgp-sha1"
MIME-Version: 1.0
Cc: "<status@ietf.org>" <status@ietf.org>
Subject: Re: [Status] Summary of STATUS BOF and the next steps
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: Tue, 03 Sep 2013 17:18:06 -0000

This is another datapoint against using "source routing" -- the term is overloaded with multiple meanings and history including "providing routing information at the source", use of SRR options, and "making a routing decision based on a source address".

"Segment Routing" is simple and captures the essence of the work (including non explicit -- meaning IGP selected -- paths).

Thanks,

-- Carlos.

On Sep 3, 2013, at 12:47 PM, Mark Townsley <mark@townsley.net> wrote:

> 
> For those who might not be aware, the homenet WG has been actively working on "source and destination routing" (SADR) techniques to solve the routing problem facing a multi-router, multi-homed, multi-prefix, IPv6 home network:
> 
> A few refs:
> 
> draft-troan-homenet-sadr
> draft-baker-ipv6-ospf-dst-src-routing
> draft-baker-ipv6-isis-dst-src-routing
> draft-boutier-homenet-source-specific-routing
> draft-baker-rtgwg-src-dst-routing-use-cases
> 
> We're working with the ADs on where to advance this, including the possibility of the rtgwg (hence baker's rtgwg document listed above). Whatever ends up coming out of homenet, rtgwg, and the WG that is forming here, we should aim to be very clear what is what. 
> 
> - Mark
> 
> P.S. Another ref, just for kicks: http://www.youtube.com/watch?v=3Omg1lJ6EQI
> 
> 
> On Sep 3, 2013, at 5:35 PM, Noel Chiappa wrote:
> 
>>> From: AshwoodsmithPeter <Peter.AshwoodSmith@huawei.com>
>> 
>>> We are revisiting source routing with new concepts. 
>> 
>> The problem is that "source routing" seems, by the time you do the set-or of
>> all the various meanings that people apply to it, to basically mean "not
>> hop-by-hop routing".
>> 
>> The problem, therefore, with calling something "source routing" is that it's
>> like me calling myself "Not Peter Ashwood-Smith". The problem is that there
>> are a lot of people whose name is "Not Peter Ashwood-Smith", so it's really a
>> pretty useless name.
>> 
>> Similarly, saying that something is "source routing" really tells you very
>> little about it - except that it's not hop-by-hop. So let's find a different,
>> and actually meaningful, name.
>> 
>> 	Noel
>> _______________________________________________
>> status mailing list
>> status@ietf.org
>> https://www.ietf.org/mailman/listinfo/status
> 
> _______________________________________________
> status mailing list
> status@ietf.org
> https://www.ietf.org/mailman/listinfo/status

v2.23.0 | Report a Bug | By Email