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

Mark Townsley <mark@townsley.net> Tue, 03 September 2013 16:48 UTC

Return-Path: <mark@townsley.net>
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 7C79121E8185 for <status@ietfa.amsl.com>; Tue, 3 Sep 2013 09:48:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.449
X-Spam-Level:
X-Spam-Status: No, score=-3.449 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 Ju3M2rosNKVl for <status@ietfa.amsl.com>; Tue, 3 Sep 2013 09:48:07 -0700 (PDT)
Received: from mail-ea0-f171.google.com (mail-ea0-f171.google.com [209.85.215.171]) by ietfa.amsl.com (Postfix) with ESMTP id 7F7E821E817C for <status@ietf.org>; Tue, 3 Sep 2013 09:48:06 -0700 (PDT)
Received: by mail-ea0-f171.google.com with SMTP id n15so3133321ead.30 for <status@ietf.org>; Tue, 03 Sep 2013 09:47:51 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:content-transfer-encoding:message-id:references:to; bh=G9i8/qo5xi7Z98Ng/7p6dnkcpln34hf+BZLxYyULjS0=; b=EPIu9AUn3+GCeVR+3+l/M/b3WAj3fo4MeVonCMbIyq1kWgoMUnsVcPzomvBJQt0g4V VN1P12xwdhEGWOtPaF/STZYcFQBYyRUEEVKevjBE6LY5wv61mAG8MAeWffuhEOEcIVMt UsAuW5tTdHzHHOfNo89UIMjltsvtSJG6Utxn6drGPndRGL+VmD74CK4quUNf+Lc2f916 8HeTAbw2FRP4zuuK070FQRAvGwVO1qVQe8T3BwMQ7Xyffs5HdD0DrEfORKygSsxP3qhb aSAfQIRk53X7nZdBzEODr0BMxBKYV/dAuz0/hH+/Q+O8cK0l3/7oPCcH4exigupZfhPQ Z5xw==
X-Gm-Message-State: ALoCoQnFLQcv6vYACRf3k0VdiRYNTy6Jj3DV9sHKQV1FTLpOiY+mPzmOnJcBdpixDN29CzrsTPsU
X-Received: by 10.14.184.3 with SMTP id r3mr6345533eem.49.1378226869787; Tue, 03 Sep 2013 09:47:49 -0700 (PDT)
Received: from ams-townsley-8913.cisco.com (173-38-208-169.cisco.com. [173.38.208.169]) by mx.google.com with ESMTPSA id f49sm32932097eec.7.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 03 Sep 2013 09:47:49 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Apple Message framework v1283)
From: Mark Townsley <mark@townsley.net>
In-Reply-To: <20130903153538.BD19618C1B8@mercury.lcs.mit.edu>
Date: Tue, 03 Sep 2013 18:47:48 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <C6190794-1904-4075-83B5-210AB4BB00AF@townsley.net>
References: <20130903153538.BD19618C1B8@mercury.lcs.mit.edu>
To: status@ietf.org
X-Mailer: Apple Mail (2.1283)
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 16:48:12 -0000

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