[OSPF] Fwd: Status BOF in Berlin

Stewart Bryant <stbryant@cisco.com> Fri, 21 June 2013 14:39 UTC

Return-Path: <stbryant@cisco.com>
X-Original-To: ospf@ietfa.amsl.com
Delivered-To: ospf@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 03D2521F9BDB; Fri, 21 Jun 2013 07:39:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.383
X-Spam-Status: No, score=-110.383 tagged_above=-999 required=5 tests=[AWL=0.215, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id faByYFTegINx; Fri, 21 Jun 2013 07:39:09 -0700 (PDT)
Received: from ams-iport-4.cisco.com (ams-iport-4.cisco.com []) by ietfa.amsl.com (Postfix) with ESMTP id B7B8C11E8193; Fri, 21 Jun 2013 07:39:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8857; q=dns/txt; s=iport; t=1371825548; x=1373035148; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to; bh=SZPcSEOoxK3ukKiU5hTJ1TDWrdeF6yPnSvZladOuWK4=; b=ZaPNa+t/BTz+JKpqtEOMviC0zBmDJ6M81l9xuTn5/uQrsZIVLlAClnsW Ovls2DwBkrjSKFtWu7gS4H9F1dTReCNgUJUYhtzp2syr9mG/9fla9XWR+ tYm+y1pSqJ7jwGmhP+vNqtXrAxVzeoO7w/Db6GXAVbNMTR/LZKLEidRh/ A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos; i="4.87,913,1363132800"; d="scan'208,217"; a="14893308"
Received: from ams-core-4.cisco.com ([]) by ams-iport-4.cisco.com with ESMTP; 21 Jun 2013 14:39:06 +0000
Received: from cisco.com (mrwint.cisco.com []) by ams-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r5LEd4u6025782 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 21 Jun 2013 14:39:04 GMT
Received: from [IPv6:::1] (localhost []) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id r5LEd3hm025510; Fri, 21 Jun 2013 15:39:03 +0100 (BST)
Message-ID: <51C46587.3020907@cisco.com>
Date: Fri, 21 Jun 2013 15:39:03 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: isis-wg <isis-wg@ietf.org>, "ospf@ietf.org" <ospf@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>, 6man@ietf.org
References: <51C352CA.6000307@cisco.com>
In-Reply-To: <51C352CA.6000307@cisco.com>
X-Forwarded-Message-Id: <51C352CA.6000307@cisco.com>
Content-Type: multipart/alternative; boundary="------------080101000407060509050103"
Cc: ops-area@ietf.org
Subject: [OSPF] Fwd: Status BOF in Berlin
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ospf>, <mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ospf>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Jun 2013 14:39:14 -0000

This BOF touches on technology of interest to each of the
working groups on the "To" list.

I apologies to those that have already seen this through
circulation to routing-discussion, but I know that not
everyone is subscribed there.

The list for discussion of this topic is status@ietf.org

- Stewart

-------- Original Message --------
Subject: 	Status BOF in Berlin
Date: 	Thu, 20 Jun 2013 20:06:50 +0100
From: 	Stewart Bryant <stbryant@cisco.com>
Reply-To: 	stbryant@cisco.com
To: 	routing-discussion@ietf.org
CC: 	status@ietf.org


  * Name: Stacked Tunnels for Source Routing (STATUS) [Was TUBAS]
  * Status: Approved
  * Description

    The IETF has two packet-based forwarding technologies: IP and MPLS.

    IP previously had a source-based routing mechanism made available
    through an IP Option. This mechanism has, however, not been widely
    used and has a number of issues that make its use inadvisable, and
    other mechanisms (such as RFC 1940
    <http://tools.ietf.org/html/rfc1940>) do not appear to have been
    implemented at all.

    The ability of a router to influence or control the forwarding path
    of an individual packet or all the packets of a given Forwarding
    Equivalence Class (FEC) is a desirable feature for a number of
    reasons including Label Switched Path stitching, egress protection,
    explicit routing, egress ASBR link selection, and backup (bypass
    tunnels, Remote Loop-Free Alternates) routing. This can be achieved
    by facilitating source-initiated selection of routes to complement
    the route selection provided by existing routing protocols for both
    inter- domain and intra-domain routes.

    Historically, distribution of MPLS label binding information was
    done by relying on label distribution protocols such as LDP and

    Several new proposals have been made to make use of the MPLS
    forwarding plane in novel but backward-compatible ways, and to
    install forwarding instructions using information distributed by the
    IGP running in the network, or through the management plane. It has
    been suggested that similar mechanisms might also be applied in IPv6.

    This BoF is intended to discuss the practicalities of various use
    cases and to establish a consensus around the problem space and
    desirability of developing solutions in this area with a view to
    determining whether the IETF should have a Working Group on this topic.

  * Responsible Area Directors: Adrian Farrel and Stewart Bryant
  * BoF Chairs: Alvaro Retana, John Scudder

  * Mailing list: https://www.ietf.org/mailman/listinfo/status

Further details can be found  at http://trac.tools.ietf.org/bof/trac/wiki

- Stewart