
Return-Path: <nobo@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 D169911E81C3 for <status@ietfa.amsl.com>; Wed, 13 Nov 2013 10:33:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.572
X-Spam-Level: 
X-Spam-Status: No, score=-10.572 tagged_above=-999 required=5 tests=[AWL=0.027, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 H+gcWBPgWcpd for <status@ietfa.amsl.com>; Wed, 13 Nov 2013 10:33:18 -0800 (PST)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id AC69811E81C4 for <status@ietf.org>; Wed, 13 Nov 2013 10:33:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1255; q=dns/txt; s=iport; t=1384367599; x=1385577199; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=5zk+aK6lq5H8SgiFVJLCYO6ioVBtG1E6IoQsL+tDPaA=; b=b0b7LjlQCejwpB7Ua0v7OqYJ0fdjyOvOd9PXm/ntBCniIw3Uep1CXgc/ gmVjCTUsH+y4jWzFA00H0EYytMIRrJlRq3op2FPq5udaeluXo1DShKGIt FGNS2bnZZOnjRVJnnOeLU2AqIPHNtu6yvwT1++DLhpqUbvrogz6w+Pgy5 A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag4FAG3Fg1KtJXHA/2dsb2JhbABbgmYhOFO+YEuBJhZ0giUBAQEEAQEBGh00CwwEAgEIEQQBAQEKFAkHJwsUCQgCBAENBQiHeQEMwAwEjy4xBwaDGoERA6obgWqBPoIq
X-IronPort-AV: E=Sophos;i="4.93,693,1378857600"; d="scan'208";a="284398472"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-3.cisco.com with ESMTP; 13 Nov 2013 18:33:18 +0000
Received: from xhc-aln-x08.cisco.com (xhc-aln-x08.cisco.com [173.36.12.82]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id rADIXHf8014092 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 13 Nov 2013 18:33:18 GMT
Received: from xmb-aln-x01.cisco.com ([fe80::747b:83e1:9755:d453]) by xhc-aln-x08.cisco.com ([173.36.12.82]) with mapi id 14.03.0123.003; Wed, 13 Nov 2013 12:33:17 -0600
From: "Nobo Akiya (nobo)" <nobo@cisco.com>
To: "Alvaro Retana (aretana)" <aretana@cisco.com>, "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>, "status@ietf.org" <status@ietf.org>
Thread-Topic: [Status] request to move draft-filsfils-rtgwg-segment-routing-use-cases-02 to wg item
Thread-Index: AQHO23E8p83WlqlDLUO90VPM+v9VCJog77WAgAKXAIA=
Date: Wed, 13 Nov 2013 18:33:17 +0000
Message-ID: <CECE764681BE964CBE1DFF78F3CDD3941DEE454B@xmb-aln-x01.cisco.com>
References: <947081B7-F174-4C4D-BE12-56F4FC3A12A8@cisco.com> <CEA6F54D.40EDD%aretana@cisco.com>
In-Reply-To: <CEA6F54D.40EDD%aretana@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [161.44.213.104]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "John G. Scudder" <jgs@juniper.net>, "Clarence Filsfils \(cfilsfil\)" <cfilsfil@cisco.com>
Subject: Re: [Status] request to move draft-filsfils-rtgwg-segment-routing-use-cases-02 to wg item
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: Wed, 13 Nov 2013 18:33:24 -0000

Support.

-Nobo

> -----Original Message-----
> From: status-bounces@ietf.org [mailto:status-bounces@ietf.org] On Behalf
> Of Alvaro Retana (aretana)
> Sent: Monday, November 11, 2013 9:00 PM
> To: Stefano Previdi (sprevidi); status@ietf.org
> Cc: John G. Scudder; Clarence Filsfils (cfilsfil)
> Subject: Re: [Status] request to move draft-filsfils-rtgwg-segment-routin=
g-
> use-cases-02 to wg item
>=20
> On 11/6/13 10:24 PM, "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
> wrote:
>=20
> Stefano:
>=20
> >according to what discussed after the presentation of SR Use Cases at
> >ietf88 spring-wg meeting, I'd like to request the adoption of
> >draft-filsfils-rtgwg-segment-routing-use-cases-02.txt as wg item.
>=20
> I believe there was support for adoption at the meeting in Vancouver..but
> we will still have to confirm it here on the list.
>=20
> List: This message officially starts the call for adoption.  Please indic=
ate your
> position about adopting this use cases draft.  The call will close on Fri=
day,
> November 22, 2013.
>=20
> Thanks!
>=20
> Alvaro.
>=20
> _______________________________________________
> status mailing list
> status@ietf.org
> https://www.ietf.org/mailman/listinfo/status

Return-Path: <saalvare@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 712C221E8096 for <status@ietfa.amsl.com>; Wed, 13 Nov 2013 10:13:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 dW1NWQrL+VMM for <status@ietfa.amsl.com>; Wed, 13 Nov 2013 10:13:54 -0800 (PST)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id D93BC11E8126 for <status@ietf.org>; Wed, 13 Nov 2013 10:13:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1237; q=dns/txt; s=iport; t=1384366431; x=1385576031; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=1yW1QOwJRSUyOH1M6kEo+Gf5S6WpOwOHDwHFAG2lH2o=; b=ICn5YPFbGAtnMppMxJ86O756ro8yY5XwGP/lY6SNhiLFmMRgXe/MzYK4 H/tbv7nX2tAFXpB29JyYYMHgH5ZFd3sm4awcKE3TbbNr6U5GCEkIsZ6H+ HU8PiJ33dr1Y5fCpePNvB/mNtOZV8QacDezqVdvZ5cji0UweENf3cmsX4 w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag0FABLAg1KtJXG8/2dsb2JhbABbgwc4U75gS4EmFnSCJQEBAQQBAQEaHTQLDAQCAQgRBAEBAQoUCQcnCxQJCAIEAQ0FCId5DcARBI8uMQcGgxqBEQOqG4FqgT6CKg
X-IronPort-AV: E=Sophos;i="4.93,693,1378857600"; d="scan'208";a="284171981"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-1.cisco.com with ESMTP; 13 Nov 2013 18:13:50 +0000
Received: from xhc-aln-x04.cisco.com (xhc-aln-x04.cisco.com [173.36.12.78]) by rcdn-core2-1.cisco.com (8.14.5/8.14.5) with ESMTP id rADIDoM0016223 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 13 Nov 2013 18:13:50 GMT
Received: from xmb-aln-x09.cisco.com ([169.254.4.234]) by xhc-aln-x04.cisco.com ([173.36.12.78]) with mapi id 14.03.0123.003; Wed, 13 Nov 2013 12:13:50 -0600
From: "Santiago Alvarez (saalvare)" <saalvare@cisco.com>
To: "Alvaro Retana (aretana)" <aretana@cisco.com>, "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>, "status@ietf.org" <status@ietf.org>
Thread-Topic: [Status] request to move draft-filsfils-rtgwg-segment-routing-use-cases-02 to wg item
Thread-Index: AQHO23E8p83WlqlDLUO90VPM+v9VCJog77WAgAKQOgA=
Date: Wed, 13 Nov 2013 18:13:49 +0000
Message-ID: <0C8935EE66D53445A3D3982BD9BE54682134EDFC@xmb-aln-x09.cisco.com>
References: <947081B7-F174-4C4D-BE12-56F4FC3A12A8@cisco.com> <CEA6F54D.40EDD%aretana@cisco.com>
In-Reply-To: <CEA6F54D.40EDD%aretana@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [128.107.163.99]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "John G. Scudder" <jgs@juniper.net>, "Clarence Filsfils \(cfilsfil\)" <cfilsfil@cisco.com>, "Santiago Alvarez \(saalvare\)" <saalvare@cisco.com>
Subject: Re: [Status] request to move draft-filsfils-rtgwg-segment-routing-use-cases-02 to wg item
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: Wed, 13 Nov 2013 18:13:59 -0000

Support.

> -----Original Message-----
> From: status-bounces@ietf.org [mailto:status-bounces@ietf.org] On
> Behalf Of Alvaro Retana (aretana)
> Sent: Monday, November 11, 2013 6:00 PM
> To: Stefano Previdi (sprevidi); status@ietf.org
> Cc: John G. Scudder; Clarence Filsfils (cfilsfil)
> Subject: Re: [Status] request to move draft-filsfils-rtgwg-segment-
> routing-use-cases-02 to wg item
>=20
> On 11/6/13 10:24 PM, "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
> wrote:
>=20
> Stefano:
>=20
> >according to what discussed after the presentation of SR Use Cases at
> >ietf88 spring-wg meeting, I'd like to request the adoption of
> >draft-filsfils-rtgwg-segment-routing-use-cases-02.txt as wg item.
>=20
> I believe there was support for adoption at the meeting in
> Vancouver..but we will still have to confirm it here on the list.
>=20
> List: This message officially starts the call for adoption.  Please
> indicate your position about adopting this use cases draft.  The call
> will close on Friday, November 22, 2013.
>=20
> Thanks!
>=20
> Alvaro.
>=20
> _______________________________________________
> status mailing list
> status@ietf.org
> https://www.ietf.org/mailman/listinfo/status


Return-Path: <rjs@rob.sh>
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 9C2A721E80A7 for <status@ietfa.amsl.com>; Wed, 13 Nov 2013 01:56:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 aXBRCN8MQUj7 for <status@ietfa.amsl.com>; Wed, 13 Nov 2013 01:56:46 -0800 (PST)
Received: from cappuccino.rob.sh (cappuccino.rob.sh [IPv6:2001:b98:201:101::10:cafe]) by ietfa.amsl.com (Postfix) with ESMTP id F3D2221E809D for <status@ietf.org>; Wed, 13 Nov 2013 01:56:45 -0800 (PST)
Received: from [31.55.43.98] (helo=[10.96.0.185]) by cappuccino.rob.sh with esmtpa (Exim 4.72) (envelope-from <rjs@rob.sh>) id 1VgXAH-0007wj-K0; Wed, 13 Nov 2013 09:55:13 +0000
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Rob Shakir <rjs@rob.sh>
In-Reply-To: <CEA6F54D.40EDD%aretana@cisco.com>
Date: Wed, 13 Nov 2013 09:56:45 +0000
Content-Transfer-Encoding: 7bit
Message-Id: <22117F29-FFEA-4267-9EA7-213513311468@rob.sh>
References: <CEA6F54D.40EDD%aretana@cisco.com>
To: "status@ietf.org" <status@ietf.org>
X-Mailer: Apple Mail (2.1510)
Subject: Re: [Status] request to move draft-filsfils-rtgwg-segment-routing-use-cases-02 to wg item
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: Wed, 13 Nov 2013 09:56:46 -0000

On 12 Nov 2013, at 02:00, Alvaro Retana (aretana) <aretana@cisco.com> wrote:

>> according to what discussed after the presentation of SR Use Cases at
>> ietf88 spring-wg meeting, I'd like to request the adoption of
>> draft-filsfils-rtgwg-segment-routing-use-cases-02.txt as wg item.
> 
> I believe there was support for adoption at the meeting in Vancouver..but
> we will still have to confirm it here on the list.
> 
> List: This message officially starts the call for adoption.  Please
> indicate your position about adopting this use cases draft.  The call will
> close on Friday, November 22, 2013.

Support as a co-author.

cheers,
r.


Return-Path: <bill.wu@huawei.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 2104021E80AC for <status@ietfa.amsl.com>; Tue, 12 Nov 2013 17:08:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.473
X-Spam-Level: 
X-Spam-Status: No, score=-5.473 tagged_above=-999 required=5 tests=[AWL=1.126,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 z58-+6Nvxz2p for <status@ietfa.amsl.com>; Tue, 12 Nov 2013 17:08:48 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 892EF11E8155 for <status@ietf.org>; Tue, 12 Nov 2013 17:08:47 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id AXU95021; Wed, 13 Nov 2013 01:08:01 +0000 (GMT)
Received: from LHREML404-HUB.china.huawei.com (10.201.5.218) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 13 Nov 2013 01:07:04 +0000
Received: from NKGEML408-HUB.china.huawei.com (10.98.56.39) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 13 Nov 2013 01:08:00 +0000
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.75]) by nkgeml408-hub.china.huawei.com ([10.98.56.39]) with mapi id 14.03.0158.001; Wed, 13 Nov 2013 09:07:54 +0800
From: Qin Wu <bill.wu@huawei.com>
To: "Alvaro Retana (aretana)" <aretana@cisco.com>, "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>, "status@ietf.org" <status@ietf.org>
Thread-Topic: [Status] request to move draft-filsfils-rtgwg-segment-routing-use-cases-02 to wg item
Thread-Index: AQHO23E8p83WlqlDLUO90VPM+v9VCJog77WAgAFy5QA=
Date: Wed, 13 Nov 2013 01:07:54 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA43C39C8F@nkgeml501-mbs.china.huawei.com>
References: <947081B7-F174-4C4D-BE12-56F4FC3A12A8@cisco.com> <CEA6F54D.40EDD%aretana@cisco.com>
In-Reply-To: <CEA6F54D.40EDD%aretana@cisco.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.138.41.149]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "John G. Scudder" <jgs@juniper.net>, "Clarence Filsfils \(cfilsfil\)" <cfilsfil@cisco.com>
Subject: Re: [Status] request to move draft-filsfils-rtgwg-segment-routing-use-cases-02 to wg item
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: Wed, 13 Nov 2013 01:08:52 -0000

Support.

-----Original Message-----
From: status-bounces@ietf.org [mailto:status-bounces@ietf.org] On Behalf Of=
 Alvaro Retana (aretana)
Sent: Tuesday, November 12, 2013 10:00 AM
To: Stefano Previdi (sprevidi); status@ietf.org
Cc: John G. Scudder; Clarence Filsfils (cfilsfil)
Subject: Re: [Status] request to move draft-filsfils-rtgwg-segment-routing-=
use-cases-02 to wg item

On 11/6/13 10:24 PM, "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
wrote:

Stefano:

>according to what discussed after the presentation of SR Use Cases at
>ietf88 spring-wg meeting, I'd like to request the adoption of
>draft-filsfils-rtgwg-segment-routing-use-cases-02.txt as wg item.

I believe there was support for adoption at the meeting in Vancouver..but
we will still have to confirm it here on the list.

List: This message officially starts the call for adoption.  Please
indicate your position about adopting this use cases draft.  The call will
close on Friday, November 22, 2013.

Thanks!

Alvaro.

_______________________________________________
status mailing list
status@ietf.org
https://www.ietf.org/mailman/listinfo/status


Return-Path: <robmgl@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 D4AF311E814D for <status@ietfa.amsl.com>; Tue, 12 Nov 2013 15:11:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
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 M5UxQYOy4gMm for <status@ietfa.amsl.com>; Tue, 12 Nov 2013 15:11:28 -0800 (PST)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id A27E011E8102 for <status@ietf.org>; Tue, 12 Nov 2013 15:11:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5094; q=dns/txt; s=iport; t=1384297886; x=1385507486; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=NgNJ/vaSKfxwmlcL0rCF0hbPIFPl0FUD/eH8mVUBLng=; b=Zs+scWxrY+Ak3QPygHPbQt6SMdfiwr86xa4Z+0E6jChuRrl2O0Te/4Ch //N/g4AuRZnMGuwmM8Bj/0yjQb7YFw/EibmnxXhZyl2Kj0CdeOadB+TP6 kt9TC3jySOgR9ApppXOVk7Sh2zF04tHYLVXEE51Z9eQyWzGwTOE3GtpAy A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlgFAFq0glKtJV2Z/2dsb2JhbABagwc4vy1LgSsWbQeCJQEBAQMBAQEBGlELBQsCAQgEFCcHIQYLFBECBA4Fh28DCQYNtTwNiWUEjG2CbgQHgyCBEQOWJIFrjFKFOIFogT4
X-IronPort-AV: E=Sophos;i="4.93,688,1378857600";  d="scan'208,217";a="283966872"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-8.cisco.com with ESMTP; 12 Nov 2013 23:11:26 +0000
Received: from xhc-aln-x14.cisco.com (xhc-aln-x14.cisco.com [173.36.12.88]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id rACNBQW8013750 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <status@ietf.org>; Tue, 12 Nov 2013 23:11:26 GMT
Received: from xmb-rcd-x01.cisco.com ([169.254.1.140]) by xhc-aln-x14.cisco.com ([173.36.12.88]) with mapi id 14.03.0123.003; Tue, 12 Nov 2013 17:11:25 -0600
From: "Roberta Maglione (robmgl)" <robmgl@cisco.com>
To: "status@ietf.org" <status@ietf.org>
Thread-Topic: [Status] request to move draft-filsfils-rtgwg-segment-routing-use-cases-02 to wg item
Thread-Index: AQHO38fjeOP3rBp2YkWNYXfPEzS5uJoiOXTs
Date: Tue, 12 Nov 2013 23:11:25 +0000
Message-ID: <2DC84F29-7011-4B1B-A354-F6EA21EFC7E0@cisco.com>
References: <CEA6F54D.40EDD%aretana@cisco.com> <5835D3B9-07D9-42D7-85E9-2626E757A3B1@gmail.com>, <CAAWndM2yXbt=Y6Vurp9c2MonSDByRiqz=_5iOKcGK4LC6sBGqg@mail.gmail.com>
In-Reply-To: <CAAWndM2yXbt=Y6Vurp9c2MonSDByRiqz=_5iOKcGK4LC6sBGqg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_2DC84F2970114B1BA354F6EA21EFC7E0ciscocom_"
MIME-Version: 1.0
Cc: "Alvaro Retana \(aretana\)" <aretana@cisco.com>, "Clarence Filsfils \(cfilsfil\)" <cfilsfil@cisco.com>, "Stefano Previdi \(sprevidi\)" <sprevidi@cisco.com>
Subject: Re: [Status] request to move draft-filsfils-rtgwg-segment-routing-use-cases-02 to wg item
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, 12 Nov 2013 23:11:33 -0000

--_000_2DC84F2970114B1BA354F6EA21EFC7E0ciscocom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Support.

Regards,
Roberta

Sent from my iPad

On 2013-11-12, at 11:54 AM, "Matt Anderson" <matt@mattanderson.net<mailto:m=
att@mattanderson.net>> wrote:

Support.



On Tue, Nov 12, 2013 at 11:15 AM, Christian Martin <christian.j.martin@gmai=
l.com<mailto:christian.j.martin@gmail.com>> wrote:
Support.

Cheers
-Chris

> On Nov 11, 2013, at 9:00 PM, "Alvaro Retana (aretana)" <aretana@cisco.com=
<mailto:aretana@cisco.com>> wrote:
>
> On 11/6/13 10:24 PM, "Stefano Previdi (sprevidi)" <sprevidi@cisco.com<mai=
lto:sprevidi@cisco.com>>
> wrote:
>
> Stefano:
>
>> according to what discussed after the presentation of SR Use Cases at
>> ietf88 spring-wg meeting, I'd like to request the adoption of
>> draft-filsfils-rtgwg-segment-routing-use-cases-02.txt as wg item.
>
> I believe there was support for adoption at the meeting in Vancouver..but
> we will still have to confirm it here on the list.
>
> List: This message officially starts the call for adoption.  Please
> indicate your position about adopting this use cases draft.  The call wil=
l
> close on Friday, November 22, 2013.
>
> Thanks!
>
> Alvaro.
>
> _______________________________________________
> status mailing list
> status@ietf.org<mailto:status@ietf.org>
> https://www.ietf.org/mailman/listinfo/status
_______________________________________________
status mailing list
status@ietf.org<mailto:status@ietf.org>
https://www.ietf.org/mailman/listinfo/status



--
Matt
_______________________________________________
status mailing list
status@ietf.org<mailto:status@ietf.org>
https://www.ietf.org/mailman/listinfo/status

--_000_2DC84F2970114B1BA354F6EA21EFC7E0ciscocom_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body dir=3D"auto">
<div>Support.</div>
<div><br>
</div>
<div>Regards,</div>
<div>Roberta<br>
<br>
Sent from my iPad</div>
<div><br>
On 2013-11-12, at 11:54 AM, &quot;Matt Anderson&quot; &lt;<a href=3D"mailto=
:matt@mattanderson.net">matt@mattanderson.net</a>&gt; wrote:<br>
<br>
</div>
<blockquote type=3D"cite">
<div>
<div dir=3D"ltr">Support.
<div><br>
</div>
</div>
<div class=3D"gmail_extra"><br>
<br>
<div class=3D"gmail_quote">On Tue, Nov 12, 2013 at 11:15 AM, Christian Mart=
in <span dir=3D"ltr">
&lt;<a href=3D"mailto:christian.j.martin@gmail.com" target=3D"_blank">chris=
tian.j.martin@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Support.<br>
<br>
Cheers<br>
-Chris<br>
<div class=3D"HOEnZb">
<div class=3D"h5"><br>
&gt; On Nov 11, 2013, at 9:00 PM, &quot;Alvaro Retana (aretana)&quot; &lt;<=
a href=3D"mailto:aretana@cisco.com">aretana@cisco.com</a>&gt; wrote:<br>
&gt;<br>
&gt; On 11/6/13 10:24 PM, &quot;Stefano Previdi (sprevidi)&quot; &lt;<a hre=
f=3D"mailto:sprevidi@cisco.com">sprevidi@cisco.com</a>&gt;<br>
&gt; wrote:<br>
&gt;<br>
&gt; Stefano:<br>
&gt;<br>
&gt;&gt; according to what discussed after the presentation of SR Use Cases=
 at<br>
&gt;&gt; ietf88 spring-wg meeting, I'd like to request the adoption of<br>
&gt;&gt; draft-filsfils-rtgwg-segment-routing-use-cases-02.txt as wg item.<=
br>
&gt;<br>
&gt; I believe there was support for adoption at the meeting in Vancouver..=
but<br>
&gt; we will still have to confirm it here on the list.<br>
&gt;<br>
&gt; List: This message officially starts the call for adoption. &nbsp;Plea=
se<br>
&gt; indicate your position about adopting this use cases draft. &nbsp;The =
call will<br>
&gt; close on Friday, November 22, 2013.<br>
&gt;<br>
&gt; Thanks!<br>
&gt;<br>
&gt; Alvaro.<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; status mailing list<br>
&gt; <a href=3D"mailto:status@ietf.org">status@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/status" target=3D"_bl=
ank">https://www.ietf.org/mailman/listinfo/status</a><br>
_______________________________________________<br>
status mailing list<br>
<a href=3D"mailto:status@ietf.org">status@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/status" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/status</a><br>
</div>
</div>
</blockquote>
</div>
<br>
<br clear=3D"all">
<div><br>
</div>
-- <br>
Matt </div>
</div>
</blockquote>
<blockquote type=3D"cite">
<div><span>_______________________________________________</span><br>
<span>status mailing list</span><br>
<span><a href=3D"mailto:status@ietf.org">status@ietf.org</a></span><br>
<span><a href=3D"https://www.ietf.org/mailman/listinfo/status">https://www.=
ietf.org/mailman/listinfo/status</a></span><br>
</div>
</blockquote>
</body>
</html>

--_000_2DC84F2970114B1BA354F6EA21EFC7E0ciscocom_--


Return-Path: <ginsberg@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 D30B521E80C9 for <status@ietfa.amsl.com>; Tue, 12 Nov 2013 14:16:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 R0AmGOA2GskK for <status@ietfa.amsl.com>; Tue, 12 Nov 2013 14:16:47 -0800 (PST)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id 0E71221E80AC for <status@ietf.org>; Tue, 12 Nov 2013 14:16:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1256; q=dns/txt; s=iport; t=1384294607; x=1385504207; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=nTOQpHe7Fr7W9Acv9mF0NnLlYdhv6w+hn+zjfgzZXNk=; b=U89r2TVnP6EHqcLqOBEN9NWw2UtqYiCV1zU6Mx9ikBWpuKecyFTwCIHv fqb3Um48+QPX34r9Lq9FBNTTs8CNStzSjngUtvtuu0eJHDtGKYKygysTX LuIw5bXTU0g0gAYA7vk/NBic+IKuhLpG/Hx3A5xU5XCLtebRFijzGg0nw U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhEFAHOoglKtJV2d/2dsb2JhbABagwc4U75aS4EqFnSCJQEBAQQBAQEaHTQXBAIBCBEEAQEBChQJBycLFAkIAgQBEgiHeQ2/OASPLjgGgxqBEQOqGYFogT6CKg
X-IronPort-AV: E=Sophos;i="4.93,688,1378857600"; d="scan'208";a="283927220"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-7.cisco.com with ESMTP; 12 Nov 2013 22:16:46 +0000
Received: from xhc-rcd-x11.cisco.com (xhc-rcd-x11.cisco.com [173.37.183.85]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id rACMGkGg032110 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <status@ietf.org>; Tue, 12 Nov 2013 22:16:46 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.229]) by xhc-rcd-x11.cisco.com ([173.37.183.85]) with mapi id 14.03.0123.003; Tue, 12 Nov 2013 16:16:46 -0600
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: "Alvaro Retana (aretana)" <aretana@cisco.com>, "status@ietf.org" <status@ietf.org>
Thread-Topic: [Status] request to move draft-filsfils-rtgwg-segment-routing-use-cases-02 to wg item
Thread-Index: AQHO23E8p83WlqlDLUO90VPM+v9VCJog77WAgAFDCcA=
Date: Tue, 12 Nov 2013 22:16:45 +0000
Message-ID: <F3ADE4747C9E124B89F0ED2180CC814F23BB4728@xmb-aln-x02.cisco.com>
References: <947081B7-F174-4C4D-BE12-56F4FC3A12A8@cisco.com> <CEA6F54D.40EDD%aretana@cisco.com>
In-Reply-To: <CEA6F54D.40EDD%aretana@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [128.107.163.140]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [Status] request to move draft-filsfils-rtgwg-segment-routing-use-cases-02 to wg item
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, 12 Nov 2013 22:16:55 -0000

Support.

   Les

> -----Original Message-----
> From: status-bounces@ietf.org [mailto:status-bounces@ietf.org] On Behalf =
Of
> Alvaro Retana (aretana)
> Sent: Monday, November 11, 2013 6:00 PM
> To: Stefano Previdi (sprevidi); status@ietf.org
> Cc: John G. Scudder; Clarence Filsfils (cfilsfil)
> Subject: Re: [Status] request to move draft-filsfils-rtgwg-segment-routin=
g-
> use-cases-02 to wg item
>=20
> On 11/6/13 10:24 PM, "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
> wrote:
>=20
> Stefano:
>=20
> >according to what discussed after the presentation of SR Use Cases at
> >ietf88 spring-wg meeting, I'd like to request the adoption of
> >draft-filsfils-rtgwg-segment-routing-use-cases-02.txt as wg item.
>=20
> I believe there was support for adoption at the meeting in Vancouver..but
> we will still have to confirm it here on the list.
>=20
> List: This message officially starts the call for adoption.  Please
> indicate your position about adopting this use cases draft.  The call wil=
l
> close on Friday, November 22, 2013.
>=20
> Thanks!
>=20
> Alvaro.
>=20
> _______________________________________________
> status mailing list
> status@ietf.org
> https://www.ietf.org/mailman/listinfo/status


Return-Path: <shtsuchi@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 28AE811E810C for <status@ietfa.amsl.com>; Tue, 12 Nov 2013 13:45:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 95dWVqmYzj96 for <status@ietfa.amsl.com>; Tue, 12 Nov 2013 13:45:46 -0800 (PST)
Received: from bgl-iport-2.cisco.com (bgl-iport-2.cisco.com [72.163.197.26]) by ietfa.amsl.com (Postfix) with ESMTP id 30A6711E8123 for <status@ietf.org>; Tue, 12 Nov 2013 13:45:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=931; q=dns/txt; s=iport; t=1384292746; x=1385502346; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=cju5IxK71ZPj4mtWnuOdZaID4D5hh753yhAw3sC7q6w=; b=dxucaFhREO7a7HbjbWVCZRI3WOIsghU45Iv2a396zbLYCzliGKY+ZjT5 4cZZRHXQoVp01NqjiT0JsC1aHsYbl+zGS595micjbvGIBDo4bCGw2ri8K C5ftG+8xyZQY8VL/CrRyC+XWnrvO3QSTCzgG12Kng3wfxaOCyylnsTUW6 8=;
X-IronPort-AV: E=Sophos;i="4.93,687,1378857600"; d="scan'208";a="36577064"
Received: from vla196-nat.cisco.com (HELO bgl-core-4.cisco.com) ([72.163.197.24]) by bgl-iport-2.cisco.com with ESMTP; 12 Nov 2013 21:45:44 +0000
Received: from tky-shtsuchi-89111.cisco.com (tky-shtsuchi-89111.cisco.com [10.71.44.92]) by bgl-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id rACLjGVt011064; Tue, 12 Nov 2013 21:45:21 GMT
Message-ID: <5282A16C.8010700@cisco.com>
Date: Wed, 13 Nov 2013 06:45:16 +0900
From: Shishio Tsuchiya <shtsuchi@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: aretana@cisco.com, sprevidi@cisco.com, status@ietf.org
References: <CEA6F54D.40EDD%aretana@cisco.com>
In-Reply-To: <CEA6F54D.40EDD%aretana@cisco.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Cc: jgs@juniper.net, shtsuchi@cisco.com, cfilsfil@cisco.com
Subject: Re: [Status] request to move draft-filsfils-rtgwg-segment-routing-use-cases-02 to wg item
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, 12 Nov 2013 21:45:51 -0000

Support/This is useful information.

Regards,
-Shishio
(2013/11/12 11:00), Alvaro Retana (aretana) wrote:
> On 11/6/13 10:24 PM, "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
> wrote:
> 
> Stefano:
> 
>> according to what discussed after the presentation of SR Use Cases at
>> ietf88 spring-wg meeting, I'd like to request the adoption of
>> draft-filsfils-rtgwg-segment-routing-use-cases-02.txt as wg item.
> 
> I believe there was support for adoption at the meeting in Vancouver..but
> we will still have to confirm it here on the list.
> 
> List: This message officially starts the call for adoption.  Please
> indicate your position about adopting this use cases draft.  The call will
> close on Friday, November 22, 2013.
> 
> Thanks!
> 
> Alvaro.
> 
> _______________________________________________
> status mailing list
> status@ietf.org
> https://www.ietf.org/mailman/listinfo/status
> 




Return-Path: <philip_matthews@magma.ca>
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 7731121F9DB8 for <status@ietfa.amsl.com>; Tue, 12 Nov 2013 10:48:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 oBTFVbT77rTA for <status@ietfa.amsl.com>; Tue, 12 Nov 2013 10:48:13 -0800 (PST)
Received: from mail-01.primus.ca (smtp3.primus.ca [209.216.129.203]) by ietfa.amsl.com (Postfix) with ESMTP id DBE5611E810F for <status@ietf.org>; Tue, 12 Nov 2013 10:47:56 -0800 (PST)
Received: from [216.9.110.1] (helo=[172.31.188.105]) by mail-01.primus.ca with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.72) (envelope-from <philip_matthews@magma.ca>) id 1VgJ0F-0001lH-1t for status@ietf.org; Tue, 12 Nov 2013 13:47:55 -0500
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
From: Philip Matthews <philip_matthews@magma.ca>
In-Reply-To: <CEA6F54D.40EDD%aretana@cisco.com>
Date: Tue, 12 Nov 2013 10:47:55 -0800
Content-Transfer-Encoding: 7bit
Message-Id: <87B990A7-7D1B-49A5-84D6-CF56CA20CE0D@magma.ca>
References: <CEA6F54D.40EDD%aretana@cisco.com>
To: status@ietf.org
X-Mailer: Apple Mail (2.1084)
X-Authenticated: philip_matthews - ([172.31.188.105]) [216.9.110.1]
Subject: Re: [Status] request to move draft-filsfils-rtgwg-segment-routing-use-cases-02 to wg item
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, 12 Nov 2013 18:48:50 -0000

Support.

On 2013-11-11, at 18:00 , Alvaro Retana (aretana) wrote:

> On 11/6/13 10:24 PM, "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
> wrote:
> 
> Stefano:
> 
>> according to what discussed after the presentation of SR Use Cases at
>> ietf88 spring-wg meeting, I'd like to request the adoption of
>> draft-filsfils-rtgwg-segment-routing-use-cases-02.txt as wg item.
> 
> I believe there was support for adoption at the meeting in Vancouver..but
> we will still have to confirm it here on the list.
> 
> List: This message officially starts the call for adoption.  Please
> indicate your position about adopting this use cases draft.  The call will
> close on Friday, November 22, 2013.
> 
> Thanks!
> 
> Alvaro.
> 
> _______________________________________________
> status mailing list
> status@ietf.org
> https://www.ietf.org/mailman/listinfo/status
> 



Return-Path: <swhyte@google.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 B98B611E8171 for <status@ietfa.amsl.com>; Tue, 12 Nov 2013 10:45:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.03
X-Spam-Level: 
X-Spam-Status: No, score=-2.03 tagged_above=-999 required=5 tests=[AWL=-0.052,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001]
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 g5IvDe7vQUfn for <status@ietfa.amsl.com>; Tue, 12 Nov 2013 10:45:01 -0800 (PST)
Received: from mail-vb0-x236.google.com (mail-vb0-x236.google.com [IPv6:2607:f8b0:400c:c02::236]) by ietfa.amsl.com (Postfix) with ESMTP id 42F0611E8169 for <status@ietf.org>; Tue, 12 Nov 2013 10:45:01 -0800 (PST)
Received: by mail-vb0-f54.google.com with SMTP id q4so1652994vbe.13 for <status@ietf.org>; Tue, 12 Nov 2013 10:45:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=68NZEyfdeRPWsqejmdQsenow1LxfEz8hb9AX3wFI7/g=; b=DdwlSf2hLuxZvbz0qnlUBW2pggVK8XnK/PLUm8HfNijHgfxwQ5MdIHqaLK/z8Z4L7y p6Y/5lERM7H8R/+URXuXfVsjC9AKp28FVvcK+GSI52MtC3gnl62Fokd3hn3vS5C5qb+R mkIr6OuYhofBrEuDpJrjc7nydqLxl2igzge63g58q+C3HViZQES0TCc0clhLBkk8yf9j 2IXB+zdo2PVPaZic7gNIQcPRQjT0oIVKZI7NyMAp/00unXHV5p41lKL7ZumCVCGiFtY4 SE5u6cWwObukEfrzNPjz1Rbg92CZNw4Qc9daRdfgeLpi2IHUiqNZb7nKR+ZSXzJPyuXl kEUQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=68NZEyfdeRPWsqejmdQsenow1LxfEz8hb9AX3wFI7/g=; b=eO5Wn5EYwa/zFtqjeKia9kLrlcbZpd6i6kGkqq3Deon4k+tnyDN/8XkNXGNf/muVCy +D9tOXkXjhINB7LSi3d+Q3BPUBTR1oUOKKhXMTTnwtjAYXWAyFs7bTi4+jzbYkbzzM+q 0yXQ5mPoMy+RcDyKgV4on2pYJ3uYhd+815fQ6h614T16Wr0olnFkMMgKckQfzqr4DLrL CHDEiYqWpJALN3d/WKkBCG5SReO1OB7OZtgDqfpKb7WyQ1YQyLO45PosOROduI/xJzQ1 EE1BNYRxWwEZlk/mpwxwMWBCJhgPzFXfRASeelIGKQyvZbaln7k2QBn97gt3H/fceudj FsHA==
X-Gm-Message-State: ALoCoQn8ew6dPhor+UOpdUckk7HPlSNtOAokPTEWowgF256HSugczhHBMnAkSgQLvCx01DvabPc7yb+S3mDn3LS/zONVMRNw3VJ2SYL9E2669fSKSQzMjzwdVLvDEU4qigbxUbAEpfPoB3rA9RrY24KvpvLu9/lMZnd790JyUve37uH6/x6k2tKQoZ5NVwO0rVgPEDkovkvF
MIME-Version: 1.0
X-Received: by 10.52.34.109 with SMTP id y13mr26611880vdi.8.1384281900274; Tue, 12 Nov 2013 10:45:00 -0800 (PST)
Received: by 10.52.106.230 with HTTP; Tue, 12 Nov 2013 10:45:00 -0800 (PST)
In-Reply-To: <CEA6F54D.40EDD%aretana@cisco.com>
References: <947081B7-F174-4C4D-BE12-56F4FC3A12A8@cisco.com> <CEA6F54D.40EDD%aretana@cisco.com>
Date: Tue, 12 Nov 2013 10:45:00 -0800
Message-ID: <CAG=Jvvh9PTfsODHxhVTr5nV1B-73C5667tXeJ-v8UUGCLp3gzA@mail.gmail.com>
From: Scott Whyte <swhyte@google.com>
To: "Alvaro Retana (aretana)" <aretana@cisco.com>
Content-Type: text/plain; charset=UTF-8
Cc: "Clarence Filsfils \(cfilsfil\)" <cfilsfil@cisco.com>, "John G. Scudder" <jgs@juniper.net>, "status@ietf.org" <status@ietf.org>, "Stefano Previdi \(sprevidi\)" <sprevidi@cisco.com>
Subject: Re: [Status] request to move draft-filsfils-rtgwg-segment-routing-use-cases-02 to wg item
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, 12 Nov 2013 18:45:01 -0000

On Mon, Nov 11, 2013 at 6:00 PM, Alvaro Retana (aretana)
<aretana@cisco.com> wrote:
> draft-filsfils-rtgwg-segment-routing-use-cases-02.txt


Support.

-Scott


Return-Path: <swallow@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 989A211E80FA for <status@ietfa.amsl.com>; Tue, 12 Nov 2013 09:46:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[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 JtqhI-NLwgIy for <status@ietfa.amsl.com>; Tue, 12 Nov 2013 09:46:06 -0800 (PST)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id 1056C21E8094 for <status@ietf.org>; Tue, 12 Nov 2013 09:43:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=881; q=dns/txt; s=iport; t=1384278230; x=1385487830; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=uF/eDgTCG1cwxjrTOfJF/VNjdv6lHCqiokFNJISIcr0=; b=QaI34/HzY2E/K1cbjl5ha9O1gfeZNPGlsPLsPzqe1qiRyS97N/RLDhcl QhtkRhOJkvTpOKgmXklOiv/WX4qY/0N17ylJZIVtEwG5qyoTDV1tHLSt2 F1ulvUUXN45Gm+Evy/OlNeD/vjxG0QaKK1Hu8JdwQnvtifMbDGBVC7Rl2 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgQFAPpnglKtJV2c/2dsb2JhbABagwc4U75LS4EqFnSCJwEEAQEBGh00CxIBCDY3CyUCBAENBYgBDb8QBI9fB4QxA5gPkgqBaIE+gio
X-IronPort-AV: E=Sophos;i="4.93,686,1378857600"; d="scan'208";a="283809360"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-8.cisco.com with ESMTP; 12 Nov 2013 17:43:37 +0000
Received: from xhc-aln-x05.cisco.com (xhc-aln-x05.cisco.com [173.36.12.79]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id rACHhbAF015593 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 12 Nov 2013 17:43:37 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.47]) by xhc-aln-x05.cisco.com ([173.36.12.79]) with mapi id 14.03.0123.003; Tue, 12 Nov 2013 11:43:37 -0600
From: "George Swallow (swallow)" <swallow@cisco.com>
To: "Alvaro Retana (aretana)" <aretana@cisco.com>, "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>, "status@ietf.org" <status@ietf.org>
Thread-Topic: [Status] request to move draft-filsfils-rtgwg-segment-routing-use-cases-02 to wg item
Thread-Index: AQHO23E8p83WlqlDLUO90VPM+v9VCJog77WAgAD20wA=
Date: Tue, 12 Nov 2013 17:43:36 +0000
Message-ID: <CEA7D2E5.93C8F%swallow@cisco.com>
In-Reply-To: <CEA6F54D.40EDD%aretana@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.8.130913
x-originating-ip: [10.98.56.165]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <CE469EBCAA50A247B3760E418731C1D6@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "George Swallow \(swallow\)" <swallow@cisco.com>, "John G. Scudder" <jgs@juniper.net>, "Clarence Filsfils \(cfilsfil\)" <cfilsfil@cisco.com>
Subject: Re: [Status] request to move draft-filsfils-rtgwg-segment-routing-use-cases-02 to wg item
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, 12 Nov 2013 17:46:11 -0000

Support.

On 11/11/13 9:00 PM, "Alvaro Retana (aretana)" <aretana@cisco.com> wrote:

>On 11/6/13 10:24 PM, "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
>wrote:
>
>Stefano:
>
>>according to what discussed after the presentation of SR Use Cases at
>>ietf88 spring-wg meeting, I'd like to request the adoption of
>>draft-filsfils-rtgwg-segment-routing-use-cases-02.txt as wg item.
>
>I believe there was support for adoption at the meeting in Vancouver..but
>we will still have to confirm it here on the list.
>
>List: This message officially starts the call for adoption.  Please
>indicate your position about adopting this use cases draft.  The call will
>close on Friday, November 22, 2013.
>
>Thanks!
>
>Alvaro.
>
>_______________________________________________
>status mailing list
>status@ietf.org
>https://www.ietf.org/mailman/listinfo/status



Return-Path: <naikumar@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 8858811E8171 for <status@ietfa.amsl.com>; Tue, 12 Nov 2013 09:02:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 xbwdHt78YX2h for <status@ietfa.amsl.com>; Tue, 12 Nov 2013 09:02:23 -0800 (PST)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id 1C23A11E8142 for <status@ietf.org>; Tue, 12 Nov 2013 09:02:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=903; q=dns/txt; s=iport; t=1384275743; x=1385485343; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=LhCZ/3m6k30o/4DbyYcBVhT8+vJVGLspwhHbvEKSqIc=; b=j6jc9xvEf1raD6DDAUpiMoYjC0JUARnRCOMJTkruOhulqfj8ww26OSmt XmkEoL9KQ1P8RDSc7V4nLhoa0bpOtmpkQbSv1lP+6jt0yXbC3TCcw85jD 6Klfz1iLePhwBdeyJJVxjPY3TQY6afEgxeMoA70p/+57JQQZwkawym7Hf k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgQFAJReglKtJXG+/2dsb2JhbABagwc4U75LS4EqFnSCJwEEAQEBGh00CxIBCDY3CyUCBAENBYgBDb8SBI9fB4QxA5gPkgqBaIE+gio
X-IronPort-AV: E=Sophos;i="4.93,686,1378857600"; d="scan'208";a="283794121"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by rcdn-iport-6.cisco.com with ESMTP; 12 Nov 2013 17:02:21 +0000
Received: from xhc-rcd-x04.cisco.com (xhc-rcd-x04.cisco.com [173.37.183.78]) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id rACH2LMS029785 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 12 Nov 2013 17:02:21 GMT
Received: from xmb-rcd-x03.cisco.com ([169.254.7.33]) by xhc-rcd-x04.cisco.com ([fe80::200:5efe:173.37.183.34%12]) with mapi id 14.03.0123.003; Tue, 12 Nov 2013 11:02:20 -0600
From: "Nagendra Kumar Nainar (naikumar)" <naikumar@cisco.com>
To: "Alvaro Retana (aretana)" <aretana@cisco.com>, "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>, "status@ietf.org" <status@ietf.org>
Thread-Topic: [Status] request to move draft-filsfils-rtgwg-segment-routing-use-cases-02 to wg item
Thread-Index: AQHO23E8p83WlqlDLUO90VPM+v9VCJog77WAgAD8EQA=
Date: Tue, 12 Nov 2013 17:02:20 +0000
Message-ID: <CEA7C938.DBC7%naikumar@cisco.com>
In-Reply-To: <CEA6F54D.40EDD%aretana@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.2.130206
x-originating-ip: [64.102.157.37]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <43B56938001F474098B888087D9A5EB1@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "John G. Scudder" <jgs@juniper.net>, "Clarence Filsfils \(cfilsfil\)" <cfilsfil@cisco.com>
Subject: Re: [Status] request to move draft-filsfils-rtgwg-segment-routing-use-cases-02 to wg item
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, 12 Nov 2013 17:02:29 -0000

Support.

Regards,
Nagendra

On 11/11/13 9:00 PM, "Alvaro Retana (aretana)" <aretana@cisco.com> wrote:

>On 11/6/13 10:24 PM, "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
>wrote:
>
>Stefano:
>
>>according to what discussed after the presentation of SR Use Cases at
>>ietf88 spring-wg meeting, I'd like to request the adoption of
>>draft-filsfils-rtgwg-segment-routing-use-cases-02.txt as wg item.
>
>I believe there was support for adoption at the meeting in Vancouver..but
>we will still have to confirm it here on the list.
>
>List: This message officially starts the call for adoption.  Please
>indicate your position about adopting this use cases draft.  The call will
>close on Friday, November 22, 2013.
>
>Thanks!
>
>Alvaro.
>
>_______________________________________________
>status mailing list
>status@ietf.org
>https://www.ietf.org/mailman/listinfo/status



Return-Path: <the.maanderson@gmail.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 C1A4621E81C0 for <status@ietfa.amsl.com>; Tue, 12 Nov 2013 08:54:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
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 M0XAK6bDQhEb for <status@ietfa.amsl.com>; Tue, 12 Nov 2013 08:54:18 -0800 (PST)
Received: from mail-vc0-x22a.google.com (mail-vc0-x22a.google.com [IPv6:2607:f8b0:400c:c03::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 2C1A021E815D for <status@ietf.org>; Tue, 12 Nov 2013 08:54:18 -0800 (PST)
Received: by mail-vc0-f170.google.com with SMTP id hv10so4508318vcb.15 for <status@ietf.org>; Tue, 12 Nov 2013 08:54:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=O3K8GqHu1CpdY6t7KZdyzeNEx9FMpvYB+OY6gVbRqlI=; b=XYOdxFW/bOUO9hgU86FAIVJxtereOmow0yvLGXn2jnoK3OyRZKY7rSpYEyPqPwoaIZ IQanfv+TS29LFdnqm2rU9/MhFxgd+faijf3M/zOSXWrY/exCINmqzJa1BS/AE5wGkGVR C+vD935aDTU5SSYgjz7fDSPq02qz7B2/zAzcpc0Th8nkiDAFrj2l5YBUDa1kv+fdbGln 8jCO7qO+BJQopCd+ISx4f3picCJIh4oW6pI1jp73u9H0uC8SpuK9vKQgScYGv2/S/ZTZ XG8UqMrDhXmyTe2Zsj0EBI16ajY4AgbsqAr64i7ZvelIz1xaibHv3pdLjLPw72JkFbF+ JBgg==
X-Received: by 10.58.246.136 with SMTP id xw8mr77194vec.41.1384275257700; Tue, 12 Nov 2013 08:54:17 -0800 (PST)
MIME-Version: 1.0
Sender: the.maanderson@gmail.com
Received: by 10.52.231.34 with HTTP; Tue, 12 Nov 2013 08:53:54 -0800 (PST)
In-Reply-To: <5835D3B9-07D9-42D7-85E9-2626E757A3B1@gmail.com>
References: <CEA6F54D.40EDD%aretana@cisco.com> <5835D3B9-07D9-42D7-85E9-2626E757A3B1@gmail.com>
From: Matt Anderson <matt@mattanderson.net>
Date: Tue, 12 Nov 2013 11:53:54 -0500
X-Google-Sender-Auth: psVBAkrrT98Yon9pT7uDRm6jVAU
Message-ID: <CAAWndM2yXbt=Y6Vurp9c2MonSDByRiqz=_5iOKcGK4LC6sBGqg@mail.gmail.com>
To: Christian Martin <christian.j.martin@gmail.com>
Content-Type: multipart/alternative; boundary=047d7bdc869e01ba0504eafdb377
Cc: "Alvaro Retana \(aretana\)" <aretana@cisco.com>, "Stefano Previdi \(sprevidi\)" <sprevidi@cisco.com>, "status@ietf.org" <status@ietf.org>, "Clarence Filsfils \(cfilsfil\)" <cfilsfil@cisco.com>, "John G. Scudder" <jgs@juniper.net>
Subject: Re: [Status] request to move draft-filsfils-rtgwg-segment-routing-use-cases-02 to wg item
X-BeenThere: status@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: matt@mattanderson.net
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, 12 Nov 2013 16:54:18 -0000

--047d7bdc869e01ba0504eafdb377
Content-Type: text/plain; charset=ISO-8859-1

Support.



On Tue, Nov 12, 2013 at 11:15 AM, Christian Martin <
christian.j.martin@gmail.com> wrote:

> Support.
>
> Cheers
> -Chris
>
> > On Nov 11, 2013, at 9:00 PM, "Alvaro Retana (aretana)" <
> aretana@cisco.com> wrote:
> >
> > On 11/6/13 10:24 PM, "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
> > wrote:
> >
> > Stefano:
> >
> >> according to what discussed after the presentation of SR Use Cases at
> >> ietf88 spring-wg meeting, I'd like to request the adoption of
> >> draft-filsfils-rtgwg-segment-routing-use-cases-02.txt as wg item.
> >
> > I believe there was support for adoption at the meeting in Vancouver..but
> > we will still have to confirm it here on the list.
> >
> > List: This message officially starts the call for adoption.  Please
> > indicate your position about adopting this use cases draft.  The call
> will
> > close on Friday, November 22, 2013.
> >
> > Thanks!
> >
> > Alvaro.
> >
> > _______________________________________________
> > 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
>



-- 
Matt

--047d7bdc869e01ba0504eafdb377
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Support.<div><br></div></div><div class=3D"gmail_extra"><b=
r><br><div class=3D"gmail_quote">On Tue, Nov 12, 2013 at 11:15 AM, Christia=
n Martin <span dir=3D"ltr">&lt;<a href=3D"mailto:christian.j.martin@gmail.c=
om" target=3D"_blank">christian.j.martin@gmail.com</a>&gt;</span> wrote:<br=
>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Support.<br>
<br>
Cheers<br>
-Chris<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
&gt; On Nov 11, 2013, at 9:00 PM, &quot;Alvaro Retana (aretana)&quot; &lt;<=
a href=3D"mailto:aretana@cisco.com">aretana@cisco.com</a>&gt; wrote:<br>
&gt;<br>
&gt; On 11/6/13 10:24 PM, &quot;Stefano Previdi (sprevidi)&quot; &lt;<a hre=
f=3D"mailto:sprevidi@cisco.com">sprevidi@cisco.com</a>&gt;<br>
&gt; wrote:<br>
&gt;<br>
&gt; Stefano:<br>
&gt;<br>
&gt;&gt; according to what discussed after the presentation of SR Use Cases=
 at<br>
&gt;&gt; ietf88 spring-wg meeting, I&#39;d like to request the adoption of<=
br>
&gt;&gt; draft-filsfils-rtgwg-segment-routing-use-cases-02.txt as wg item.<=
br>
&gt;<br>
&gt; I believe there was support for adoption at the meeting in Vancouver..=
but<br>
&gt; we will still have to confirm it here on the list.<br>
&gt;<br>
&gt; List: This message officially starts the call for adoption. =A0Please<=
br>
&gt; indicate your position about adopting this use cases draft. =A0The cal=
l will<br>
&gt; close on Friday, November 22, 2013.<br>
&gt;<br>
&gt; Thanks!<br>
&gt;<br>
&gt; Alvaro.<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; status mailing list<br>
&gt; <a href=3D"mailto:status@ietf.org">status@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/status" target=3D"_bl=
ank">https://www.ietf.org/mailman/listinfo/status</a><br>
_______________________________________________<br>
status mailing list<br>
<a href=3D"mailto:status@ietf.org">status@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/status" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/status</a><br>
</div></div></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>=
Matt
</div>

--047d7bdc869e01ba0504eafdb377--


Return-Path: <christian.j.martin@gmail.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 A94F111E81A4 for <status@ietfa.amsl.com>; Tue, 12 Nov 2013 08:15:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.203
X-Spam-Level: 
X-Spam-Status: No, score=-1.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
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 LNZSIghHHLfS for <status@ietfa.amsl.com>; Tue, 12 Nov 2013 08:15:22 -0800 (PST)
Received: from mail-yh0-x232.google.com (mail-yh0-x232.google.com [IPv6:2607:f8b0:4002:c01::232]) by ietfa.amsl.com (Postfix) with ESMTP id 33A1311E810C for <status@ietf.org>; Tue, 12 Nov 2013 08:15:22 -0800 (PST)
Received: by mail-yh0-f50.google.com with SMTP id b12so612266yha.9 for <status@ietf.org>; Tue, 12 Nov 2013 08:15:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:in-reply-to:mime-version:content-transfer-encoding :content-type:message-id:cc:from:subject:date:to; bh=ZlKS4ZsCpFYHElanPZKcjbJy5KeZEIdvXED7qHjoWzo=; b=fZHqlgd5SBkDVY2L6p0dRx2rxVHl2LvxJgu6Iutq00TkR1DhvW2nAusMqN19rS+PJ1 vgTwuj1yZEZIJbQ32yXJ/TnNJ43J3ci7QpmeWch0kYzjng93t5SntZBUF9QkIeYy/ZYS JQfkFYZlMCQXFWdTRcaW4UAGw15kIx8OeQfeSq6+ivtY7gXbGCwywQcRZ7XlFavNG393 Vz1G70PXBEywUGHaBqjomII7kjG6/ENPjhNb++AHm4XTCAMci6Ax4ZPpTKrr55LuP0nG iSkWTItBX1toJ4/Q43q/z7tcqS+h4JXaTN871iOqvlKHi6JJeO9MkNgXihFFaJssV5wp eZAw==
X-Received: by 10.236.173.41 with SMTP id u29mr7101209yhl.72.1384272921669; Tue, 12 Nov 2013 08:15:21 -0800 (PST)
Received: from [10.107.79.138] (mobile-166-147-111-043.mycingular.net. [166.147.111.43]) by mx.google.com with ESMTPSA id q9sm49074960yhk.16.2013.11.12.08.15.16 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 12 Nov 2013 08:15:20 -0800 (PST)
References: <CEA6F54D.40EDD%aretana@cisco.com>
In-Reply-To: <CEA6F54D.40EDD%aretana@cisco.com>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <5835D3B9-07D9-42D7-85E9-2626E757A3B1@gmail.com>
X-Mailer: iPhone Mail (11A501)
From: Christian Martin <christian.j.martin@gmail.com>
Date: Tue, 12 Nov 2013 11:15:12 -0500
To: "Alvaro Retana (aretana)" <aretana@cisco.com>
Cc: "Clarence Filsfils \(cfilsfil\)" <cfilsfil@cisco.com>, "John G. Scudder" <jgs@juniper.net>, "status@ietf.org" <status@ietf.org>, "Stefano Previdi \(sprevidi\)" <sprevidi@cisco.com>
Subject: Re: [Status] request to move draft-filsfils-rtgwg-segment-routing-use-cases-02 to wg item
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, 12 Nov 2013 16:15:22 -0000

Support.

Cheers
-Chris

> On Nov 11, 2013, at 9:00 PM, "Alvaro Retana (aretana)" <aretana@cisco.com>=
 wrote:
>=20
> On 11/6/13 10:24 PM, "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
> wrote:
>=20
> Stefano:
>=20
>> according to what discussed after the presentation of SR Use Cases at
>> ietf88 spring-wg meeting, I'd like to request the adoption of
>> draft-filsfils-rtgwg-segment-routing-use-cases-02.txt as wg item.
>=20
> I believe there was support for adoption at the meeting in Vancouver..but
> we will still have to confirm it here on the list.
>=20
> List: This message officially starts the call for adoption.  Please
> indicate your position about adopting this use cases draft.  The call will=

> close on Friday, November 22, 2013.
>=20
> Thanks!
>=20
> Alvaro.
>=20
> _______________________________________________
> status mailing list
> status@ietf.org
> https://www.ietf.org/mailman/listinfo/status


Return-Path: <sulrich@botwerks.org>
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 446E321E8093 for <status@ietfa.amsl.com>; Tue, 12 Nov 2013 06:06:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.977
X-Spam-Level: 
X-Spam-Status: No, score=-5.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_MED=-4]
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 n9OI3jT9Xrdv for <status@ietfa.amsl.com>; Tue, 12 Nov 2013 06:05:47 -0800 (PST)
Received: from na3sys009aog119.obsmtp.com (na3sys009aog119.obsmtp.com [74.125.149.246]) by ietfa.amsl.com (Postfix) with SMTP id 32FCA11E816D for <status@ietf.org>; Tue, 12 Nov 2013 06:05:43 -0800 (PST)
Received: from mail-qa0-f53.google.com ([209.85.216.53]) (using TLSv1) by na3sys009aob119.postini.com ([74.125.148.12]) with SMTP ID DSNKUoI1tnJ9+BSXdT70ZmVjKBzT2k3Uwih8@postini.com; Tue, 12 Nov 2013 06:05:47 PST
Received: by mail-qa0-f53.google.com with SMTP id k4so2839880qaq.5 for <status@ietf.org>; Tue, 12 Nov 2013 06:05:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=botwerks.org; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=fs4LyQRzZ68BRrD+Mnp+aV6vi9TEopHgLBIl3gHds/Y=; b=TX4dDI8+MtVwiCzpmDvvlFYoQwRNfq50h+HyksvRKeqKIi7zQKdE2M4fs3CqCf3yiW ZMryEv4vFs3ivNx7x8y3VG3oiTizxd5vUqIg7E5ZEdGWm8zGPWEQJkJQfY/5U2lWtjga pGf8IprdzDfHOcBNhkojbvdKE1Op1LOF3h8LY=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=fs4LyQRzZ68BRrD+Mnp+aV6vi9TEopHgLBIl3gHds/Y=; b=RasHdeqjO/19i0eH+2eOGz9uFW9rVR1ANOtPPh7tUysvUlVmERN3lCevIVacEkLyGG 2YbzeEMF2JwrdK1GNqrj30jL2CqJLXCeG5xAQyOzZAaA6jAEc/bb351qp9mjkyZ2mALX NGWi2PnRZU7rr7VV+LTMEnwPHQCDjzsty/NfRmEfYZ2ZWeO894gbfIgv9NCacw15xHHM 9TSvBgJCXWUxpQcjov4et38Kk4WSHztvpuzSJHJqHL/qHXsKLvEdkr2QdumLRsLO40fw oRlXDahtH1W+HCCmDB0jfjwrxR3s01D2o4pfYisI6eZAhyt3y4b3q/5zd4yB/9JHxnMJ Zw/w==
X-Gm-Message-State: ALoCoQlH5DP8cjo4qAPYepA+hyi8IkTuI8EdBEDFE537RdoPLhoZl5aNwT9PUzyjuMABTxGXczjHoUwetKNjPMX3B3sMeTyR6MW8/1bxF+sSSk3apIZeEe8DvkBYhsCdGjV3cDvfmrFmKVwwaxfIuwnDwh5uFhxexg==
X-Received: by 10.49.1.230 with SMTP id 6mr57291637qep.48.1384265142454; Tue, 12 Nov 2013 06:05:42 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.49.1.230 with SMTP id 6mr57291613qep.48.1384265142322; Tue, 12 Nov 2013 06:05:42 -0800 (PST)
Received: by 10.96.227.136 with HTTP; Tue, 12 Nov 2013 06:05:42 -0800 (PST)
In-Reply-To: <CEA6F54D.40EDD%aretana@cisco.com>
References: <947081B7-F174-4C4D-BE12-56F4FC3A12A8@cisco.com> <CEA6F54D.40EDD%aretana@cisco.com>
Date: Tue, 12 Nov 2013 08:05:42 -0600
Message-ID: <CAORhBqxRLxZfhzL0sg6BX7VQ3gqNcSvF0UEy_aGPRGc3jdur+w@mail.gmail.com>
From: steve ulrich <sulrich@botwerks.org>
To: "Alvaro Retana (aretana)" <aretana@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "Clarence Filsfils \(cfilsfil\)" <cfilsfil@cisco.com>, "John G. Scudder" <jgs@juniper.net>, "status@ietf.org" <status@ietf.org>, "Stefano Previdi \(sprevidi\)" <sprevidi@cisco.com>
Subject: Re: [Status] request to move draft-filsfils-rtgwg-segment-routing-use-cases-02 to wg item
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, 12 Nov 2013 14:06:00 -0000

support.

On Mon, Nov 11, 2013 at 8:00 PM, Alvaro Retana (aretana)
<aretana@cisco.com> wrote:
> On 11/6/13 10:24 PM, "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
> wrote:
>
> Stefano:
>
>>according to what discussed after the presentation of SR Use Cases at
>>ietf88 spring-wg meeting, I'd like to request the adoption of
>>draft-filsfils-rtgwg-segment-routing-use-cases-02.txt as wg item.
>
> I believe there was support for adoption at the meeting in Vancouver..but
> we will still have to confirm it here on the list.
>
> List: This message officially starts the call for adoption.  Please
> indicate your position about adopting this use cases draft.  The call will
> close on Friday, November 22, 2013.
>
> Thanks!
>
> Alvaro.
>
> _______________________________________________
> status mailing list
> status@ietf.org
> https://www.ietf.org/mailman/listinfo/status



-- 
steve ulrich (sulrich@botwerks.*)


Return-Path: <saku@ytti.fi>
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 B259E11E813D for <status@ietfa.amsl.com>; Tue, 12 Nov 2013 05:58:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level: 
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, 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 3cz8hmaX2LtH for <status@ietfa.amsl.com>; Tue, 12 Nov 2013 05:58:06 -0800 (PST)
Received: from mail-oa0-f42.google.com (mail-oa0-f42.google.com [209.85.219.42]) by ietfa.amsl.com (Postfix) with ESMTP id 2A24711E8143 for <status@ietf.org>; Tue, 12 Nov 2013 05:58:05 -0800 (PST)
Received: by mail-oa0-f42.google.com with SMTP id h16so3025622oag.15 for <status@ietf.org>; Tue, 12 Nov 2013 05:58:05 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=fokp25jIX4SXKagjN+iosVUwSH97WzPX7qFr6nrs0A0=; b=NzVLTuY94XwyKefbeTJEkDjsSKlALzY09SZ9hhceobEzg6HbqKuxqGa4oqWR6p7zTg E/LfZ0aV+nNcg1PT0kFOyYQZfOu2XZjqso1IeRXwN8UnzDxTltfLdDDyQ4ju6u953LzV b1fXMreK3yoXss3YObHLVfxE6oJOXTdP+McZQDqSGQaN50FXoQBXBxetVwt8gdcHREBE mjrjm1wDwGBSHj3KKhP2poHNp+gGmZCBNwC5PVLoA3KpPhmCJkareMQEeq3IXzO+SM0/ jwI/celL6McJrq7EXGbVT7mUzSqLRzfXa9Db2721OWYz8vXoRdhmluWYOEpMeMWgFD3f mfQw==
X-Gm-Message-State: ALoCoQnHv0+hLSg0FUjzmgKaMuvCFB1tc+mu2+z1xVE4SJiMRl4hUI0ktKFmnaOu5BKhX49Z4KbA
MIME-Version: 1.0
X-Received: by 10.182.84.132 with SMTP id z4mr11441854oby.49.1384264685330; Tue, 12 Nov 2013 05:58:05 -0800 (PST)
Received: by 10.182.220.193 with HTTP; Tue, 12 Nov 2013 05:58:05 -0800 (PST)
In-Reply-To: <CA7A7C64CC4ADB458B74477EA99DF6F5021B362083@HE111643.EMEA1.CDS.T-INTERNAL.COM>
References: <947081B7-F174-4C4D-BE12-56F4FC3A12A8@cisco.com> <CEA6F54D.40EDD%aretana@cisco.com> <CA7A7C64CC4ADB458B74477EA99DF6F5021B362083@HE111643.EMEA1.CDS.T-INTERNAL.COM>
Date: Tue, 12 Nov 2013 15:58:05 +0200
Message-ID: <CAAeewD98OJuR5cDrQ+3vwWJWnmHV_qL2_q2Va49B97K84MtF7g@mail.gmail.com>
From: Saku Ytti <saku@ytti.fi>
To: Ruediger.Geib@telekom.de
Content-Type: multipart/alternative; boundary=089e0111c09ad8377204eafb3c94
Cc: "status@ietf.org" <status@ietf.org>, aretana@cisco.com, Clarence Filsfils <cfilsfil@cisco.com>, "Stefano Previdi \(sprevidi\)" <sprevidi@cisco.com>, "John G. Scudder" <jgs@juniper.net>
Subject: Re: [Status] request to move draft-filsfils-rtgwg-segment-routing-use-cases-02 to wg item
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, 12 Nov 2013 13:58:10 -0000

--089e0111c09ad8377204eafb3c94
Content-Type: text/plain; charset=UTF-8

ACK, support.


On 12 November 2013 09:12, <Ruediger.Geib@telekom.de> wrote:

> Alvaro,
>
> I favor adoption as a WG draft.
>
> Regards,
>
> Ruediger
>
> -----Original Message-----
> From: status-bounces@ietf.org [mailto:status-bounces@ietf.org] On Behalf
> Of Alvaro Retana (aretana)
> Sent: Tuesday, November 12, 2013 3:00 AM
> To: Stefano Previdi (sprevidi); status@ietf.org
> Cc: John G. Scudder; Clarence Filsfils (cfilsfil)
> Subject: Re: [Status] request to move
> draft-filsfils-rtgwg-segment-routing-use-cases-02 to wg item
>
> On 11/6/13 10:24 PM, "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
> wrote:
>
> Stefano:
>
> >according to what discussed after the presentation of SR Use Cases at
> >ietf88 spring-wg meeting, I'd like to request the adoption of
> >draft-filsfils-rtgwg-segment-routing-use-cases-02.txt as wg item.
>
> I believe there was support for adoption at the meeting in Vancouver..but
> we will still have to confirm it here on the list.
>
> List: This message officially starts the call for adoption.  Please
> indicate your position about adopting this use cases draft.  The call will
> close on Friday, November 22, 2013.
>
> Thanks!
>
> Alvaro.
>
> _______________________________________________
> 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
>



-- 
  ++ytti

--089e0111c09ad8377204eafb3c94
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">ACK, support.</div><div class=3D"gmail_extra"><br><br><div=
 class=3D"gmail_quote">On 12 November 2013 09:12,  <span dir=3D"ltr">&lt;<a=
 href=3D"mailto:Ruediger.Geib@telekom.de" target=3D"_blank">Ruediger.Geib@t=
elekom.de</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Alvaro,<br>
<br>
I favor adoption as a WG draft.<br>
<br>
Regards,<br>
<br>
Ruediger<br>
<div class=3D"im HOEnZb"><br>
-----Original Message-----<br>
From: <a href=3D"mailto:status-bounces@ietf.org">status-bounces@ietf.org</a=
> [mailto:<a href=3D"mailto:status-bounces@ietf.org">status-bounces@ietf.or=
g</a>] On Behalf Of Alvaro Retana (aretana)<br>
Sent: Tuesday, November 12, 2013 3:00 AM<br>
To: Stefano Previdi (sprevidi); <a href=3D"mailto:status@ietf.org">status@i=
etf.org</a><br>
Cc: John G. Scudder; Clarence Filsfils (cfilsfil)<br>
Subject: Re: [Status] request to move draft-filsfils-rtgwg-segment-routing-=
use-cases-02 to wg item<br>
<br>
</div><div class=3D"HOEnZb"><div class=3D"h5">On 11/6/13 10:24 PM, &quot;St=
efano Previdi (sprevidi)&quot; &lt;<a href=3D"mailto:sprevidi@cisco.com">sp=
revidi@cisco.com</a>&gt;<br>
wrote:<br>
<br>
Stefano:<br>
<br>
&gt;according to what discussed after the presentation of SR Use Cases at<b=
r>
&gt;ietf88 spring-wg meeting, I&#39;d like to request the adoption of<br>
&gt;draft-filsfils-rtgwg-segment-routing-use-cases-02.txt as wg item.<br>
<br>
I believe there was support for adoption at the meeting in Vancouver..but<b=
r>
we will still have to confirm it here on the list.<br>
<br>
List: This message officially starts the call for adoption. =C2=A0Please<br=
>
indicate your position about adopting this use cases draft. =C2=A0The call =
will<br>
close on Friday, November 22, 2013.<br>
<br>
Thanks!<br>
<br>
Alvaro.<br>
<br>
_______________________________________________<br>
status mailing list<br>
<a href=3D"mailto:status@ietf.org">status@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/status" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/status</a><br>
_______________________________________________<br>
status mailing list<br>
<a href=3D"mailto:status@ietf.org">status@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/status" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/status</a><br>
</div></div></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>=
=C2=A0 ++ytti
</div>

--089e0111c09ad8377204eafb3c94--


Return-Path: <mach.chen@huawei.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 24A1621E80BA for <status@ietfa.amsl.com>; Tue, 12 Nov 2013 01:25:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.238
X-Spam-Level: 
X-Spam-Status: No, score=-6.238 tagged_above=-999 required=5 tests=[AWL=0.361,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 P6Cuthfv0o4H for <status@ietfa.amsl.com>; Tue, 12 Nov 2013 01:25:06 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 6C6E221E80AC for <status@ietf.org>; Tue, 12 Nov 2013 01:25:06 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id AXU30519; Tue, 12 Nov 2013 09:25:05 +0000 (GMT)
Received: from LHREML405-HUB.china.huawei.com (10.201.5.242) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 12 Nov 2013 09:24:10 +0000
Received: from SZXEML417-HUB.china.huawei.com (10.82.67.156) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 12 Nov 2013 09:25:04 +0000
Received: from szxeml558-mbs.china.huawei.com ([169.254.8.159]) by szxeml417-hub.china.huawei.com ([10.82.67.156]) with mapi id 14.03.0158.001; Tue, 12 Nov 2013 17:24:59 +0800
From: Mach Chen <mach.chen@huawei.com>
To: "Alvaro Retana (aretana)" <aretana@cisco.com>, "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>, "status@ietf.org" <status@ietf.org>
Thread-Topic: [Status] request to move draft-filsfils-rtgwg-segment-routing-use-cases-02 to wg item
Thread-Index: AQHO23E8p83WlqlDLUO90VPM+v9VCJog77WAgABrV3A=
Date: Tue, 12 Nov 2013 09:24:59 +0000
Message-ID: <F73A3CB31E8BE34FA1BBE3C8F0CB2AE25CF1ECAE@szxeml558-mbs.china.huawei.com>
References: <947081B7-F174-4C4D-BE12-56F4FC3A12A8@cisco.com> <CEA6F54D.40EDD%aretana@cisco.com>
In-Reply-To: <CEA6F54D.40EDD%aretana@cisco.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.97.72]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "John G. Scudder" <jgs@juniper.net>, "Clarence Filsfils \(cfilsfil\)" <cfilsfil@cisco.com>
Subject: Re: [Status] request to move draft-filsfils-rtgwg-segment-routing-use-cases-02 to wg item
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, 12 Nov 2013 09:25:11 -0000

Support.

Best regards,
Mach

> -----Original Message-----
> From: status-bounces@ietf.org [mailto:status-bounces@ietf.org] On Behalf =
Of
> Alvaro Retana (aretana)
> Sent: Tuesday, November 12, 2013 10:00 AM
> To: Stefano Previdi (sprevidi); status@ietf.org
> Cc: John G. Scudder; Clarence Filsfils (cfilsfil)
> Subject: Re: [Status] request to move
> draft-filsfils-rtgwg-segment-routing-use-cases-02 to wg item
>=20
> On 11/6/13 10:24 PM, "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
> wrote:
>=20
> Stefano:
>=20
> >according to what discussed after the presentation of SR Use Cases at
> >ietf88 spring-wg meeting, I'd like to request the adoption of
> >draft-filsfils-rtgwg-segment-routing-use-cases-02.txt as wg item.
>=20
> I believe there was support for adoption at the meeting in Vancouver..but=
 we will
> still have to confirm it here on the list.
>=20
> List: This message officially starts the call for adoption.  Please indic=
ate your
> position about adopting this use cases draft.  The call will close on Fri=
day,
> November 22, 2013.
>=20
> Thanks!
>=20
> Alvaro.
>=20
> _______________________________________________
> status mailing list
> status@ietf.org
> https://www.ietf.org/mailman/listinfo/status


Return-Path: <stephane.litkowski@orange.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 E8CED21E80AC for <status@ietfa.amsl.com>; Tue, 12 Nov 2013 01:10:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.144
X-Spam-Level: 
X-Spam-Status: No, score=-2.144 tagged_above=-999 required=5 tests=[AWL=0.104,  BAYES_00=-2.599, HELO_EQ_FR=0.35, UNPARSEABLE_RELAY=0.001]
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 mdEq-IYoEL3b for <status@ietfa.amsl.com>; Tue, 12 Nov 2013 01:10:51 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias245.francetelecom.com [80.12.204.245]) by ietfa.amsl.com (Postfix) with ESMTP id 194E511E8100 for <status@ietf.org>; Tue, 12 Nov 2013 01:10:51 -0800 (PST)
Received: from omfeda08.si.francetelecom.fr (unknown [xx.xx.xx.201]) by omfeda10.si.francetelecom.fr (ESMTP service) with ESMTP id 8BF9537440A; Tue, 12 Nov 2013 10:10:49 +0100 (CET)
Received: from PUEXCH81.nanterre.francetelecom.fr (unknown [10.101.44.34]) by omfeda08.si.francetelecom.fr (ESMTP service) with ESMTP id 6A5873840BA; Tue, 12 Nov 2013 10:10:49 +0100 (CET)
Received: from PUEXCB2F.nanterre.francetelecom.fr ([10.101.44.44]) by PUEXCH81.nanterre.francetelecom.fr ([10.101.44.34]) with mapi; Tue, 12 Nov 2013 10:10:49 +0100
From: <stephane.litkowski@orange.com>
To: "Alvaro Retana (aretana)" <aretana@cisco.com>, "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>, "status@ietf.org" <status@ietf.org>
Date: Tue, 12 Nov 2013 10:10:47 +0100
Thread-Topic: [Status] request to move draft-filsfils-rtgwg-segment-routing-use-cases-02 to wg item
Thread-Index: AQHO23E8p83WlqlDLUO90VPM+v9VCJog77WAgABni8A=
Message-ID: <6298_1384247449_5281F099_6298_19138_1_EEE55384044474429A926C625D0FCC810992657BCB@PUEXCB2F.nanterre.francetelecom.fr>
References: <947081B7-F174-4C4D-BE12-56F4FC3A12A8@cisco.com> <CEA6F54D.40EDD%aretana@cisco.com>
In-Reply-To: <CEA6F54D.40EDD%aretana@cisco.com>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: fr-FR
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2013.11.12.74814
Cc: "John G. Scudder" <jgs@juniper.net>, "Clarence Filsfils \(cfilsfil\)" <cfilsfil@cisco.com>
Subject: Re: [Status] request to move draft-filsfils-rtgwg-segment-routing-use-cases-02 to wg item
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, 12 Nov 2013 09:10:56 -0000

Support


-----Message d'origine-----
De=A0: status-bounces@ietf.org [mailto:status-bounces@ietf.org] De la part =
de Alvaro Retana (aretana)
Envoy=E9=A0: mardi 12 novembre 2013 03:00
=C0=A0: Stefano Previdi (sprevidi); status@ietf.org
Cc=A0: John G. Scudder; Clarence Filsfils (cfilsfil)
Objet=A0: Re: [Status] request to move draft-filsfils-rtgwg-segment-routing=
-use-cases-02 to wg item

On 11/6/13 10:24 PM, "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
wrote:

Stefano:

>according to what discussed after the presentation of SR Use Cases at
>ietf88 spring-wg meeting, I'd like to request the adoption of=20
>draft-filsfils-rtgwg-segment-routing-use-cases-02.txt as wg item.

I believe there was support for adoption at the meeting in Vancouver..but w=
e will still have to confirm it here on the list.

List: This message officially starts the call for adoption.  Please indicat=
e your position about adopting this use cases draft.  The call will close o=
n Friday, November 22, 2013.

Thanks!

Alvaro.

_______________________________________________
status mailing list
status@ietf.org
https://www.ietf.org/mailman/listinfo/status

___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou =
falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been =
modified, changed or falsified.
Thank you.



Return-Path: <xuxiaohu@huawei.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 9E0BA21E80F7 for <status@ietfa.amsl.com>; Tue, 12 Nov 2013 00:42:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.171
X-Spam-Level: *
X-Spam-Status: No, score=1.171 tagged_above=-999 required=5 tests=[AWL=-1.617,  BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, CN_BODY_35=0.339,  MIME_8BIT_HEADER=0.3, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4, SARE_SUB_ENC_GB2312=1.345]
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 M0Ua0VwqI4Mo for <status@ietfa.amsl.com>; Tue, 12 Nov 2013 00:42:09 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 80E9921E80E6 for <status@ietf.org>; Tue, 12 Nov 2013 00:42:08 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BAE15352; Tue, 12 Nov 2013 08:42:07 +0000 (GMT)
Received: from LHREML401-HUB.china.huawei.com (10.201.5.240) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 12 Nov 2013 08:41:52 +0000
Received: from nkgeml405-hub.china.huawei.com (10.98.56.36) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 12 Nov 2013 08:42:04 +0000
Received: from NKGEML512-MBS.china.huawei.com ([169.254.8.193]) by nkgeml405-hub.china.huawei.com ([10.98.56.36]) with mapi id 14.03.0158.001; Tue, 12 Nov 2013 16:41:59 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: "Alvaro Retana (aretana)" <aretana@cisco.com>, "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>, "status@ietf.org" <status@ietf.org>
Thread-Topic: [Status] request to move draft-filsfils-rtgwg-segment-routing-use-cases-02 to wg item
Thread-Index: AQHO23E8p83WlqlDLUO90VPM+v9VCJog77WAgABfWUA=
Date: Tue, 12 Nov 2013 08:41:58 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08228427@NKGEML512-MBS.china.huawei.com>
References: <947081B7-F174-4C4D-BE12-56F4FC3A12A8@cisco.com> <CEA6F54D.40EDD%aretana@cisco.com>
In-Reply-To: <CEA6F54D.40EDD%aretana@cisco.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.134]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "John G. Scudder" <jgs@juniper.net>, "Clarence Filsfils \(cfilsfil\)" <cfilsfil@cisco.com>
Subject: [Status] =?gb2312?b?tPC4tDogIHJlcXVlc3QgdG8gbW92ZSBkcmFmdC1maWxz?= =?gb2312?b?Zmlscy1ydGd3Zy1zZWdtZW50LXJvdXRpbmctdXNlLWNhc2VzLTAyIHRvIHdn?= =?gb2312?b?IGl0ZW0=?=
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, 12 Nov 2013 08:42:16 -0000

U3VwcG9ydC4NCg0KWGlhb2h1DQoNCj4gLS0tLS3Tyrz+1K28/i0tLS0tDQo+ILeivP7Iyzogc3Rh
dHVzLWJvdW5jZXNAaWV0Zi5vcmcgW21haWx0bzpzdGF0dXMtYm91bmNlc0BpZXRmLm9yZ10gtPqx
7SBBbHZhcm8NCj4gUmV0YW5hIChhcmV0YW5hKQ0KPiC3osvNyrG85DogMjAxM8TqMTHUwjEyyNUg
MTA6MDANCj4gytW8/sjLOiBTdGVmYW5vIFByZXZpZGkgKHNwcmV2aWRpKTsgc3RhdHVzQGlldGYu
b3JnDQo+ILOty806IEpvaG4gRy4gU2N1ZGRlcjsgQ2xhcmVuY2UgRmlsc2ZpbHMgKGNmaWxzZmls
KQ0KPiDW98ziOiBSZTogW1N0YXR1c10gcmVxdWVzdCB0byBtb3ZlDQo+IGRyYWZ0LWZpbHNmaWxz
LXJ0Z3dnLXNlZ21lbnQtcm91dGluZy11c2UtY2FzZXMtMDIgdG8gd2cgaXRlbQ0KPiANCj4gT24g
MTEvNi8xMyAxMDoyNCBQTSwgIlN0ZWZhbm8gUHJldmlkaSAoc3ByZXZpZGkpIiA8c3ByZXZpZGlA
Y2lzY28uY29tPg0KPiB3cm90ZToNCj4gDQo+IFN0ZWZhbm86DQo+IA0KPiA+YWNjb3JkaW5nIHRv
IHdoYXQgZGlzY3Vzc2VkIGFmdGVyIHRoZSBwcmVzZW50YXRpb24gb2YgU1IgVXNlIENhc2VzIGF0
DQo+ID5pZXRmODggc3ByaW5nLXdnIG1lZXRpbmcsIEknZCBsaWtlIHRvIHJlcXVlc3QgdGhlIGFk
b3B0aW9uIG9mDQo+ID5kcmFmdC1maWxzZmlscy1ydGd3Zy1zZWdtZW50LXJvdXRpbmctdXNlLWNh
c2VzLTAyLnR4dCBhcyB3ZyBpdGVtLg0KPiANCj4gSSBiZWxpZXZlIHRoZXJlIHdhcyBzdXBwb3J0
IGZvciBhZG9wdGlvbiBhdCB0aGUgbWVldGluZyBpbiBWYW5jb3V2ZXIuLmJ1dCB3ZQ0KPiB3aWxs
IHN0aWxsIGhhdmUgdG8gY29uZmlybSBpdCBoZXJlIG9uIHRoZSBsaXN0Lg0KPiANCj4gTGlzdDog
VGhpcyBtZXNzYWdlIG9mZmljaWFsbHkgc3RhcnRzIHRoZSBjYWxsIGZvciBhZG9wdGlvbi4gIFBs
ZWFzZSBpbmRpY2F0ZSB5b3VyDQo+IHBvc2l0aW9uIGFib3V0IGFkb3B0aW5nIHRoaXMgdXNlIGNh
c2VzIGRyYWZ0LiAgVGhlIGNhbGwgd2lsbCBjbG9zZSBvbiBGcmlkYXksDQo+IE5vdmVtYmVyIDIy
LCAyMDEzLg0KPiANCj4gVGhhbmtzIQ0KPiANCj4gQWx2YXJvLg0KPiANCj4gX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4gc3RhdHVzIG1haWxpbmcgbGlz
dA0KPiBzdGF0dXNAaWV0Zi5vcmcNCj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0
aW5mby9zdGF0dXMNCg==


Return-Path: <cfilsfil@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 8926511E8110 for <status@ietfa.amsl.com>; Tue, 12 Nov 2013 00:20:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 avbGxvk7KYvc for <status@ietfa.amsl.com>; Tue, 12 Nov 2013 00:20:10 -0800 (PST)
Received: from ams-iport-3.cisco.com (ams-iport-3.cisco.com [144.254.224.146]) by ietfa.amsl.com (Postfix) with ESMTP id 8513411E80EC for <status@ietf.org>; Tue, 12 Nov 2013 00:20:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=819; q=dns/txt; s=iport; t=1384244410; x=1385454010; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=NClfbxOxxFpc6T7QrCJg1iL6BOInlgoE28IHfcZF718=; b=Yl7IoDXNO/SYunbSLA4Qcpa9g5J2Sbx/257jHjoWgRSSYNVu3mwdKys7 wpuXr53iIEtXP6h08TJIu9b/Nq8D0G12/S+v4YgOky666gZJfoZyhs0JU 1jyNfWnS4lzKbSh161FmV2sdO905chruxTvhoqd7smMKQswaLWUMWBGgy o=;
X-IronPort-AV: E=Sophos;i="4.93,683,1378857600"; d="scan'208";a="18976804"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-3.cisco.com with ESMTP; 12 Nov 2013 08:20:09 +0000
Received: from [10.61.70.92] (ams3-vpn-dhcp1628.cisco.com [10.61.70.92]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id rAC8JqMU023605; Tue, 12 Nov 2013 08:19:54 GMT
Message-ID: <5281E4A9.4050804@cisco.com>
Date: Tue, 12 Nov 2013 09:19:53 +0100
From: Clarence Filsfils <cfilsfil@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: "Alvaro Retana (aretana)" <aretana@cisco.com>
References: <CEA6F54D.40EDD%aretana@cisco.com>
In-Reply-To: <CEA6F54D.40EDD%aretana@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Tue, 12 Nov 2013 05:51:16 -0800
Cc: "John G. Scudder" <jgs@juniper.net>, "status@ietf.org" <status@ietf.org>, "Stefano Previdi \(sprevidi\)" <sprevidi@cisco.com>
Subject: Re: [Status] request to move draft-filsfils-rtgwg-segment-routing-use-cases-02 to wg item
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, 12 Nov 2013 08:20:23 -0000

Support as co-author

Cheers,
Clarence

On 12.11.13 03:00, Alvaro Retana (aretana) wrote:
> On 11/6/13 10:24 PM, "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
> wrote:
>
> Stefano:
>
>> according to what discussed after the presentation of SR Use Cases at
>> ietf88 spring-wg meeting, I'd like to request the adoption of
>> draft-filsfils-rtgwg-segment-routing-use-cases-02.txt as wg item.
>
> I believe there was support for adoption at the meeting in Vancouver..but
> we will still have to confirm it here on the list.
>
> List: This message officially starts the call for adoption.  Please
> indicate your position about adopting this use cases draft.  The call will
> close on Friday, November 22, 2013.
>
> Thanks!
>
> Alvaro.
>
> .
>

-- 
Please excuse brief mail, broken wrist


Return-Path: <bruno.decraene@orange.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 EDF5921E80CC for <status@ietfa.amsl.com>; Tue, 12 Nov 2013 00:12:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.548
X-Spam-Level: 
X-Spam-Status: No, score=-2.548 tagged_above=-999 required=5 tests=[AWL=0.050,  BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
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 m54NIJKM+EJN for <status@ietfa.amsl.com>; Tue, 12 Nov 2013 00:12:13 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by ietfa.amsl.com (Postfix) with ESMTP id 146DF11E80ED for <status@ietf.org>; Tue, 12 Nov 2013 00:12:12 -0800 (PST)
Received: from omfedm06.si.francetelecom.fr (unknown [xx.xx.xx.2]) by omfedm12.si.francetelecom.fr (ESMTP service) with ESMTP id F2CCD18C340; Tue, 12 Nov 2013 09:12:10 +0100 (CET)
Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.1.186]) by omfedm06.si.francetelecom.fr (ESMTP service) with ESMTP id D2FCA27C0B9; Tue, 12 Nov 2013 09:12:10 +0100 (CET)
Received: from PEXCVZYM11.corporate.adroot.infra.ftgroup ([fe80::a441:e6a9:6143:6f0f]) by PEXCVZYH01.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.03.0158.001; Tue, 12 Nov 2013 09:12:10 +0100
From: <bruno.decraene@orange.com>
To: "Alvaro Retana (aretana)" <aretana@cisco.com>, "John G. Scudder" <jgs@juniper.net>
Thread-Topic: [Status] request to move draft-filsfils-rtgwg-segment-routing-use-cases-02 to wg item
Thread-Index: AQHO23E8p83WlqlDLUO90VPM+v9VCJog77WAgABWt0A=
Date: Tue, 12 Nov 2013 08:12:10 +0000
Message-ID: <7886_1384243930_5281E2DA_7886_2719_1_53C29892C857584299CBF5D05346208A070A3A41@PEXCVZYM11.corporate.adroot.infra.ftgroup>
References: <947081B7-F174-4C4D-BE12-56F4FC3A12A8@cisco.com> <CEA6F54D.40EDD%aretana@cisco.com>
In-Reply-To: <CEA6F54D.40EDD%aretana@cisco.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.197.38.3]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2013.11.12.74814
Cc: "Stefano Previdi \(sprevidi\)" <sprevidi@cisco.com>, "Clarence Filsfils \(cfilsfil\)" <cfilsfil@cisco.com>, "status@ietf.org" <status@ietf.org>
Subject: Re: [Status] request to move draft-filsfils-rtgwg-segment-routing-use-cases-02 to wg item
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, 12 Nov 2013 08:12:19 -0000

Alvaro, John,

> request the adoption of draft-filsfils-rtgwg-segment-routing-use-cases-02=
.txt as wg item.

Support as co-author.

Regards,
Bruno

>-----Original Message-----
>From: >Alvaro Retana (aretana) >Sent: Tuesday, November 12, 2013 3:00 AM
>
>On 11/6/13 10:24 PM, "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
>wrote:
>
>Stefano:
>
>>according to what discussed after the presentation of SR Use Cases at
>>ietf88 spring-wg meeting, I'd like to request the adoption of
>>draft-filsfils-rtgwg-segment-routing-use-cases-02.txt as wg item.
>
>I believe there was support for adoption at the meeting in Vancouver..but
>we will still have to confirm it here on the list.
>
>List: This message officially starts the call for adoption.  Please
>indicate your position about adopting this use cases draft.  The call will
>close on Friday, November 22, 2013.
>
>Thanks!
>
>Alvaro.
>
>_______________________________________________
>status mailing list
>status@ietf.org
>https://www.ietf.org/mailman/listinfo/status

___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou =
falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been =
modified, changed or falsified.
Thank you.



Return-Path: <sriganeshkini@gmail.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 B906D11E81D5 for <status@ietfa.amsl.com>; Mon, 11 Nov 2013 23:54:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001]
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 OFJ+f5G63DzF for <status@ietfa.amsl.com>; Mon, 11 Nov 2013 23:54:11 -0800 (PST)
Received: from mail-pa0-x22e.google.com (mail-pa0-x22e.google.com [IPv6:2607:f8b0:400e:c03::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 5611111E819B for <status@ietf.org>; Mon, 11 Nov 2013 23:54:11 -0800 (PST)
Received: by mail-pa0-f46.google.com with SMTP id rd3so1398680pab.33 for <status@ietf.org>; Mon, 11 Nov 2013 23:54:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=D6nhWP/mF/Dl8fP0SjGj78JxIikc4KkKQ3XnXLKHs3I=; b=WgGr4GmbxXwc2kliayEAPgoamfxD0WsB/t6YHDQUegp8PXoRst4mexi8imZj6IEMUy wvSyJ38kOYP14Gij4bZgO7qDg72r+vcOsTkrlfUNNDzAQs5d1iZu0boL/Ml4wX7yfRbH YaKNsfSmfkK9snpSz50GEfqYoTpdmfYSMQ/yFMYZqxUOBTjb00ffZS57+mFf188Ewh9h nCaw9561z46RKoSp5GTRteDRpZezdnZf2aGactiAMJ/UEDzWrlg5A+bMz+0J5GjbEc9z 6oHgeD9mbq5Qby21lApGMvhQNOgTGxeuK0nL1lA40g1c2Xe2BV7Hi/aXhCi49U0CiPyz MkRw==
X-Received: by 10.66.118.129 with SMTP id km1mr7747364pab.127.1384242851097; Mon, 11 Nov 2013 23:54:11 -0800 (PST)
MIME-Version: 1.0
Sender: sriganeshkini@gmail.com
Received: by 10.70.0.228 with HTTP; Mon, 11 Nov 2013 23:53:40 -0800 (PST)
In-Reply-To: <CEA6F54D.40EDD%aretana@cisco.com>
References: <947081B7-F174-4C4D-BE12-56F4FC3A12A8@cisco.com> <CEA6F54D.40EDD%aretana@cisco.com>
From: Sriganesh Kini <sriganesh.kini@ericsson.com>
Date: Mon, 11 Nov 2013 23:53:40 -0800
X-Google-Sender-Auth: xpOgr9nJXigg0zW2LsVaQE9J6Ak
Message-ID: <CAOndX-tFwn2v82W0aW6fgVCP8RGZ5WMg8BCgmNGpG4a0_OLX9w@mail.gmail.com>
To: "Alvaro Retana (aretana)" <aretana@cisco.com>
Content-Type: text/plain; charset=UTF-8
Cc: "Clarence Filsfils \(cfilsfil\)" <cfilsfil@cisco.com>, "John G. Scudder" <jgs@juniper.net>, "status@ietf.org" <status@ietf.org>, "Stefano Previdi \(sprevidi\)" <sprevidi@cisco.com>
Subject: Re: [Status] request to move draft-filsfils-rtgwg-segment-routing-use-cases-02 to wg item
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, 12 Nov 2013 07:54:11 -0000

Support as co-author.

- Sri

On Mon, Nov 11, 2013 at 6:00 PM, Alvaro Retana (aretana)
<aretana@cisco.com> wrote:
> On 11/6/13 10:24 PM, "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
> wrote:
>
> Stefano:
>
>>according to what discussed after the presentation of SR Use Cases at
>>ietf88 spring-wg meeting, I'd like to request the adoption of
>>draft-filsfils-rtgwg-segment-routing-use-cases-02.txt as wg item.
>
> I believe there was support for adoption at the meeting in Vancouver..but
> we will still have to confirm it here on the list.
>
> List: This message officially starts the call for adoption.  Please
> indicate your position about adopting this use cases draft.  The call will
> close on Friday, November 22, 2013.
>
> Thanks!
>
> Alvaro.
>
> _______________________________________________
> status mailing list
> status@ietf.org
> https://www.ietf.org/mailman/listinfo/status


Return-Path: <Ruediger.Geib@telekom.de>
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 13B8011E80FB for <status@ietfa.amsl.com>; Mon, 11 Nov 2013 23:12:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.049
X-Spam-Level: 
X-Spam-Status: No, score=-3.049 tagged_above=-999 required=5 tests=[AWL=0.200,  BAYES_00=-2.599, HELO_EQ_DE=0.35, 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 evmnJmBOvlJj for <status@ietfa.amsl.com>; Mon, 11 Nov 2013 23:12:51 -0800 (PST)
Received: from tcmail93.telekom.de (tcmail93.telekom.de [80.149.113.205]) by ietfa.amsl.com (Postfix) with ESMTP id 9C3FB21E8097 for <status@ietf.org>; Mon, 11 Nov 2013 23:12:51 -0800 (PST)
Received: from he113472.emea1.cds.t-internal.com ([10.134.93.130]) by tcmail91.telekom.de with ESMTP/TLS/AES128-SHA; 12 Nov 2013 08:12:49 +0100
Received: from HE111643.EMEA1.CDS.T-INTERNAL.COM ([169.254.3.39]) by HE113472.emea1.cds.t-internal.com ([::1]) with mapi; Tue, 12 Nov 2013 08:12:49 +0100
From: <Ruediger.Geib@telekom.de>
To: <aretana@cisco.com>
Date: Tue, 12 Nov 2013 08:12:48 +0100
Thread-Topic: [Status] request to move draft-filsfils-rtgwg-segment-routing-use-cases-02 to wg item
Thread-Index: AQHO23E8p83WlqlDLUO90VPM+v9VCJog77WAgABGSEA=
Message-ID: <CA7A7C64CC4ADB458B74477EA99DF6F5021B362083@HE111643.EMEA1.CDS.T-INTERNAL.COM>
References: <947081B7-F174-4C4D-BE12-56F4FC3A12A8@cisco.com> <CEA6F54D.40EDD%aretana@cisco.com>
In-Reply-To: <CEA6F54D.40EDD%aretana@cisco.com>
Accept-Language: en-US, de-DE
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, de-DE
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: jgs@juniper.net, sprevidi@cisco.com, cfilsfil@cisco.com, status@ietf.org
Subject: Re: [Status] request to move draft-filsfils-rtgwg-segment-routing-use-cases-02 to wg item
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, 12 Nov 2013 07:12:56 -0000

Alvaro,

I favor adoption as a WG draft.

Regards,

Ruediger

-----Original Message-----
From: status-bounces@ietf.org [mailto:status-bounces@ietf.org] On Behalf Of=
 Alvaro Retana (aretana)
Sent: Tuesday, November 12, 2013 3:00 AM
To: Stefano Previdi (sprevidi); status@ietf.org
Cc: John G. Scudder; Clarence Filsfils (cfilsfil)
Subject: Re: [Status] request to move draft-filsfils-rtgwg-segment-routing-=
use-cases-02 to wg item

On 11/6/13 10:24 PM, "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
wrote:

Stefano:

>according to what discussed after the presentation of SR Use Cases at
>ietf88 spring-wg meeting, I'd like to request the adoption of
>draft-filsfils-rtgwg-segment-routing-use-cases-02.txt as wg item.

I believe there was support for adoption at the meeting in Vancouver..but
we will still have to confirm it here on the list.

List: This message officially starts the call for adoption.  Please
indicate your position about adopting this use cases draft.  The call will
close on Friday, November 22, 2013.

Thanks!

Alvaro.

_______________________________________________
status mailing list
status@ietf.org
https://www.ietf.org/mailman/listinfo/status


Return-Path: <rraszuk@gmail.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 AC92111E810E for <status@ietfa.amsl.com>; Mon, 11 Nov 2013 22:19:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.556
X-Spam-Level: 
X-Spam-Status: No, score=-1.556 tagged_above=-999 required=5 tests=[AWL=0.422,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001]
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 KXucOUY-dQIb for <status@ietfa.amsl.com>; Mon, 11 Nov 2013 22:19:14 -0800 (PST)
Received: from mail-ie0-x230.google.com (mail-ie0-x230.google.com [IPv6:2607:f8b0:4001:c03::230]) by ietfa.amsl.com (Postfix) with ESMTP id 0313C11E80E2 for <status@ietf.org>; Mon, 11 Nov 2013 22:19:04 -0800 (PST)
Received: by mail-ie0-f176.google.com with SMTP id x13so6406125ief.21 for <status@ietf.org>; Mon, 11 Nov 2013 22:19:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=Ou6p7c+T7nJ/JJG0xFgkxKFGjYTI8UrbikOwDaN7cNQ=; b=S/hClvJutcpkYJsN+IUXZksKdOvJawjAawn4kJnw7cVA/CZYXhlSi5O2ztnvNuQnr0 EjInm48IriNNHwer8wcYSmhsE3hPUdzaAS9Q7XTgY8PhVbDkAsc9ei7/sEeUcD6a5Z4U N9iHMfXL6RQYx6lPbF8VrOiZPTeHleuVlIl7oi6JL/N1Ks+7VJWqHa77ygPXGoav8wi7 bFZMSD5F4jrfn04wXrNW+Owe+uFJwttdchsa5HSdcfaW20XRmCIBXbuuQmCfQG3vhBW9 gPKbGHYLMNLOLkBt5XMV1tG2g49GLtMNIQkhL+c9YocW4j8A9hdqaA7kPRaHdLFmuXAq D7lA==
MIME-Version: 1.0
X-Received: by 10.50.11.67 with SMTP id o3mr14616122igb.55.1384237144347; Mon, 11 Nov 2013 22:19:04 -0800 (PST)
Sender: rraszuk@gmail.com
Received: by 10.64.61.129 with HTTP; Mon, 11 Nov 2013 22:19:04 -0800 (PST)
In-Reply-To: <CEA6F54D.40EDD%aretana@cisco.com>
References: <947081B7-F174-4C4D-BE12-56F4FC3A12A8@cisco.com> <CEA6F54D.40EDD%aretana@cisco.com>
Date: Tue, 12 Nov 2013 07:19:04 +0100
X-Google-Sender-Auth: V3SyF9R5A-IbeSvir-viyRDh3Vg
Message-ID: <CA+b+ER=NMM872ffE=Me5u-X9FTzxEPGgxdqZPvw3__VQ_fZbPA@mail.gmail.com>
From: Robert Raszuk <robert@raszuk.net>
To: "Alvaro Retana (aretana)" <aretana@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "Clarence Filsfils \(cfilsfil\)" <cfilsfil@cisco.com>, "John G. Scudder" <jgs@juniper.net>, "status@ietf.org" <status@ietf.org>, "Stefano Previdi \(sprevidi\)" <sprevidi@cisco.com>
Subject: Re: [Status] request to move draft-filsfils-rtgwg-segment-routing-use-cases-02 to wg item
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, 12 Nov 2013 06:19:14 -0000

support.

r.

On Tue, Nov 12, 2013 at 3:00 AM, Alvaro Retana (aretana)
<aretana@cisco.com> wrote:
> On 11/6/13 10:24 PM, "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
> wrote:
>
> Stefano:
>
>>according to what discussed after the presentation of SR Use Cases at
>>ietf88 spring-wg meeting, I'd like to request the adoption of
>>draft-filsfils-rtgwg-segment-routing-use-cases-02.txt as wg item.
>
> I believe there was support for adoption at the meeting in Vancouver..but
> we will still have to confirm it here on the list.
>
> List: This message officially starts the call for adoption.  Please
> indicate your position about adopting this use cases draft.  The call will
> close on Friday, November 22, 2013.
>
> Thanks!
>
> Alvaro.
>
> _______________________________________________
> status mailing list
> status@ietf.org
> https://www.ietf.org/mailman/listinfo/status


Return-Path: <wim.henderickx@alcatel-lucent.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 55FD511E8103 for <status@ietfa.amsl.com>; Mon, 11 Nov 2013 22:08:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.28
X-Spam-Level: 
X-Spam-Status: No, score=-9.28 tagged_above=-999 required=5 tests=[AWL=1.319,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 EzPRK2HoWOgk for <status@ietfa.amsl.com>; Mon, 11 Nov 2013 22:07:54 -0800 (PST)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id 5E95511E80D9 for <status@ietf.org>; Mon, 11 Nov 2013 22:07:52 -0800 (PST)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (h135-239-2-122.lucent.com [135.239.2.122]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id rAC67iXn005582 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 12 Nov 2013 00:07:46 -0600 (CST)
Received: from FR711WXCHHUB01.zeu.alcatel-lucent.com (fr711wxchhub01.zeu.alcatel-lucent.com [135.239.2.111]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id rAC67il8017563 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 12 Nov 2013 07:07:44 +0100
Received: from FR711WXCHMBA05.zeu.alcatel-lucent.com ([169.254.1.146]) by FR711WXCHHUB01.zeu.alcatel-lucent.com ([135.239.2.111]) with mapi id 14.02.0247.003; Tue, 12 Nov 2013 07:07:44 +0100
From: "Henderickx, Wim (Wim)" <wim.henderickx@alcatel-lucent.com>
To: "'pierre.francois@imdea.org'" <pierre.francois@imdea.org>, "'jeff.tantsura@ericsson.com'" <jeff.tantsura@ericsson.com>
Thread-Topic: [Status] request to move draft-filsfils-rtgwg-segment-routing-use-cases-02 to wg item
Thread-Index: AQHO32EkSKO5qdh0dEa4378w7hhibJohHDyV
Date: Tue, 12 Nov 2013 06:07:43 +0000
Message-ID: <82FB08F009780940837EB830C283F28408E88625@FR711WXCHMBA05.zeu.alcatel-lucent.com>
In-Reply-To: <96EF5ECD-7883-4D6F-862E-01974EEC8BC2@imdea.org>
Accept-Language: nl-BE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.239.27.39]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
Cc: "'cfilsfil@cisco.com'" <cfilsfil@cisco.com>, "'aretana@cisco.com'" <aretana@cisco.com>, "'status@ietf.org'" <status@ietf.org>, "'sprevidi@cisco.com'" <sprevidi@cisco.com>, "'jgs@juniper.net'" <jgs@juniper.net>
Subject: Re: [Status] request to move	draft-filsfils-rtgwg-segment-routing-use-cases-02 to wg item
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, 12 Nov 2013 06:08:00 -0000

Support as co-author

Cheers,
Wim
_________________
sent from blackberry

----- Original Message -----
From: Pierre Francois [mailto:pierre.francois@imdea.org]
Sent: Tuesday, November 12, 2013 05:38 AM=0A=
To: Jeff Tantsura <jeff.tantsura@ericsson.com>
Cc: Alvaro Retana (aretana) <aretana@cisco.com>; Stefano Previdi (sprevidi)=
 <sprevidi@cisco.com>; status@ietf.org <status@ietf.org>; Clarence Filsfils=
 (cfilsfil) <cfilsfil@cisco.com>; John G. Scudder <jgs@juniper.net>
Subject: Re: [Status] request to move	draft-filsfils-rtgwg-segment-routing-=
use-cases-02 to wg item

Same.=20

Sent from my iPhone

> On Nov 12, 2013, at 5:31 AM, Jeff Tantsura <jeff.tantsura@ericsson.com> w=
rote:
>=20
> Yes/support as coauthor=20
>=20
> Regards,
> Jeff
>=20
>> On Nov 11, 2013, at 18:00, "Alvaro Retana (aretana)" <aretana@cisco.com>=
 wrote:
>>=20
>> On 11/6/13 10:24 PM, "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
>> wrote:
>>=20
>> Stefano:
>>=20
>>> according to what discussed after the presentation of SR Use Cases at
>>> ietf88 spring-wg meeting, I'd like to request the adoption of
>>> draft-filsfils-rtgwg-segment-routing-use-cases-02.txt as wg item.
>>=20
>> I believe there was support for adoption at the meeting in Vancouver..bu=
t
>> we will still have to confirm it here on the list.
>>=20
>> List: This message officially starts the call for adoption.  Please
>> indicate your position about adopting this use cases draft.  The call wi=
ll
>> close on Friday, November 22, 2013.
>>=20
>> Thanks!
>>=20
>> Alvaro.
>>=20
>> _______________________________________________
>> 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
_______________________________________________
status mailing list
status@ietf.org
https://www.ietf.org/mailman/listinfo/status


Return-Path: <pierre.francois@imdea.org>
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 F2FB311E811D for <status@ietfa.amsl.com>; Mon, 11 Nov 2013 20:39:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.203
X-Spam-Level: 
X-Spam-Status: No, score=-1.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
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 5sf8gZiRFvWl for <status@ietfa.amsl.com>; Mon, 11 Nov 2013 20:39:04 -0800 (PST)
Received: from estafeta21.imdea.org (maquina46.madrimasd.org [193.145.15.46]) by ietfa.amsl.com (Postfix) with ESMTP id BC29D11E8117 for <status@ietf.org>; Mon, 11 Nov 2013 20:39:01 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by estafeta21.imdea.org (imdea mail daemon) with ESMTP id 395881B7624;  Tue, 12 Nov 2013 05:37:50 +0100 (CET)
X-Virus-Scanned: by antispam-antivirus system at imdea.org
Received: from estafeta21.imdea.org ([127.0.0.1]) by localhost (estafeta21.imdea.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bullTT8NuU4F; Tue, 12 Nov 2013 05:37:49 +0100 (CET)
Received: from [10.179.209.103] (212.Red-176-83-95.dynamicIP.rima-tde.net [176.83.95.212]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: pierre.francois) by estafeta21.imdea.org (imdea mail daemon) with ESMTPSA id A9D031B7623; Tue, 12 Nov 2013 05:37:49 +0100 (CET)
References: <947081B7-F174-4C4D-BE12-56F4FC3A12A8@cisco.com> <CEA6F54D.40EDD%aretana@cisco.com> <5737C915-2EFF-401B-8106-791A9BAED2A6@ericsson.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <5737C915-2EFF-401B-8106-791A9BAED2A6@ericsson.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <96EF5ECD-7883-4D6F-862E-01974EEC8BC2@imdea.org>
X-Mailer: iPhone Mail (11A501)
From: Pierre Francois <pierre.francois@imdea.org>
Date: Tue, 12 Nov 2013 05:38:55 +0100
To: Jeff Tantsura <jeff.tantsura@ericsson.com>
Cc: "Alvaro Retana \(aretana\)" <aretana@cisco.com>, "Stefano Previdi \(sprevidi\)" <sprevidi@cisco.com>, "status@ietf.org" <status@ietf.org>, "Clarence Filsfils \(cfilsfil\)" <cfilsfil@cisco.com>, "John G. Scudder" <jgs@juniper.net>
Subject: Re: [Status] request to move draft-filsfils-rtgwg-segment-routing-use-cases-02 to wg item
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, 12 Nov 2013 04:39:09 -0000

Same.=20

Sent from my iPhone

> On Nov 12, 2013, at 5:31 AM, Jeff Tantsura <jeff.tantsura@ericsson.com> wr=
ote:
>=20
> Yes/support as coauthor=20
>=20
> Regards,
> Jeff
>=20
>> On Nov 11, 2013, at 18:00, "Alvaro Retana (aretana)" <aretana@cisco.com> w=
rote:
>>=20
>> On 11/6/13 10:24 PM, "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
>> wrote:
>>=20
>> Stefano:
>>=20
>>> according to what discussed after the presentation of SR Use Cases at
>>> ietf88 spring-wg meeting, I'd like to request the adoption of
>>> draft-filsfils-rtgwg-segment-routing-use-cases-02.txt as wg item.
>>=20
>> I believe there was support for adoption at the meeting in Vancouver..but=

>> we will still have to confirm it here on the list.
>>=20
>> List: This message officially starts the call for adoption.  Please
>> indicate your position about adopting this use cases draft.  The call wil=
l
>> close on Friday, November 22, 2013.
>>=20
>> Thanks!
>>=20
>> Alvaro.
>>=20
>> _______________________________________________
>> 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


Return-Path: <jeff.tantsura@ericsson.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 38BA311E811D for <status@ietfa.amsl.com>; Mon, 11 Nov 2013 20:31:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.476
X-Spam-Level: 
X-Spam-Status: No, score=-2.476 tagged_above=-999 required=5 tests=[AWL=0.123,  BAYES_00=-2.599]
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 h+De0Mz-Tq9L for <status@ietfa.amsl.com>; Mon, 11 Nov 2013 20:31:36 -0800 (PST)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) by ietfa.amsl.com (Postfix) with ESMTP id 49C6411E8117 for <status@ietf.org>; Mon, 11 Nov 2013 20:31:36 -0800 (PST)
X-AuditID: c6180641-b7fbd8e0000011cc-85-5281af2779c1
Received: from EUSAAHC003.ericsson.se (Unknown_Domain [147.117.188.81]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id 9B.AE.04556.72FA1825; Tue, 12 Nov 2013 05:31:35 +0100 (CET)
Received: from EUSAAMB106.ericsson.se ([147.117.188.123]) by EUSAAHC003.ericsson.se ([147.117.188.81]) with mapi id 14.02.0328.009; Mon, 11 Nov 2013 23:31:35 -0500
From: Jeff Tantsura <jeff.tantsura@ericsson.com>
To: "Alvaro Retana (aretana)" <aretana@cisco.com>
Thread-Topic: [Status] request to move draft-filsfils-rtgwg-segment-routing-use-cases-02 to wg item
Thread-Index: AQHO23E8p83WlqlDLUO90VPM+v9VCJog77WAgAAZjHU=
Date: Tue, 12 Nov 2013 04:31:34 +0000
Message-ID: <5737C915-2EFF-401B-8106-791A9BAED2A6@ericsson.com>
References: <947081B7-F174-4C4D-BE12-56F4FC3A12A8@cisco.com>, <CEA6F54D.40EDD%aretana@cisco.com>
In-Reply-To: <CEA6F54D.40EDD%aretana@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrOLMWRmVeSWpSXmKPExsUyuXRPoK76+sYgg3UbpC3+/tzKaLFzdg+b xcwbX1kt1u9+xGTxuvkikwOrx5TfG1k9liz5yeRxvekqewBzFJdNSmpOZllqkb5dAldG98LV 7AVn2St+/vvE0sA4l62LkZNDQsBEonPPbChbTOLCvfVANheHkMARRon9ez8yQjjLGSXuf28E q2ITMJD4/+04C4gtImAoMfPmfhaQImaBHYwSN27dZQJJCAukSLzbvZ4NoihVYtfKO1C2lcSh /xPAmlkEVCX+rvwOZvMK2Etc2bGIFcQWEoiXOH78JiOIzSmgLzH50kMwmxHovO+n1oDNZxYQ l7j1ZD4TxNkCEkv2nGeGsEUlXj7+xwpRoyOxYPcnNghbW2LZwtfMELsEJU7OfMIygVF0FpJR s5C0zELSMgtJywJGllWMHKXFqWW56UaGmxiBkXNMgs1xB+OCT5aHGKU5WJTEeb+8dQ4SEkhP LEnNTk0tSC2KLyrNSS0+xMjEwSnVwMhzeuXGSWVO6117t7zPDPeaOiEmbp7z+yABNpZWc8kw j+DqW/taFFVeKamzimxwvcl4a17RiXsuRcL91bYv/PZyaQmWfzsx+94E/hMPjx2xnL5jw/xf +t/qgrrSrnGePfhATpHz2P5d135bdemlrGEs5HasSd94kafRepvx9by12VOWXDtZ90SJpTgj 0VCLuag4EQDj+x53agIAAA==
Cc: "Clarence Filsfils \(cfilsfil\)" <cfilsfil@cisco.com>, "John G. Scudder" <jgs@juniper.net>, "status@ietf.org" <status@ietf.org>, "Stefano Previdi \(sprevidi\)" <sprevidi@cisco.com>
Subject: Re: [Status] request to move draft-filsfils-rtgwg-segment-routing-use-cases-02 to wg item
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, 12 Nov 2013 04:31:42 -0000

Yes/support as coauthor=20

Regards,
Jeff

> On Nov 11, 2013, at 18:00, "Alvaro Retana (aretana)" <aretana@cisco.com> =
wrote:
>=20
> On 11/6/13 10:24 PM, "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
> wrote:
>=20
> Stefano:
>=20
>> according to what discussed after the presentation of SR Use Cases at
>> ietf88 spring-wg meeting, I'd like to request the adoption of
>> draft-filsfils-rtgwg-segment-routing-use-cases-02.txt as wg item.
>=20
> I believe there was support for adoption at the meeting in Vancouver..but
> we will still have to confirm it here on the list.
>=20
> List: This message officially starts the call for adoption.  Please
> indicate your position about adopting this use cases draft.  The call wil=
l
> close on Friday, November 22, 2013.
>=20
> Thanks!
>=20
> Alvaro.
>=20
> _______________________________________________
> status mailing list
> status@ietf.org
> https://www.ietf.org/mailman/listinfo/status


Return-Path: <xuxiaohu@huawei.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 35FC211E819A for <status@ietfa.amsl.com>; Mon, 11 Nov 2013 19:07:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.13
X-Spam-Level: *
X-Spam-Status: No, score=1.13 tagged_above=-999 required=5 tests=[AWL=-1.658,  BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, CN_BODY_35=0.339,  MIME_8BIT_HEADER=0.3, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4, SARE_SUB_ENC_GB2312=1.345]
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 ABFPfrGQFYzW for <status@ietfa.amsl.com>; Mon, 11 Nov 2013 19:07:29 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 6583511E8189 for <status@ietf.org>; Mon, 11 Nov 2013 19:07:28 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id AXT99412; Tue, 12 Nov 2013 03:07:27 +0000 (GMT)
Received: from LHREML406-HUB.china.huawei.com (10.201.5.243) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 12 Nov 2013 03:06:32 +0000
Received: from NKGEML403-HUB.china.huawei.com (10.98.56.34) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 12 Nov 2013 03:07:26 +0000
Received: from NKGEML512-MBS.china.huawei.com ([169.254.8.193]) by nkgeml403-hub.china.huawei.com ([10.98.56.34]) with mapi id 14.03.0158.001; Tue, 12 Nov 2013 09:56:32 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: "Alvaro Retana (aretana)" <aretana@cisco.com>, "<status@ietf.org>" <status@ietf.org>
Thread-Topic: DRAFT minutes from the SPRING 1st WG meeting at IETF88
Thread-Index: AQHO2cSHklPivvqJ6ke/Dt+VYcH8LZogt4eAgAAo4IA=
Date: Tue, 12 Nov 2013 01:56:31 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08228298@NKGEML512-MBS.china.huawei.com>
References: <A5C2F302-5500-4535-B880-DF9BC08C0603@cisco.com> <CEA6C3B6.40E61%aretana@cisco.com>
In-Reply-To: <CEA6C3B6.40E61%aretana@cisco.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.134]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "Carlos Pignataro \(cpignata\)" <cpignata@cisco.com>
Subject: [Status] =?gb2312?b?tPC4tDogRFJBRlQgbWludXRlcyBmcm9tIHRoZSBTUFJJ?= =?gb2312?b?TkcgMXN0IFdHIG1lZXRpbmcgYXQgSUVURjg4?=
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, 12 Nov 2013 03:07:44 -0000

SGkgQWx2YXJvLA0KDQpUaGUgZm9sbG93aW5nIG1pbnV0ZXMgaXMgbm90IGNvcnJlY3Qgc2luY2Ug
ZHJhZnQteHUtcnRnd2ctZ2xvYmFsLWxhYmVsLWFkdiBoYXMgbm90IGJlZW4gcHJlc2VudGVkLg0K
DQpvIEFkdmVydGlzaW5nIEdsb2JhbCBMYWJlbHMgVXNpbmcgSUdQDQoNCiAgaHR0cDovL3Rvb2xz
LmlldGYub3JnL2h0bWwvZHJhZnQteHUtcnRnd2ctZ2xvYmFsLWxhYmVsLWFkdg0KDQogIFhpYW9o
dSBYdSAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgMTAgbWludXRl
cw0KDQo/QWx2YXJvOiBZb3UgaGF2ZSA0IG1pbnV0ZXOhrQ0KP1poZW5iaW46IE5leHQuIEJhY2tn
cm91bmQsIFZpcnR1YWwgT3BlcmF0b3JzIHdhbnQgdG8gdXNlIHZpcnR1YWwgbmV0d29yayB0byBk
ZXBsb3kgc2VydmljZXMuIFRoZXkgZG8gbm90IHdhbnQgdG8ga25vdyB0aGUgZGV0YWlscyBvZiB0
aGUgcGh5c2ljYWwgbmV0d29yay4gQmFzZWQgb24gdGhpcyB3ZSBoYXZlIHRoaXMgZG9jLg0KP6Gt
IGhlcmUgd2UgaW1wbGVtZW50IHRoZSBNUExTIHZpcnR1YWwgbmV0d29yay4gVGhpcyBpcyB0aGUg
cGh5c2ljYWwgbmV0d29yayBvcGVyYXRvci4gVGhlcmUgaXMgYW4gSUdQIGNvbnRyb2xsZXIgYW5k
IElHUCBjbGllbnQuIFRoZXJloa9zIGEgY2VudHJhbCBJR1AgY29udHJvbGxlci4gQW5kIHRoZXJl
IGFyZSB2aXJ0dWFsIG5ldHdvcmsgb3BlcmF0b3JzIHRoYXQgY2FuIGhhdmUgdmlydHVhbCBuZXR3
b3JrIHRvcG9sb2dpZXMuIA0KP6GtIGhlcmUgd2UgY2FuIHNlZSBhbiBleGFtcGxlLiBUaGUgTVBM
UyBHbG9iYWwgbGFiZWwgaWRlbnRpZmllcyB0aGUgdG9wb2xvZ3kuIFlvdSBkbyBub3Qgc2VlIHRo
ZSBkZXRhaWxzIG9mIHRoZSB1bmRlcmx5aW5nIG5ldHdvcmsuDQo/oa0gV2UgaGF2ZSB0aGlzIGRy
YWZ0IGluIElTSVMsIGFuZCB3ZSBhbnQgdGhpcyBzb2x1dGlvbiBmb3IgZmFpbHVyZSBzb2x1dGlv
bnMuDQo/oa0gd2UgcHJvcG9zZSB0aGVzZSBhdHRyaWJ1dGVzIGZvciBhIHZpcnR1YWwgbGluay4g
DQo/oa0gdGhpcyBpcyB0aGUgZm9yd2FyZGluZyBpbiB0aGUgdmlydHVhbCBuZXR3b3JrLiBXZSBo
YXZlIHRoZSB2aXJ0dWFsIGxpbmssIHZpcnR1YWwgbm9kZSwgYW5kIHZpcnR1YWwgdG9wb2xvZ3ku
DQo/oa0gV2Ugd2FudCB0byBidWlsZCB0aGUgZ2xvYmFsIGxhYmVsIGZvciBtdXRpLXRvcG9sb2d5
IEZJQi4NCg0KDQpCZXN0IHJlZ2FyZHMsDQpYaWFvaHUNCj4gLS0tLS3Tyrz+1K28/i0tLS0tDQo+
ILeivP7Iyzogc3RhdHVzLWJvdW5jZXNAaWV0Zi5vcmcgW21haWx0bzpzdGF0dXMtYm91bmNlc0Bp
ZXRmLm9yZ10gtPqx7SBBbHZhcm8NCj4gUmV0YW5hIChhcmV0YW5hKQ0KPiC3osvNyrG85DogMjAx
M8TqMTHUwjEyyNUgNjoyNw0KPiDK1bz+yMs6IDxzdGF0dXNAaWV0Zi5vcmc+DQo+ILOty806IENh
cmxvcyBQaWduYXRhcm8gKGNwaWduYXRhKQ0KPiDW98ziOiBSZTogW1N0YXR1c10gRFJBRlQgbWlu
dXRlcyBmcm9tIHRoZSBTUFJJTkcgMXN0IFdHIG1lZXRpbmcgYXQgSUVURjg4DQo+IA0KPiBIaSEN
Cj4gDQo+IEkganVzdCBwb3N0ZWQgdGhlICh1cGRhdGVkKSBkcmFmdCBtaW51dGVzIGZyb20gbGFz
dCB3ZWVrLg0KPiANCj4gaHR0cDovL3d3dy5pZXRmLm9yZy9wcm9jZWVkaW5ncy84OC9taW51dGVz
L21pbnV0ZXMtODgtc3ByaW5nDQo+IA0KPiBUaGFua3MgdG8gQ2FybG9zIGZvciBiZWluZyB0aGUg
bm90ZSB0YWtlci4NCj4gDQo+IEFsdmFyby4NCj4gDQo+IF9fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fDQo+IHN0YXR1cyBtYWlsaW5nIGxpc3QNCj4gc3RhdHVz
QGlldGYub3JnDQo+IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vc3RhdHVz
DQo=


Return-Path: <aretana@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 9301911E819B for <status@ietfa.amsl.com>; Mon, 11 Nov 2013 18:00:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 rAKQckjCVwPM for <status@ietfa.amsl.com>; Mon, 11 Nov 2013 18:00:17 -0800 (PST)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id C8D5711E8184 for <status@ietf.org>; Mon, 11 Nov 2013 18:00:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=633; q=dns/txt; s=iport; t=1384221618; x=1385431218; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=F+TfZM0P9JjyVzzgUFxKRWifJn2owuJ20Yb1+5mvjgk=; b=YHX+N9qeJF6dtym7OgK5vLpgzK2xXfUjcJFwmD1Imyy0o2fMaWqsk2Jl yKPi2Ok7z4BIzW5eOjI1tTITDzLhcnYoY2almhQD7xlCf406oT3gUIgJ5 07ucs5hq87XKhG2XIA02vkwZ1MaE9e2lNvigHt02rN+KxjYUy0lle7Cj8 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgsFADGLgVKtJV2Z/2dsb2JhbABZgweBC78bgUEWdIIsHR0/EgEINkIlAgQBDQWIAb5Uj1oHhDADmA+SCoFogT6CKg
X-IronPort-AV: E=Sophos;i="4.93,681,1378857600"; d="scan'208";a="283461675"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-7.cisco.com with ESMTP; 12 Nov 2013 02:00:11 +0000
Received: from xhc-rcd-x04.cisco.com (xhc-rcd-x04.cisco.com [173.37.183.78]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id rAC20B3X006789 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 12 Nov 2013 02:00:11 GMT
Received: from xmb-aln-x15.cisco.com ([169.254.9.147]) by xhc-rcd-x04.cisco.com ([fe80::200:5efe:173.37.183.34%12]) with mapi id 14.03.0123.003; Mon, 11 Nov 2013 20:00:11 -0600
From: "Alvaro Retana (aretana)" <aretana@cisco.com>
To: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>, "status@ietf.org" <status@ietf.org>
Thread-Topic: request to move draft-filsfils-rtgwg-segment-routing-use-cases-02 to wg item
Thread-Index: AQHO23E8p83WlqlDLUO90VPM+v9VCJog77WA
Date: Tue, 12 Nov 2013 02:00:10 +0000
Message-ID: <CEA6F54D.40EDD%aretana@cisco.com>
In-Reply-To: <947081B7-F174-4C4D-BE12-56F4FC3A12A8@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.117.15.4]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <EFEEA4AC2337DF418F73B589A65113B2@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "John G. Scudder" <jgs@juniper.net>, "Clarence Filsfils \(cfilsfil\)" <cfilsfil@cisco.com>
Subject: Re: [Status] request to move draft-filsfils-rtgwg-segment-routing-use-cases-02 to wg item
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, 12 Nov 2013 02:00:23 -0000

On 11/6/13 10:24 PM, "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
wrote:

Stefano:

>according to what discussed after the presentation of SR Use Cases at
>ietf88 spring-wg meeting, I'd like to request the adoption of
>draft-filsfils-rtgwg-segment-routing-use-cases-02.txt as wg item.

I believe there was support for adoption at the meeting in Vancouver..but
we will still have to confirm it here on the list.

List: This message officially starts the call for adoption.  Please
indicate your position about adopting this use cases draft.  The call will
close on Friday, November 22, 2013.

Thanks!

Alvaro.



Return-Path: <ida@brumund.ca>
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 CD26B21E8147 for <status@ietfa.amsl.com>; Mon, 11 Nov 2013 17:22:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.676
X-Spam-Level: 
X-Spam-Status: No, score=-2.676 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, 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 1SrHm7XJpHVs for <status@ietfa.amsl.com>; Mon, 11 Nov 2013 17:22:18 -0800 (PST)
Received: from mail-lb0-f180.google.com (mail-lb0-f180.google.com [209.85.217.180]) by ietfa.amsl.com (Postfix) with ESMTP id F347D21E8142 for <status@ietf.org>; Mon, 11 Nov 2013 17:22:17 -0800 (PST)
Received: by mail-lb0-f180.google.com with SMTP id y6so3876872lbh.25 for <status@ietf.org>; Mon, 11 Nov 2013 17:22:13 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=MpxpsCHLRPMwUJLKoGPsuwIvv9kwvoqiKI0SZNTL7/k=; b=RHTpdYTlfX9JC7fUSVCgMSAIr6ZDrYjAc30aevnCjCeizjJsZ2kcTB/Qqhy8RJIh+8 Qr/Ijyoo8RPuvE/td3e00i0FfrhlVhGXVoEXl1L67YvS4W0Jwv3nATb3xzrL61uREoym kIXySXZKrabR+h5Qp8lefih2RwoKQc/9Gx/uLtVcfv4AJJlQU/nq8vJDTvf7z8atImDZ KtiuZK8zqfV0qcg2F1KhGEelrzhD2mDqBhxB37vIZ2mjZz8x8zdCnq/xX2oMP2PDnE9D dvWaAVty0TJ4DQUl4fmTTZQmDbpkZXAeMYJNk9sQ32HPGlhkRgjJzOEUvyw+pYiXuIPP j1Jg==
X-Gm-Message-State: ALoCoQk0Q71yW5T2XxnXG3d+d9iUoPCJBCNqGJ2oEfuN05jus50zJxZD8CGRaxcyHCnxljp9U1kC
MIME-Version: 1.0
X-Received: by 10.112.125.33 with SMTP id mn1mr24117555lbb.8.1384219333355; Mon, 11 Nov 2013 17:22:13 -0800 (PST)
Received: by 10.112.168.103 with HTTP; Mon, 11 Nov 2013 17:22:13 -0800 (PST)
X-Originating-IP: [24.114.70.141]
In-Reply-To: <mailman.144.1383854476.12253.status@ietf.org>
References: <mailman.144.1383854476.12253.status@ietf.org>
Date: Mon, 11 Nov 2013 20:22:13 -0500
Message-ID: <CALFC0Y3V6ZTb+X_r6CZW6kBwtPy3-enzF5ryRzu2_pX7EUmPkw@mail.gmail.com>
From: Ida Leung <ida@brumund.ca>
To: status@ietf.org
Content-Type: multipart/alternative; boundary=089e0116136aa7fd2e04eaf0ad80
Subject: Re: [Status] status Digest, Vol 6, Issue 3
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, 12 Nov 2013 01:22:23 -0000

--089e0116136aa7fd2e04eaf0ad80
Content-Type: text/plain; charset=ISO-8859-1

I will support the move of the SR user cases to the WG item.  A lot of the
user cases in the draft are applied to my company as well.

Thanks,

...Ida


On Thu, Nov 7, 2013 at 3:01 PM, <status-request@ietf.org> wrote:

> If you have received this digest without all the individual message
> attachments you will need to update your digest options in your list
> subscription.  To do so, go to
>
> https://www.ietf.org/mailman/listinfo/status
>
> Click the 'Unsubscribe or edit options' button, log in, and set "Get
> MIME or Plain Text Digests?" to MIME.  You can set this option
> globally for all the list digests you receive at this point.
>
>
>
> Send status mailing list submissions to
>         status@ietf.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://www.ietf.org/mailman/listinfo/status
> or, via email, send a message with subject or body 'help' to
>         status-request@ietf.org
>
> You can reach the person managing the list at
>         status-owner@ietf.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of status digest..."
>
> Today's Topics:
>
>    1. request to move
>       draft-filsfils-rtgwg-segment-routing-use-cases-02 to wg item
>       (Stefano Previdi (sprevidi))
>
>
> ---------- Forwarded message ----------
> From: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
> To: "John G. Scudder" <jgs@juniper.net>, "Alvaro Retana (aretana)" <
> aretana@cisco.com>, "status@ietf.org" <status@ietf.org>
> Cc: "Clarence Filsfils \(cfilsfil\)" <cfilsfil@cisco.com>
> Date: Thu, 7 Nov 2013 04:24:23 +0000
> Subject: [Status] request to move
> draft-filsfils-rtgwg-segment-routing-use-cases-02 to wg item
> John, Alvaro, All,
>
> according to what discussed after the presentation of SR Use Cases at
> ietf88 spring-wg meeting, I'd like to request the adoption of
> draft-filsfils-rtgwg-segment-routing-use-cases-02.txt as wg item.
>
> Thanks.
> s.
>
>
>
>
> _______________________________________________
> status mailing list
> status@ietf.org
> https://www.ietf.org/mailman/listinfo/status
>
>

--089e0116136aa7fd2e04eaf0ad80
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I will support the move of the SR user cases to the WG ite=
m. =A0A lot of the user cases in the draft are applied to my company as wel=
l.<div><br></div><div>Thanks,</div><div><br></div><div>...Ida</div></div><d=
iv class=3D"gmail_extra">
<br><br><div class=3D"gmail_quote">On Thu, Nov 7, 2013 at 3:01 PM,  <span d=
ir=3D"ltr">&lt;<a href=3D"mailto:status-request@ietf.org" target=3D"_blank"=
>status-request@ietf.org</a>&gt;</span> wrote:<br><blockquote class=3D"gmai=
l_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left=
:1ex">
If you have received this digest without all the individual message<br>
attachments you will need to update your digest options in your list<br>
subscription. =A0To do so, go to<br>
<br>
<a href=3D"https://www.ietf.org/mailman/listinfo/status" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/status</a><br>
<br>
Click the &#39;Unsubscribe or edit options&#39; button, log in, and set &qu=
ot;Get<br>
MIME or Plain Text Digests?&quot; to MIME. =A0You can set this option<br>
globally for all the list digests you receive at this point.<br>
<br>
<br>
<br>
Send status mailing list submissions to<br>
=A0 =A0 =A0 =A0 <a href=3D"mailto:status@ietf.org">status@ietf.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
=A0 =A0 =A0 =A0 <a href=3D"https://www.ietf.org/mailman/listinfo/status" ta=
rget=3D"_blank">https://www.ietf.org/mailman/listinfo/status</a><br>
or, via email, send a message with subject or body &#39;help&#39; to<br>
=A0 =A0 =A0 =A0 <a href=3D"mailto:status-request@ietf.org">status-request@i=
etf.org</a><br>
<br>
You can reach the person managing the list at<br>
=A0 =A0 =A0 =A0 <a href=3D"mailto:status-owner@ietf.org">status-owner@ietf.=
org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than &quot;Re: Contents of status digest...&quot;<br>
<br>Today&#39;s Topics:<br>
<br>
=A0 =A01. request to move<br>
=A0 =A0 =A0 draft-filsfils-rtgwg-segment-routing-use-cases-02 to wg item<br=
>
=A0 =A0 =A0 (Stefano Previdi (sprevidi))<br>
<br><br>---------- Forwarded message ----------<br>From:=A0&quot;Stefano Pr=
evidi (sprevidi)&quot; &lt;<a href=3D"mailto:sprevidi@cisco.com">sprevidi@c=
isco.com</a>&gt;<br>To:=A0&quot;John G. Scudder&quot; &lt;<a href=3D"mailto=
:jgs@juniper.net">jgs@juniper.net</a>&gt;, &quot;Alvaro Retana (aretana)&qu=
ot; &lt;<a href=3D"mailto:aretana@cisco.com">aretana@cisco.com</a>&gt;, &qu=
ot;<a href=3D"mailto:status@ietf.org">status@ietf.org</a>&quot; &lt;<a href=
=3D"mailto:status@ietf.org">status@ietf.org</a>&gt;<br>
Cc:=A0&quot;Clarence Filsfils \(cfilsfil\)&quot; &lt;<a href=3D"mailto:cfil=
sfil@cisco.com">cfilsfil@cisco.com</a>&gt;<br>Date:=A0Thu, 7 Nov 2013 04:24=
:23 +0000<br>Subject:=A0[Status] request to move draft-filsfils-rtgwg-segme=
nt-routing-use-cases-02 to wg item<br>
John, Alvaro, All,<br>
<br>
according to what discussed after the presentation of SR Use Cases at<br>
ietf88 spring-wg meeting, I&#39;d like to request the adoption of<br>
draft-filsfils-rtgwg-segment-routing-use-cases-02.txt as wg item.<br>
<br>
Thanks.<br>
s.<br>
<br>
<br>
<br>
<br>_______________________________________________<br>
status mailing list<br>
<a href=3D"mailto:status@ietf.org">status@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/status" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/status</a><br>
<br></blockquote></div><br></div>

--089e0116136aa7fd2e04eaf0ad80--


Return-Path: <aretana@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 C906321E8092 for <status@ietfa.amsl.com>; Mon, 11 Nov 2013 14:27:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.587
X-Spam-Level: 
X-Spam-Status: No, score=-10.587 tagged_above=-999 required=5 tests=[AWL=0.012, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 gPribB49iSjM for <status@ietfa.amsl.com>; Mon, 11 Nov 2013 14:27:08 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id E9EC411E80F9 for <status@ietf.org>; Mon, 11 Nov 2013 14:27:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=187; q=dns/txt; s=iport; t=1384208828; x=1385418428; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=ikvoKGS2URtJM/4vjiNbrpJk7c9JJ3ZN5IFrw0tqHio=; b=lNF73XYYqYPcangqdVe4KBwx+eg+GZhpzqDqdh/fjqpbfRfbh80WAhac lWhiBTI4V9LR+vbOLlYstdsA7f+w6dy8uS6nrHF5EkzTfihGIWO6RPYkA qk0ifxON/myGZ6FDFomJKfKjY0p7Y1wvYnv+8ZI95lxTdm4/K0J/OEFRI c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhEFAAhZgVKtJV2Y/2dsb2JhbABZgwc4U78OCIFGFnSCLDo/EgEINkIlAgQODod4Db5Lj2MHhDADmA+SCoMmgio
X-IronPort-AV: E=Sophos;i="4.93,680,1378857600"; d="scan'208";a="283393626"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-2.cisco.com with ESMTP; 11 Nov 2013 22:27:07 +0000
Received: from xhc-aln-x14.cisco.com (xhc-aln-x14.cisco.com [173.36.12.88]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id rABMR7Ne001144 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <status@ietf.org>; Mon, 11 Nov 2013 22:27:07 GMT
Received: from xmb-aln-x15.cisco.com ([169.254.9.147]) by xhc-aln-x14.cisco.com ([173.36.12.88]) with mapi id 14.03.0123.003; Mon, 11 Nov 2013 16:27:07 -0600
From: "Alvaro Retana (aretana)" <aretana@cisco.com>
To: "<status@ietf.org>" <status@ietf.org>
Thread-Topic: DRAFT minutes from the SPRING 1st WG meeting at IETF88
Thread-Index: AQHO2cSHklPivvqJ6ke/Dt+VYcH8LZogt4eA
Date: Mon, 11 Nov 2013 22:27:06 +0000
Message-ID: <CEA6C3B6.40E61%aretana@cisco.com>
In-Reply-To: <A5C2F302-5500-4535-B880-DF9BC08C0603@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.117.15.4]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <26ABBF2707BF374E8DC00F906741F611@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "Carlos Pignataro \(cpignata\)" <cpignata@cisco.com>
Subject: Re: [Status] DRAFT minutes from the SPRING 1st WG meeting at IETF88
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: Mon, 11 Nov 2013 22:27:13 -0000

Hi!

I just posted the (updated) draft minutes from last week.

http://www.ietf.org/proceedings/88/minutes/minutes-88-spring

Thanks to Carlos for being the note taker.

Alvaro.



Return-Path: <sprevidi@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 E68C811E8105 for <status@ietfa.amsl.com>; Wed,  6 Nov 2013 20:24:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[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 cx79ozv4QVpd for <status@ietfa.amsl.com>; Wed,  6 Nov 2013 20:24:26 -0800 (PST)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id 6009811E80F5 for <status@ietf.org>; Wed,  6 Nov 2013 20:24:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=244; q=dns/txt; s=iport; t=1383798266; x=1385007866; h=from:to:cc:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=YpbqIukLWFLjicYIvr7nQGTnOfx95p5nBfkqNj2qsmg=; b=Ti+z2IsoNyBfhqi6LQR50c6bVU9UydSBh8NuXN0RoKY1n+QTWNNkeoO2 cEzjotbW7cNhMOEah28tKxHvMuLfNwmroiOsBRptKOOHeFGHJ6DB3Z3Ok ii9ujvPVoEBweByyyvcZJFpjPl9sZaGdRwy2LclpvNfYMBVio3Ii4I7vZ 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgIFADsVe1KtJV2Y/2dsb2JhbABagweBC78cgSkWdIIsOj8SAT5CJwQBDYgGvnqPWYMngRADmAySCoMmgio
X-IronPort-AV: E=Sophos;i="4.93,649,1378857600"; d="scan'208";a="281749090"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-5.cisco.com with ESMTP; 07 Nov 2013 04:24:25 +0000
Received: from xhc-aln-x09.cisco.com (xhc-aln-x09.cisco.com [173.36.12.83]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id rA74OOsn005361 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 7 Nov 2013 04:24:25 GMT
Received: from xmb-rcd-x01.cisco.com ([169.254.1.140]) by xhc-aln-x09.cisco.com ([173.36.12.83]) with mapi id 14.03.0123.003; Wed, 6 Nov 2013 22:24:24 -0600
From: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
To: "John G. Scudder" <jgs@juniper.net>, "Alvaro Retana (aretana)" <aretana@cisco.com>, "status@ietf.org" <status@ietf.org>
Thread-Topic: request to move draft-filsfils-rtgwg-segment-routing-use-cases-02 to wg item
Thread-Index: AQHO23E8p83WlqlDLUO90VPM+v9VCA==
Date: Thu, 7 Nov 2013 04:24:23 +0000
Message-ID: <947081B7-F174-4C4D-BE12-56F4FC3A12A8@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.61.214.229]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <B00840DBA25A4C46AC635B33F94D595D@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "Clarence Filsfils \(cfilsfil\)" <cfilsfil@cisco.com>
Subject: [Status] request to move draft-filsfils-rtgwg-segment-routing-use-cases-02 to wg item
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: Thu, 07 Nov 2013 04:24:32 -0000

John, Alvaro, All,

according to what discussed after the presentation of SR Use Cases at=20
ietf88 spring-wg meeting, I'd like to request the adoption of=20
draft-filsfils-rtgwg-segment-routing-use-cases-02.txt as wg item.

Thanks.
s.




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 5E9F911E825C for <status@ietfa.amsl.com>; Mon,  4 Nov 2013 17:15:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.193
X-Spam-Level: 
X-Spam-Status: No, score=-109.193 tagged_above=-999 required=5 tests=[AWL=-1.191, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_31=0.6, J_CHICKENPOX_51=0.6, MIME_QP_LONG_LINE=1.396, 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 UftDm1dOox7l for <status@ietfa.amsl.com>; Mon,  4 Nov 2013 17:15:38 -0800 (PST)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id A2DEF11E8349 for <status@ietf.org>; Mon,  4 Nov 2013 17:15:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=55904; q=dns/txt; s=iport; t=1383614137; x=1384823737; h=from:to:cc:subject:date:message-id:mime-version; bh=f6aGicTUJiMpK4xpsVD7wdpAXkWhO6vkkpjUVom+sp0=; b=S+PXUSuAavlUukonM1bjOBfyf5uW1ljcRREdMhCPdgUj7BhFW+jnMmm6 IEd6ajep3+9e0q1a1hR0O/bqMSSJd29HSN+UNL19Pof2+NMHNQyN8n6c6 STngXRVRfuxDchhwfhGBQzlSsbFcH/dsTV/PydvLxnzGQ7c4barUy7/J2 U=;
X-Files: ietf88-spring-minutes.html, signature.asc : 48094, 203
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApIGACdGeFKtJXG9/2dsb2JhbABPCoMHOFO2cohHgScUAnSBYCoiGgFeEgEGFB8BAQUBPxcQBA4FDg0Eh2INkB+uHI4OBwQBgT4qBIJ5gQ4DkC6BMIJNg1+BL5BagyaBaAEfIg
X-IronPort-AV: E=Sophos;i="4.93,636,1378857600";  d="asc'?html'217?scan'217,208,217";a="277655688"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by rcdn-iport-9.cisco.com with ESMTP; 05 Nov 2013 01:15:35 +0000
Received: from xhc-aln-x07.cisco.com (xhc-aln-x07.cisco.com [173.36.12.81]) by rcdn-core2-2.cisco.com (8.14.5/8.14.5) with ESMTP id rA51FZJJ005802 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 5 Nov 2013 01:15:35 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.229]) by xhc-aln-x07.cisco.com ([173.36.12.81]) with mapi id 14.03.0123.003; Mon, 4 Nov 2013 19:15:33 -0600
From: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
To: "<status@ietf.org>" <status@ietf.org>
Thread-Topic: DRAFT minutes from the SPRING 1st WG meeting at IETF88
Thread-Index: AQHO2cSHklPivvqJ6ke/Dt+VYcH8LQ==
Date: Tue, 5 Nov 2013 01:15:34 +0000
Message-ID: <A5C2F302-5500-4535-B880-DF9BC08C0603@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.85.165.158]
Content-Type: multipart/signed; boundary="Apple-Mail=_DDA20643-CF83-4F69-824F-4F513F6EDC34"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Cc: "Alvaro Retana \(aretana\)" <aretana@cisco.com>, John Scudder <jgs@juniper.net>
Subject: [Status] DRAFT minutes from the SPRING 1st WG meeting at IETF88
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, 05 Nov 2013 01:15:44 -0000

--Apple-Mail=_DDA20643-CF83-4F69-824F-4F513F6EDC34
Content-Type: multipart/mixed;
	boundary="Apple-Mail=_9581EB51-105F-4B22-84C6-5EEA6030A755"


--Apple-Mail=_9581EB51-105F-4B22-84C6-5EEA6030A755
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii

SPRING,

Please find $subject attached.

Comments and corrections most welcome!

Carlos Pignataro.

--Apple-Mail=_9581EB51-105F-4B22-84C6-5EEA6030A755
Content-Disposition: attachment;
	filename=ietf88-spring-minutes.html
Content-Type: text/html;
	name="ietf88-spring-minutes.html"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" =
"http://www.w3.org/TR/html4/strict.dtd">
<html>
<head>
  <meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8">
  <meta http-equiv=3D"Content-Style-Type" content=3D"text/css">
  <title></title>
  <meta name=3D"Generator" content=3D"Cocoa HTML Writer">
  <meta name=3D"CocoaVersion" content=3D"1265">
  <style type=3D"text/css">
    p.p1 {margin: 0.0px 0.0px 14.0px 0.0px; font: 14.0px Arial}
    p.p2 {margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Arial}
    p.p3 {margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Arial; =
min-height: 14.0px}
    p.p4 {margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Arial; color: =
#042eee}
    li.li2 {margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Arial}
    span.s1 {text-decoration: underline ; color: #042eee}
    span.s2 {color: #000000}
    span.s3 {text-decoration: underline}
    ul.ul1 {list-style-type: disc}
    ul.ul2 {list-style-type: circle}
  </style>
</head>
<body>
<p class=3D"p1"><b>IETF-88 spring meeting minutes</b></p>
<p class=3D"p2">Source Packet Routing in Networking WG (spring)</p>
<p class=3D"p2">IETF 88 (Vancouver) Agenda</p>
<p class=3D"p3"><br></p>
<p class=3D"p2">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D</p>
<p class=3D"p3"><br></p>
<p class=3D"p2">CHAIR(s):=C2=A0 John Scudder &lt;<a =
href=3D"mailto:jgs@juniper.net"><span =
class=3D"s1">jgs@juniper.net</span></a>&gt;</p>
<p class=3D"p2">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
 Alvaro Retana &lt;<a href=3D"mailto:aretana@cisco.com"><span =
class=3D"s1">aretana@cisco.com</span></a>&gt;</p>
<p class=3D"p3"><br></p>
<p class=3D"p2">MONDAY, November 4, 2013</p>
<p class=3D"p2">1450-1720=C2=A0 Afternoon Session II</p>
<p class=3D"p2">Regency B</p>
<p class=3D"p3"><br></p>
<p class=3D"p2"><b>Meeting starts at 14:51 local time</b></p>
<p class=3D"p3"><br></p>
<p class=3D"p2">o Administrivia</p>
<p class=3D"p2">=C2=A0 =
Chairs=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 20 minutes</p>
<p class=3D"p3"><br></p>
<p class=3D"p2">=C2=A0 - Note Well</p>
<p class=3D"p2">=C2=A0 - Scribe</p>
<p class=3D"p2">=C2=A0 - Blue Sheets</p>
<p class=3D"p2">=C2=A0 - Charter Review</p>
<p class=3D"p3"><br></p>
<ul class=3D"ul1">
  <li class=3D"li2">Alvaro: This is the first time that we meet, this is =
Alvaro and John.</li>
  <li class=3D"li2">=E2=80=A6 Carlos is here taking notes. Always here =
the NOTE WELL. Make sure you know that by participating in the IETF to =
agree to the IETF process, you understand that meetings are being =
recorded, et al.</li>
  <li class=3D"li2">=E2=80=A6 Blue sheets are going around. First agenda =
bashing and then charter review=E2=80=A6</li>
  <li class=3D"li2">=E2=80=A6 We have a very full agenda. Any changes =
you;d want to propose?</li>
  <li class=3D"li2">Someone shouts: move charter to the end.</li>
  <li class=3D"li2">Alvaro: The agenda matches the order in the charter, =
so first we have use cases. Ida will join Stefano, that=E2=80=99s the =
only change. We might not get to all the items on the second part of the =
agenda. Other items? No, great.</li>
  <li class=3D"li2">=E2=80=A6 This is the charter, which has been =
discussed *a lot*. It went to the IESG, external review, etc. If you =
have comments please make them but at this time that might be comments =
for clarification.</li>
  <li class=3D"li2">=E2=80=A6 second part of the charter, from the IESG =
review, for every data plane we need to have a security analysis. This =
is important for every piece of work that comes in</li>
  <li class=3D"li2">John: And to re-emphasize, it=E2=80=99s important =
that that happens early on and not late.</li>
  <li class=3D"li2">Alvaro: Page 3 of the charter, says that any =
modifications or extensions need to be done in the WG responsible for =
that protocol. We will send requirements but protocol work will happen =
in other working groups.</li>
  <li class=3D"li2">=E2=80=A6 keep that in mind as we develop solutions =
and where solution work should go. Note the text at the bottom are the =
charter items. We will talk about requirements, who owns the data plane =
will talk about the solution.</li>
  <li class=3D"li2">=E2=80=A6 and the last page of the charter lists the =
Milestones. This should march the charter items. I do not think anyone =
should have issues with the dates, but please speak up.</li>
  <li class=3D"li2">Thomas Narten makes a motion to have people =
shift-sit-left so that people standing up can sit down.</li>
  <li class=3D"li2">John pleads for people to raise their hands if they =
are next to an empty sit.</li>
</ul>
<p class=3D"p3"><br></p>
<p class=3D"p2">o Segment Routing Use Cases</p>
<p class=3D"p4"><span class=3D"s2">=C2=A0 <a =
href=3D"http://tools.ietf.org/html/draft-filsfils-rtgwg-segment-routing-us=
e-cases"><span =
class=3D"s3">http://tools.ietf.org/html/draft-filsfils-rtgwg-segment-routi=
ng-use-cases</span></a></span></p>
<p class=3D"p2">=C2=A0 Stefano Previdi and Ida Leung =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=
 =C2=A0 =C2=A0 =C2=A0 =C2=A0 15 minutes</p>
<ul class=3D"ul1">
  <li class=3D"li2">Stefano: Presenting the SR use case draft, that =
we=E2=80=99ve been doing for the last 4 months. We are splitting the =
content in separate drafts, and thus we have the following docs that =
have been or will be submitted very soon.</li>
  <li class=3D"li2">=E2=80=A6 We have SR/LDP interop, OAM from Rudigher, =
and three to be published.</li>
  <li class=3D"li2">=E2=80=A6 this is the list of authors, which is =
growing given these documents.</li>
  <li class=3D"li2">=E2=80=A6 Next slide =E2=80=94 those are the =
sections in the generic use case draft, in 5-10 minutes I cannot go into =
details. We will take time in explaining the main use cases, like =
TE.</li>
  <li class=3D"li2">=E2=80=A6 Next slide: The main use case is efficient =
transport of MPLS services, shorter path, and keeping the ECMP awareness =
even for explicit routing. The ability of running explicit routing =
without extra signaling (no LDP, no RSVP), and if you run MPLS with =
IPv6, you do not need to wait for LDPv6</li>
  <li class=3D"li2">...The real operator problem to solve is CoS-based =
TE, for Asia to Europe go to the US, but for a different traffic take a =
different path based on delay.</li>
  <li class=3D"li2">=E2=80=A6the alternative was multiple TE tunnels, =
but the advantage of SR is that identifiers from Asia domain will =
attract traffic to Asia, and from there it would flow to Europe. Solving =
a problem sensible to operators.</li>
  <li class=3D"li2">=E2=80=A6 Next Ida will present.</li>
  <li class=3D"li2">Ida: I am Ida from Rogers. We have cable TV and =
internet business, and we have individual lab to deliver each. Wireless =
only from Wireless access point. Cable only from Cable access =
point.=C2=A0</li>
  <li class=3D"li2">=E2=80=A6 Now, I actually have more service from one =
network cost to another domain. That=E2=80=99s my problem statement. =
Different networks, all have their IGP, and I need to find a way to keep =
my traffic cost low. Moving to 10G, 100G, I need to find a way how to =
stop expanding.</li>
  <li class=3D"li2">=E2=80=A6 Some traffic I also want on explicit =
paths. Even in the lab, it is way too complicated to deploy and =
operation to maintain. I need a solution, something simple.</li>
  <li class=3D"li2">=E2=80=A6 I need something like myself, simple and =
straightforward. One mechanism to fulfill all the requirements.=C2=A0</li>=

  <li class=3D"li2">=E2=80=A6 I am excited for SPRING because it helped =
me find a solution to this.</li>
  <li class=3D"li2">=E2=80=A6 the first use case is typical, I have an =
Internet exit point. I need to provision from my Dual Plane Network to =
my Single Plane Network, and SPRING provides me that mechanism. Now I =
actually can build more NNI and control which NNI to go from my dual =
plane to my single plane network.</li>
  <li class=3D"li2">=E2=80=A6 I can actually stop growing these (dual =
plane) WAN links. I do not need to continue to build here, and I can =
save money. Ultimatelly will not have dual plane, my big dream is to not =
have the dual plane network.</li>
  <li class=3D"li2">=E2=80=A6 this other slide is more about Server =
(slide 5). Some of my traffic I do not want them to follow my IGP =
metric. Now SPTING can give me an answer to that.</li>
  <li class=3D"li2">=E2=80=A6 this are my two use cases. I do not build =
a network from one vendor. I need all vendors to bring SPRING.</li>
  <li class=3D"li2">Questions:</li>
  <ul class=3D"ul2">
    <li class=3D"li2">Stewart: IP, MPLS, or both?</li>
    <li class=3D"li2">Ida: First, MPLS. Second, IPv6, I also have my =
usage.</li>
  </ul>
</ul>
<p class=3D"p3"><br></p>
<p class=3D"p2">o Performance Engineered LSPs using the Segment Routing =
Data-Plane</p>
<p class=3D"p4"><span class=3D"s2">=C2=A0 <a =
href=3D"http://tools.ietf.org/html/draft-shakir-rtgwg-sr-performance-engin=
eered-lsps"><span =
class=3D"s3">http://tools.ietf.org/html/draft-shakir-rtgwg-sr-performance-=
engineered-lsps</span></a></span></p>
<p class=3D"p2">=C2=A0 Rob =
Shakir=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 10 minutes</p>
<ul class=3D"ul1">
  <li class=3D"li2">Rob: I am Rob from BT, this is traffic engineering =
with constraints. Essentially IGP metrics are one method to delver =
traffic, but we have other traffic that has other constraints. We have =
an overlay network, this provides connectivity for. So, we try to meet =
those constraints in our existing network core without building a new =
network, which would be inefficient.</li>
  <li class=3D"li2">=E2=80=A6 we see an increase of things that need =
guarantees, broadcast services for example.</li>
  <li class=3D"li2">=E2=80=A6 in the draft we try to explain two modes: =
the first one is Head-end based calculation, like colors on the IGP, =
using the existing cSPF.</li>
  <li class=3D"li2">=E2=80=A6 one of the reasons why we like this, is =
that routing is based on affinity, we are not updating any state on the =
network. There=E2=80=99s no clear requirements.</li>
  <li class=3D"li2">=E2=80=A6 (slide 4) however, we also thing there is =
a requirement to support centralized computation. Global optimization we =
can go for. This using a PCE, using PCEP, in the future might be =
generalized using I2RS type of work.=C2=A0</li>
  <li class=3D"li2">=E2=80=A6 this introduces more requirements like =
topology discovery.</li>
  <li class=3D"li2">=E2=80=A6 (slide 5) the other bit we are trying to =
cover on this draft is taking advantage of ECMPs, and explicit =
protection mechanisms. With a segment we can control that behavior. =
Covering things like how we do IPFRR. We might consolidate a use-case =
drafts, some things in this drafts should fall out.</li>
  <li class=3D"li2">=E2=80=A6 this draft should cover these requirements =
on per flow basis.</li>
  <li class=3D"li2">=E2=80=A6 question, comments, rotten fruit?</li>
  <li class=3D"li2">Questions:</li>
  <ul class=3D"ul2">
    <li class=3D"li2">Ed=C2=A0Crabbe, speaking for Lucy Young: What =
granularity flow are you describing?</li>
    <li class=3D"li2">Rob: DSCP based, particular markings, particular =
FECs, classes. Very flexible.</li>
    <li class=3D"li2">Ed: Which is really feedback for the PCE WG.</li>
    <li class=3D"li2">Alvaro: This is very important to discuss, because =
it is the first item, use cases. Are there any concerns with use =
cases?</li>
    <li class=3D"li2">&lt;silence&gt;</li>
    <li class=3D"li2">Alvaro: Stefano said you will split into smaller =
drafts.</li>
    <li class=3D"li2">Stefano: In fact, we already splited the content =
of the use case draft. What you will see is additional drafts with other =
use cases.</li>
    <li class=3D"li2">Rob: Yes.</li>
    <li class=3D"li2">John: Are you guys ready to ask for WG draft?</li>
    <li class=3D"li2">Stefano: Is there risk on asking?</li>
    <li class=3D"li2">John: No risk, this is the first item.</li>
    <li class=3D"li2">Stefano: I=E2=80=99ve no reason not to ask, so I =
will ask.</li>
    <li class=3D"li2">John: We will take it to the list, as always. If =
you have concerns, express them.</li>
  </ul>
</ul>
<p class=3D"p3"><br></p>
<p class=3D"p2">o Segment Routing Architecture</p>
<p class=3D"p4"><span class=3D"s2">=C2=A0 <a =
href=3D"http://tools.ietf.org/html/draft-filsfils-rtgwg-segment-routing"><=
span =
class=3D"s3">http://tools.ietf.org/html/draft-filsfils-rtgwg-segment-routi=
ng</span></a></span></p>
<p class=3D"p2">=C2=A0 Stefano =
Previdi=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0 15 minutes</p>
<ul class=3D"ul1">
  <li class=3D"li2">Stefano: OK, now talking about the Segment Routing =
Architecture. 10-15 mins?</li>
  <li class=3D"li2">=E2=80=A6 this is the architecture, it is the 2nd =
version, 3rd version but 2nd incarnation of that draft.=C2=A0</li>
  <li class=3D"li2">=E2=80=A6 this is the list of use cases, and =
protocol extensions. Those protocol extensions will be presented in =
their respective working groups.</li>
  <li class=3D"li2">=E2=80=A6 The SR architecture aims to support =
multiple use cases, some of which can be grouped together on a =
per-dataplane or a functionality. It is not required by the architecture =
to support all these parts.</li>
  <li class=3D"li2">=E2=80=A6 SR is about segments, and a segment can =
represent a service, context, locator, etc. The identifiers are taken =
either from a local or global space.=C2=A0</li>
  <li class=3D"li2">=E2=80=A6 SR can be used in a fully-distributed =
fashion, or optimization. It supports the different flavors of the =
architecture.</li>
  <li class=3D"li2">=E2=80=A6 data planes, we support of course the MPLS =
DP as-is, we expect no changes from MPLS in the past 15-18 years.</li>
  <li class=3D"li2">=E2=80=A6 IPv6 we do require some extensions, which =
already exist, consistent with RFC 2460. We have some work to do here =
still, but today too early and we will publish something by next =
IETF.</li>
  <li class=3D"li2">=E2=80=A6 in regards to implementations, we have =
some implementations and soon we will publish an interoperability =
report. The feedback we get from use and troubleshooting is great.</li>
  <li class=3D"li2">=E2=80=A6 what is Segment Routing about? This =
picture (slide 6) explains everything. Every node has a global =
identifier. If you put label 72 on a packet, the packet will reach node =
C. So if you put 72, 78, 65, the node will go C, O, Z. Nothing really =
new in the MPLS data plane.</li>
  <li class=3D"li2">=E2=80=A6 so, again, from an architecture =
perspective, we talk about these operations: push, pop, swap.=C2=A0</li>
  <li class=3D"li2">=E2=80=A6 we have a different between local segments =
and global segments. The local has significance in the context of the =
node advertising the segment. Typically it is an adjacency with a node. =
It needs to be known only by the node.</li>
  <li class=3D"li2">=E2=80=A6 global segment has global significance. =
This is what the architecture specifies, we do support local label =
spaces from a global index. Even if different MPLS platforms support =
different label spaces, we can advertise an index.</li>
  <li class=3D"li2">=E2=80=A6 we said this many many times, the key =
advantage of SR is the lack of state in the network. The amount of =
traffic or explicit path will not generate state in the network.</li>
  <li class=3D"li2">=E2=80=A6 We define in the architecture three types =
of segments, or two and a half. The first one is a prefix, global. One =
type of prefix is a node segment. It has the semantic of being node =
identifier. And then you have the adjacency segment, which is a link =
between two nodes.</li>
  <li class=3D"li2">=E2=80=A6 in the case of a node segment, the new =
sub-TLV called segment identifier in OSPF or ISIS, any node can push the =
label and the packet will reach the destination in the shortest =
path.</li>
  <li class=3D"li2">=E2=80=A6 the adjacency segment, those have local =
significance. Only understood by the router that originates them. Allows =
to define any explicit path along the network.=C2=A0</li>
  <li class=3D"li2">=E2=80=A6 in this case (slide 14) we might want to =
advertise more than one identifier per adjacency. We can use this for =
link bundles.</li>
  <li class=3D"li2">=E2=80=A6 this is an example of mixing identifiers. =
My packet will travel shortest path to C, then to the link to O, then =
the shortest path from O to Z. This can be done also not using the =
adjacency label. Does the same thing with labels representing only =
nodes.</li>
  <li class=3D"li2">=E2=80=A6 the use of adj. identifier is useful, but =
most cases you can do the same with node identifier.</li>
  <li class=3D"li2">=E2=80=A6 we made these extensions to OSPF and =
IS-IS. Again, absolutely no changes to the data plan itself.</li>
  <li class=3D"li2">=E2=80=A6 we started talking about service segments, =
it is premature to talk about them. When you build the stack of labels =
to put on the packet, you may also want to enforce a specific service =
chain. No changes to the architecture.</li>
  <li class=3D"li2">=E2=80=A6 OK, questions?</li>
  <li class=3D"li2">Questions:</li>
  <ul class=3D"ul2">
    <li class=3D"li2">Anoop from Dell: Inone of the slides you said you =
have implementation, is that MPLS, IPv6, or both</li>
    <li class=3D"li2">Stefano: We have both, but IPv6 we may want to =
continue some architectural work.</li>
    <li class=3D"li2">Anoop: so you are using the existing source =
routing for IPv6?</li>
    <li class=3D"li2">Stefano: Yes, extension heareds.</li>
    <li class=3D"li2">Stewart Bryant AD: You made a reference to the =
Type 0 routing header in RFC2460, and that was the mechanism that gave =
the ADs a lot of headache. It would be useful to pull that out and =
socialize it with Int-Area ADs to know if we are on the right track or =
not.</li>
    <li class=3D"li2">Stefano: Sure.</li>
    <li class=3D"li2">Xhenbin from Huawei: Two comments. First, in =
practice, many vendors implemented MPLS label stacks with a limitation =
on stack size, on hardware. Second, for segment routing, we need to keep =
forwarding mechanism for MPLS Multicast. This is a challenge and adds =
complexity.</li>
    <li class=3D"li2">Stefano: Let me ask the second one first. Dino is =
there, for multicast it will be complex. Regarding the label stack, yes, =
if you want to express a path by using one label per hop, that could be =
a problem for some implementations.</li>
    <li class=3D"li2">=E2=80=A6 but you can see most cases are solved =
with a limited number of labels. Label stack has not been raised as an =
issue.</li>
    <li class=3D"li2">Xhenbin: Maybe node segment and link segment. =46rom=
 the Seamless MPLS architecture, in this architecture there are more =
links and more nodes.</li>
    <li class=3D"li2">Stefano: It=E2=80=99s not the number of links, it =
is the complexity you have on the explicit path.</li>
    <li class=3D"li2">Xhenbin: My concern is scalability, limit =
usage.</li>
    <li class=3D"li2">Stefano: I do not think so, at all.</li>
    <li class=3D"li2">Xhenbin: You will have to calculate label stack =
carefully.</li>
    <li class=3D"li2">Dino: To quote Dave Katz, take any simple problem, =
and will be hard with multicast. But it does not need to be. I=E2=80=99d =
recumbent tunneling and pushing the multicast to edges.</li>
    <li class=3D"li2">Stefano: Yes</li>
    <li class=3D"li2">Someone: You have different size =
advertisements.</li>
    <li class=3D"li2">Stefano: In ISIS advertising a size of bits is =
complicated.</li>
    <li class=3D"li2">Someone: TTL will be useful.</li>
    <li class=3D"li2">Stefano: That is in the data plane. This is in the =
control plane.</li>
    <li class=3D"li2">Someone: The other comment was the length of the =
stack. For the load balancing case and entropy label will be hard.</li>
    <li class=3D"li2">John: More on EL later.</li>
    <li class=3D"li2">Ahmed from Cisco: The label size is not an =
issue.</li>
    <li class=3D"li2">Ed Crabbe: obviously I support the effort, but I =
do think that the length of label stack is actually an issue in LERs. =
Your milage will vary, it is a fact, you will have to do the =
analysis.</li>
    <li class=3D"li2">Stefano: Yes, we are confident based on our =
analysis. But good point.</li>
    <li class=3D"li2">Rob: Since the label stack keeps coming back, =
maybe we need to put a draft with anonymized data from operators.</li>
    <li class=3D"li2">Ed: Again, it depends on your topology but you =
need to do that analysis.</li>
    <li class=3D"li2">John S, as individual: It is great to present data =
about existing networks, but today=E2=80=99s networks are not =
tomorrow=E2=80=99s, so we should do that analysis as well.</li>
    <li class=3D"li2">Dino: General comment about SR. The idea could be =
good, I do not know if it will be good. The fact that you need to make =
so many protocol changes=E2=80=A6 can you do this without so many =
changes?</li>
    <li class=3D"li2">Stefano: We have to agree on =E2=80=9Cso many=E2=80=9D=
, we have 3 sub-TLVs.</li>
    <li class=3D"li2">Dino: The fact that you have a single TLV, means =
everyone needs to upgrade their routers. And if you have these changes =
now, you will have a lot more.</li>
    <li class=3D"li2">Stefano: Just to assure you we have =
implementations, it addresses valid use cases.</li>
    <li class=3D"li2">Robert R: Response to Dino: There is one draft =
with Keyur, we are defining BGP Vector router, one change, control plane =
independent of IGP extensions.</li>
    <li class=3D"li2">Xhenbin: Regarding service chain, you have more =
changes. Analyze top of the label stack. Service header will be kept in =
the forwarding. So maybe we have to do different. See the service label =
firstly. That would be changes to the MPLS data plane. You have to =
remove top of label for forwarding then make process based on the =
service label.</li>
    <li class=3D"li2">Stefano: No, sorry. I think you got it wrong, but =
let=E2=80=99s wait on the service chain draft. It=E2=80=99s difficult to =
discuss.=C2=A0</li>
  </ul>
</ul>
<p class=3D"p3"><br></p>
<p class=3D"p2">o Supporting Source/Explicitly Routed Tunnels via =
Stacked LSPs</p>
<p class=3D"p4"><span class=3D"s2">=C2=A0 <a =
href=3D"http://tools.ietf.org/html/draft-gredler-spring-mpls"><span =
class=3D"s3">http://tools.ietf.org/html/draft-gredler-spring-mpls</span></=
a></span></p>
<p class=3D"p2">=C2=A0 Hannes =
Gredler=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0 10 minutes</p>
<ul class=3D"ul1">
  <li class=3D"li2">Hannes: Hi, I am Hannes. I want to pick on Dino=E2=80=99=
s comment that less is better. Yakov, Luay, Sri, and me have put some =
thoughts on how much architecture we need. We want to reuse the MPLS =
architecture as is, do we need all this architecture?</li>
  <li class=3D"li2">=E2=80=A6 can it be that for achieving explicit =
routing we could use existing architectural documents, specifically RFC =
3031.</li>
  <li class=3D"li2">=E2=80=A6 we have a set of definitions in there that =
can be used for Segment Routing. Explicitly Routed is any tunnel that =
deviates from IGP. At the time of writing the draft, that was RSVP-TE or =
CR-LDP.</li>
  <li class=3D"li2">=E2=80=A6 the question is can we establish =
explicitly routed tunnels without the core router signaling?</li>
  <li class=3D"li2">=E2=80=A6 we think the answer is Yes. Essentially =
here each label in the stack represents an egress point.</li>
  <li class=3D"li2">=E2=80=A6 furthermore, one of the things that RFC =
3031 talks about is how to learn the label state. Existing protocols =
need a directed session, otherwise it is not possible to have label =
state. With the IGP flooding machinery we can reach nodes not directly =
adjacent.</li>
  <li class=3D"li2">=E2=80=A6 how does this work? Today we have more =
segments. The middle segment here can be an explicit path brought up by =
RSVP, or it could be a stacked together LSP brought by the IGP =
extensions that Stefano and others are proposing.=C2=A0</li>
  <li class=3D"li2">=E2=80=A6 we have here 3 segments. LDP, RSVP, and =
RSVP. In fact, if one really wants to describe an explicit route, it =
just needs to track the dependency of ingress-egress pairs. If there is =
one that matches the constraints, use it. Before we used to have a cSPF =
machinery, put all the requirements, and comes back with a result. Here, =
skips the last step and looks into the IGP or RSVP database finding =
snippets.</li>
  <li class=3D"li2">=E2=80=A6 if we draw a comparison, and try to =
translate, here=E2=80=99s the rosetta stone for that: segment is nothing =
but an MPLS label adversed by intermediate point. segment list is MPLS =
segment stack, and advertising in OSPF/ISIS is using that as segment =
distribution.</li>
  <li class=3D"li2">=E2=80=A6 in summary, we do not think that there is =
a need for further architectural documents to describe segment stacking. =
We want to use segment stacking to build segments using the existing =
architecture</li>
  <li class=3D"li2">Questions:</li>
  <ul class=3D"ul2">
    <li class=3D"li2">Greg M.: I think the second buller is not correct, =
special purpose label do not respond to segment.</li>
    <li class=3D"li2">Hannes: It can be a service.</li>
    <li class=3D"li2">Greg: No, OAM.</li>
    <li class=3D"li2">John: Are you saying that every label stack is not =
a label list?</li>
    <li class=3D"li2">Greg: No, not every element.</li>
    <li class=3D"li2">Peter L: How do this apply if my labels are IPv6 =
labels, do you have more slides?</li>
    <li class=3D"li2">Hannes: This is about label stacking for the MPLS =
data plane. It is not about how to introduce source routing for =
IPv6.</li>
    <li class=3D"li2">Stefano: In segment routing a segment can also =
identify an OAM instruction, or any instruction. Just for the analogy. =
Here the idea looks like an improvement because you improve scalability, =
but why don=E2=80=99t you go to the next level and get rid of RSVP in =
the core?</li>
    <li class=3D"li2">Hannes: It does not need to be RSVP only.</li>
    <li class=3D"li2">Ed: Sorry, I am not really sure I agree with that. =
Getting rid of RSVP in the core has a lot of benefits.</li>
    <li class=3D"li2">Hannes: OK, but my question is getting rid of RSVP =
also imply getting rig of explicit router paths. RSVP is an example</li>
    <li class=3D"li2">Ed: I was addressing your verbatim.</li>
    <li class=3D"li2">Dino: If you already have labels in the IGP, you =
do not need them in the RSVP, why extra protocol? That was Stefano=E2=80=99=
s point.</li>
    <li class=3D"li2">Hannes: The proposed protocol extensions are not a =
full stop replacement of RSVP or LDP. They are a partial replacement, at =
least we see a shift of functionality.</li>
    <li class=3D"li2">Stefano: No, but let=E2=80=99s not argue. In this =
case you reduce state from the core but you do not remove it. My comment =
is that you need to remove state from the core.</li>
    <li class=3D"li2">Himanshu Shah, Ciena: You mention Traffic =
Engineering.</li>
    <li class=3D"li2">Hannes; No, I mentioned Explicit Routing.</li>
    <li class=3D"li2">Himanshu: OK, how does a router know that a set of =
nodes have become extremely congested?</li>
    <li class=3D"li2">Hannes: Rob had mentioned that he will build on =
extended IGP metrics. Allows to inject into the TE control plane.</li>
    <li class=3D"li2">Jeff Haas: It is worth pointing out that you could =
get rid of RSVP, or LDP, etc. RSVP does more things than just CPU =
cycles, and in some cases you need to have these things =
interoperate.</li>
    <li class=3D"li2">Ed: Yes, you could replace RSVP, and PCE =
extensions, or alternate with BGP single label + Flowspec.</li>
    <li class=3D"li2">Hannes: Is the topic if we can replace RSVP?</li>
    <li class=3D"li2">Ed: It was your statement.</li>
    <li class=3D"li2">Hannes: For centralized, =C2=A0yes, for =
distributed no.</li>
    <li class=3D"li2">Rob: The point about can you remove RSVP. You have =
engineering demands, something has to keep state. It does not matter to =
me if it is in RSVP or a controller. My point is that we do not deploy =
RSVP because we cannot make it scale. TE requirements are not about =
scale. If you can do that in a stateless case, you would do that.</li>
    <li class=3D"li2">John: Hannes talk is not about replacing =
RSVP.</li>
    <li class=3D"li2">Hannes: Happy to talk about it later on.</li>
    <li class=3D"li2">Ron Bonica: There are two conversations. One is in =
this minimal architectural framework versus the bigger architecture =
docs, the second is about replace RSVP. I want to talk about the former, =
which architecture is better. We should run the use cases through the =
architectures, and see if both pass, then we can invoke the =
smaller.</li>
    <li class=3D"li2">Someone2: If you look at the SR architecture =
document form Stefano, there are things not in RFC 3031. Node segment =
IDs representing multiple nodes. 3031 you have limited scope on node. =
Some things are not represented in 3031.</li>
    <li class=3D"li2">Rob: Response for Rob. To me this is not a =
replacement. To me, this is the part of the MPLS part of the SR =
architecture.</li>
    <li class=3D"li2">Hannes; Exactly, can we get away from the =
architecture in MPLS. We put the diligence of lawyers figuring out =
what=E2=80=99s defined and what=E2=80=99s not.</li>
    <li class=3D"li2">Ron B: It may be that there are concepts that are =
not in 3031, but the question is whether you need those to address the =
use cases we hard today.</li>
    <li class=3D"li2">John: Thanks everybody.</li>
  </ul>
</ul>
<p class=3D"p3"><br></p>
<p class=3D"p2">o Segment Routing Fast Reroute</p>
<p class=3D"p4"><span class=3D"s2">=C2=A0 <a =
href=3D"http://tools.ietf.org/html/draft-francois-sr-frr"><span =
class=3D"s3">http://tools.ietf.org/html/draft-francois-sr-frr</span></a></=
span></p>
<p class=3D"p2">=C2=A0 Bruno =
Decraene=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0 10 minutes</p>
<ul class=3D"ul1">
  <li class=3D"li2">Bruno: Presenting the Fast ReRoute Use case. This =
was presented in Berlin.</li>
  <li class=3D"li2">=E2=80=A6 this use case already documented in a =
draft.</li>
  <li class=3D"li2">=E2=80=A6 SR is directly applicable to these: first =
to remove LFA, get rid of t-LDP session. An extension is directed =
LFA.</li>
  <li class=3D"li2">=E2=80=A6 now going further. SR can use any number =
of nodes. What we are proposing now is FR from PLR to destination.</li>
  <li class=3D"li2">=E2=80=A6 First step is to compute the post =
convergence path, regular SPF, not new topology.</li>
  <li class=3D"li2">=E2=80=A6 So step two is to find the closest Q-node. =
There are four algorithms in the draft depending on link protection or =
node protection, or per next-hop of per-prefix.</li>
  <li class=3D"li2">=E2=80=A6 P node is the node that we want to reach. =
First we need to compute three SPT. SPT new. I use the green color for =
the new topology, and red for the old topology.</li>
  <li class=3D"li2">=E2=80=A6 we need to compute RDnew, which is the =
distance from old. FDold is SDold minus SFold. How can we get SD and SF? =
=46rom SPT old.</li>
  <li class=3D"li2">=E2=80=A6 now, RDnew, it is SDnew minus SRnew, =
because by design we enforce the new shortest path.</li>
  <li class=3D"li2">=E2=80=A6 now we know that it will use F to reach D. =
We will compare the shortest path. We are going to compare the path via =
F is FD. So if RDnew, R isn=E2=80=99t going to use F.</li>
  <li class=3D"li2">=E2=80=A6 the shortest list of segments to reach Q. =
P zero. We compute again, recurse, we call it P1, and so on. In most =
cases in our simulations we get 99% of cases.</li>
  <li class=3D"li2">=E2=80=A6 so we call it topology independent FRR. =
Provides 100% coverage for link and node protection. If your metric is =
based on delay, it is the shortest delay path. Best path per IGP =
metrics. And typically provisioned with enough capacity.</li>
  <li class=3D"li2">=E2=80=A6 it is policy friendly by default.</li>
  <li class=3D"li2">=E2=80=A6 Sorry we missed the deadline.=C2=A0</li>
  <li class=3D"li2">=E2=80=A6 So now, how much is this solution =
applicable? Directly applicable to Node Segments (SR), MPLS/LDP, and =
IP/IGP FECs.</li>
  <li class=3D"li2">=E2=80=A6 for SR adjacency segments is more complex. =
We cannot protect the adjacency because it is one per segment. We push F =
in order to enforce a route to F. We have two solutions. Directly =
applicable to people using TE.</li>
  <li class=3D"li2">=E2=80=A6 Questions?</li>
  <li class=3D"li2">=E2=80=A6 it is a bit =E2=80=9Cmath=E2=80=9D.</li>
  <li class=3D"li2">Questions:</li>
  <ul class=3D"ul2">
    <li class=3D"li2">Alvaro: Anyone? questions, comments?</li>
    <li class=3D"li2">Hannes: LFA, remote LFA, this seems like =
approaching light speed, the closer you get, the more exponential the =
number of energy you need to put. One suggestion: if the link is going =
down and queuing that constrain the cSFF and pushing the label =
stack.</li>
    <li class=3D"li2">Bruno: That=E2=80=99s exactly for node protection. =
But we are not enforcing, we are using the new path.</li>
    <li class=3D"li2">Hannes: So that=E2=80=99s for node =
protection?</li>
    <li class=3D"li2">Bruno: Yes, exactly.</li>
  </ul>
</ul>
<p class=3D"p3"><br></p>
<p class=3D"p2">o Segment Routing MPLS and SR/LDP Interoperability</p>
<p class=3D"p4"><span class=3D"s2">=C2=A0 <a =
href=3D"http://tools.ietf.org/html/draft-filsfils-spring-segment-routing-m=
pls"><span =
class=3D"s3">http://tools.ietf.org/html/draft-filsfils-spring-segment-rout=
ing-mpls</span></a></span></p>
<p class=3D"p4"><span class=3D"s2">=C2=A0 <a =
href=3D"http://tools.ietf.org/html/draft-filsfils-spring-segment-routing-l=
dp-interop"><span =
class=3D"s3">http://tools.ietf.org/html/draft-filsfils-spring-segment-rout=
ing-ldp-interop</span></a></span></p>
<p class=3D"p2">=C2=A0 Stefano =
Previdi=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0 10 minutes</p>
<ul class=3D"ul1">
  <li class=3D"li2">Stefano: I am back. This is SR with MPLS. We took it =
out from the architecture to have the architecture completely data plane =
agnostic.</li>
  <li class=3D"li2">=E2=80=A6 Segment in MPLS dataplane is a label. =
Obviously there is interop between SR and LDP/RSVP, documented is the =
LDP one.</li>
  <li class=3D"li2">=E2=80=A6 the improvement of SR over MPLS is the =
ability to do ECMP. And obviously no state in the core.</li>
  <li class=3D"li2">=E2=80=A6 the operations are PUSH, POP, SWAP, and we =
have equivalents.</li>
  <li class=3D"li2">=E2=80=A6 So LDP and RS interop, here=E2=80=99s a =
nice example. You can see from the advertisement from right to left, you =
can see the LDP advertisement goes into the LDP neighbor, and we use a =
functionality from SR introduced to IGP which is called a mapping label. =
So a node can add on behalf of nodes that do not support SR. So all =
routers will learn the mapping between F and label. And the SR/LDP =
capable nodes will translate with LDP label. It is just a ammeter of =
constructing the right label in the FIB.</li>
  <li class=3D"li2">=E2=80=A6 which means that the introduction of SR =
into an MPLS network is smooth, you do not need a forklift upgrade.</li>
  <li class=3D"li2">Questions?</li>
</ul>
<p class=3D"p3"><br></p>
<p class=3D"p2">=3D=3D=3D=3D=3D=C2=A0</p>
<p class=3D"p3"><br></p>
<ul class=3D"ul1">
  <li class=3D"li2">Alvaro: That concludes the first half, going into =
the second half.</li>
  <li class=3D"li2">=E2=80=A6 for the remaining presentation we would =
not fit them all, but please cut your presentation by a minute.</li>
</ul>
<p class=3D"p3"><br></p>
<p class=3D"p3"><br></p>
<p class=3D"p2">o Signaling Entropy Label Capability Using Interior =
Gateway Protocols</p>
<p class=3D"p4"><span class=3D"s2">=C2=A0 <a =
href=3D"http://tools.ietf.org/html/draft-xu-mpls-el-capability-signaling-i=
gp"><span =
class=3D"s3">http://tools.ietf.org/html/draft-xu-mpls-el-capability-signal=
ing-igp</span></a></span></p>
<p class=3D"p2">=C2=A0 Xiaohu =
Xu=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 5 minutes</p>
<ul class=3D"ul1">
  <li class=3D"li2">Xiaohu: It=E2=80=99s about signaling EL using =
IGP.=C2=A0</li>
  <li class=3D"li2">=E2=80=A6 a new TLV in the opaque LSA will advertise =
the RI, and a new sub-TLV is defined.=C2=A0</li>
  <li class=3D"li2">=E2=80=A6 thanks</li>
  <li class=3D"li2">Questions:</li>
  <ul class=3D"ul2">
    <li class=3D"li2">Ed: I question its utility. If you add a new =
sub-TLV you already have. If you do it with PCE, you have by PCE nego. =
So why?</li>
    <li class=3D"li2">Xiaohu: This is to advertise EL capability.</li>
    <li class=3D"li2">Ed: But, why?</li>
    <li class=3D"li2">Someone from Juniper: It is different to handle EL =
as egress versus transit. Need to distinguish those two =
capabilities.</li>
    <li class=3D"li2">=E2=80=A6 there was also a discussion on label =
size, you probably need to advefsize that.</li>
    <li class=3D"li2">Xiaohu: How many labels has been discussed but we =
decided we want to advertise the issue in the next draft, and we can =
come back.</li>
    <li class=3D"li2">Rob: I do not understand why signal. If nodes can =
hash, then they do hash.</li>
    <li class=3D"li2">Xiaohu: The segment routing use of label =
stack.</li>
    <li class=3D"li2">Rob: Fine, but the LSR can only look four labels =
deep, so you build a different stack?</li>
    <li class=3D"li2">Greg: You cannot do it in one lookup.</li>
    <li class=3D"li2">Alvaro: Great discussions, although we cannot hear =
it. Keep in mind that extensions for things that already exist are not =
done here. It=E2=80=99s good to socialize. =C2=A0=C2=A0</li>
  </ul>
</ul>
<p class=3D"p3"><br></p>
<p class=3D"p2">o Entropy labels for source routed stacked tunnels</p>
<p class=3D"p4"><span class=3D"s2">=C2=A0 <a =
href=3D"http://tools.ietf.org/html/draft-kini-mpls-entropy-label-src-stack=
ed-tunnels"><span =
class=3D"s3">http://tools.ietf.org/html/draft-kini-mpls-entropy-label-src-=
stacked-tunnels</span></a></span></p>
<p class=3D"p2">=C2=A0 Kireeti =
Kompella=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 10 minutes</p>
<ul class=3D"ul1">
  <li class=3D"li2">Kireeti: Did I actually signed up for this?</li>
  <li class=3D"li2">=E2=80=A6 so, umm, ah. so, uhmm.=C2=A0</li>
  <li class=3D"li2">=E2=80=A6 RFC 6790 says use EL for load balancing. =
Because in the middle of the network you do not have context of what=E2=80=
=99s going on. So you add an EL to the Tunnel Label. Then the transit =
LSR should use this label stack for LB.</li>
  <li class=3D"li2">=E2=80=A6 what happens with SR or SPRING or STATUS =
is that you have very deep label stacks, and you want to try to put an =
entropy label in there=E2=80=A6 some people say you do not need to use =
EL with SR. But you still do, for a couple of reasons. You have =
LAGs.</li>
  <li class=3D"li2">=E2=80=A6 so we looked at three ways of doing this. =
Single EL for the entire stack. You have this ELI/EL really deep in the =
stack that you might not be able to use.</li>
  <li class=3D"li2">=E2=80=A6 another way to do it is the idea from =
6790, which is every tunnel adds EL/ELI. You might not want to do =
that.</li>
  <li class=3D"li2">=E2=80=A6 the last one we did is adding ELI/EL =
after, so then you re-use after the pop, by pushing under the next =
tunnel.=C2=A0</li>
  <li class=3D"li2">=E2=80=A6 that magical operation might be difficult =
for some hardware, but that=E2=80=99s a detail.</li>
  <li class=3D"li2">=E2=80=A6 Another is at =E2=80=9Creadable stack =
depths=E2=80=9D. To do this, you have to know how many labels each LSR =
can process, so I think that=E2=80=99s what was being mumbled in the =
previous presentation.=C2=A0</li>
  <li class=3D"li2">=E2=80=A6 so there are other work related to EL. The =
first question is: do we want good load balancing with segment routing. =
And if you do, how do you want to it? None of the methods here are =
really ideal. So I think that answering the first question is important. =
If we do, we need to pick the least of all evils.</li>
  <li class=3D"li2">Questions:</li>
  <ul class=3D"ul2">
    <li class=3D"li2">John: Does anyone want to speak in favor of *not* =
using entropy? Then we can see which one.</li>
    <li class=3D"li2">Stewart: Is there any danger of misinterpreting =
labels for a router?</li>
    <li class=3D"li2">Kireeti: We have ELI</li>
    <li class=3D"li2">Stewart: What does a router do if it does not =
understand ELI?</li>
    <li class=3D"li2">Kireeti: Drops the packet.</li>
    <li class=3D"li2">Sam Aldrin: How are you going to ensure the =
explicit path?</li>
    <li class=3D"li2">Kireeti: So, it=E2=80=99s not an explicit path as =
people has said many times. You have node labels where you can get from =
a point to a point far away. Or you can have a adjacency labels. You can =
use the entropy label in either of these cases.</li>
    <li class=3D"li2">=E2=80=A6 if these are the exact set of links and =
none have LAGs, then in that case EL is not interesting.</li>
    <li class=3D"li2">Sam: You can figure out how to go from point A to =
point B.</li>
    <li class=3D"li2">Kireeti: Yes, that=E2=80=99s why it should not be =
called explicit path.</li>
    <li class=3D"li2">Ed: It=E2=80=99s a loose sourced explicit =
path.</li>
    <li class=3D"li2">=E2=80=A6 I have a comment here. We are talking =
about intermediate nodes, maybe older hardware that cannot use EL. =
Versus older HW that cannot understand EL. How do you negotiate?</li>
    <li class=3D"li2">Kireeti: We would guess it, we do not have a =
context to know if the last label is an PW label, or a VPN label with =
IPv4 directly below, or others. We used to guess it, sometimes get it =
right, sometimes not.</li>
    <li class=3D"li2">Ed: I am not against. Probably good idea, probably =
necessary, but you are not solving the whole problem. Unless you are =
finding out depth in the stack advertised, you are not solving the whole =
problem.</li>
    <li class=3D"li2">Kireeti: Moving it closer to the top, means it is =
associated to the tunnel. But now with SR, it is not so accessible.</li>
    <li class=3D"li2">Someone2: I believe EL is required, the question =
is how in the architecture get to a solution.</li>
    <li class=3D"li2">=E2=80=A6 the worst case I=E2=80=99ve seen is 8-9 =
labels, excluding entropy.</li>
    <li class=3D"li2">=E2=80=A6 I=E2=80=99d like to understand which of =
the 3 proposals you suggest. My preference is the 1st one you presented. =
Needs more feedback on if it is possible of feasible. How do we =
choose?</li>
    <li class=3D"li2">John: Let me propose that Entropy is not a =
bold-on, it is a key architectural element that needs to be covered in =
the architecture document. There;s a proposal on the table and =
interested parties.</li>
    <li class=3D"li2">Ed: Tangential comment =E2=80=94 people are very =
optimistic on the number of labels that can be pushed. I heard 10, and I =
won=E2=80=99t throw numbers but seems like high.</li>
    <li class=3D"li2">Kireeti: There are 3 proposals. People are talking =
about optimizing the label stack. If you reasonable expect to push 5 =
labels, maybe you can push 7, then you can use this.</li>
    <li class=3D"li2">=E2=80=A6 John asked the question about whether we =
care about Entropy but then answered that it is fundamental.</li>
    <li class=3D"li2">John: We need to answer that on the list.</li>
    <li class=3D"li2">Mark Townsley: If we are taking EL more =
fundamentally into the SR architecture, might we get rid of the =
ELI?</li>
    <li class=3D"li2">Kireeti: No.</li>
    <li class=3D"li2">Mark: Think harder. We might be able to.</li>
    <li class=3D"li2">John: The charter says do not tinkle with existing =
databases.</li>
    <li class=3D"li2">Ross C.: I will take my comment to the list.</li>
  </ul>
</ul>
<p class=3D"p3"><br></p>
<p class=3D"p2">o Analysis of the Overhead of Source Routing in SP =
Networks</p>
<p class=3D"p4"><span class=3D"s2">=C2=A0 <a =
href=3D"http://tools.ietf.org/html/draft-ashwood-sdnrg-state-reduction"><s=
pan =
class=3D"s3">http://tools.ietf.org/html/draft-ashwood-sdnrg-state-reductio=
n</span></a></span></p>
<p class=3D"p2">=C2=A0 Peter =
Ashwook-Smith=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 5 =
minutes</p>
<ul class=3D"ul1">
  <li class=3D"li2">Peter: Kireeti gave me a good segway to this =
meeting.</li>
  <li class=3D"li2">=E2=80=A6 rather than had waving about what we heard =
in Berlin, I asked for data. Four SPs replied and gave me 7 =
links.=C2=A0</li>
  <li class=3D"li2">=E2=80=A6 I was able to compute BW increase and =
overhead, and produced a little plot.</li>
  <li class=3D"li2">=E2=80=A6 this is a worst case, which might not be a =
case, but it gives you an upper bound.</li>
  <li class=3D"li2">=E2=80=A6 I won;t go over all diagrams, but the two =
upper most charts are more interesting. 40% of packets are under 100 =
bytes, but that=E2=80=99s less than 5% of the total bandwidth. Most of =
the links have these characteristics. One of the links which is a mobile =
backhaul with PW has much smaller packets.</li>
  <li class=3D"li2">=E2=80=A6 if you take this data and extrapolate, =
these are the curves you get. The 12 byte overhead, it would impose 2-3 =
% overhead, and max 6%.</li>
  <li class=3D"li2">=E2=80=A6 obviously this is small amount of data, =
but better than handwaving. Hopefully people find it useful.</li>
  <li class=3D"li2">Questions:</li>
  <ul class=3D"ul2">
    <li class=3D"li2">Ed C: This is useful. I=E2=80=99m glad you are =
doing it. My issue is my sample size.</li>
    <li class=3D"li2">Peter: I look forward to your addition to the =
sample.</li>
    <li class=3D"li2">Ed: It is dependent upon time, etc, etc,.</li>
    <li class=3D"li2">Peter: Yes, one is very coarse, one is very =
granular. And if another SP wants to contribute we will use it =
anonymously.</li>
  </ul>
</ul>
<p class=3D"p3"><br></p>
<p class=3D"p2">o Usecases of MPLS Global Label</p>
<p class=3D"p4"><span class=3D"s2">=C2=A0 <a =
href=3D"http://tools.ietf.org/html/draft-li-mpls-global-label-usecases"><s=
pan =
class=3D"s3">http://tools.ietf.org/html/draft-li-mpls-global-label-usecase=
s</span></a></span></p>
<p class=3D"p2">=C2=A0 A Framework of MPLS Global Label</p>
<p class=3D"p4"><span class=3D"s2">=C2=A0 <a =
href=3D"http://tools.ietf.org/html/draft-li-mpls-global-label-framework"><=
span =
class=3D"s3">http://tools.ietf.org/html/draft-li-mpls-global-label-framewo=
rk</span></a></span></p>
<p class=3D"p2">=C2=A0 =
TBD=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =
10 minutes</p>
<ul class=3D"ul1">
  <li class=3D"li2">Zhenbin: First is global label. Three uses: First =
Identification of the location, second, identification of the service, =
and third, identification of the Network</li>
  <li class=3D"li2">=E2=80=A6 For=C2=A0the identification of =
the=C2=A0location, we have VPLS multicast over MP2MP LSPs, segment based =
EVPN, and MPLS OAM for LDP LSPs.</li>
  <li class=3D"li2">=E2=80=A6 For=C2=A0the identification of the =
service, local protection of PE node.</li>
  <li class=3D"li2">=E2=80=A6 and for the identification of the Network, =
MPLS network virtualization mechanisms based on MPLS Global Label</li>
</ul>
<p class=3D"p3"><br></p>
<p class=3D"p2">o Framework of Network Virtualization Based on MPLS =
Global Label</p>
<p class=3D"p4"><span class=3D"s2">=C2=A0 <a =
href=3D"http://tools.ietf.org/html/draft-li-mpls-network-virtualization-fr=
amework"><span =
class=3D"s3">http://tools.ietf.org/html/draft-li-mpls-network-virtualizati=
on-framework</span></a></span></p>
<p class=3D"p2">=C2=A0 =
TBD=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =
10 minutes</p>
<ul class=3D"ul1">
  <li class=3D"li2">Zhenbin: Here we introduce the framework.=C2=A0</li>
  <li class=3D"li2">=E2=80=A6 What label should be used for MPLS Global =
Label? Two options, use the traditional MPLS label range, of resolving =
conflicts between global and existing label range, proposing a mega =
label.</li>
  <li class=3D"li2">=E2=80=A6 this is the control plane mechanism. =
Here=E2=80=99s the steps. It is better to be allocation from a central =
control point. The controller can share MPLS global label range for all =
nodes.</li>
  <li class=3D"li2">=E2=80=A6 it can send the label request to the =
controller, then the global label mapping message is received and =
installed.</li>
  <li class=3D"li2">=E2=80=A6 there are different applications. The =
first one is BGP-based, the second one is IGP-based, and the third one =
is PCE-based.</li>
</ul>
<p class=3D"p3"><br></p>
<p class=3D"p2">o Advertising Global Labels Using IGP</p>
<p class=3D"p4"><span class=3D"s2">=C2=A0 <a =
href=3D"http://tools.ietf.org/html/draft-xu-rtgwg-global-label-adv"><span =
class=3D"s3">http://tools.ietf.org/html/draft-xu-rtgwg-global-label-adv</s=
pan></a></span></p>
<p class=3D"p2">=C2=A0 Xiaohu =
Xu=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 10 minutes</p>
<ul class=3D"ul1">
  <li class=3D"li2">Alvaro: You have 4 minutes=E2=80=A6</li>
  <li class=3D"li2">Zhenbin: Next. Background, Virtual Operators want to =
use virtual network to deploy services. They do not want to know the =
details of the physical network. Based on this we have this doc.</li>
  <li class=3D"li2">=E2=80=A6 here we implement the MPLS virtual =
network. This is the physical network operator. There is an IGP =
controller and IGP client. There=E2=80=99s a central IGP controller. And =
there are virtual network operators that can have virtual network =
topologies.=C2=A0</li>
  <li class=3D"li2">=E2=80=A6 here we can see an example. The MPLS =
Global label identifies the topology. You do not see the details of the =
underlying network.</li>
  <li class=3D"li2">=E2=80=A6 We have this draft in ISIS, and we ant =
this solution for failure solutions.</li>
  <li class=3D"li2">=E2=80=A6 we propose these attributes for a virtual =
link.=C2=A0</li>
  <li class=3D"li2">=E2=80=A6 this is the forwarding in the virtual =
network. We have the virtual link, virtual node, and virtual =
topology.</li>
  <li class=3D"li2">=E2=80=A6 We want to build the global label for =
muti-topology FIB.</li>
</ul>
<p class=3D"p2">o =C2=A0Wrap:</p>
<ul class=3D"ul1">
  <li class=3D"li2">Alvaro: We have one more presentation.</li>
  <li class=3D"li2">People shouting: We saw this one already.</li>
  <li class=3D"li2">Alvaro: Actually, don;t leave=E2=80=A6</li>
  <li class=3D"li2">=E2=80=A6 there seems to be consensus that we can =
leave now.</li>
</ul>
</body>
</html>

--Apple-Mail=_9581EB51-105F-4B22-84C6-5EEA6030A755
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii



--Apple-Mail=_9581EB51-105F-4B22-84C6-5EEA6030A755--

--Apple-Mail=_DDA20643-CF83-4F69-824F-4F513F6EDC34
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAlJ4RrUACgkQtfDPGTp3USyEPACbBGl9+8tB0IOqgSQuKhh4YAFL
Z4IAnipc7ITE5cROnHwz3nRyHhVUjoo/
=HLte
-----END PGP SIGNATURE-----

--Apple-Mail=_DDA20643-CF83-4F69-824F-4F513F6EDC34--


From hannes@juniper.net  Mon Nov 18 01:24:41 2013
Return-Path: <hannes@juniper.net>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6FC611E80FA for <spring@ietfa.amsl.com>; Mon, 18 Nov 2013 01:24:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.097
X-Spam-Level: 
X-Spam-Status: No, score=-5.097 tagged_above=-999 required=5 tests=[AWL=1.502,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 ltq7DFlPfSC4 for <spring@ietfa.amsl.com>; Mon, 18 Nov 2013 01:24:34 -0800 (PST)
Received: from tx2outboundpool.messaging.microsoft.com (tx2ehsobe004.messaging.microsoft.com [65.55.88.14]) by ietfa.amsl.com (Postfix) with ESMTP id AA1EC11E8132 for <spring@ietf.org>; Mon, 18 Nov 2013 01:24:29 -0800 (PST)
Received: from mail63-tx2-R.bigfish.com (10.9.14.243) by TX2EHSOBE012.bigfish.com (10.9.40.32) with Microsoft SMTP Server id 14.1.225.22; Mon, 18 Nov 2013 09:24:28 +0000
Received: from mail63-tx2 (localhost [127.0.0.1])	by mail63-tx2-R.bigfish.com (Postfix) with ESMTP id 17DAF80753	for <spring@ietf.org>; Mon, 18 Nov 2013 09:24:28 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.237.149; KIP:(null); UIP:(null); IPV:NLI; H:BY2PRD0511HT002.namprd05.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -23
X-BigFish: VPS-23(zz98dI9371I1432Izz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h1d1ah1d2ah1fc6hzz8275ch1de098h1033IL8275bh8275dh1de097hz2fh2a8h839h946hd25he5bhf0ah1288h12a5h12a9h12bdh137ah139eh13b6h1441h14ddh1504h1537h162dh1631h1662h1758h1898h18e1h1946h19b5h19ceh1ad9h1b0ah224fh1d0ch1d2eh1d3fh1dfeh1dffh1e1dh1e23h1fe8h1ff5h2052h20b3h2218h2216h1155h)
Received-SPF: pass (mail63-tx2: domain of juniper.net designates 157.56.237.149 as permitted sender) client-ip=157.56.237.149; envelope-from=hannes@juniper.net; helo=BY2PRD0511HT002.namprd05.prod.outlook.com ; .outlook.com ; 
Received: from mail63-tx2 (localhost.localdomain [127.0.0.1]) by mail63-tx2 (MessageSwitch) id 1384766666239071_26771; Mon, 18 Nov 2013 09:24:26 +0000 (UTC)
Received: from TX2EHSMHS037.bigfish.com (unknown [10.9.14.243])	by mail63-tx2.bigfish.com (Postfix) with ESMTP id F3215260085	for <spring@ietf.org>; Mon, 18 Nov 2013 09:24:25 +0000 (UTC)
Received: from BY2PRD0511HT002.namprd05.prod.outlook.com (157.56.237.149) by TX2EHSMHS037.bigfish.com (10.9.99.137) with Microsoft SMTP Server (TLS) id 14.16.227.3; Mon, 18 Nov 2013 09:24:23 +0000
Received: from hannes-sslvpn-nc.jnpr.net (193.110.55.17) by pod51010.outlook.com (10.255.129.37) with Microsoft SMTP Server (TLS) id 14.16.371.2; Mon, 18 Nov 2013 09:24:22 +0000
From: Hannes Gredler <hannes@juniper.net>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 18 Nov 2013 10:24:15 +0100
References: <C30B286F-3453-4027-AB24-03ACEAA8F10C@juniper.net>
To: <spring@ietf.org>
Message-ID: <FF585B07-B4D6-4EDC-A813-B340D47D64CB@juniper.net>
MIME-Version: 1.0 (Apple Message framework v1283)
X-Mailer: Apple Mail (2.1283)
X-Originating-IP: [193.110.55.17]
X-OriginatorOrg: juniper.net
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Subject: [spring] request to move draft-filsfils-rtgwg-segment-routing-use-cases-02 to wg item
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Stacked Tunnels for Source Routing \(STATUS\)." <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/spring>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Nov 2013 09:24:41 -0000

Begin forwarded message:

> From: Hannes Gredler <hannes@juniper.net>
> Subject: Re: [Status] request to move =
draft-filsfils-rtgwg-segment-routing-use-cases-02 to wg item
> Date: November 18, 2013 10:13:20 AM GMT+01:00
> To: status@ietf.org
> Cc: John Scudder <jgs@juniper.net>, "Alvaro Retana (aretana)" =
<aretana@cisco.com>, "Clarence Filsfils (cfilsfil)" =
<cfilsfil@cisco.com>, "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
>=20
> support - (with a few caveats) - particularly where a 'solution' =
rather than
> a 'use case' is being described:
>=20
> ---
>=20
> -cut section 2 as it describes a solution and not necessarily belongs
> into a 'use-case' draft.
>=20
> -section 3.1: use-case drafts should not contain forward references
> to the 'solution' drafts - please cut the last paragraph.
> a note that the required protocol extension SHOULD support
> advertisement of backup paths would be ok.
>=20
> -section 4.1: TE without Bandwidth Admission Control is called
> 'Explicit Routing' - the current expression is a bit awkward;
>  - Its like ordering a Pizza without cheese - this is not a Pizza any
>    longer, right ?
>=20
> -section 4.1.1 'Anycast node segment' - this again is a solution and
> not the problem =85
>=20
> -section 4.1.1.1 we rather should make over this section to discuss =
the
> requirements of disjointness, what implications this has to real-world
> topologies rather than describing a 'Anycast SID based solution'.
> i can imagine that there are customers who want to use a central
> controller without the notion of any cast SIDs at all ...
>=20
> -section 4.1.2 add a reference to the OSPF and BGP/LS extended TE =
metrics.
>=20
> -section 4.1.3 i'd like to add a section which describes inter-domain =
TE
> by using label stacking, which seems a more general case rather than
> just using one label for egress link-selection.
>=20
> -section 5: i am not sure wether service-chaining is
>   (1) in-charter and to what extend the
>   (2) overlap with SFC working group is. -
>   suggest to cut this one.
>=20
> ---
>=20
>=20
> not sure if you need another co-author (as the list is fairly =
impressive),
> but i can contribute cycles/text for the editing work if you want.
>=20
> thanks,
>=20
> /hannes
>=20
>=20
> On Nov 7, 2013, at 5:24 AM, Stefano Previdi (sprevidi) wrote:
>=20
>> John, Alvaro, All,
>>=20
>> according to what discussed after the presentation of SR Use Cases at=20=

>> ietf88 spring-wg meeting, I'd like to request the adoption of=20
>> draft-filsfils-rtgwg-segment-routing-use-cases-02.txt as wg item.
>>=20
>> Thanks.
>> s.
>=20



From aretana@cisco.com  Mon Nov 18 07:51:34 2013
Return-Path: <aretana@cisco.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7959D11E81C5 for <spring@ietfa.amsl.com>; Mon, 18 Nov 2013 07:51:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
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 13go418EHfsO for <spring@ietfa.amsl.com>; Mon, 18 Nov 2013 07:51:29 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id E730D11E818F for <spring@ietf.org>; Mon, 18 Nov 2013 07:47:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2189; q=dns/txt; s=iport; t=1384789654; x=1385999254; h=from:to:subject:date:message-id:mime-version; bh=ZbxB8CVJI4/JFAQy4hA03P9awCMgP9VxzkZqXoDH9vY=; b=V2ECcLilOhj8Lpxv9Wnbt+qSGnppI8mKfyNYID9sN1IaAkIdsdJA+E5y aMmOYC1iduaBnrHZ3KZeuMwZbowVWERLWofRaNkNWC9rZR6xwa99USEI7 adGz13UmtC04d/uMpQ9ag1VM9MGJ4gw32EIFGoCOC4tuiSE39sbvnZQMM U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AnwJAEY2ilKtJV2a/2dsb2JhbABZgkNEOFO2bIlkFm0HgiyBCwEMAXMnBIgUDaEgoTyNF4cKA5gQgS+QXoMogWgFPQ
X-IronPort-AV: E=Sophos;i="4.93,724,1378857600";  d="scan'208,217";a="285804429"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-2.cisco.com with ESMTP; 18 Nov 2013 15:47:06 +0000
Received: from xhc-aln-x15.cisco.com (xhc-aln-x15.cisco.com [173.36.12.89]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id rAIFl6tD016943 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <spring@ietf.org>; Mon, 18 Nov 2013 15:47:06 GMT
Received: from xmb-aln-x15.cisco.com ([169.254.9.147]) by xhc-aln-x15.cisco.com ([173.36.12.89]) with mapi id 14.03.0123.003; Mon, 18 Nov 2013 09:47:06 -0600
From: "Alvaro Retana (aretana)" <aretana@cisco.com>
To: "spring@ietf.org" <spring@ietf.org>
Thread-Topic: IPR Declarations in spring
Thread-Index: AQHO5HVuWcmbfKC0oUCemBdA0YwYcA==
Date: Mon, 18 Nov 2013 15:47:05 +0000
Message-ID: <CEAFA0A7.41B20%aretana@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.117.15.4]
Content-Type: multipart/alternative; boundary="_000_CEAFA0A741B20aretanaciscocom_"
MIME-Version: 1.0
Subject: [spring] IPR Declarations in spring
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Stacked Tunnels for Source Routing \(STATUS\)." <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/spring>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Nov 2013 15:51:34 -0000

--_000_CEAFA0A741B20aretanaciscocom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi!

Please review the rules about disclosing intellectual property as expressed=
 in RFC 3979 and at http://trac.tools.ietf.org/group/iesg/trac/wiki/Intelle=
ctualProperty.

Following the example of other WGs, we have decided to adopt the following =
process:  poll authors/contributors on their compliance with IETF IPR rules=
 prior to moving a document to the next step in the WG process, e.g., befor=
e an individual draft becomes a WG document or a WG document goes to last c=
all.  IOW, no document will advance until we receive a response from all th=
e authors/contributors.

Thanks!

Alvaro + John


--_000_CEAFA0A741B20aretanaciscocom_
Content-Type: text/html; charset="us-ascii"
Content-ID: <B728646991463949A96D999D14939153@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif; ">
<div>Hi!</div>
<div><br>
</div>
<div>
<div>Please review the rules about disclosing intellectual property as expr=
essed in RFC 3979 and at
<a href=3D"http://trac.tools.ietf.org/group/iesg/trac/wiki/IntellectualProp=
erty">http://trac.tools.ietf.org/group/iesg/trac/wiki/IntellectualProperty<=
/a>.</div>
<div><br>
</div>
<div>Following the example of other WGs, we have decided to adopt the follo=
wing process: &nbsp;poll authors/contributors on their compliance with IETF=
 IPR rules prior to moving a document to the next step in the WG process, e=
.g., before an individual draft becomes
 a WG document or a WG document goes to last call. &nbsp;IOW, no document w=
ill advance until we receive a response from all the authors/contributors.<=
/div>
</div>
<div><br>
</div>
<div>Thanks!</div>
<div><br>
</div>
<div>Alvaro &#43; John</div>
<div><br>
</div>
</body>
</html>

--_000_CEAFA0A741B20aretanaciscocom_--

From aretana@cisco.com  Mon Nov 18 07:53:01 2013
Return-Path: <aretana@cisco.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FC9E11E812D for <spring@ietfa.amsl.com>; Mon, 18 Nov 2013 07:53:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
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 l9TR9EkTcq0o for <spring@ietfa.amsl.com>; Mon, 18 Nov 2013 07:52:55 -0800 (PST)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id 120B011E81A4 for <spring@ietf.org>; Mon, 18 Nov 2013 07:50:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1647; q=dns/txt; s=iport; t=1384789832; x=1385999432; h=from:to:cc:subject:date:message-id:mime-version; bh=24moWwpH/WGl3o29fNN+NkQx2zEqz2/xtvDB1XZPP58=; b=GpxVwoOUVZE7z80VpMfDZxAWDxYm2172sH1C4rtUn3s9KTLqnpLt4usM +byZI+HBRX91kEDlsHV1IRHgIgOAQEuIAMosRqhQZMH6F6/nBz79Nwk/m 0k4ZSIPDZDr/vTuYYBhcge9lkFp4lLftwzIdcVB/jmM2YNcehKTZnfb1o Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Al8GAEY2ilKtJV2Y/2dsb2JhbABZgkNEgQu/NoEaFm0HghwQHVwSAQsBdCcEDogGwlIXj2mEOAOYEJINgyiCKg
X-IronPort-AV: E=Sophos;i="4.93,724,1378857600";  d="scan'208,217";a="285842178"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-5.cisco.com with ESMTP; 18 Nov 2013 15:50:31 +0000
Received: from xhc-rcd-x13.cisco.com (xhc-rcd-x13.cisco.com [173.37.183.87]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id rAIFoV3p026911 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 18 Nov 2013 15:50:31 GMT
Received: from xmb-aln-x15.cisco.com ([169.254.9.147]) by xhc-rcd-x13.cisco.com ([173.37.183.87]) with mapi id 14.03.0123.003; Mon, 18 Nov 2013 09:50:31 -0600
From: "Alvaro Retana (aretana)" <aretana@cisco.com>
To: "draft-filsfils-rtgwg-segment-routing-use-cases@tools.ietf.org" <draft-filsfils-rtgwg-segment-routing-use-cases@tools.ietf.org>
Thread-Topic: IRP Claims related to draft-filsfils-rtgwg-segment-routing-use-cases
Thread-Index: AQHO5HXoHhlKZZ4m5EGmUvN6dvJ6Wg==
Date: Mon, 18 Nov 2013 15:50:30 +0000
Message-ID: <CEAFA174.41B29%aretana@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.117.15.4]
Content-Type: multipart/alternative; boundary="_000_CEAFA17441B29aretanaciscocom_"
MIME-Version: 1.0
Cc: "spring@ietf.org" <spring@ietf.org>
Subject: [spring] IRP Claims related to draft-filsfils-rtgwg-segment-routing-use-cases
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Stacked Tunnels for Source Routing \(STATUS\)." <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/spring>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Nov 2013 15:53:01 -0000

--_000_CEAFA17441B29aretanaciscocom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi!

In parallel to the call for adoption of this draft, I want to formally ask =
the authors (no additional contributors are listed in the latest version of=
 the draft) to please respond to this message indicating whether or not you=
 are aware of any relevant IPR.  The draft will not progress (pending the r=
esults of the WG Adoption Call) until we have received a response from each=
 author.

Thanks!

Alvaro.


--_000_CEAFA17441B29aretanaciscocom_
Content-Type: text/html; charset="us-ascii"
Content-ID: <1BE9C49BB261E045A5A19014B7BD072A@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif; ">
<div>Hi!</div>
<div><br>
</div>
<div>In parallel to the call for adoption of this draft,&nbsp;I want to for=
mally ask the authors (no additional contributors are listed in the latest =
version of the draft) to please respond to this message indicating whether =
or not you are aware of any relevant
 IPR. &nbsp;The draft will not progress (pending the results of the WG Adop=
tion Call) until we have received a response from each author.</div>
<div><br>
</div>
<div>Thanks!</div>
<div><br>
</div>
<div>Alvaro.</div>
<br>
</body>
</html>

--_000_CEAFA17441B29aretanaciscocom_--

From wim.henderickx@alcatel-lucent.com  Mon Nov 18 07:58:59 2013
Return-Path: <wim.henderickx@alcatel-lucent.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E265111E8159 for <spring@ietfa.amsl.com>; Mon, 18 Nov 2013 07:58:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
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 ARlRDB4RE0An for <spring@ietfa.amsl.com>; Mon, 18 Nov 2013 07:58:22 -0800 (PST)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id 8A49911E810A for <spring@ietf.org>; Mon, 18 Nov 2013 07:54:55 -0800 (PST)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (h135-239-2-42.lucent.com [135.239.2.42]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id rAIFsoFn009368 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 18 Nov 2013 09:54:52 -0600 (CST)
Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id rAIFsm0c015688 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 18 Nov 2013 16:54:50 +0100
Received: from FR711WXCHMBA07.zeu.alcatel-lucent.com ([169.254.3.62]) by FR711WXCHHUB02.zeu.alcatel-lucent.com ([135.239.2.112]) with mapi id 14.02.0247.003; Mon, 18 Nov 2013 16:54:49 +0100
From: "Henderickx, Wim (Wim)" <wim.henderickx@alcatel-lucent.com>
To: "Alvaro Retana (aretana)" <aretana@cisco.com>, "draft-filsfils-rtgwg-segment-routing-use-cases@tools.ietf.org" <draft-filsfils-rtgwg-segment-routing-use-cases@tools.ietf.org>
Thread-Topic: IRP Claims related to draft-filsfils-rtgwg-segment-routing-use-cases
Thread-Index: AQHO5HXoHhlKZZ4m5EGmUvN6dvJ6WpoqjTeA
Date: Mon, 18 Nov 2013 15:54:49 +0000
Message-ID: <CEAF7841.93A0F%wim.henderickx@alcatel-lucent.com>
In-Reply-To: <CEAFA174.41B29%aretana@cisco.com>
Accept-Language: nl-BE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.8.130913
x-originating-ip: [135.239.27.38]
Content-Type: multipart/alternative; boundary="_000_CEAF784193A0Fwimhenderickxalcatellucentcom_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
Cc: "spring@ietf.org" <spring@ietf.org>
Subject: Re: [spring] IRP Claims related to draft-filsfils-rtgwg-segment-routing-use-cases
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Stacked Tunnels for Source Routing \(STATUS\)." <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/spring>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Nov 2013 15:59:00 -0000

--_000_CEAF784193A0Fwimhenderickxalcatellucentcom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Not aware of IPR

From: "Alvaro Retana (aretana)" <aretana@cisco.com<mailto:aretana@cisco.com=
>>
Date: Monday 18 November 2013 16:50
To: "draft-filsfils-rtgwg-segment-routing-use-cases@tools.ietf.org<mailto:d=
raft-filsfils-rtgwg-segment-routing-use-cases@tools.ietf.org>" <draft-filsf=
ils-rtgwg-segment-routing-use-cases@tools.ietf.org<mailto:draft-filsfils-rt=
gwg-segment-routing-use-cases@tools.ietf.org>>
Cc: "spring@ietf.org<mailto:spring@ietf.org>" <spring@ietf.org<mailto:sprin=
g@ietf.org>>
Subject: IRP Claims related to draft-filsfils-rtgwg-segment-routing-use-cas=
es
Resent-From: <draft-alias-bounces@tools.ietf.org<mailto:draft-alias-bounces=
@tools.ietf.org>>
Resent-To: Bruno Decraene <bruno.decraene@orange.com<mailto:bruno.decraene@=
orange.com>>, Clarence Filsfil <cfilsfil@cisco.com<mailto:cfilsfil@cisco.co=
m>>, <edc@google.com<mailto:edc@google.com>>, Igor Milojevic <igormilojevic=
@telekom.rs<mailto:igormilojevic@telekom.rs>>, <jeff.tantsura@ericsson.com<=
mailto:jeff.tantsura@ericsson.com>>, Martin Horneffer <martin.horneffer@tel=
ekom.de<mailto:martin.horneffer@telekom.de>>, <pierre.francois@imdea.org<ma=
ilto:pierre.francois@imdea.org>>, Rob Shakir <rob.shakir@bt.com<mailto:rob.=
shakir@bt.com>>, <saku@ytti.fi<mailto:saku@ytti.fi>>, <sprevidi@cisco.com<m=
ailto:sprevidi@cisco.com>>, <sriganesh.kini@ericsson.com<mailto:sriganesh.k=
ini@ericsson.com>>, <stephane.litkowski@orange.com<mailto:stephane.litkowsk=
i@orange.com>>, Wim Henderickx <wim.henderickx@alcatel-lucent.com<mailto:wi=
m.henderickx@alcatel-lucent.com>>
Resent-Date: Monday 18 November 2013 16:51

Hi!

In parallel to the call for adoption of this draft, I want to formally ask =
the authors (no additional contributors are listed in the latest version of=
 the draft) to please respond to this message indicating whether or not you=
 are aware of any relevant IPR.  The draft will not progress (pending the r=
esults of the WG Adoption Call) until we have received a response from each=
 author.

Thanks!

Alvaro.


--_000_CEAF784193A0Fwimhenderickxalcatellucentcom_
Content-Type: text/html; charset="us-ascii"
Content-ID: <4620710ECFC24C44B74CD8AFFD6E9A55@exchange.lucent.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif;">
<div>Not aware of IPR</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:b=
lack; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM:=
 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;=
 BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style=3D"font-weight:bold">From: </span>&quot;Alvaro Retana (aretana)=
&quot; &lt;<a href=3D"mailto:aretana@cisco.com">aretana@cisco.com</a>&gt;<b=
r>
<span style=3D"font-weight:bold">Date: </span>Monday 18 November 2013 16:50=
<br>
<span style=3D"font-weight:bold">To: </span>&quot;<a href=3D"mailto:draft-f=
ilsfils-rtgwg-segment-routing-use-cases@tools.ietf.org">draft-filsfils-rtgw=
g-segment-routing-use-cases@tools.ietf.org</a>&quot; &lt;<a href=3D"mailto:=
draft-filsfils-rtgwg-segment-routing-use-cases@tools.ietf.org">draft-filsfi=
ls-rtgwg-segment-routing-use-cases@tools.ietf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Cc: </span>&quot;<a href=3D"mailto:spring@=
ietf.org">spring@ietf.org</a>&quot; &lt;<a href=3D"mailto:spring@ietf.org">=
spring@ietf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>IRP Claims related to draf=
t-filsfils-rtgwg-segment-routing-use-cases<br>
<span style=3D"font-weight:bold">Resent-From: </span>&lt;<a href=3D"mailto:=
draft-alias-bounces@tools.ietf.org">draft-alias-bounces@tools.ietf.org</a>&=
gt;<br>
<span style=3D"font-weight:bold">Resent-To: </span>Bruno Decraene &lt;<a hr=
ef=3D"mailto:bruno.decraene@orange.com">bruno.decraene@orange.com</a>&gt;, =
Clarence Filsfil &lt;<a href=3D"mailto:cfilsfil@cisco.com">cfilsfil@cisco.c=
om</a>&gt;, &lt;<a href=3D"mailto:edc@google.com">edc@google.com</a>&gt;,
 Igor Milojevic &lt;<a href=3D"mailto:igormilojevic@telekom.rs">igormilojev=
ic@telekom.rs</a>&gt;, &lt;<a href=3D"mailto:jeff.tantsura@ericsson.com">je=
ff.tantsura@ericsson.com</a>&gt;, Martin Horneffer &lt;<a href=3D"mailto:ma=
rtin.horneffer@telekom.de">martin.horneffer@telekom.de</a>&gt;,
 &lt;<a href=3D"mailto:pierre.francois@imdea.org">pierre.francois@imdea.org=
</a>&gt;, Rob Shakir &lt;<a href=3D"mailto:rob.shakir@bt.com">rob.shakir@bt=
.com</a>&gt;, &lt;<a href=3D"mailto:saku@ytti.fi">saku@ytti.fi</a>&gt;, &lt=
;<a href=3D"mailto:sprevidi@cisco.com">sprevidi@cisco.com</a>&gt;,
 &lt;<a href=3D"mailto:sriganesh.kini@ericsson.com">sriganesh.kini@ericsson=
.com</a>&gt;, &lt;<a href=3D"mailto:stephane.litkowski@orange.com">stephane=
.litkowski@orange.com</a>&gt;, Wim Henderickx &lt;<a href=3D"mailto:wim.hen=
derickx@alcatel-lucent.com">wim.henderickx@alcatel-lucent.com</a>&gt;<br>
<span style=3D"font-weight:bold">Resent-Date: </span>Monday 18 November 201=
3 16:51<br>
</div>
<div><br>
</div>
<div>
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-famil=
y: Calibri, sans-serif; ">
<div>Hi!</div>
<div><br>
</div>
<div>In parallel to the call for adoption of this draft,&nbsp;I want to for=
mally ask the authors (no additional contributors are listed in the latest =
version of the draft) to please respond to this message indicating whether =
or not you are aware of any relevant
 IPR. &nbsp;The draft will not progress (pending the results of the WG Adop=
tion Call) until we have received a response from each author.</div>
<div><br>
</div>
<div>Thanks!</div>
<div><br>
</div>
<div>Alvaro.</div>
<br>
</div>
</div>
</span>
</body>
</html>

--_000_CEAF784193A0Fwimhenderickxalcatellucentcom_--

From stephane.litkowski@orange.com  Mon Nov 18 08:05:27 2013
Return-Path: <stephane.litkowski@orange.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB1FD11E8172 for <spring@ietfa.amsl.com>; Mon, 18 Nov 2013 08:05:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.353
X-Spam-Level: 
X-Spam-Status: No, score=0.353 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, UNPARSEABLE_RELAY=0.001]
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 V2GKY13XxoJb for <spring@ietfa.amsl.com>; Mon, 18 Nov 2013 08:05:20 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias245.francetelecom.com [80.12.204.245]) by ietfa.amsl.com (Postfix) with ESMTP id 2E13D21F8C3E for <spring@ietf.org>; Mon, 18 Nov 2013 08:03:16 -0800 (PST)
Received: from omfeda08.si.francetelecom.fr (unknown [xx.xx.xx.201]) by omfeda14.si.francetelecom.fr (ESMTP service) with ESMTP id 667112AC6A9; Mon, 18 Nov 2013 17:03:15 +0100 (CET)
Received: from puexch91.nanterre.francetelecom.fr (unknown [10.101.44.48]) by omfeda08.si.francetelecom.fr (ESMTP service) with ESMTP id 4073E384073; Mon, 18 Nov 2013 17:03:15 +0100 (CET)
Received: from PUEXCB2F.nanterre.francetelecom.fr ([10.101.44.44]) by puexch91.nanterre.francetelecom.fr ([10.101.44.48]) with mapi; Mon, 18 Nov 2013 17:03:14 +0100
From: <stephane.litkowski@orange.com>
To: "Alvaro Retana (aretana)" <aretana@cisco.com>, "draft-filsfils-rtgwg-segment-routing-use-cases@tools.ietf.org" <draft-filsfils-rtgwg-segment-routing-use-cases@tools.ietf.org>
Date: Mon, 18 Nov 2013 17:03:13 +0100
Thread-Topic: IRP Claims related to draft-filsfils-rtgwg-segment-routing-use-cases
Thread-Index: AQHO5HXoHhlKZZ4m5EGmUvN6dvJ6WporJmug
Message-ID: <8803_1384790595_528A3A43_8803_11653_14_EEE55384044474429A926C625D0FCC810995A98480@PUEXCB2F.nanterre.francetelecom.fr>
References: <CEAFA174.41B29%aretana@cisco.com>
In-Reply-To: <CEAFA174.41B29%aretana@cisco.com>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: fr-FR
Content-Type: multipart/alternative; boundary="_000_EEE55384044474429A926C625D0FCC810995A98480PUEXCB2Fnante_"
MIME-Version: 1.0
X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2013.11.18.84815
Cc: "spring@ietf.org" <spring@ietf.org>
Subject: Re: [spring] IRP Claims related to draft-filsfils-rtgwg-segment-routing-use-cases
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Stacked Tunnels for Source Routing \(STATUS\)." <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/spring>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Nov 2013 16:05:27 -0000

--_000_EEE55384044474429A926C625D0FCC810995A98480PUEXCB2Fnante_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Not aware of IPR


De : Alvaro Retana (aretana) [mailto:aretana@cisco.com]
Envoy=E9 : lundi 18 novembre 2013 16:51
=C0 : draft-filsfils-rtgwg-segment-routing-use-cases@tools.ietf.org
Cc : spring@ietf.org
Objet : IRP Claims related to draft-filsfils-rtgwg-segment-routing-use-cases

Hi!

In parallel to the call for adoption of this draft, I want to formally ask =
the authors (no additional contributors are listed in the latest version of=
 the draft) to please respond to this message indicating whether or not you=
 are aware of any relevant IPR.  The draft will not progress (pending the r=
esults of the WG Adoption Call) until we have received a response from each=
 author.

Thanks!

Alvaro.


___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou =
falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been =
modified, changed or falsified.
Thank you.


--_000_EEE55384044474429A926C625D0FCC810995A98480PUEXCB2Fnante_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; charset=3Diso-8859-=
1">
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><meta name=3DGenerator content=3D"Microso=
ft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DFR link=3Dblue vlink=
=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'fon=
t-size:10.5pt;font-family:"Calibri","sans-serif";color:black'>Not aware of =
IPR<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0=
pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></spa=
n></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Cal=
ibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><div sty=
le=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'=
><p class=3DMsoNormal><b><span style=3D'font-size:10.0pt;font-family:"Tahom=
a","sans-serif"'>De&nbsp;:</span></b><span style=3D'font-size:10.0pt;font-f=
amily:"Tahoma","sans-serif"'> Alvaro Retana (aretana) [mailto:aretana@cisco=
.com] <br><b>Envoy=E9&nbsp;:</b> lundi 18 novembre 2013 16:51<br><b>=C0&nbs=
p;:</b> draft-filsfils-rtgwg-segment-routing-use-cases@tools.ietf.org<br><b=
>Cc&nbsp;:</b> spring@ietf.org<br><b>Objet&nbsp;:</b> IRP Claims related to=
 draft-filsfils-rtgwg-segment-routing-use-cases<o:p></o:p></span></p></div>=
</div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal><=
span style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif";color:bla=
ck'>Hi!<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span style=3D=
'font-size:10.5pt;font-family:"Calibri","sans-serif";color:black'><o:p>&nbs=
p;</o:p></span></p></div><div><p class=3DMsoNormal><span style=3D'font-size=
:10.5pt;font-family:"Calibri","sans-serif";color:black'>In parallel to the =
call for adoption of this draft,&nbsp;I want to formally ask the authors (n=
o additional contributors are listed in the latest version of the draft) to=
 please respond to this message indicating whether or not you are aware of =
any relevant IPR. &nbsp;The draft will not progress (pending the results of=
 the WG Adoption Call) until we have received a response from each author.<=
o:p></o:p></span></p></div><div><p class=3DMsoNormal><span style=3D'font-si=
ze:10.5pt;font-family:"Calibri","sans-serif";color:black'><o:p>&nbsp;</o:p>=
</span></p></div><div><p class=3DMsoNormal><span style=3D'font-size:10.5pt;=
font-family:"Calibri","sans-serif";color:black'>Thanks!<o:p></o:p></span></=
p></div><div><p class=3DMsoNormal><span style=3D'font-size:10.5pt;font-fami=
ly:"Calibri","sans-serif";color:black'><o:p>&nbsp;</o:p></span></p></div><d=
iv><p class=3DMsoNormal><span style=3D'font-size:10.5pt;font-family:"Calibr=
i","sans-serif";color:black'>Alvaro.<o:p></o:p></span></p></div><p class=3D=
MsoNormal><span style=3D'font-size:10.5pt;font-family:"Calibri","sans-serif=
";color:black'><o:p>&nbsp;</o:p></span></p></div><PRE>_____________________=
___________________________________________________________________________=
_________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages el=
ectroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou =
falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been =
modified, changed or falsified.
Thank you.
</PRE></body></html>=

--_000_EEE55384044474429A926C625D0FCC810995A98480PUEXCB2Fnante_--

From sprevidi@cisco.com  Mon Nov 18 08:12:30 2013
Return-Path: <sprevidi@cisco.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 684B111E8109 for <spring@ietfa.amsl.com>; Mon, 18 Nov 2013 08:12:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 roH-sYrWqbyC for <spring@ietfa.amsl.com>; Mon, 18 Nov 2013 08:12:24 -0800 (PST)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) by ietfa.amsl.com (Postfix) with ESMTP id 21CDD11E8122 for <spring@ietf.org>; Mon, 18 Nov 2013 08:08:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=601; q=dns/txt; s=iport; t=1384790925; x=1386000525; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=bqyrMVXW9HfgqsynkTDw/XNejylqWoGP3HOljeatItI=; b=Fno+KRcNt651a1yD2hzyV7I/tha2WyDewzZ7O+dg29g38tqaeeFLIapW EK8nn0MBSihJXxVDWIlWOidxAbLNGeLGwrL3ipJX5UVrWJErrQRCL+dfG fD1SJEok1fWJ6ySDmqUvwcriMqIPfXjFZJfGonZBn9EkXG2uwAlInM2bp o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgoFAO86ilKtJV2b/2dsb2JhbABZgwd/DL82gRsWdIIlAQEBAwEdHT8FCwIBCDYQMiUCBA6IAAbCQxePNjMHhDEDmBCSDYMogio
X-IronPort-AV: E=Sophos;i="4.93,724,1378857600";  d="scan'208";a="360029"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by alln-iport-3.cisco.com with ESMTP; 18 Nov 2013 16:08:30 +0000
Received: from xhc-rcd-x03.cisco.com (xhc-rcd-x03.cisco.com [173.37.183.77]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id rAIG8UhI004139 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 18 Nov 2013 16:08:30 GMT
Received: from xmb-rcd-x01.cisco.com ([169.254.1.140]) by xhc-rcd-x03.cisco.com ([173.37.183.77]) with mapi id 14.03.0123.003; Mon, 18 Nov 2013 10:08:29 -0600
From: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
To: "Alvaro Retana (aretana)" <aretana@cisco.com>
Thread-Topic: IRP Claims related to draft-filsfils-rtgwg-segment-routing-use-cases
Thread-Index: AQHO5HXoHhlKZZ4m5EGmUvN6dvJ6WporjHwA
Date: Mon, 18 Nov 2013 16:08:29 +0000
Message-ID: <66C21242-9C79-4863-8901-503134285534@cisco.com>
References: <CEAFA174.41B29%aretana@cisco.com>
In-Reply-To: <CEAFA174.41B29%aretana@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.61.160.136]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <37996CFDC96EE2438EB0D4B50E45B6DE@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "spring@ietf.org" <spring@ietf.org>, "draft-filsfils-rtgwg-segment-routing-use-cases@tools.ietf.org" <draft-filsfils-rtgwg-segment-routing-use-cases@tools.ietf.org>
Subject: Re: [spring] IRP Claims related to draft-filsfils-rtgwg-segment-routing-use-cases
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Stacked Tunnels for Source Routing \(STATUS\)." <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/spring>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Nov 2013 16:12:30 -0000

Hi,

there is IPR that is in the process of being disclosed.

Thanks.
s.


On Nov 18, 2013, at 4:50 PM, Alvaro Retana (aretana) wrote:

> Hi!
>=20
> In parallel to the call for adoption of this draft, I want to formally as=
k the authors (no additional contributors are listed in the latest version =
of the draft) to please respond to this message indicating whether or not y=
ou are aware of any relevant IPR.  The draft will not progress (pending the=
 results of the WG Adoption Call) until we have received a response from ea=
ch author.
>=20
> Thanks!
>=20
> Alvaro.
>=20


From jeff.tantsura@ericsson.com  Mon Nov 18 08:18:58 2013
Return-Path: <jeff.tantsura@ericsson.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3AD911E81A1 for <spring@ietfa.amsl.com>; Mon, 18 Nov 2013 08:18:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 IVZbYM+wG3ZE for <spring@ietfa.amsl.com>; Mon, 18 Nov 2013 08:18:52 -0800 (PST)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id 8CC2111E80EE for <spring@ietf.org>; Mon, 18 Nov 2013 08:16:38 -0800 (PST)
X-AuditID: c618062d-b7f278e000005a8f-37-528a3d65b7fe
Received: from EUSAAHC004.ericsson.se (Unknown_Domain [147.117.188.84]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id 35.21.23183.56D3A825; Mon, 18 Nov 2013 17:16:37 +0100 (CET)
Received: from EUSAAMB109.ericsson.se ([147.117.188.126]) by EUSAAHC004.ericsson.se ([147.117.188.84]) with mapi id 14.02.0328.009; Mon, 18 Nov 2013 11:16:37 -0500
From: Jeff Tantsura <jeff.tantsura@ericsson.com>
To: "Alvaro Retana (aretana)" <aretana@cisco.com>
Thread-Topic: IRP Claims related to draft-filsfils-rtgwg-segment-routing-use-cases
Thread-Index: AQHO5HXoHhlKZZ4m5EGmUvN6dvJ6WporKjEw
Date: Mon, 18 Nov 2013 16:16:37 +0000
Message-ID: <4B379E02-E273-46D6-958E-ADCD7B668530@ericsson.com>
References: <CEAFA174.41B29%aretana@cisco.com>
In-Reply-To: <CEAFA174.41B29%aretana@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrNLMWRmVeSWpSXmKPExsUyuXRPiG6qbVeQwcndkhZ/f25ltJi5bjKr xfELvxkdmD2m/N7I6rFkyU8mjy+XP7MFMEdx2aSk5mSWpRbp2yVwZazZ7lhwgaXi0oc/zA2M 55i7GDk5JARMJK4/72aDsMUkLtxbD2RzcQgJHGGUWD5/OTuEs5xRYseiCWAdbAIGEv+/HWcB sUUEDCVm3tzPAlLELLCGUWLKmv9gCWGBYInek0fYIIpCJLb/vgHVYCTxpvEDO4jNIqAqsWPj RLAaXgF7iTU7uhhBbCEBPYlrs8+xdjFycHAK6Evs2CQOEmYEuu77qTVMIDazgLjErSfzmSCu FpBYsuc81DeiEi8f/2OFqNGRWLD7ExuErS2xbOFrZohVghInZz5hmcAoOgvJqFlIWmYhaZmF pGUBI8sqRo7S4tSy3HQjg02MwAg5JsGmu4Nxz0vLQ4zSHCxK4rxf3joHCQmkJ5akZqemFqQW xReV5qQWH2Jk4uCUamBslb1dYny182TI1uSkpIcd3WurV/n2dK36oXSUUd7DiWOCsEbO+w0X OHk0g1QUqt9aiHVN2F3fKbh+5u2MZxt5H0Zx1pkdWvxxs6aNWveP10V+C/z2TDn9es3Mg78i W9lXPv81NXL1xvXrf3ptYWVh6FAKepf4ReFVZmC4bviyFWdMQtKWTlRVYinOSDTUYi4qTgQA zI7buF4CAAA=
Cc: "spring@ietf.org" <spring@ietf.org>, "draft-filsfils-rtgwg-segment-routing-use-cases@tools.ietf.org" <draft-filsfils-rtgwg-segment-routing-use-cases@tools.ietf.org>
Subject: Re: [spring] IRP Claims related to draft-filsfils-rtgwg-segment-routing-use-cases
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Stacked Tunnels for Source Routing \(STATUS\)." <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/spring>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Nov 2013 16:18:59 -0000

Not aware of any IPR.

Regards,
Jeff

> On Nov 18, 2013, at 7:50 AM, "Alvaro Retana (aretana)" <aretana@cisco.com=
> wrote:
>=20
> Hi!
>=20
> In parallel to the call for adoption of this draft, I want to formally as=
k the authors (no additional contributors are listed in the latest version =
of the draft) to please respond to this message indicating whether or not y=
ou are aware of any relevant IPR.  The draft will not progress (pending the=
 results of the WG Adoption Call) until we have received a response from ea=
ch author.
>=20
> Thanks!
>=20
> Alvaro.
>=20

From pierre.francois@imdea.org  Mon Nov 18 08:19:03 2013
Return-Path: <pierre.francois@imdea.org>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7160911E80EE for <spring@ietfa.amsl.com>; Mon, 18 Nov 2013 08:19:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 kk3VRyxb2XBN for <spring@ietfa.amsl.com>; Mon, 18 Nov 2013 08:18:57 -0800 (PST)
Received: from estafeta21.imdea.org (maquina46.madrimasd.org [193.145.15.46]) by ietfa.amsl.com (Postfix) with ESMTP id 400F511E8190 for <spring@ietf.org>; Mon, 18 Nov 2013 08:16:39 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by estafeta21.imdea.org (imdea mail daemon) with ESMTP id B06E01B0072;  Mon, 18 Nov 2013 17:15:18 +0100 (CET)
X-Virus-Scanned: by antispam-antivirus system at imdea.org
Received: from estafeta21.imdea.org ([127.0.0.1]) by localhost (estafeta21.imdea.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2oxKx6R8McEd; Mon, 18 Nov 2013 17:15:18 +0100 (CET)
Received: from ams3-vpn-dhcp8103.cisco.com (173-38-208-169.cisco.com [173.38.208.169]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: pierre.francois) by estafeta21.imdea.org (imdea mail daemon) with ESMTPSA id 4AB3F1B0071; Mon, 18 Nov 2013 17:15:18 +0100 (CET)
Content-Type: multipart/alternative; boundary="Apple-Mail=_05F757DA-1C23-4A92-AB1C-D9B524C9D9F1"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Pierre Francois <pierre.francois@imdea.org>
In-Reply-To: <CEAFA174.41B29%aretana@cisco.com>
Date: Mon, 18 Nov 2013 17:16:32 +0100
Message-Id: <9144882A-7872-4CEB-A122-45DB8C1D46D6@imdea.org>
References: <CEAFA174.41B29%aretana@cisco.com>
To: "Alvaro Retana (aretana)" <aretana@cisco.com>
X-Mailer: Apple Mail (2.1510)
Cc: "spring@ietf.org" <spring@ietf.org>, "draft-filsfils-rtgwg-segment-routing-use-cases@tools.ietf.org" <draft-filsfils-rtgwg-segment-routing-use-cases@tools.ietf.org>
Subject: Re: [spring] IRP Claims related to draft-filsfils-rtgwg-segment-routing-use-cases
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Stacked Tunnels for Source Routing \(STATUS\)." <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/spring>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Nov 2013 16:19:03 -0000

--Apple-Mail=_05F757DA-1C23-4A92-AB1C-D9B524C9D9F1
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hello,=20

There is IPR that is in the process of being disclosed.=20

Regards,=20

Pierre.


On Nov 18, 2013, at 4:50 PM, "Alvaro Retana (aretana)" =
<aretana@cisco.com> wrote:

> Hi!
>=20
> In parallel to the call for adoption of this draft, I want to formally =
ask the authors (no additional contributors are listed in the latest =
version of the draft) to please respond to this message indicating =
whether or not you are aware of any relevant IPR.  The draft will not =
progress (pending the results of the WG Adoption Call) until we have =
received a response from each author.
>=20
> Thanks!
>=20
> Alvaro.
>=20


--Apple-Mail=_05F757DA-1C23-4A92-AB1C-D9B524C9D9F1
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hello,&nbsp;<div><br></div><div>There is IPR that is in the process of being disclosed.&nbsp;</div><div><br></div><div>Regards,&nbsp;</div><div><br></div><div>Pierre.</div><div><br></div><div><br><div><div>On Nov 18, 2013, at 4:50 PM, "Alvaro Retana (aretana)" &lt;<a href="mailto:aretana@cisco.com">aretana@cisco.com</a>&gt; wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">

<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">

<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; font-size: 14px; font-family: Calibri, sans-serif; ">
<div>Hi!</div>
<div><br>
</div>
<div>In parallel to the call for adoption of this draft,&nbsp;I want to formally ask the authors (no additional contributors are listed in the latest version of the draft) to please respond to this message indicating whether or not you are aware of any relevant
 IPR. &nbsp;The draft will not progress (pending the results of the WG Adoption Call) until we have received a response from each author.</div>
<div><br>
</div>
<div>Thanks!</div>
<div><br>
</div>
<div>Alvaro.</div>
<br>
</div>

</blockquote></div><br></div></body></html>
--Apple-Mail=_05F757DA-1C23-4A92-AB1C-D9B524C9D9F1--

From saku@ytti.fi  Mon Nov 18 08:45:26 2013
Return-Path: <saku@ytti.fi>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D120611E80E2 for <spring@ietfa.amsl.com>; Mon, 18 Nov 2013 08:45:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.203
X-Spam-Level: 
X-Spam-Status: No, score=-2.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, 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 07yKqRurGO+U for <spring@ietfa.amsl.com>; Mon, 18 Nov 2013 08:45:21 -0800 (PST)
Received: from mail-bk0-f54.google.com (mail-bk0-f54.google.com [209.85.214.54]) by ietfa.amsl.com (Postfix) with ESMTP id 36E6E11E8135 for <spring@ietf.org>; Mon, 18 Nov 2013 08:43:05 -0800 (PST)
Received: by mail-bk0-f54.google.com with SMTP id v16so861020bkz.27 for <spring@ietf.org>; Mon, 18 Nov 2013 08:42:59 -0800 (PST)
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:cc:content-transfer-encoding:message-id:references :to; bh=XmgbgboAomXh2l44cMvIfZ9D15nk1+Gkc8N+8LQe4OU=; b=VDBdQffIHq2rab87trQj+JPRIbC8HZxhCSqS1RZRkftWrZh4CVVD/+8OdN02HVhEy5 xXhK4FEPr5iSzPg47O0M9harQfpMm0sUqAQBcqCX7q1F2usPFQnLD9eTw/7LS90YYHKj Z+jzkIL8RaPW/3SKweAncZ5HyCpBxTVGq8AlJRdZhKArmONQYhXhmyuDT4bfvEUgp5DQ W0a/IS2zk/lzx7LEVuXIyxfJpKva7y2osUpfeFme6Z9uwnzmHxCMNPq3Eo9ToQCv/h8N Uup7X6fYFrPyU+CmFE3pV1f65NKl5tPV41mDIBwwQa0YKRlbbPqIcI7BYToPKc9UgNKA vuuA==
X-Gm-Message-State: ALoCoQnyTTVzvSjoJa3m72ch2iFjNXUbbCr/S1O27ovbQJz4ta+fUmisr3pSPd581+ieZsFTqSCj
X-Received: by 10.204.127.135 with SMTP id g7mr33049bks.42.1384792979312; Mon, 18 Nov 2013 08:42:59 -0800 (PST)
Received: from ?IPv6:2001:67c:17a0::71af:f497:bb0b:f764? ([2001:67c:17a0:0:71af:f497:bb0b:f764]) by mx.google.com with ESMTPSA id j6sm6643495bki.17.2013.11.18.08.42.57 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 18 Nov 2013 08:42:58 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
From: Saku Ytti <saku@ytti.fi>
X-Mailer: iPad Mail (11B511)
In-Reply-To: <CEAFA174.41B29%aretana@cisco.com>
Date: Mon, 18 Nov 2013 18:42:59 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <4F40234E-4DC6-4B85-B06E-F5CC96472826@ytti.fi>
References: <CEAFA174.41B29%aretana@cisco.com>
To: "Alvaro Retana (aretana)" <aretana@cisco.com>
Cc: "spring@ietf.org" <spring@ietf.org>, "draft-filsfils-rtgwg-segment-routing-use-cases@tools.ietf.org" <draft-filsfils-rtgwg-segment-routing-use-cases@tools.ietf.org>
Subject: Re: [spring] IRP Claims related to draft-filsfils-rtgwg-segment-routing-use-cases
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Stacked Tunnels for Source Routing \(STATUS\)." <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/spring>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Nov 2013 16:45:27 -0000

Not aware of any relevant IPR

--=20
  ++ytti


> On 18 Nov 2013, at 17:50, "Alvaro Retana (aretana)" <aretana@cisco.com> wr=
ote:
>=20
> Hi!
>=20
> In parallel to the call for adoption of this draft, I want to formally ask=
 the authors (no additional contributors are listed in the latest version of=
 the draft) to please respond to this message indicating whether or not you a=
re aware of any relevant IPR.  The draft will not progress (pending the resu=
lts of the WG Adoption Call) until we have received a response from each aut=
hor.
>=20
> Thanks!
>=20
> Alvaro.
>=20

From sriganeshkini@gmail.com  Mon Nov 18 08:45:27 2013
Return-Path: <sriganeshkini@gmail.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4541711E80E2 for <spring@ietfa.amsl.com>; Mon, 18 Nov 2013 08:45:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
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 x0Fb7MUi8d+e for <spring@ietfa.amsl.com>; Mon, 18 Nov 2013 08:45:26 -0800 (PST)
Received: from mail-pb0-x229.google.com (mail-pb0-x229.google.com [IPv6:2607:f8b0:400e:c01::229]) by ietfa.amsl.com (Postfix) with ESMTP id 7B30611E80FB for <spring@ietf.org>; Mon, 18 Nov 2013 08:43:37 -0800 (PST)
Received: by mail-pb0-f41.google.com with SMTP id jt11so7041755pbb.28 for <spring@ietf.org>; Mon, 18 Nov 2013 08:43:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=WzMjWrN2ATVz2a1qEhxQXvsnVEjOvmva3EhKxgXasY4=; b=DkJ0rGAEHq/fm+d32Ol/LXjbgZR43sXQqJK2i6tbVhk3OQtgariCysCySSg6FhIJr9 va7wKrFtQPxGsYSwuN2Ileh54vd/cHYy23+DlbGCq9G9WaRRdQIoEm38NMoAqqThZFF+ wPU65x2ShxcYmEyBKNiaqUwRgWBtwBieoauR9kmQu3NqD2MeP7jaE4FhzW1nwKKhW+oz X0mJjx+EW0su3Q+oQ8aVwGkE7d6pZciEWZCCIe1OvvRR8CY4GUczOpCef2oaWm9XWdLl SD12+ji3QQTxTE8DaH2fZMuvWunn8ngqxTbAizHjA0YZ+E6NGmhuNPIbIzMurKBXLFPT r03A==
MIME-Version: 1.0
X-Received: by 10.66.118.204 with SMTP id ko12mr1386406pab.184.1384792999169;  Mon, 18 Nov 2013 08:43:19 -0800 (PST)
Received: by 10.70.0.228 with HTTP; Mon, 18 Nov 2013 08:43:19 -0800 (PST)
In-Reply-To: <CEAFA174.41B29%aretana@cisco.com>
References: <CEAFA174.41B29%aretana@cisco.com>
Date: Mon, 18 Nov 2013 08:43:19 -0800
Message-ID: <CAOndX-u+bJPOs9hPTkBeZr40OUz5ENG5JEC_XyKH9QnDTeRGiA@mail.gmail.com>
From: Sri <sriganeshkini@gmail.com>
To: "Alvaro Retana (aretana)" <aretana@cisco.com>
Content-Type: multipart/alternative; boundary=e89a8ffbaa2bcd956004eb763e6d
Cc: "spring@ietf.org" <spring@ietf.org>, "draft-filsfils-rtgwg-segment-routing-use-cases@tools.ietf.org" <draft-filsfils-rtgwg-segment-routing-use-cases@tools.ietf.org>
Subject: Re: [spring] IRP Claims related to draft-filsfils-rtgwg-segment-routing-use-cases
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Stacked Tunnels for Source Routing \(STATUS\)." <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/spring>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Nov 2013 16:45:27 -0000

--e89a8ffbaa2bcd956004eb763e6d
Content-Type: text/plain; charset=UTF-8

Not aware of any IPR.

Thanks
- Sri

On Monday, November 18, 2013, Alvaro Retana (aretana) wrote:

>  Hi!
>
>  In parallel to the call for adoption of this draft, I want to formally
> ask the authors (no additional contributors are listed in the latest
> version of the draft) to please respond to this message indicating whether
> or not you are aware of any relevant IPR.  The draft will not progress
> (pending the results of the WG Adoption Call) until we have received a
> response from each author.
>
>  Thanks!
>
>  Alvaro.
>
>

--e89a8ffbaa2bcd956004eb763e6d
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Not aware of any IPR.<div><br></div><div>Thanks</div><div>- Sri<br><br>On M=
onday, November 18, 2013, Alvaro Retana (aretana)  wrote:<br><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;p=
adding-left:1ex">




<div style=3D"font-size:14px;font-family:Calibri,sans-serif;word-wrap:break=
-word">
<div>Hi!</div>
<div><br>
</div>
<div>In parallel to the call for adoption of this draft,=C2=A0I want to for=
mally ask the authors (no additional contributors are listed in the latest =
version of the draft) to please respond to this message indicating whether =
or not you are aware of any relevant
 IPR. =C2=A0The draft will not progress (pending the results of the WG Adop=
tion Call) until we have received a response from each author.</div>
<div><br>
</div>
<div>Thanks!</div>
<div><br>
</div>
<div>Alvaro.</div>
<br>
</div>

</blockquote></div>

--e89a8ffbaa2bcd956004eb763e6d--

From edc@google.com  Mon Nov 18 08:40:24 2013
Return-Path: <edc@google.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36EF011E8141 for <spring@ietfa.amsl.com>; Mon, 18 Nov 2013 08:40:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001]
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 h8JvN3qFVTPl for <spring@ietfa.amsl.com>; Mon, 18 Nov 2013 08:40:22 -0800 (PST)
Received: from mail-wi0-x22c.google.com (mail-wi0-x22c.google.com [IPv6:2a00:1450:400c:c05::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 29F9F11E8152 for <spring@ietf.org>; Mon, 18 Nov 2013 08:39:35 -0800 (PST)
Received: by mail-wi0-f172.google.com with SMTP id en1so2261885wid.11 for <spring@ietf.org>; Mon, 18 Nov 2013 08:39:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=w1S82Vbx+B4AkvZQj0hZq6hukowgg9m/ahZsCulFkss=; b=Op587NLXYLR53sjJiM4O7OL+vLNWSSEdADsCaP9PNNEgYOZAPdiDRypvB6TbiyJ7ed ZBaIl5qtN+NEzuplF9dXyCx9eG/HR9/PrNjWueSwiwZPScVQk6NzMNg3+7DEYyMeTKqi P3gwzLGHBZ7Tuy9r4WmKGk/FDOEcs9ksyaCtlPyRQARmSBaUEr2hWHJmF9j99Iq/0lgd 9YtNvhDC6X7wUuCdHhuW2sj7yX6N+eI2fRM9tyztmUl8NCsVdKXAGBt/8RAjbsPeMHED NN0kEJ2nUsntEi9e8doZvWmuw5Tl2dIbwA+tW4TRdyC2Tc78HivlAZEMfRWbwfWT6eDU +zqg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=w1S82Vbx+B4AkvZQj0hZq6hukowgg9m/ahZsCulFkss=; b=JC3QRq1kyaPhbUQuyksdtAxQlEb21Nd5mSuhXAcrB2vBfuDuMnfEy1JSngs1GozYPU OClaVxki2tjTM8yd6Bps1tnjcP0mO0rtb7qHhEKpLXWmKOTDam7E0tR+Mg5acEmmBoq1 x1KQaY3EmI63pcgu2DVS01dvoZN0H6/C6TKKvP/abg5nU7QF+l3K2ziJtAcf68vKP8Zt IVMVKet7FR0+VS0uvjt6jN1uaokCS/eGsan97oQdE4/V1CU/6WjckAotKUNDHk9F/GC0 AxQ4hkK7OaRIXPGMAu3s2ifk/v20YrdS7BqbjGtal5NjTqIczfh9uq2c4FYNeysCACVM yFeA==
X-Gm-Message-State: ALoCoQlo1ttMsO+0AvP1hMxOY8Ov+nOwffTCA6Cp/trI7YI6H3FF3tS3cSXp9Y2Fw+Aswc8gzFHhYXidLrTk6lMsCCeIgv00xLaUIFvVyHuG9Eu32R0MoX9RuTMKAOdWPHWn8er78nAUUZFOgecJK9iyP1vLqfHvFIV9z6GM/b51YlAEU2X3Ue73Y3X+ocVyRrr1akm9brx4
X-Received: by 10.194.121.228 with SMTP id ln4mr2018459wjb.50.1384792750511; Mon, 18 Nov 2013 08:39:10 -0800 (PST)
MIME-Version: 1.0
Received: by 10.194.23.3 with HTTP; Mon, 18 Nov 2013 08:38:30 -0800 (PST)
In-Reply-To: <CEAFA174.41B29%aretana@cisco.com>
References: <CEAFA174.41B29%aretana@cisco.com>
From: Edward Crabbe <edc@google.com>
Date: Mon, 18 Nov 2013 08:38:30 -0800
Message-ID: <CACKN6JEiSM6ypam4OgkqGnHKmzAkhvstRQ6LR2JPmBryeqAJsA@mail.gmail.com>
To: "Alvaro Retana (aretana)" <aretana@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Mailman-Approved-At: Mon, 18 Nov 2013 13:49:18 -0800
Cc: "spring@ietf.org" <spring@ietf.org>, "draft-filsfils-rtgwg-segment-routing-use-cases@tools.ietf.org" <draft-filsfils-rtgwg-segment-routing-use-cases@tools.ietf.org>
Subject: Re: [spring] IRP Claims related to draft-filsfils-rtgwg-segment-routing-use-cases
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Stacked Tunnels for Source Routing \(STATUS\)." <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Nov 2013 16:40:24 -0000

Not aware of any IPR.

On Mon, Nov 18, 2013 at 7:50 AM, Alvaro Retana (aretana)
<aretana@cisco.com> wrote:
> Hi!
>
> In parallel to the call for adoption of this draft, I want to formally ask
> the authors (no additional contributors are listed in the latest version of
> the draft) to please respond to this message indicating whether or not you
> are aware of any relevant IPR.  The draft will not progress (pending the
> results of the WG Adoption Call) until we have received a response from each
> author.
>
> Thanks!
>
> Alvaro.
>

From maho@lab.dtag.de  Mon Nov 18 09:04:23 2013
Return-Path: <maho@lab.dtag.de>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC2C811E813B for <spring@ietfa.amsl.com>; Mon, 18 Nov 2013 09:04:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.8
X-Spam-Level: 
X-Spam-Status: No, score=-1.8 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, HELO_MISMATCH_DE=1.448, HTML_MESSAGE=0.001, 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 4yK3WQM63gXG for <spring@ietfa.amsl.com>; Mon, 18 Nov 2013 09:04:19 -0800 (PST)
Received: from owl.lab.dtag.de (Owl.lab.DTAG.DE [194.25.1.236]) by ietfa.amsl.com (Postfix) with ESMTP id 2670E11E8138 for <spring@ietf.org>; Mon, 18 Nov 2013 09:04:13 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by owl.lab.dtag.de (Postfix) with ESMTP id 42C7E597381; Mon, 18 Nov 2013 18:04:10 +0100 (CET)
Received: from tsunami-neu.26.lab.dtag.de (o.Boggart.lab.dtag.de [62.153.176.78]) by owl.lab.dtag.de (Postfix) with ESMTPSA id 09E2F59736E; Mon, 18 Nov 2013 18:04:09 +0100 (CET)
Message-ID: <528A4889.8020208@lab.dtag.de>
Date: Mon, 18 Nov 2013 18:04:09 +0100
From: Martin Horneffer <maho@lab.dtag.de>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: "Alvaro Retana (aretana)" <aretana@cisco.com>,  "draft-filsfils-rtgwg-segment-routing-use-cases@tools.ietf.org" <draft-filsfils-rtgwg-segment-routing-use-cases@tools.ietf.org>
References: <CEAFA174.41B29%aretana@cisco.com>
In-Reply-To: <CEAFA174.41B29%aretana@cisco.com>
Content-Type: multipart/alternative; boundary="------------030102070302030906060102"
X-Mailman-Approved-At: Mon, 18 Nov 2013 13:49:18 -0800
Cc: "spring@ietf.org" <spring@ietf.org>
Subject: Re: [spring] IRP Claims related to draft-filsfils-rtgwg-segment-routing-use-cases
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Stacked Tunnels for Source Routing \(STATUS\)." <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Nov 2013 17:04:23 -0000

This is a multi-part message in MIME format.
--------------030102070302030906060102
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

I'm not aware of any IPR.

Best regards, Martin

Am 18.11.13 16:50, schrieb Alvaro Retana (aretana):
> Hi!
>
> In parallel to the call for adoption of this draft, I want to formally 
> ask the authors (no additional contributors are listed in the latest 
> version of the draft) to please respond to this message indicating 
> whether or not you are aware of any relevant IPR.  The draft will not 
> progress (pending the results of the WG Adoption Call) until we have 
> received a response from each author.
>
> Thanks!
>
> Alvaro.
>
>
>
> _______________________________________________
> spring mailing list
> spring@ietf.org
> https://www.ietf.org/mailman/listinfo/spring


##############################################
# Mail Account for technical purposes only
##############################################
--------------030102070302030906060102
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">I'm not aware of any IPR.<br>
      <br>
      Best regards, Martin<br>
      <br>
      Am 18.11.13 16:50, schrieb Alvaro Retana (aretana):<br>
    </div>
    <blockquote cite="mid:CEAFA174.41B29%25aretana@cisco.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <div>Hi!</div>
      <div><br>
      </div>
      <div>In parallel to the call for adoption of this draft,&nbsp;I want to
        formally ask the authors (no additional contributors are listed
        in the latest version of the draft) to please respond to this
        message indicating whether or not you are aware of any relevant
        IPR. &nbsp;The draft will not progress (pending the results of the WG
        Adoption Call) until we have received a response from each
        author.</div>
      <div><br>
      </div>
      <div>Thanks!</div>
      <div><br>
      </div>
      <div>Alvaro.</div>
      <br>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
spring mailing list
<a class="moz-txt-link-abbreviated" href="mailto:spring@ietf.org">spring@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/spring">https://www.ietf.org/mailman/listinfo/spring</a>
</pre>
    </blockquote>
    <br>
  
<br><pre>
##############################################
# Mail Account for technical purposes only
##############################################
</pre><br>
</body>
</html>

--------------030102070302030906060102--

From cfilsfil@cisco.com  Mon Nov 18 23:45:48 2013
Return-Path: <cfilsfil@cisco.com>
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 C845A1AC7F1 for <spring@ietfa.amsl.com>; Mon, 18 Nov 2013 23:45:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.026
X-Spam-Level: 
X-Spam-Status: No, score=-10.026 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.525, 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 AkKJDXKzdH9w for <spring@ietfa.amsl.com>; Mon, 18 Nov 2013 23:45:47 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) by ietfa.amsl.com (Postfix) with ESMTP id 5F6451AC829 for <spring@ietf.org>; Mon, 18 Nov 2013 23:45:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=625; q=dns/txt; s=iport; t=1384847142; x=1386056742; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=Ktnu0qnmsf5ZDa7j97bRjMEjNV5WzdkLRu8u+ge+/WA=; b=lsTC6F7WFOiKy9dGdT2IOA2zMINr0Qo7SvbLEt5dsPkjSz7PnoUzkEEm FqMvIs8BKWIxIOjpYx9r3FYvvSNzbfMUvcxNgVXmTkmRvFMLCAMU6nnTz QpHU+upBGNY5e+pwR+inlorzQJp3PWAX00Y9K7zHXFKVgxeY93zEnuvi5 A=;
X-IronPort-AV: E=Sophos;i="4.93,727,1378857600";  d="scan'208";a="132509"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by aer-iport-2.cisco.com with ESMTP; 19 Nov 2013 07:45:41 +0000
Received: from [10.61.161.75] ([10.61.161.75]) by ams-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id rAJ7jVac005191; Tue, 19 Nov 2013 07:45:34 GMT
Message-ID: <528B171A.9020804@cisco.com>
Date: Tue, 19 Nov 2013 02:45:30 -0500
From: Clarence Filsfils <cfilsfil@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: "Alvaro Retana (aretana)" <aretana@cisco.com>
References: <CEAFA174.41B29%aretana@cisco.com>
In-Reply-To: <CEAFA174.41B29%aretana@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "spring@ietf.org" <spring@ietf.org>, "draft-filsfils-rtgwg-segment-routing-use-cases@tools.ietf.org" <draft-filsfils-rtgwg-segment-routing-use-cases@tools.ietf.org>
Subject: Re: [spring] IRP Claims related to draft-filsfils-rtgwg-segment-routing-use-cases
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Stacked Tunnels for Source Routing \(STATUS\)." <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Nov 2013 07:45:49 -0000

There is IPR that is in the process of being disclosed.

Cheers,
Clarence


On 18.11.13 10:50, Alvaro Retana (aretana) wrote:
> Hi!
>
> In parallel to the call for adoption of this draft, I want to formally
> ask the authors (no additional contributors are listed in the latest
> version of the draft) to please respond to this message indicating
> whether or not you are aware of any relevant IPR.  The draft will not
> progress (pending the results of the WG Adoption Call) until we have
> received a response from each author.
>
> Thanks!
>
> Alvaro.
>

-- 
Please excuse brief mail, broken wrist

From jdrake@juniper.net  Tue Nov 19 04:56:24 2013
Return-Path: <jdrake@juniper.net>
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 001351ADF80 for <spring@ietfa.amsl.com>; Tue, 19 Nov 2013 04:56:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 jkiLG_NmBiQq for <spring@ietfa.amsl.com>; Tue, 19 Nov 2013 04:56:21 -0800 (PST)
Received: from ch1outboundpool.messaging.microsoft.com (ch1ehsobe003.messaging.microsoft.com [216.32.181.183]) by ietfa.amsl.com (Postfix) with ESMTP id 4B63B1ADF7A for <spring@ietf.org>; Tue, 19 Nov 2013 04:56:21 -0800 (PST)
Received: from mail78-ch1-R.bigfish.com (10.43.68.237) by CH1EHSOBE022.bigfish.com (10.43.70.79) with Microsoft SMTP Server id 14.1.225.22; Tue, 19 Nov 2013 12:56:15 +0000
Received: from mail78-ch1 (localhost [127.0.0.1])	by mail78-ch1-R.bigfish.com (Postfix) with ESMTP id 0A4C71E0AA5	for <spring@ietf.org>; Tue, 19 Nov 2013 12:56:15 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT002.namprd05.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -27
X-BigFish: VPS-27(z579ehz98dI9371I542I1432I72dMzz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h1d1ah1d2ah1fc6hzc2hz8275ch1de098h1033IL17326ah8275bh8275dh1de097h186068hz2fh109h2a8h839h944hd24hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah224fh1d07h1d0ch1d2eh1d3fh1de9h1dfeh1dffh1fe8h1ff5h2216h9a9j1155h)
Received-SPF: pass (mail78-ch1: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=jdrake@juniper.net; helo=BL2PRD0510HT002.namprd05.prod.outlook.com ; .outlook.com ; 
X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(377454003)(13464003)(24454002)(18374002)(189002)(199002)(51704005)(80022001)(46102001)(31966008)(2656002)(83322001)(19580405001)(74662001)(56776001)(66066001)(65816001)(50986001)(47976001)(54316002)(74502001)(47446002)(87936001)(19580395003)(224303002)(81342001)(87266001)(80976001)(4396001)(49866001)(74316001)(47736001)(81816001)(74366001)(81686001)(1941001)(81542001)(79102001)(76576001)(77982001)(51856001)(56816003)(54356001)(76796001)(74876001)(76786001)(74706001)(15975445006)(15202345003)(53806001)(83072001)(224313003)(76482001)(63696002)(69226001)(59766001)(33646001)(85306002)(24736002); DIR:OUT; SFP:; SCL:1; SRVR:BLUPR05MB436; H:BLUPR05MB562.namprd05.prod.outlook.com; CLIP:66.129.241.16; FPR:; RD:InfoNoRecords; MX:1; A:1; LANG:en; 
Received: from mail78-ch1 (localhost.localdomain [127.0.0.1]) by mail78-ch1 (MessageSwitch) id 1384865773747138_1290; Tue, 19 Nov 2013 12:56:13 +0000 (UTC)
Received: from CH1EHSMHS041.bigfish.com (snatpool1.int.messaging.microsoft.com [10.43.68.245])	by mail78-ch1.bigfish.com (Postfix) with ESMTP id A1041160179 for <spring@ietf.org>; Tue, 19 Nov 2013 12:56:13 +0000 (UTC)
Received: from BL2PRD0510HT002.namprd05.prod.outlook.com (157.56.240.101) by CH1EHSMHS041.bigfish.com (10.43.69.250) with Microsoft SMTP Server (TLS) id 14.16.227.3; Tue, 19 Nov 2013 12:56:12 +0000
Received: from BLUPR05MB436.namprd05.prod.outlook.com (10.141.27.152) by BL2PRD0510HT002.namprd05.prod.outlook.com (10.255.100.37) with Microsoft SMTP Server (TLS) id 14.16.383.1; Tue, 19 Nov 2013 12:56:12 +0000
Received: from BLUPR05MB562.namprd05.prod.outlook.com (10.141.202.141) by BLUPR05MB436.namprd05.prod.outlook.com (10.141.27.152) with Microsoft SMTP Server (TLS) id 15.0.820.5; Tue, 19 Nov 2013 12:56:10 +0000
Received: from BLUPR05MB562.namprd05.prod.outlook.com ([10.141.202.141]) by BLUPR05MB562.namprd05.prod.outlook.com ([10.141.202.141]) with mapi id 15.00.0820.005; Tue, 19 Nov 2013 12:56:10 +0000
From: John E Drake <jdrake@juniper.net>
To: Hannes Gredler <hannes@juniper.net>, "spring@ietf.org" <spring@ietf.org>
Thread-Topic: [spring] request to move draft-filsfils-rtgwg-segment-routing-use-cases-02 to wg item
Thread-Index: AQHO5EAg8rSgHEsSZ0W7Ffpw9bM26posgisg
Date: Tue, 19 Nov 2013 12:56:09 +0000
Message-ID: <cd284b4d3d8e43c8a46dcb963fb7a1af@BLUPR05MB562.namprd05.prod.outlook.com>
References: <C30B286F-3453-4027-AB24-03ACEAA8F10C@juniper.net> <FF585B07-B4D6-4EDC-A813-B340D47D64CB@juniper.net>
In-Reply-To: <FF585B07-B4D6-4EDC-A813-B340D47D64CB@juniper.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.241.16]
x-forefront-prvs: 0035B15214
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Subject: Re: [spring] request to move	draft-filsfils-rtgwg-segment-routing-use-cases-02 to wg item
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Stacked Tunnels for Source Routing \(STATUS\)." <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Nov 2013 12:56:24 -0000

Hi,

The draft is a very good start but it needs to be more focused.  What is th=
e plan for incorporating material from the following drafts into it:

http://tools.ietf.org/html/draft-geib-spring-oam-usecase-00

http://tools.ietf.org/html/draft-gredler-ospf-label-advertisement-03

http://tools.ietf.org/html/draft-kim-source-routing-use-cases-00

http://tools.ietf.org/html/draft-shakir-rtgwg-sr-performance-engineered-lsp=
s-00

I would also suggest a global replace of the term 'segment routing' with th=
e term 'explicit routing' which seemed to have support on the mailing list.

Yours Irrespectively,

John

> -----Original Message-----
> From: spring-bounces@ietf.org [mailto:spring-bounces@ietf.org] On Behalf =
Of
> Hannes Gredler
> Sent: Monday, November 18, 2013 1:24 AM
> To: spring@ietf.org
> Subject: [spring] request to move draft-filsfils-rtgwg-segment-routing-us=
e-
> cases-02 to wg item
>=20
> Begin forwarded message:
>=20
> > From: Hannes Gredler <hannes@juniper.net>
> > Subject: Re: [Status] request to move
> > draft-filsfils-rtgwg-segment-routing-use-cases-02 to wg item
> > Date: November 18, 2013 10:13:20 AM GMT+01:00
> > To: status@ietf.org
> > Cc: John Scudder <jgs@juniper.net>, "Alvaro Retana (aretana)"
> > <aretana@cisco.com>, "Clarence Filsfils (cfilsfil)"
> > <cfilsfil@cisco.com>, "Stefano Previdi (sprevidi)"
> > <sprevidi@cisco.com>
> >
> > support - (with a few caveats) - particularly where a 'solution'
> > rather than a 'use case' is being described:
> >
> > ---
> >
> > -cut section 2 as it describes a solution and not necessarily belongs
> > into a 'use-case' draft.
> >
> > -section 3.1: use-case drafts should not contain forward references to
> > the 'solution' drafts - please cut the last paragraph.
> > a note that the required protocol extension SHOULD support
> > advertisement of backup paths would be ok.
> >
> > -section 4.1: TE without Bandwidth Admission Control is called
> > 'Explicit Routing' - the current expression is a bit awkward;
> >  - Its like ordering a Pizza without cheese - this is not a Pizza any
> >    longer, right ?
> >
> > -section 4.1.1 'Anycast node segment' - this again is a solution and
> > not the problem ...
> >
> > -section 4.1.1.1 we rather should make over this section to discuss
> > the requirements of disjointness, what implications this has to
> > real-world topologies rather than describing a 'Anycast SID based solut=
ion'.
> > i can imagine that there are customers who want to use a central
> > controller without the notion of any cast SIDs at all ...
> >
> > -section 4.1.2 add a reference to the OSPF and BGP/LS extended TE metri=
cs.
> >
> > -section 4.1.3 i'd like to add a section which describes inter-domain
> > TE by using label stacking, which seems a more general case rather
> > than just using one label for egress link-selection.
> >
> > -section 5: i am not sure wether service-chaining is
> >   (1) in-charter and to what extend the
> >   (2) overlap with SFC working group is. -
> >   suggest to cut this one.
> >
> > ---
> >
> >
> > not sure if you need another co-author (as the list is fairly
> > impressive), but i can contribute cycles/text for the editing work if y=
ou want.
> >
> > thanks,
> >
> > /hannes
> >
> >
> > On Nov 7, 2013, at 5:24 AM, Stefano Previdi (sprevidi) wrote:
> >
> >> John, Alvaro, All,
> >>
> >> according to what discussed after the presentation of SR Use Cases at
> >> ietf88 spring-wg meeting, I'd like to request the adoption of
> >> draft-filsfils-rtgwg-segment-routing-use-cases-02.txt as wg item.
> >>
> >> Thanks.
> >> s.
> >
>=20
>=20
> _______________________________________________
> spring mailing list
> spring@ietf.org
> https://www.ietf.org/mailman/listinfo/spring
>=20



From rraszuk@gmail.com  Tue Nov 19 06:43:08 2013
Return-Path: <rraszuk@gmail.com>
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 B646B1ADFF0 for <spring@ietfa.amsl.com>; Tue, 19 Nov 2013 06:43:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level: 
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no
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 A4i58quyn00f for <spring@ietfa.amsl.com>; Tue, 19 Nov 2013 06:43:06 -0800 (PST)
Received: from mail-ie0-x234.google.com (mail-ie0-x234.google.com [IPv6:2607:f8b0:4001:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id A45951ADFED for <spring@ietf.org>; Tue, 19 Nov 2013 06:43:06 -0800 (PST)
Received: by mail-ie0-f180.google.com with SMTP id tp5so3994565ieb.11 for <spring@ietf.org>; Tue, 19 Nov 2013 06:43:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=YPAW6njF0rCxIBLcyupMMNQWpHxW85b2+tsIYEhJfRQ=; b=h8FjzkU0IgEw9WfI3Nfosx4Ny4nN1pFqv6PVKQhe/AWzK8kYuB46yDZbXOjNCZD+bJ ojOOQGBoxfJ/uj/GIGasYf/ZnE3Lg+7G/Dybr6DKqlwludtqofwgyrLsFQTPMJswdI64 jeFARwgvDFhxDDQDY8djY7zdiD0Ale3JG4T7O/MS7pVXIcD6nWhhN/JWDiiJz/yXX9CU YVBre5uj3kSSWtoeDt+0Wf7o6sz7Yp3oPGfr1+xM3wfdYqMPylarrpAs7HvQiIyMg7Hg SiKcjhzCNYBEb85k+QpGJ6LIDEsM45xGXmBm07b38StfygZ/xkHirtxY+4ztey7xH6g7 v+WA==
MIME-Version: 1.0
X-Received: by 10.50.164.130 with SMTP id yq2mr18832191igb.53.1384872180540; Tue, 19 Nov 2013 06:43:00 -0800 (PST)
Sender: rraszuk@gmail.com
Received: by 10.64.61.129 with HTTP; Tue, 19 Nov 2013 06:43:00 -0800 (PST)
In-Reply-To: <cd284b4d3d8e43c8a46dcb963fb7a1af@BLUPR05MB562.namprd05.prod.outlook.com>
References: <C30B286F-3453-4027-AB24-03ACEAA8F10C@juniper.net> <FF585B07-B4D6-4EDC-A813-B340D47D64CB@juniper.net> <cd284b4d3d8e43c8a46dcb963fb7a1af@BLUPR05MB562.namprd05.prod.outlook.com>
Date: Tue, 19 Nov 2013 15:43:00 +0100
X-Google-Sender-Auth: C7AsXf_Abqi-ZU4XgLxzPIj5N-c
Message-ID: <CA+b+ERnAPz7GQ2Hvhoh8mrRH=rNO7M81QLKvmHZ6FqvoRW_Sdg@mail.gmail.com>
From: Robert Raszuk <robert@raszuk.net>
To: John E Drake <jdrake@juniper.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Hannes Gredler <hannes@juniper.net>, "spring@ietf.org" <spring@ietf.org>
Subject: Re: [spring] request to move draft-filsfils-rtgwg-segment-routing-use-cases-02 to wg item
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Stacked Tunnels for Source Routing \(STATUS\)." <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Nov 2013 14:43:08 -0000

Hello John,

I think that incorporating the material from below drafts is exactly
opposite to keeping the draft "more focused". So which one do you
suggest ?

Best,
R.

On Tue, Nov 19, 2013 at 1:56 PM, John E Drake <jdrake@juniper.net> wrote:
> Hi,
>
> The draft is a very good start but it needs to be more focused.  What is the plan for incorporating material from the following drafts into it:
>
> http://tools.ietf.org/html/draft-geib-spring-oam-usecase-00
>
> http://tools.ietf.org/html/draft-gredler-ospf-label-advertisement-03
>
> http://tools.ietf.org/html/draft-kim-source-routing-use-cases-00
>
> http://tools.ietf.org/html/draft-shakir-rtgwg-sr-performance-engineered-lsps-00
>
> I would also suggest a global replace of the term 'segment routing' with the term 'explicit routing' which seemed to have support on the mailing list.
>
> Yours Irrespectively,
>
> John
>
>> -----Original Message-----
>> From: spring-bounces@ietf.org [mailto:spring-bounces@ietf.org] On Behalf Of
>> Hannes Gredler
>> Sent: Monday, November 18, 2013 1:24 AM
>> To: spring@ietf.org
>> Subject: [spring] request to move draft-filsfils-rtgwg-segment-routing-use-
>> cases-02 to wg item
>>
>> Begin forwarded message:
>>
>> > From: Hannes Gredler <hannes@juniper.net>
>> > Subject: Re: [Status] request to move
>> > draft-filsfils-rtgwg-segment-routing-use-cases-02 to wg item
>> > Date: November 18, 2013 10:13:20 AM GMT+01:00
>> > To: status@ietf.org
>> > Cc: John Scudder <jgs@juniper.net>, "Alvaro Retana (aretana)"
>> > <aretana@cisco.com>, "Clarence Filsfils (cfilsfil)"
>> > <cfilsfil@cisco.com>, "Stefano Previdi (sprevidi)"
>> > <sprevidi@cisco.com>
>> >
>> > support - (with a few caveats) - particularly where a 'solution'
>> > rather than a 'use case' is being described:
>> >
>> > ---
>> >
>> > -cut section 2 as it describes a solution and not necessarily belongs
>> > into a 'use-case' draft.
>> >
>> > -section 3.1: use-case drafts should not contain forward references to
>> > the 'solution' drafts - please cut the last paragraph.
>> > a note that the required protocol extension SHOULD support
>> > advertisement of backup paths would be ok.
>> >
>> > -section 4.1: TE without Bandwidth Admission Control is called
>> > 'Explicit Routing' - the current expression is a bit awkward;
>> >  - Its like ordering a Pizza without cheese - this is not a Pizza any
>> >    longer, right ?
>> >
>> > -section 4.1.1 'Anycast node segment' - this again is a solution and
>> > not the problem ...
>> >
>> > -section 4.1.1.1 we rather should make over this section to discuss
>> > the requirements of disjointness, what implications this has to
>> > real-world topologies rather than describing a 'Anycast SID based solution'.
>> > i can imagine that there are customers who want to use a central
>> > controller without the notion of any cast SIDs at all ...
>> >
>> > -section 4.1.2 add a reference to the OSPF and BGP/LS extended TE metrics.
>> >
>> > -section 4.1.3 i'd like to add a section which describes inter-domain
>> > TE by using label stacking, which seems a more general case rather
>> > than just using one label for egress link-selection.
>> >
>> > -section 5: i am not sure wether service-chaining is
>> >   (1) in-charter and to what extend the
>> >   (2) overlap with SFC working group is. -
>> >   suggest to cut this one.
>> >
>> > ---
>> >
>> >
>> > not sure if you need another co-author (as the list is fairly
>> > impressive), but i can contribute cycles/text for the editing work if you want.
>> >
>> > thanks,
>> >
>> > /hannes
>> >
>> >
>> > On Nov 7, 2013, at 5:24 AM, Stefano Previdi (sprevidi) wrote:
>> >
>> >> John, Alvaro, All,
>> >>
>> >> according to what discussed after the presentation of SR Use Cases at
>> >> ietf88 spring-wg meeting, I'd like to request the adoption of
>> >> draft-filsfils-rtgwg-segment-routing-use-cases-02.txt as wg item.
>> >>
>> >> Thanks.
>> >> s.
>> >
>>
>>
>> _______________________________________________
>> spring mailing list
>> spring@ietf.org
>> https://www.ietf.org/mailman/listinfo/spring
>>
>
>
> _______________________________________________
> spring mailing list
> spring@ietf.org
> https://www.ietf.org/mailman/listinfo/spring

From rbonica@juniper.net  Tue Nov 19 06:57:31 2013
Return-Path: <rbonica@juniper.net>
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 17BAD1ADFF9 for <spring@ietfa.amsl.com>; Tue, 19 Nov 2013 06:57:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.601
X-Spam-Level: 
X-Spam-Status: No, score=-102.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 TNY-hBPbuo7Q for <spring@ietfa.amsl.com>; Tue, 19 Nov 2013 06:57:29 -0800 (PST)
Received: from am1outboundpool.messaging.microsoft.com (am1ehsobe006.messaging.microsoft.com [213.199.154.209]) by ietfa.amsl.com (Postfix) with ESMTP id EAA2F1ADFE7 for <spring@ietf.org>; Tue, 19 Nov 2013 06:57:28 -0800 (PST)
Received: from mail1-am1-R.bigfish.com (10.3.201.246) by AM1EHSOBE026.bigfish.com (10.3.207.148) with Microsoft SMTP Server id 14.1.225.22; Tue, 19 Nov 2013 14:57:22 +0000
Received: from mail1-am1 (localhost [127.0.0.1])	by mail1-am1-R.bigfish.com (Postfix) with ESMTP id 737413C02E9;	Tue, 19 Nov 2013 14:57:22 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT005.namprd05.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -25
X-BigFish: VPS-25(z579ehz98dI9371I103dK542I1432Izz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h1d1ah1d2ah1fc6hzz1de098h1033IL8275dh1de097h186068hz2fh109h2a8h839h944hd24hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah224fh1d07h1d0ch1d2eh1d3fh1de9h1dfeh1dffh1e1dh1fe8h1ff5h2216h9a9j1155h)
Received-SPF: pass (mail1-am1: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=rbonica@juniper.net; helo=BL2PRD0510HT005.namprd05.prod.outlook.com ; .outlook.com ; 
X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(51704005)(24454002)(41574002)(199002)(189002)(13464003)(377454003)(69226001)(74706001)(19580405001)(83322001)(81686001)(81816001)(76482001)(81542001)(81342001)(87266001)(59766001)(76576001)(77096001)(87936001)(2656002)(77982001)(76786001)(76796001)(224313003)(15975445006)(56816003)(51856001)(80022001)(74316001)(65816001)(74662001)(4396001)(66066001)(46102001)(54356001)(53806001)(74502001)(74876001)(80976001)(47976001)(74366001)(50986001)(19580395003)(85306002)(79102001)(49866001)(54316002)(224303002)(63696002)(47736001)(83072001)(31966008)(33646001)(56776001)(47446002)(24736002); DIR:OUT; SFP:; SCL:1; SRVR:CO1PR05MB444; H:CO1PR05MB442.namprd05.prod.outlook.com; CLIP:66.129.241.15; FPR:; RD:InfoNoRecords; A:1; MX:1; LANG:en; 
Received: from mail1-am1 (localhost.localdomain [127.0.0.1]) by mail1-am1 (MessageSwitch) id 1384873040446919_27976; Tue, 19 Nov 2013 14:57:20 +0000 (UTC)
Received: from AM1EHSMHS006.bigfish.com (unknown [10.3.201.253])	by mail1-am1.bigfish.com (Postfix) with ESMTP id 5EC34A005A;	Tue, 19 Nov 2013 14:57:20 +0000 (UTC)
Received: from BL2PRD0510HT005.namprd05.prod.outlook.com (157.56.240.101) by AM1EHSMHS006.bigfish.com (10.3.207.106) with Microsoft SMTP Server (TLS) id 14.16.227.3; Tue, 19 Nov 2013 14:57:19 +0000
Received: from CO1PR05MB444.namprd05.prod.outlook.com (10.141.73.140) by BL2PRD0510HT005.namprd05.prod.outlook.com (10.255.100.40) with Microsoft SMTP Server (TLS) id 14.16.383.1; Tue, 19 Nov 2013 14:57:18 +0000
Received: from CO1PR05MB442.namprd05.prod.outlook.com (10.141.73.146) by CO1PR05MB444.namprd05.prod.outlook.com (10.141.73.140) with Microsoft SMTP Server (TLS) id 15.0.785.10; Tue, 19 Nov 2013 14:57:15 +0000
Received: from CO1PR05MB442.namprd05.prod.outlook.com ([169.254.13.67]) by CO1PR05MB442.namprd05.prod.outlook.com ([169.254.13.146]) with mapi id 15.00.0785.001; Tue, 19 Nov 2013 14:57:14 +0000
From: Ronald Bonica <rbonica@juniper.net>
To: Clarence Filsfils <cfilsfil@cisco.com>, "Alvaro Retana (aretana)" <aretana@cisco.com>
Thread-Topic: [spring] IRP Claims related to draft-filsfils-rtgwg-segment-routing-use-cases
Thread-Index: AQHO5HXoHhlKZZ4m5EGmUvN6dvJ6WposLbcAgAB283A=
Date: Tue, 19 Nov 2013 14:57:14 +0000
Message-ID: <57d00406c35d47fba874c65b7af9c4ec@CO1PR05MB442.namprd05.prod.outlook.com>
References: <CEAFA174.41B29%aretana@cisco.com> <528B171A.9020804@cisco.com>
In-Reply-To: <528B171A.9020804@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.241.15]
x-forefront-prvs: 0035B15214
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Cc: "spring@ietf.org" <spring@ietf.org>, "draft-filsfils-rtgwg-segment-routing-use-cases@tools.ietf.org" <draft-filsfils-rtgwg-segment-routing-use-cases@tools.ietf.org>
Subject: Re: [spring] IRP Claims related to	draft-filsfils-rtgwg-segment-routing-use-cases
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Stacked Tunnels for Source Routing \(STATUS\)." <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Nov 2013 14:57:31 -0000

Folks,

It is strange for IPR to be associated with a use-case document. Could it b=
e that the use-case document assumes solutions and that the IPR is associat=
ed with the assumed solutions?

If that is the case, we should probably remove the assumed solutions from t=
he document. (This is appropriate because it is a use-case document.) Then =
the authors could re-evaluate the document to determine whether it is still=
 IPR encumbered.

                                                   Ron


> -----Original Message-----
> From: spring [mailto:spring-bounces@ietf.org] On Behalf Of Clarence
> Filsfils
> Sent: Tuesday, November 19, 2013 2:46 AM
> To: Alvaro Retana (aretana)
> Cc: spring@ietf.org; draft-filsfils-rtgwg-segment-routing-use-
> cases@tools.ietf.org
> Subject: Re: [spring] IRP Claims related to draft-filsfils-rtgwg-
> segment-routing-use-cases
>=20
>=20
> There is IPR that is in the process of being disclosed.
>=20
> Cheers,
> Clarence
>=20
>=20
> On 18.11.13 10:50, Alvaro Retana (aretana) wrote:
> > Hi!
> >
> > In parallel to the call for adoption of this draft, I want to
> formally
> > ask the authors (no additional contributors are listed in the latest
> > version of the draft) to please respond to this message indicating
> > whether or not you are aware of any relevant IPR.  The draft will not
> > progress (pending the results of the WG Adoption Call) until we have
> > received a response from each author.
> >
> > Thanks!
> >
> > Alvaro.
> >
>=20
> --
> Please excuse brief mail, broken wrist
> _______________________________________________
> spring mailing list
> spring@ietf.org
> https://www.ietf.org/mailman/listinfo/spring
>=20



From jdrake@juniper.net  Tue Nov 19 07:01:26 2013
Return-Path: <jdrake@juniper.net>
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 1B25E1AE001 for <spring@ietfa.amsl.com>; Tue, 19 Nov 2013 07:01:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 6zIDJAeXlGkI for <spring@ietfa.amsl.com>; Tue, 19 Nov 2013 07:01:23 -0800 (PST)
Received: from am1outboundpool.messaging.microsoft.com (am1ehsobe002.messaging.microsoft.com [213.199.154.205]) by ietfa.amsl.com (Postfix) with ESMTP id 4DB531ADFE7 for <spring@ietf.org>; Tue, 19 Nov 2013 07:01:23 -0800 (PST)
Received: from mail64-am1-R.bigfish.com (10.3.201.229) by AM1EHSOBE001.bigfish.com (10.3.204.21) with Microsoft SMTP Server id 14.1.225.22; Tue, 19 Nov 2013 15:01:16 +0000
Received: from mail64-am1 (localhost [127.0.0.1])	by mail64-am1-R.bigfish.com (Postfix) with ESMTP id B487B380383; Tue, 19 Nov 2013 15:01:16 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT001.namprd05.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -28
X-BigFish: VPS-28(z579ehz98dI9371I542I1432I1418I72dMzz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h1d1ah1d2ah1fc6hzz8275ch1de098h1033IL17326ah8275bh8275dh1de097h186068hz2fh109h2a8h839h944hd24hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah224fh1d07h1d0ch1d2eh1d3fh1de9h1dfeh1dffh1fe8h1ff5h2216h9a9j1155h)
Received-SPF: pass (mail64-am1: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=jdrake@juniper.net; helo=BL2PRD0510HT001.namprd05.prod.outlook.com ; .outlook.com ; 
X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(24454002)(18374002)(199002)(189002)(51704005)(377454003)(13464003)(51444003)(54356001)(76796001)(76786001)(74876001)(74706001)(77982001)(79102001)(76576001)(56816003)(51856001)(63696002)(69226001)(59766001)(85306002)(33646001)(53806001)(15202345003)(15975445006)(76482001)(83072001)(74502001)(47446002)(65816001)(50986001)(47976001)(54316002)(81342001)(19580395003)(87936001)(2656002)(31966008)(83322001)(19580405001)(80022001)(46102001)(74662001)(66066001)(56776001)(81542001)(81686001)(80976001)(4396001)(87266001)(74366001)(81816001)(74316001)(47736001)(49866001)(24736002); DIR:OUT; SFP:; SCL:1; SRVR:BLUPR05MB436; H:BLUPR05MB562.namprd05.prod.outlook.com; CLIP:66.129.241.16; FPR:; RD:InfoNoRecords; A:1; MX:1; LANG:en; 
Received: from mail64-am1 (localhost.localdomain [127.0.0.1]) by mail64-am1 (MessageSwitch) id 1384873274885670_5738; Tue, 19 Nov 2013 15:01:14 +0000 (UTC)
Received: from AM1EHSMHS004.bigfish.com (unknown [10.3.201.246])	by mail64-am1.bigfish.com (Postfix) with ESMTP id D503D1603F0;	Tue, 19 Nov 2013 15:01:14 +0000 (UTC)
Received: from BL2PRD0510HT001.namprd05.prod.outlook.com (157.56.240.101) by AM1EHSMHS004.bigfish.com (10.3.207.104) with Microsoft SMTP Server (TLS) id 14.16.227.3; Tue, 19 Nov 2013 15:01:13 +0000
Received: from BLUPR05MB436.namprd05.prod.outlook.com (10.141.27.152) by BL2PRD0510HT001.namprd05.prod.outlook.com (10.255.100.36) with Microsoft SMTP Server (TLS) id 14.16.383.1; Tue, 19 Nov 2013 15:01:10 +0000
Received: from BLUPR05MB562.namprd05.prod.outlook.com (10.141.202.141) by BLUPR05MB436.namprd05.prod.outlook.com (10.141.27.152) with Microsoft SMTP Server (TLS) id 15.0.820.5; Tue, 19 Nov 2013 15:01:08 +0000
Received: from BLUPR05MB562.namprd05.prod.outlook.com ([10.141.202.141]) by BLUPR05MB562.namprd05.prod.outlook.com ([10.141.202.141]) with mapi id 15.00.0820.005; Tue, 19 Nov 2013 15:01:08 +0000
From: John E Drake <jdrake@juniper.net>
To: Robert Raszuk <robert@raszuk.net>
Thread-Topic: [spring] request to move draft-filsfils-rtgwg-segment-routing-use-cases-02 to wg item
Thread-Index: AQHO5TWutgb3+PtTgEqOQorcQfpvSJosoYvg
Date: Tue, 19 Nov 2013 15:01:07 +0000
Message-ID: <d30b2cd0568f4e86b6f8c838214e7614@BLUPR05MB562.namprd05.prod.outlook.com>
References: <C30B286F-3453-4027-AB24-03ACEAA8F10C@juniper.net> <FF585B07-B4D6-4EDC-A813-B340D47D64CB@juniper.net> <cd284b4d3d8e43c8a46dcb963fb7a1af@BLUPR05MB562.namprd05.prod.outlook.com> <CA+b+ERnAPz7GQ2Hvhoh8mrRH=rNO7M81QLKvmHZ6FqvoRW_Sdg@mail.gmail.com>
In-Reply-To: <CA+b+ERnAPz7GQ2Hvhoh8mrRH=rNO7M81QLKvmHZ6FqvoRW_Sdg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.241.16]
x-forefront-prvs: 0035B15214
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Cc: Hannes Gredler <hannes@juniper.net>, "spring@ietf.org" <spring@ietf.org>
Subject: Re: [spring] request to move draft-filsfils-rtgwg-segment-routing-use-cases-02 to wg item
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Stacked Tunnels for Source Routing \(STATUS\)." <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Nov 2013 15:01:26 -0000

Robert,

I'm sorry, I think the draft needs to be more focused on use cases and I ag=
ree with you that the set of use cases need to be comprehensive.  (As an as=
ide, why do people use double quotation marks so randomly?  http://www.amaz=
on.com/exec/obidos/ASIN/0811876454/uncrate-20)   =20

Yours Irrespectively,

John

> -----Original Message-----
> From: spring [mailto:spring-bounces@ietf.org] On Behalf Of Robert Raszuk
> Sent: Tuesday, November 19, 2013 6:43 AM
> To: John E Drake
> Cc: Hannes Gredler; spring@ietf.org
> Subject: Re: [spring] request to move draft-filsfils-rtgwg-segment-routin=
g-use-
> cases-02 to wg item
>=20
> Hello John,
>=20
> I think that incorporating the material from below drafts is exactly oppo=
site to
> keeping the draft "more focused". So which one do you suggest ?
>=20
> Best,
> R.
>=20
> On Tue, Nov 19, 2013 at 1:56 PM, John E Drake <jdrake@juniper.net> wrote:
> > Hi,
> >
> > The draft is a very good start but it needs to be more focused.  What i=
s the
> plan for incorporating material from the following drafts into it:
> >
> > http://tools.ietf.org/html/draft-geib-spring-oam-usecase-00
> >
> > http://tools.ietf.org/html/draft-gredler-ospf-label-advertisement-03
> >
> > http://tools.ietf.org/html/draft-kim-source-routing-use-cases-00
> >
> > http://tools.ietf.org/html/draft-shakir-rtgwg-sr-performance-engineere
> > d-lsps-00
> >
> > I would also suggest a global replace of the term 'segment routing' wit=
h the
> term 'explicit routing' which seemed to have support on the mailing list.
> >
> > Yours Irrespectively,
> >
> > John
> >
> >> -----Original Message-----
> >> From: spring-bounces@ietf.org [mailto:spring-bounces@ietf.org] On
> >> Behalf Of Hannes Gredler
> >> Sent: Monday, November 18, 2013 1:24 AM
> >> To: spring@ietf.org
> >> Subject: [spring] request to move
> >> draft-filsfils-rtgwg-segment-routing-use-
> >> cases-02 to wg item
> >>
> >> Begin forwarded message:
> >>
> >> > From: Hannes Gredler <hannes@juniper.net>
> >> > Subject: Re: [Status] request to move
> >> > draft-filsfils-rtgwg-segment-routing-use-cases-02 to wg item
> >> > Date: November 18, 2013 10:13:20 AM GMT+01:00
> >> > To: status@ietf.org
> >> > Cc: John Scudder <jgs@juniper.net>, "Alvaro Retana (aretana)"
> >> > <aretana@cisco.com>, "Clarence Filsfils (cfilsfil)"
> >> > <cfilsfil@cisco.com>, "Stefano Previdi (sprevidi)"
> >> > <sprevidi@cisco.com>
> >> >
> >> > support - (with a few caveats) - particularly where a 'solution'
> >> > rather than a 'use case' is being described:
> >> >
> >> > ---
> >> >
> >> > -cut section 2 as it describes a solution and not necessarily
> >> > belongs into a 'use-case' draft.
> >> >
> >> > -section 3.1: use-case drafts should not contain forward references
> >> > to the 'solution' drafts - please cut the last paragraph.
> >> > a note that the required protocol extension SHOULD support
> >> > advertisement of backup paths would be ok.
> >> >
> >> > -section 4.1: TE without Bandwidth Admission Control is called
> >> > 'Explicit Routing' - the current expression is a bit awkward;
> >> >  - Its like ordering a Pizza without cheese - this is not a Pizza an=
y
> >> >    longer, right ?
> >> >
> >> > -section 4.1.1 'Anycast node segment' - this again is a solution
> >> > and not the problem ...
> >> >
> >> > -section 4.1.1.1 we rather should make over this section to discuss
> >> > the requirements of disjointness, what implications this has to
> >> > real-world topologies rather than describing a 'Anycast SID based
> solution'.
> >> > i can imagine that there are customers who want to use a central
> >> > controller without the notion of any cast SIDs at all ...
> >> >
> >> > -section 4.1.2 add a reference to the OSPF and BGP/LS extended TE
> metrics.
> >> >
> >> > -section 4.1.3 i'd like to add a section which describes
> >> > inter-domain TE by using label stacking, which seems a more general
> >> > case rather than just using one label for egress link-selection.
> >> >
> >> > -section 5: i am not sure wether service-chaining is
> >> >   (1) in-charter and to what extend the
> >> >   (2) overlap with SFC working group is. -
> >> >   suggest to cut this one.
> >> >
> >> > ---
> >> >
> >> >
> >> > not sure if you need another co-author (as the list is fairly
> >> > impressive), but i can contribute cycles/text for the editing work i=
f you
> want.
> >> >
> >> > thanks,
> >> >
> >> > /hannes
> >> >
> >> >
> >> > On Nov 7, 2013, at 5:24 AM, Stefano Previdi (sprevidi) wrote:
> >> >
> >> >> John, Alvaro, All,
> >> >>
> >> >> according to what discussed after the presentation of SR Use Cases
> >> >> at
> >> >> ietf88 spring-wg meeting, I'd like to request the adoption of
> >> >> draft-filsfils-rtgwg-segment-routing-use-cases-02.txt as wg item.
> >> >>
> >> >> Thanks.
> >> >> s.
> >> >
> >>
> >>
> >> _______________________________________________
> >> spring mailing list
> >> spring@ietf.org
> >> https://www.ietf.org/mailman/listinfo/spring
> >>
> >
> >
> > _______________________________________________
> > spring mailing list
> > spring@ietf.org
> > https://www.ietf.org/mailman/listinfo/spring
> _______________________________________________
> spring mailing list
> spring@ietf.org
> https://www.ietf.org/mailman/listinfo/spring
>=20



From rraszuk@gmail.com  Tue Nov 19 07:07:46 2013
Return-Path: <rraszuk@gmail.com>
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 DD1191AE00C for <spring@ietfa.amsl.com>; Tue, 19 Nov 2013 07:07:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level: 
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no
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 l-zeOwBUMw8X for <spring@ietfa.amsl.com>; Tue, 19 Nov 2013 07:07:45 -0800 (PST)
Received: from mail-ie0-x22e.google.com (mail-ie0-x22e.google.com [IPv6:2607:f8b0:4001:c03::22e]) by ietfa.amsl.com (Postfix) with ESMTP id D3C931ADFA0 for <spring@ietf.org>; Tue, 19 Nov 2013 07:07:44 -0800 (PST)
Received: by mail-ie0-f174.google.com with SMTP id at1so5399033iec.5 for <spring@ietf.org>; Tue, 19 Nov 2013 07:07:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=z+HP2exjS2zHhuFP2mGWZGCFtv53XZ8bgETYd0GurP0=; b=mZDImLuezri1vosnk33eUPYdKQDTWBpII2n4uWPhbyYpVz+f11B8glrJSiu0bqJoNx h6UmfoTNHmANWytZ1QdwRaqaEvSa2wGYXzVmAFz80wf8+HFrE6obSlUEnpj+cCkzb/mQ JJFzGTQK2sxEfWpJoDLOA83ZGB8IOstu0Lz0QWzQBMCS7vYSkfA5gzT9pFrInCu3FKvy nI0KnspgW54ScB62fn2CglyIOf6Mg64B49152DcpB/ZlMKw4C91tT7qxwkg6L9whf41y ZUKgIZ7OLQ1/eBOUqXk357vZ8Dx/z9pSlM4V8bXvypP6UbW0pMb/dffs9gvn5uubzLhL xU+Q==
MIME-Version: 1.0
X-Received: by 10.43.136.136 with SMTP id ik8mr206992icc.75.1384873658853; Tue, 19 Nov 2013 07:07:38 -0800 (PST)
Sender: rraszuk@gmail.com
Received: by 10.64.61.129 with HTTP; Tue, 19 Nov 2013 07:07:38 -0800 (PST)
In-Reply-To: <d30b2cd0568f4e86b6f8c838214e7614@BLUPR05MB562.namprd05.prod.outlook.com>
References: <C30B286F-3453-4027-AB24-03ACEAA8F10C@juniper.net> <FF585B07-B4D6-4EDC-A813-B340D47D64CB@juniper.net> <cd284b4d3d8e43c8a46dcb963fb7a1af@BLUPR05MB562.namprd05.prod.outlook.com> <CA+b+ERnAPz7GQ2Hvhoh8mrRH=rNO7M81QLKvmHZ6FqvoRW_Sdg@mail.gmail.com> <d30b2cd0568f4e86b6f8c838214e7614@BLUPR05MB562.namprd05.prod.outlook.com>
Date: Tue, 19 Nov 2013 16:07:38 +0100
X-Google-Sender-Auth: 3VKVwj30LN7kv31UhiSxBnMPDfA
Message-ID: <CA+b+ER=58rHRT9Y4+ckymqgxwoh0_Wx3hqMpTLai2fL0oGFudQ@mail.gmail.com>
From: Robert Raszuk <robert@raszuk.net>
To: John E Drake <jdrake@juniper.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Hannes Gredler <hannes@juniper.net>, "spring@ietf.org" <spring@ietf.org>
Subject: Re: [spring] request to move draft-filsfils-rtgwg-segment-routing-use-cases-02 to wg item
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Stacked Tunnels for Source Routing \(STATUS\)." <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Nov 2013 15:07:47 -0000

Hi John,

> I'm sorry, I think the draft needs to be more focused on use cases and
> I agree with you that the set of use cases need to be comprehensive.

For me the current set of use cases constitutes an essence of what
needs to be stated in the draft in question. Adding or deleting new
ones may not bring value and may only dilute the document.

> (As an aside, why do people use double quotation marks so randomly?
> http://www.amazon.com/exec/obidos/ASIN/0811876454/uncrate-20)

There was nothing random in using double quotation in my reply .. I
was simply quoting your text expression verbatim. Hint:
http://en.wikipedia.org/wiki/Quote

Best,
R.


>> Sent: Tuesday, November 19, 2013 6:43 AM
>> To: John E Drake
>> Cc: Hannes Gredler; spring@ietf.org
>> Subject: Re: [spring] request to move draft-filsfils-rtgwg-segment-routing-use-
>> cases-02 to wg item
>>
>> Hello John,
>>
>> I think that incorporating the material from below drafts is exactly opposite to
>> keeping the draft "more focused". So which one do you suggest ?
>>
>> Best,
>> R.
>>
>> On Tue, Nov 19, 2013 at 1:56 PM, John E Drake <jdrake@juniper.net> wrote:
>> > Hi,
>> >
>> > The draft is a very good start but it needs to be more focused.  What is the
>> plan for incorporating material from the following drafts into it:
>> >
>> > http://tools.ietf.org/html/draft-geib-spring-oam-usecase-00
>> >
>> > http://tools.ietf.org/html/draft-gredler-ospf-label-advertisement-03
>> >
>> > http://tools.ietf.org/html/draft-kim-source-routing-use-cases-00
>> >
>> > http://tools.ietf.org/html/draft-shakir-rtgwg-sr-performance-engineere
>> > d-lsps-00
>> >
>> > I would also suggest a global replace of the term 'segment routing' with the
>> term 'explicit routing' which seemed to have support on the mailing list.
>> >
>> > Yours Irrespectively,
>> >
>> > John
>> >
>> >> -----Original Message-----
>> >> From: spring-bounces@ietf.org [mailto:spring-bounces@ietf.org] On
>> >> Behalf Of Hannes Gredler
>> >> Sent: Monday, November 18, 2013 1:24 AM
>> >> To: spring@ietf.org
>> >> Subject: [spring] request to move
>> >> draft-filsfils-rtgwg-segment-routing-use-
>> >> cases-02 to wg item
>> >>
>> >> Begin forwarded message:
>> >>
>> >> > From: Hannes Gredler <hannes@juniper.net>
>> >> > Subject: Re: [Status] request to move
>> >> > draft-filsfils-rtgwg-segment-routing-use-cases-02 to wg item
>> >> > Date: November 18, 2013 10:13:20 AM GMT+01:00
>> >> > To: status@ietf.org
>> >> > Cc: John Scudder <jgs@juniper.net>, "Alvaro Retana (aretana)"
>> >> > <aretana@cisco.com>, "Clarence Filsfils (cfilsfil)"
>> >> > <cfilsfil@cisco.com>, "Stefano Previdi (sprevidi)"
>> >> > <sprevidi@cisco.com>
>> >> >
>> >> > support - (with a few caveats) - particularly where a 'solution'
>> >> > rather than a 'use case' is being described:
>> >> >
>> >> > ---
>> >> >
>> >> > -cut section 2 as it describes a solution and not necessarily
>> >> > belongs into a 'use-case' draft.
>> >> >
>> >> > -section 3.1: use-case drafts should not contain forward references
>> >> > to the 'solution' drafts - please cut the last paragraph.
>> >> > a note that the required protocol extension SHOULD support
>> >> > advertisement of backup paths would be ok.
>> >> >
>> >> > -section 4.1: TE without Bandwidth Admission Control is called
>> >> > 'Explicit Routing' - the current expression is a bit awkward;
>> >> >  - Its like ordering a Pizza without cheese - this is not a Pizza any
>> >> >    longer, right ?
>> >> >
>> >> > -section 4.1.1 'Anycast node segment' - this again is a solution
>> >> > and not the problem ...
>> >> >
>> >> > -section 4.1.1.1 we rather should make over this section to discuss
>> >> > the requirements of disjointness, what implications this has to
>> >> > real-world topologies rather than describing a 'Anycast SID based
>> solution'.
>> >> > i can imagine that there are customers who want to use a central
>> >> > controller without the notion of any cast SIDs at all ...
>> >> >
>> >> > -section 4.1.2 add a reference to the OSPF and BGP/LS extended TE
>> metrics.
>> >> >
>> >> > -section 4.1.3 i'd like to add a section which describes
>> >> > inter-domain TE by using label stacking, which seems a more general
>> >> > case rather than just using one label for egress link-selection.
>> >> >
>> >> > -section 5: i am not sure wether service-chaining is
>> >> >   (1) in-charter and to what extend the
>> >> >   (2) overlap with SFC working group is. -
>> >> >   suggest to cut this one.
>> >> >
>> >> > ---
>> >> >
>> >> >
>> >> > not sure if you need another co-author (as the list is fairly
>> >> > impressive), but i can contribute cycles/text for the editing work if you
>> want.
>> >> >
>> >> > thanks,
>> >> >
>> >> > /hannes
>> >> >
>> >> >
>> >> > On Nov 7, 2013, at 5:24 AM, Stefano Previdi (sprevidi) wrote:
>> >> >
>> >> >> John, Alvaro, All,
>> >> >>
>> >> >> according to what discussed after the presentation of SR Use Cases
>> >> >> at
>> >> >> ietf88 spring-wg meeting, I'd like to request the adoption of
>> >> >> draft-filsfils-rtgwg-segment-routing-use-cases-02.txt as wg item.
>> >> >>
>> >> >> Thanks.
>> >> >> s.
>> >> >
>> >>
>> >>
>> >> _______________________________________________
>> >> spring mailing list
>> >> spring@ietf.org
>> >> https://www.ietf.org/mailman/listinfo/spring
>> >>
>> >
>> >
>> > _______________________________________________
>> > spring mailing list
>> > spring@ietf.org
>> > https://www.ietf.org/mailman/listinfo/spring
>> _______________________________________________
>> spring mailing list
>> spring@ietf.org
>> https://www.ietf.org/mailman/listinfo/spring
>>
>
>

From rraszuk@gmail.com  Tue Nov 19 07:11:46 2013
Return-Path: <rraszuk@gmail.com>
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 657DB1AE001 for <spring@ietfa.amsl.com>; Tue, 19 Nov 2013 07:11:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level: 
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no
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 3pIsxl83kKcP for <spring@ietfa.amsl.com>; Tue, 19 Nov 2013 07:11:39 -0800 (PST)
Received: from mail-ie0-x236.google.com (mail-ie0-x236.google.com [IPv6:2607:f8b0:4001:c03::236]) by ietfa.amsl.com (Postfix) with ESMTP id 8B5A81AE013 for <spring@ietf.org>; Tue, 19 Nov 2013 07:11:39 -0800 (PST)
Received: by mail-ie0-f182.google.com with SMTP id as1so4968099iec.41 for <spring@ietf.org>; Tue, 19 Nov 2013 07:11:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=6W0yrrp7BjPfDJyxLR+YB2Lljfq8I6OIjUHahMQ1DVo=; b=EjkEbep0JHM08wWC60EsoY1G34nasUBAqJWFnhwOGna4rkU0Dx5W8BlOXlC+D6f468 CwvIfg4PmUEv0xMnFvI9cRe0eg4pz20GErh8sNKH0zQumItQk1n44iuRXCM+zSu8L/XN 32facZ9Tih0ZLOmdoE2htP6rmj54yM3Mh5EFowHHYqxnfsm8PaduePD+9U75ydpqKeVX zOpTmuFLb8TEgMm8hnEhFPSwRydHx4PTECvLU97a4pNslq9x2EXnY8ft2CTOBMOmzfY0 PjgK6LrAnNgnK7K68Fkb+KOCUBPJch2Zzrvwb9p4y764OjB4vJYOJOWRyHdLVedRl9bx 6JTA==
MIME-Version: 1.0
X-Received: by 10.50.16.45 with SMTP id c13mr19158040igd.55.1384873893493; Tue, 19 Nov 2013 07:11:33 -0800 (PST)
Sender: rraszuk@gmail.com
Received: by 10.64.61.129 with HTTP; Tue, 19 Nov 2013 07:11:33 -0800 (PST)
In-Reply-To: <57d00406c35d47fba874c65b7af9c4ec@CO1PR05MB442.namprd05.prod.outlook.com>
References: <CEAFA174.41B29%aretana@cisco.com> <528B171A.9020804@cisco.com> <57d00406c35d47fba874c65b7af9c4ec@CO1PR05MB442.namprd05.prod.outlook.com>
Date: Tue, 19 Nov 2013 16:11:33 +0100
X-Google-Sender-Auth: cv_dJ1m7R1ARMGuCDGMKZASx73A
Message-ID: <CA+b+ER=75UkOrt5=gN76F-YBaSi574E_6OUMs+hT7HiJ06657w@mail.gmail.com>
From: Robert Raszuk <robert@raszuk.net>
To: Ronald Bonica <rbonica@juniper.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "Alvaro Retana \(aretana\)" <aretana@cisco.com>, "spring@ietf.org" <spring@ietf.org>, Clarence Filsfils <cfilsfil@cisco.com>, "draft-filsfils-rtgwg-segment-routing-use-cases@tools.ietf.org" <draft-filsfils-rtgwg-segment-routing-use-cases@tools.ietf.org>
Subject: Re: [spring] IRP Claims related to draft-filsfils-rtgwg-segment-routing-use-cases
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Stacked Tunnels for Source Routing \(STATUS\)." <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Nov 2013 15:11:46 -0000

Hello Ron,

IPR can refer to either solutions or application of the solutions.
Both are valid IPR claims.

I find use cases as typical application of the solutions.

Note that use cases is not a problem statement. For the latter indeed
IPR could be odd, however for the former it seems to me like perfectly
valid claim.

Best,
R.

On Tue, Nov 19, 2013 at 3:57 PM, Ronald Bonica <rbonica@juniper.net> wrote:
> Folks,
>
> It is strange for IPR to be associated with a use-case document. Could it be that the use-case document assumes solutions and that the IPR is associated with the assumed solutions?
>
> If that is the case, we should probably remove the assumed solutions from the document. (This is appropriate because it is a use-case document.) Then the authors could re-evaluate the document to determine whether it is still IPR encumbered.
>
>                                                    Ron
>
>
>> -----Original Message-----
>> From: spring [mailto:spring-bounces@ietf.org] On Behalf Of Clarence
>> Filsfils
>> Sent: Tuesday, November 19, 2013 2:46 AM
>> To: Alvaro Retana (aretana)
>> Cc: spring@ietf.org; draft-filsfils-rtgwg-segment-routing-use-
>> cases@tools.ietf.org
>> Subject: Re: [spring] IRP Claims related to draft-filsfils-rtgwg-
>> segment-routing-use-cases
>>
>>
>> There is IPR that is in the process of being disclosed.
>>
>> Cheers,
>> Clarence
>>
>>
>> On 18.11.13 10:50, Alvaro Retana (aretana) wrote:
>> > Hi!
>> >
>> > In parallel to the call for adoption of this draft, I want to
>> formally
>> > ask the authors (no additional contributors are listed in the latest
>> > version of the draft) to please respond to this message indicating
>> > whether or not you are aware of any relevant IPR.  The draft will not
>> > progress (pending the results of the WG Adoption Call) until we have
>> > received a response from each author.
>> >
>> > Thanks!
>> >
>> > Alvaro.
>> >
>>
>> --
>> Please excuse brief mail, broken wrist
>> _______________________________________________
>> spring mailing list
>> spring@ietf.org
>> https://www.ietf.org/mailman/listinfo/spring
>>
>
>
> _______________________________________________
> spring mailing list
> spring@ietf.org
> https://www.ietf.org/mailman/listinfo/spring

From rbonica@juniper.net  Tue Nov 19 07:19:51 2013
Return-Path: <rbonica@juniper.net>
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 99F5F1AE012 for <spring@ietfa.amsl.com>; Tue, 19 Nov 2013 07:19:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.901
X-Spam-Level: 
X-Spam-Status: No, score=-101.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, 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 MhrNv7d17C3U for <spring@ietfa.amsl.com>; Tue, 19 Nov 2013 07:19:49 -0800 (PST)
Received: from db8outboundpool.messaging.microsoft.com (mail-db8lp0188.outbound.messaging.microsoft.com [213.199.154.188]) by ietfa.amsl.com (Postfix) with ESMTP id 2304B1ADFF3 for <spring@ietf.org>; Tue, 19 Nov 2013 07:19:48 -0800 (PST)
Received: from mail115-db8-R.bigfish.com (10.174.8.250) by DB8EHSOBE014.bigfish.com (10.174.4.77) with Microsoft SMTP Server id 14.1.225.22; Tue, 19 Nov 2013 15:19:42 +0000
Received: from mail115-db8 (localhost [127.0.0.1])	by mail115-db8-R.bigfish.com (Postfix) with ESMTP id EACE440430;	Tue, 19 Nov 2013 15:19:41 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT001.namprd05.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: 1
X-BigFish: VPS1(z579ehz1432Izz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h1d1ah1d2ah1fc6hzzz2fh109h2a8h839h944hd24hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah224fh1d07h1d0ch1d2eh1d3fh1de9h1dfeh1dffh1e1dh1fe8h1ff5h2216h9a9j1155h)
Received-SPF: pass (mail115-db8: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=rbonica@juniper.net; helo=BL2PRD0510HT001.namprd05.prod.outlook.com ; .outlook.com ; 
X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(51704005)(199002)(189002)(81342001)(81686001)(85306002)(74502001)(80022001)(63696002)(80976001)(47446002)(83322001)(65816001)(31966008)(74662001)(87936001)(2656002)(69226001)(76786001)(74316001)(81816001)(56776001)(74706001)(50986001)(76796001)(49866001)(47736001)(33646001)(51856001)(53806001)(54356001)(76576001)(77982001)(79102001)(54316002)(76482001)(81542001)(66066001)(83072001)(47976001)(4396001)(59766001)(46102001)(77096001)(56816003)(74876001)(87266001)(74366001)(24736002); DIR:OUT; SFP:; SCL:1; SRVR:CO1PR05MB443; H:CO1PR05MB442.namprd05.prod.outlook.com; CLIP:66.129.241.15; FPR:; RD:InfoNoRecords; A:1; MX:1; LANG:en; 
Received: from mail115-db8 (localhost.localdomain [127.0.0.1]) by mail115-db8 (MessageSwitch) id 1384874380282770_9214; Tue, 19 Nov 2013 15:19:40 +0000 (UTC)
Received: from DB8EHSMHS032.bigfish.com (unknown [10.174.8.250])	by mail115-db8.bigfish.com (Postfix) with ESMTP id 375F12C006A; Tue, 19 Nov 2013 15:19:40 +0000 (UTC)
Received: from BL2PRD0510HT001.namprd05.prod.outlook.com (157.56.240.101) by DB8EHSMHS032.bigfish.com (10.174.4.42) with Microsoft SMTP Server (TLS) id 14.16.227.3; Tue, 19 Nov 2013 15:19:33 +0000
Received: from CO1PR05MB443.namprd05.prod.outlook.com (10.141.73.152) by BL2PRD0510HT001.namprd05.prod.outlook.com (10.255.100.36) with Microsoft SMTP Server (TLS) id 14.16.383.1; Tue, 19 Nov 2013 15:19:30 +0000
Received: from CO1PR05MB442.namprd05.prod.outlook.com (10.141.73.146) by CO1PR05MB443.namprd05.prod.outlook.com (10.141.73.152) with Microsoft SMTP Server (TLS) id 15.0.785.10; Tue, 19 Nov 2013 15:19:27 +0000
Received: from CO1PR05MB442.namprd05.prod.outlook.com ([169.254.13.67]) by CO1PR05MB442.namprd05.prod.outlook.com ([169.254.13.146]) with mapi id 15.00.0785.001; Tue, 19 Nov 2013 15:19:27 +0000
From: Ronald Bonica <rbonica@juniper.net>
To: Robert Raszuk <robert@raszuk.net>
Thread-Topic: [spring] IRP Claims related to draft-filsfils-rtgwg-segment-routing-use-cases
Thread-Index: AQHO5TmrRB4uG000XEqFSMlQhRXWJJosqchQ
Date: Tue, 19 Nov 2013 15:19:27 +0000
Message-ID: <b0700b29dfbf48a89ffdd4c020384b2a@CO1PR05MB442.namprd05.prod.outlook.com>
References: <CEAFA174.41B29%aretana@cisco.com>	<528B171A.9020804@cisco.com> <57d00406c35d47fba874c65b7af9c4ec@CO1PR05MB442.namprd05.prod.outlook.com> <CA+b+ER=75UkOrt5=gN76F-YBaSi574E_6OUMs+hT7HiJ06657w@mail.gmail.com>
In-Reply-To: <CA+b+ER=75UkOrt5=gN76F-YBaSi574E_6OUMs+hT7HiJ06657w@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.241.15]
x-forefront-prvs: 0035B15214
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Cc: "Alvaro Retana \(aretana\)" <aretana@cisco.com>, "spring@ietf.org" <spring@ietf.org>, Clarence Filsfils <cfilsfil@cisco.com>, "draft-filsfils-rtgwg-segment-routing-use-cases@tools.ietf.org" <draft-filsfils-rtgwg-segment-routing-use-cases@tools.ietf.org>
Subject: Re: [spring] IRP Claims related to draft-filsfils-rtgwg-segment-routing-use-cases
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Stacked Tunnels for Source Routing \(STATUS\)." <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Nov 2013 15:19:51 -0000

>=20
> IPR can refer to either solutions or application of the solutions.
> Both are valid IPR claims.
>=20

Hi Robert,

Do we agree that solutions should not appear in a use-case document? (The q=
uestion is not rhetorical.)

If we agree that a solution should not appear in a use-case document, how c=
an the document possibly talk about its application?

                                                    Ron




From sprevidi@cisco.com  Tue Nov 19 07:23:26 2013
Return-Path: <sprevidi@cisco.com>
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 04E0D1AE049; Tue, 19 Nov 2013 07:23:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.026
X-Spam-Level: 
X-Spam-Status: No, score=-10.026 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.525, 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 0UOvGCIlBeXc; Tue, 19 Nov 2013 07:23:24 -0800 (PST)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) by ietfa.amsl.com (Postfix) with ESMTP id 1AF5A1AE026; Tue, 19 Nov 2013 07:23:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1652; q=dns/txt; s=iport; t=1384874598; x=1386084198; h=from:to:subject:date:message-id:references:content-id: content-transfer-encoding:mime-version; bh=7q5cc7nN9cFrUUvY1Ur27r35MtQqIYDeN+AGvigYaNg=; b=cqk3orcpzcBvJuF2jRxSqKKhs32HvLXAJp31m7assXXb1xBibZ6BCUoq M/1plkRxOBM2NmDRpI+lXDrHUFzMMjyiU0+Wo2SDK60sgeYn3KJF/fKW7 ozTRtbU/qRQKom2FkboOVHncNXUjr/skUw4TVyc5D0mVvDAVHkXwC/KOo E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhAFAHKBi1KtJV2b/2dsb2JhbABZgweBC78+gSEWdIIlAQEBAwEdHUQLAgEZAwECAR4QMhsCCAIEARIbh2AGvzUXj2SDGoESA5gSkg2DKIIq
X-IronPort-AV: E=Sophos;i="4.93,729,1378857600";  d="scan'208";a="622702"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by alln-iport-1.cisco.com with ESMTP; 19 Nov 2013 15:23:18 +0000
Received: from xhc-aln-x13.cisco.com (xhc-aln-x13.cisco.com [173.36.12.87]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id rAJFNHGL015534 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 19 Nov 2013 15:23:18 GMT
Received: from xmb-rcd-x01.cisco.com ([169.254.1.140]) by xhc-aln-x13.cisco.com ([173.36.12.87]) with mapi id 14.03.0123.003; Tue, 19 Nov 2013 09:23:17 -0600
From: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
To: "Alvaro Retana (aretana)" <aretana@cisco.com>, "John G. Scudder" <jgs@juniper.net>, "spring@ietf.org" <spring@ietf.org>, "status@ietf.org" <status@ietf.org>
Thread-Topic: IRP Claims related to draft-filsfils-rtgwg-segment-routing-use-cases
Thread-Index: AQHO5TtFHhlKZZ4m5EGmUvN6dvJ6Wg==
Date: Tue, 19 Nov 2013 15:23:17 +0000
Message-ID: <8425DDA7-6E3C-450C-BF5F-F174E154A98C@cisco.com>
References: <405192AB-8B51-4A5B-86F4-D86A3C8705FA@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.61.93.121]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <F671A0F716C14C42B92E41B66452EA27@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [spring] Fwd: IRP Claims related to draft-filsfils-rtgwg-segment-routing-use-cases
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Stacked Tunnels for Source Routing \(STATUS\)." <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Nov 2013 15:23:26 -0000

re-sending.

s.


Begin forwarded message:

> From: stefano previdi <sprevidi@cisco.com>
> Subject: Re: IRP Claims related to draft-filsfils-rtgwg-segment-routing-u=
se-cases
> Date: November 18, 2013 6:57:58 PM GMT+01:00
> To: "John G. Scudder" <jgs@juniper.net>, "Alvaro Retana (aretana)" <areta=
na@cisco.com>
> Cc: spring@ietf.org
>=20
> John, Alvaro, All,
>=20
> the IPR in the process of being disclosed concerns part of the content=20
> of the -02 draft (that is more a solution than the description of SR=20
> use cases, as Hannes pointed out).
>=20
> As already anticipated during the spring meeting in Vancouver, we're=20
> in the process of updating the use-cases draft by moving out sections=20
> that will become separate drafts.
>=20
> Therefore, future versions of the use-cases draft will no longer=20
> covered by any IPR.
>=20
> Thanks.
>=20
> s.
>=20
>=20
> On Nov 18, 2013, at 5:08 PM, Stefano Previdi (sprevidi) wrote:
>=20
>> Hi,
>>=20
>> there is IPR that is in the process of being disclosed.
>>=20
>> Thanks.
>> s.
>>=20
>>=20
>> On Nov 18, 2013, at 4:50 PM, Alvaro Retana (aretana) wrote:
>>=20
>>> Hi!
>>>=20
>>> In parallel to the call for adoption of this draft, I want to formally =
ask the authors (no additional contributors are listed in the latest versio=
n of the draft) to please respond to this message indicating whether or not=
 you are aware of any relevant IPR.  The draft will not progress (pending t=
he results of the WG Adoption Call) until we have received a response from =
each author.
>>>=20
>>> Thanks!
>>>=20
>>> Alvaro.
>>>=20
>>=20
>=20


From rraszuk@gmail.com  Tue Nov 19 07:26:52 2013
Return-Path: <rraszuk@gmail.com>
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 84F721AE050 for <spring@ietfa.amsl.com>; Tue, 19 Nov 2013 07:26:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level: 
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no
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 JAxh8td_zeO9 for <spring@ietfa.amsl.com>; Tue, 19 Nov 2013 07:26:51 -0800 (PST)
Received: from mail-ie0-x235.google.com (mail-ie0-x235.google.com [IPv6:2607:f8b0:4001:c03::235]) by ietfa.amsl.com (Postfix) with ESMTP id 6202B1AE047 for <spring@ietf.org>; Tue, 19 Nov 2013 07:26:51 -0800 (PST)
Received: by mail-ie0-f181.google.com with SMTP id e14so4342777iej.26 for <spring@ietf.org>; Tue, 19 Nov 2013 07:26:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=JTp30/lrAlM7ACQLUkqdwPMKR4Z+XSm+9tGBiYPqZKc=; b=ouaSWuVlgZZT6jj46+dJK0KUgt+fHlxlggRzh2SxsU2QPzMViLuSkXfHxI4hh5CXuE xSNwX4XY0ITL4/Ud4nGspeEDHQVG8zw2JsGRCc2JmPkgWb4ZoxWxElZFa+rasqRxi9mW TeTcCGMEqVeQOohzEagMVnVvYOP9F7jVz6U6SdglYA2XuefJlEV3M0wGcErepoxjLirB mBtgyXlMin/VhURy+Y0rHc3czuuLyn/5wAsAPGbDJ/fYh794NZ0jthpYlDjXicrQTPcL tr697i1d/LwCiqYYGbUJv4SCEB3s/C9I7xR63ipPhk8vySkFp9M6O4druf7CTu1JoRN2 zIHQ==
MIME-Version: 1.0
X-Received: by 10.43.8.66 with SMTP id or2mr1749558icb.19.1384874805343; Tue, 19 Nov 2013 07:26:45 -0800 (PST)
Sender: rraszuk@gmail.com
Received: by 10.64.61.129 with HTTP; Tue, 19 Nov 2013 07:26:45 -0800 (PST)
In-Reply-To: <b0700b29dfbf48a89ffdd4c020384b2a@CO1PR05MB442.namprd05.prod.outlook.com>
References: <CEAFA174.41B29%aretana@cisco.com> <528B171A.9020804@cisco.com> <57d00406c35d47fba874c65b7af9c4ec@CO1PR05MB442.namprd05.prod.outlook.com> <CA+b+ER=75UkOrt5=gN76F-YBaSi574E_6OUMs+hT7HiJ06657w@mail.gmail.com> <b0700b29dfbf48a89ffdd4c020384b2a@CO1PR05MB442.namprd05.prod.outlook.com>
Date: Tue, 19 Nov 2013 16:26:45 +0100
X-Google-Sender-Auth: Xhz-tr80-m_ZI78MB4mWBbwLF2o
Message-ID: <CA+b+ERntS1sxMJHD5FW6R-EvJuS-g1q5h5qyuXfLOEcEho5jeg@mail.gmail.com>
From: Robert Raszuk <robert@raszuk.net>
To: Ronald Bonica <rbonica@juniper.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "Alvaro Retana \(aretana\)" <aretana@cisco.com>, "spring@ietf.org" <spring@ietf.org>, Clarence Filsfils <cfilsfil@cisco.com>, "draft-filsfils-rtgwg-segment-routing-use-cases@tools.ietf.org" <draft-filsfils-rtgwg-segment-routing-use-cases@tools.ietf.org>
Subject: Re: [spring] IRP Claims related to draft-filsfils-rtgwg-segment-routing-use-cases
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Stacked Tunnels for Source Routing \(STATUS\)." <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Nov 2013 15:26:52 -0000

Hi Ron,

I think you are still mixing problem statement with use cases.

Problem statement should not talk about solutions nor their applications.

Use cases is a document which explains how set of solutions can fix
real problems and why proposed solutions are needed. It does not
however define in detail the solution.

Example:

Problem: I need to steer traffic of shortest path via node D.

Use case: I use segment routing to shift traffic off the shortest path.

Architecture and protocol extension will detail how segment routing
will accomplish that.

For me the distinction is pretty clear.

Best,
R.


On Tue, Nov 19, 2013 at 4:19 PM, Ronald Bonica <rbonica@juniper.net> wrote:
>>
>> IPR can refer to either solutions or application of the solutions.
>> Both are valid IPR claims.
>>
>
> Hi Robert,
>
> Do we agree that solutions should not appear in a use-case document? (The question is not rhetorical.)
>
> If we agree that a solution should not appear in a use-case document, how can the document possibly talk about its application?
>
>                                                     Ron
>
>
>

From jdrake@juniper.net  Tue Nov 19 07:37:51 2013
Return-Path: <jdrake@juniper.net>
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 C1E3C1A1F74 for <spring@ietfa.amsl.com>; Tue, 19 Nov 2013 07:37:51 -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, RCVD_IN_DNSWL_NONE=-0.0001, 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 SOxW4zuJvGKw for <spring@ietfa.amsl.com>; Tue, 19 Nov 2013 07:37:49 -0800 (PST)
Received: from db9outboundpool.messaging.microsoft.com (mail-db9lp0251.outbound.messaging.microsoft.com [213.199.154.251]) by ietfa.amsl.com (Postfix) with ESMTP id 717F11A1F62 for <spring@ietf.org>; Tue, 19 Nov 2013 07:37:48 -0800 (PST)
Received: from mail222-DB9-R.bigfish.com (10.174.16.230) by DB9EHSOBE030.bigfish.com (10.174.14.93) with Microsoft SMTP Server id 14.1.225.22; Tue, 19 Nov 2013 15:37:41 +0000
Received: from mail222-DB9 (localhost [127.0.0.1])	by mail222-DB9-R.bigfish.com (Postfix) with ESMTP id CA91D460972;	Tue, 19 Nov 2013 15:37:41 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT005.namprd05.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -28
X-BigFish: VPS-28(z579ehz98dI9371I542I1432I1418I72dMzz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h1d1ah1d2ah1fc6hzz8275ch1de098h1033IL17326ah8275bh8275dh1de097h186068hz2fh109h2a8h839h944hd24hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah224fh1d07h1d0ch1d2eh1d3fh1de9h1dfeh1dffh1fe8h1ff5h2216h9a9j1155h)
Received-SPF: pass (mail222-DB9: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=jdrake@juniper.net; helo=BL2PRD0510HT005.namprd05.prod.outlook.com ; .outlook.com ; 
X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(24454002)(18374002)(199002)(189002)(51704005)(377454003)(13464003)(51444003)(54356001)(76796001)(76786001)(74876001)(74706001)(77982001)(79102001)(76576001)(56816003)(51856001)(63696002)(69226001)(59766001)(85306002)(33646001)(53806001)(15202345003)(15975445006)(76482001)(83072001)(74502001)(47446002)(65816001)(50986001)(47976001)(54316002)(81342001)(19580395003)(87936001)(2656002)(31966008)(83322001)(19580405001)(80022001)(46102001)(74662001)(66066001)(56776001)(81542001)(81686001)(80976001)(4396001)(87266001)(74366001)(81816001)(74316001)(47736001)(49866001)(24736002); DIR:OUT; SFP:; SCL:1; SRVR:BLUPR05MB436; H:BLUPR05MB562.namprd05.prod.outlook.com; CLIP:66.129.241.16; FPR:; RD:InfoNoRecords; A:1; MX:1; LANG:en; 
Received: from mail222-DB9 (localhost.localdomain [127.0.0.1]) by mail222-DB9 (MessageSwitch) id 1384875460467647_3155; Tue, 19 Nov 2013 15:37:40 +0000 (UTC)
Received: from DB9EHSMHS028.bigfish.com (unknown [10.174.16.241])	by mail222-DB9.bigfish.com (Postfix) with ESMTP id 647E3180045; Tue, 19 Nov 2013 15:37:40 +0000 (UTC)
Received: from BL2PRD0510HT005.namprd05.prod.outlook.com (157.56.240.101) by DB9EHSMHS028.bigfish.com (10.174.14.38) with Microsoft SMTP Server (TLS) id 14.16.227.3; Tue, 19 Nov 2013 15:37:38 +0000
Received: from BLUPR05MB436.namprd05.prod.outlook.com (10.141.27.152) by BL2PRD0510HT005.namprd05.prod.outlook.com (10.255.100.40) with Microsoft SMTP Server (TLS) id 14.16.383.1; Tue, 19 Nov 2013 15:37:32 +0000
Received: from BLUPR05MB562.namprd05.prod.outlook.com (10.141.202.141) by BLUPR05MB436.namprd05.prod.outlook.com (10.141.27.152) with Microsoft SMTP Server (TLS) id 15.0.820.5; Tue, 19 Nov 2013 15:37:30 +0000
Received: from BLUPR05MB562.namprd05.prod.outlook.com ([10.141.202.141]) by BLUPR05MB562.namprd05.prod.outlook.com ([10.141.202.141]) with mapi id 15.00.0820.005; Tue, 19 Nov 2013 15:37:30 +0000
From: John E Drake <jdrake@juniper.net>
To: Robert Raszuk <robert@raszuk.net>
Thread-Topic: [spring] request to move draft-filsfils-rtgwg-segment-routing-use-cases-02 to wg item
Thread-Index: AQHO5TWutgb3+PtTgEqOQorcQfpvSJosoYvggAAGNQCAAAdtEA==
Date: Tue, 19 Nov 2013 15:37:29 +0000
Message-ID: <3e3e03398d484f30978f14c07ab01b7c@BLUPR05MB562.namprd05.prod.outlook.com>
References: <C30B286F-3453-4027-AB24-03ACEAA8F10C@juniper.net> <FF585B07-B4D6-4EDC-A813-B340D47D64CB@juniper.net> <cd284b4d3d8e43c8a46dcb963fb7a1af@BLUPR05MB562.namprd05.prod.outlook.com> <CA+b+ERnAPz7GQ2Hvhoh8mrRH=rNO7M81QLKvmHZ6FqvoRW_Sdg@mail.gmail.com> <d30b2cd0568f4e86b6f8c838214e7614@BLUPR05MB562.namprd05.prod.outlook.com> <CA+b+ER=58rHRT9Y4+ckymqgxwoh0_Wx3hqMpTLai2fL0oGFudQ@mail.gmail.com>
In-Reply-To: <CA+b+ER=58rHRT9Y4+ckymqgxwoh0_Wx3hqMpTLai2fL0oGFudQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.241.16]
x-forefront-prvs: 0035B15214
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Cc: Hannes Gredler <hannes@juniper.net>, "spring@ietf.org" <spring@ietf.org>
Subject: Re: [spring] request to move draft-filsfils-rtgwg-segment-routing-use-cases-02 to wg item
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Stacked Tunnels for Source Routing \(STATUS\)." <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Nov 2013 15:37:52 -0000

Yours Irrespectively,

John

> -----Original Message-----
> From: rraszuk@gmail.com [mailto:rraszuk@gmail.com] On Behalf Of Robert
> Raszuk
> Sent: Tuesday, November 19, 2013 7:08 AM
> To: John E Drake
> Cc: Hannes Gredler; spring@ietf.org
> Subject: Re: [spring] request to move draft-filsfils-rtgwg-segment-routin=
g-use-
> cases-02 to wg item
>=20
> Hi John,
>=20
> > I'm sorry, I think the draft needs to be more focused on use cases and
> > I agree with you that the set of use cases need to be comprehensive.
>=20
> For me the current set of use cases constitutes an essence of what needs =
to
> be stated in the draft in question. Adding or deleting new ones may not b=
ring
> value and may only dilute the document.

[JD]  It would be interesting to see if the authors of these drafts agree w=
ith you.=20

>=20
> > (As an aside, why do people use double quotation marks so randomly?
> > http://www.amazon.com/exec/obidos/ASIN/0811876454/uncrate-20)
>=20
> There was nothing random in using double quotation in my reply .. I was s=
imply
> quoting your text expression verbatim. Hint:
> http://en.wikipedia.org/wiki/Quote

[JD]  I guess the limiting case would be "Hint:"?

>=20
> Best,
> R.
>=20
>=20
> >> Sent: Tuesday, November 19, 2013 6:43 AM
> >> To: John E Drake
> >> Cc: Hannes Gredler; spring@ietf.org
> >> Subject: Re: [spring] request to move
> >> draft-filsfils-rtgwg-segment-routing-use-
> >> cases-02 to wg item
> >>
> >> Hello John,
> >>
> >> I think that incorporating the material from below drafts is exactly
> >> opposite to keeping the draft "more focused". So which one do you sugg=
est
> ?
> >>
> >> Best,
> >> R.
> >>
> >> On Tue, Nov 19, 2013 at 1:56 PM, John E Drake <jdrake@juniper.net>
> wrote:
> >> > Hi,
> >> >
> >> > The draft is a very good start but it needs to be more focused.
> >> > What is the
> >> plan for incorporating material from the following drafts into it:
> >> >
> >> > http://tools.ietf.org/html/draft-geib-spring-oam-usecase-00
> >> >
> >> > http://tools.ietf.org/html/draft-gredler-ospf-label-advertisement-0
> >> > 3
> >> >
> >> > http://tools.ietf.org/html/draft-kim-source-routing-use-cases-00
> >> >
> >> > http://tools.ietf.org/html/draft-shakir-rtgwg-sr-performance-engine
> >> > ere
> >> > d-lsps-00
> >> >
> >> > I would also suggest a global replace of the term 'segment routing'
> >> > with the
> >> term 'explicit routing' which seemed to have support on the mailing li=
st.
> >> >
> >> > Yours Irrespectively,
> >> >
> >> > John
> >> >
> >> >> -----Original Message-----
> >> >> From: spring-bounces@ietf.org [mailto:spring-bounces@ietf.org] On
> >> >> Behalf Of Hannes Gredler
> >> >> Sent: Monday, November 18, 2013 1:24 AM
> >> >> To: spring@ietf.org
> >> >> Subject: [spring] request to move
> >> >> draft-filsfils-rtgwg-segment-routing-use-
> >> >> cases-02 to wg item
> >> >>
> >> >> Begin forwarded message:
> >> >>
> >> >> > From: Hannes Gredler <hannes@juniper.net>
> >> >> > Subject: Re: [Status] request to move
> >> >> > draft-filsfils-rtgwg-segment-routing-use-cases-02 to wg item
> >> >> > Date: November 18, 2013 10:13:20 AM GMT+01:00
> >> >> > To: status@ietf.org
> >> >> > Cc: John Scudder <jgs@juniper.net>, "Alvaro Retana (aretana)"
> >> >> > <aretana@cisco.com>, "Clarence Filsfils (cfilsfil)"
> >> >> > <cfilsfil@cisco.com>, "Stefano Previdi (sprevidi)"
> >> >> > <sprevidi@cisco.com>
> >> >> >
> >> >> > support - (with a few caveats) - particularly where a 'solution'
> >> >> > rather than a 'use case' is being described:
> >> >> >
> >> >> > ---
> >> >> >
> >> >> > -cut section 2 as it describes a solution and not necessarily
> >> >> > belongs into a 'use-case' draft.
> >> >> >
> >> >> > -section 3.1: use-case drafts should not contain forward
> >> >> > references to the 'solution' drafts - please cut the last paragra=
ph.
> >> >> > a note that the required protocol extension SHOULD support
> >> >> > advertisement of backup paths would be ok.
> >> >> >
> >> >> > -section 4.1: TE without Bandwidth Admission Control is called
> >> >> > 'Explicit Routing' - the current expression is a bit awkward;
> >> >> >  - Its like ordering a Pizza without cheese - this is not a Pizza=
 any
> >> >> >    longer, right ?
> >> >> >
> >> >> > -section 4.1.1 'Anycast node segment' - this again is a solution
> >> >> > and not the problem ...
> >> >> >
> >> >> > -section 4.1.1.1 we rather should make over this section to
> >> >> > discuss the requirements of disjointness, what implications this
> >> >> > has to real-world topologies rather than describing a 'Anycast
> >> >> > SID based
> >> solution'.
> >> >> > i can imagine that there are customers who want to use a central
> >> >> > controller without the notion of any cast SIDs at all ...
> >> >> >
> >> >> > -section 4.1.2 add a reference to the OSPF and BGP/LS extended
> >> >> > TE
> >> metrics.
> >> >> >
> >> >> > -section 4.1.3 i'd like to add a section which describes
> >> >> > inter-domain TE by using label stacking, which seems a more
> >> >> > general case rather than just using one label for egress link-sel=
ection.
> >> >> >
> >> >> > -section 5: i am not sure wether service-chaining is
> >> >> >   (1) in-charter and to what extend the
> >> >> >   (2) overlap with SFC working group is. -
> >> >> >   suggest to cut this one.
> >> >> >
> >> >> > ---
> >> >> >
> >> >> >
> >> >> > not sure if you need another co-author (as the list is fairly
> >> >> > impressive), but i can contribute cycles/text for the editing
> >> >> > work if you
> >> want.
> >> >> >
> >> >> > thanks,
> >> >> >
> >> >> > /hannes
> >> >> >
> >> >> >
> >> >> > On Nov 7, 2013, at 5:24 AM, Stefano Previdi (sprevidi) wrote:
> >> >> >
> >> >> >> John, Alvaro, All,
> >> >> >>
> >> >> >> according to what discussed after the presentation of SR Use
> >> >> >> Cases at
> >> >> >> ietf88 spring-wg meeting, I'd like to request the adoption of
> >> >> >> draft-filsfils-rtgwg-segment-routing-use-cases-02.txt as wg item=
.
> >> >> >>
> >> >> >> Thanks.
> >> >> >> s.
> >> >> >
> >> >>
> >> >>
> >> >> _______________________________________________
> >> >> spring mailing list
> >> >> spring@ietf.org
> >> >> https://www.ietf.org/mailman/listinfo/spring
> >> >>
> >> >
> >> >
> >> > _______________________________________________
> >> > spring mailing list
> >> > spring@ietf.org
> >> > https://www.ietf.org/mailman/listinfo/spring
> >> _______________________________________________
> >> spring mailing list
> >> spring@ietf.org
> >> https://www.ietf.org/mailman/listinfo/spring
> >>
> >
> >
>=20



From jdrake@juniper.net  Tue Nov 19 07:45:28 2013
Return-Path: <jdrake@juniper.net>
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 EBAA31ADF0F for <spring@ietfa.amsl.com>; Tue, 19 Nov 2013 07:45:28 -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, RCVD_IN_DNSWL_NONE=-0.0001, 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 MG_ul0kl8Fsf for <spring@ietfa.amsl.com>; Tue, 19 Nov 2013 07:45:26 -0800 (PST)
Received: from db8outboundpool.messaging.microsoft.com (mail-db8lp0186.outbound.messaging.microsoft.com [213.199.154.186]) by ietfa.amsl.com (Postfix) with ESMTP id 6C8E51A1F62 for <spring@ietf.org>; Tue, 19 Nov 2013 07:45:26 -0800 (PST)
Received: from mail131-db8-R.bigfish.com (10.174.8.230) by DB8EHSOBE039.bigfish.com (10.174.4.102) with Microsoft SMTP Server id 14.1.225.22; Tue, 19 Nov 2013 15:45:17 +0000
Received: from mail131-db8 (localhost [127.0.0.1])	by mail131-db8-R.bigfish.com (Postfix) with ESMTP id ABE764E00CE;	Tue, 19 Nov 2013 15:45:17 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT005.namprd05.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -22
X-BigFish: VPS-22(z579ehz98dI9371I542I1432Izz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h1d1ah1d2ah1fc6hzc2hz8275ch1de098h1033IL8275dh1de097h186068hz2fh109h2a8h839h944hd24hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah224fh1d07h1d0ch1d2eh1d3fh1de9h1dfeh1dffh1fe8h1ff5h2216h9a9j1155h)
Received-SPF: pass (mail131-db8: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=jdrake@juniper.net; helo=BL2PRD0510HT005.namprd05.prod.outlook.com ; .outlook.com ; 
X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(24454002)(377454003)(189002)(199002)(13464003)(51704005)(74876001)(224303002)(224313003)(77982001)(2656002)(81816001)(59766001)(56816003)(80022001)(65816001)(81342001)(74706001)(76786001)(63696002)(76796001)(33646001)(79102001)(76576001)(66066001)(85306002)(87936001)(81686001)(81542001)(76482001)(74316001)(74502001)(47446002)(83322001)(19580395003)(74366001)(19580405001)(80976001)(4396001)(50986001)(47976001)(49866001)(47736001)(53806001)(69226001)(31966008)(74662001)(54356001)(46102001)(56776001)(54316002)(15975445006)(1941001)(87266001)(51856001)(83072001)(24736002); DIR:OUT; SFP:; SCL:1; SRVR:BLUPR05MB433; H:BLUPR05MB562.namprd05.prod.outlook.com; CLIP:66.129.241.16; FPR:; RD:InfoNoRecords; MX:1; A:1; LANG:en; 
Received: from mail131-db8 (localhost.localdomain [127.0.0.1]) by mail131-db8 (MessageSwitch) id 1384875916614423_408; Tue, 19 Nov 2013 15:45:16 +0000 (UTC)
Received: from DB8EHSMHS032.bigfish.com (unknown [10.174.8.254])	by mail131-db8.bigfish.com (Postfix) with ESMTP id 90AB8380075; Tue, 19 Nov 2013 15:45:16 +0000 (UTC)
Received: from BL2PRD0510HT005.namprd05.prod.outlook.com (157.56.240.101) by DB8EHSMHS032.bigfish.com (10.174.4.42) with Microsoft SMTP Server (TLS) id 14.16.227.3; Tue, 19 Nov 2013 15:45:16 +0000
Received: from BLUPR05MB433.namprd05.prod.outlook.com (10.141.27.140) by BL2PRD0510HT005.namprd05.prod.outlook.com (10.255.100.40) with Microsoft SMTP Server (TLS) id 14.16.383.1; Tue, 19 Nov 2013 15:45:14 +0000
Received: from BLUPR05MB562.namprd05.prod.outlook.com (10.141.202.141) by BLUPR05MB433.namprd05.prod.outlook.com (10.141.27.140) with Microsoft SMTP Server (TLS) id 15.0.820.5; Tue, 19 Nov 2013 15:45:13 +0000
Received: from BLUPR05MB562.namprd05.prod.outlook.com ([10.141.202.141]) by BLUPR05MB562.namprd05.prod.outlook.com ([10.141.202.141]) with mapi id 15.00.0820.005; Tue, 19 Nov 2013 15:45:13 +0000
From: John E Drake <jdrake@juniper.net>
To: Robert Raszuk <robert@raszuk.net>, Ronald Bonica <rbonica@juniper.net>
Thread-Topic: [spring] IRP Claims related to draft-filsfils-rtgwg-segment-routing-use-cases
Thread-Index: AQHO5TwI8yxWsXPYp0eI4del5AdnSpossbag
Date: Tue, 19 Nov 2013 15:45:12 +0000
Message-ID: <11b35e92dc3b4415b69ea3e94cdbcf8e@BLUPR05MB562.namprd05.prod.outlook.com>
References: <CEAFA174.41B29%aretana@cisco.com> <528B171A.9020804@cisco.com> <57d00406c35d47fba874c65b7af9c4ec@CO1PR05MB442.namprd05.prod.outlook.com> <CA+b+ER=75UkOrt5=gN76F-YBaSi574E_6OUMs+hT7HiJ06657w@mail.gmail.com> <b0700b29dfbf48a89ffdd4c020384b2a@CO1PR05MB442.namprd05.prod.outlook.com> <CA+b+ERntS1sxMJHD5FW6R-EvJuS-g1q5h5qyuXfLOEcEho5jeg@mail.gmail.com>
In-Reply-To: <CA+b+ERntS1sxMJHD5FW6R-EvJuS-g1q5h5qyuXfLOEcEho5jeg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.241.16]
x-forefront-prvs: 0035B15214
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Cc: "Alvaro Retana \(aretana\)" <aretana@cisco.com>, "spring@ietf.org" <spring@ietf.org>, Clarence Filsfils <cfilsfil@cisco.com>, "draft-filsfils-rtgwg-segment-routing-use-cases@tools.ietf.org" <draft-filsfils-rtgwg-segment-routing-use-cases@tools.ietf.org>
Subject: Re: [spring] IRP Claims related to	draft-filsfils-rtgwg-segment-routing-use-cases
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Stacked Tunnels for Source Routing \(STATUS\)." <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Nov 2013 15:45:29 -0000

Robert,

I think you meant to say 'explicit routing'.  As I understand it the purpos=
e of use cases is to gather functional requirements.=20

Yours Irrespectively,

John

> -----Original Message-----
> From: spring [mailto:spring-bounces@ietf.org] On Behalf Of Robert Raszuk
> Sent: Tuesday, November 19, 2013 7:27 AM
> To: Ronald Bonica
> Cc: Alvaro Retana (aretana); spring@ietf.org; Clarence Filsfils; draft-fi=
lsfils-
> rtgwg-segment-routing-use-cases@tools.ietf.org
> Subject: Re: [spring] IRP Claims related to draft-filsfils-rtgwg-segment-=
routing-
> use-cases
>=20
> Hi Ron,
>=20
> I think you are still mixing problem statement with use cases.
>=20
> Problem statement should not talk about solutions nor their applications.
>=20
> Use cases is a document which explains how set of solutions can fix real
> problems and why proposed solutions are needed. It does not however defin=
e
> in detail the solution.
>=20
> Example:
>=20
> Problem: I need to steer traffic of shortest path via node D.
>=20
> Use case: I use segment routing to shift traffic off the shortest path.
>=20
> Architecture and protocol extension will detail how segment routing will
> accomplish that.
>=20
> For me the distinction is pretty clear.
>=20
> Best,
> R.
>=20
>=20
> On Tue, Nov 19, 2013 at 4:19 PM, Ronald Bonica <rbonica@juniper.net>
> wrote:
> >>
> >> IPR can refer to either solutions or application of the solutions.
> >> Both are valid IPR claims.
> >>
> >
> > Hi Robert,
> >
> > Do we agree that solutions should not appear in a use-case document?
> > (The question is not rhetorical.)
> >
> > If we agree that a solution should not appear in a use-case document, h=
ow
> can the document possibly talk about its application?
> >
> >                                                     Ron
> >
> >
> >
> _______________________________________________
> spring mailing list
> spring@ietf.org
> https://www.ietf.org/mailman/listinfo/spring
>=20



From rbonica@juniper.net  Tue Nov 19 08:45:20 2013
Return-Path: <rbonica@juniper.net>
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 BEFC01AE0CB for <spring@ietfa.amsl.com>; Tue, 19 Nov 2013 08:45:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.601
X-Spam-Level: 
X-Spam-Status: No, score=-102.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 rKHKyey4jBQ3 for <spring@ietfa.amsl.com>; Tue, 19 Nov 2013 08:45:18 -0800 (PST)
Received: from am1outboundpool.messaging.microsoft.com (am1ehsobe003.messaging.microsoft.com [213.199.154.206]) by ietfa.amsl.com (Postfix) with ESMTP id 3E11B1AE0CC for <spring@ietf.org>; Tue, 19 Nov 2013 08:45:18 -0800 (PST)
Received: from mail62-am1-R.bigfish.com (10.3.201.244) by AM1EHSOBE012.bigfish.com (10.3.207.134) with Microsoft SMTP Server id 14.1.225.22; Tue, 19 Nov 2013 16:45:11 +0000
Received: from mail62-am1 (localhost [127.0.0.1])	by mail62-am1-R.bigfish.com (Postfix) with ESMTP id ABDCF4E0450; Tue, 19 Nov 2013 16:45:11 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT002.namprd05.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -22
X-BigFish: VPS-22(z579ehz98dI9371I542I1432Izz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h1d1ah1d2ah1fc6hzz8275ch1de098h1033IL8275bh8275dh1de097hz2fh109h2a8h839h944hd24hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah224fh1d07h1d0ch1d2eh1d3fh1de9h1dfeh1dffh1e1dh1fe8h1ff5h2216h9a9j1155h)
Received-SPF: pass (mail62-am1: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=rbonica@juniper.net; helo=BL2PRD0510HT002.namprd05.prod.outlook.com ; .outlook.com ; 
X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(51704005)(13464003)(24454002)(199002)(189002)(377454003)(19580395003)(81342001)(81686001)(85306002)(74502001)(80022001)(63696002)(80976001)(47446002)(83322001)(65816001)(31966008)(74662001)(87936001)(19580405001)(2656002)(69226001)(76786001)(74316001)(81816001)(56776001)(74706001)(50986001)(76796001)(49866001)(47736001)(33646001)(51856001)(53806001)(54356001)(76576001)(77982001)(79102001)(54316002)(76482001)(81542001)(66066001)(83072001)(47976001)(4396001)(59766001)(46102001)(77096001)(56816003)(74876001)(87266001)(74366001)(24736002); DIR:OUT; SFP:; SCL:1; SRVR:CO1PR05MB443; H:CO1PR05MB442.namprd05.prod.outlook.com; CLIP:66.129.241.15; FPR:; RD:InfoNoRecords; A:1; MX:1; LANG:en; 
Received: from mail62-am1 (localhost.localdomain [127.0.0.1]) by mail62-am1 (MessageSwitch) id 1384879508917489_29201; Tue, 19 Nov 2013 16:45:08 +0000 (UTC)
Received: from AM1EHSMHS014.bigfish.com (unknown [10.3.201.233])	by mail62-am1.bigfish.com (Postfix) with ESMTP id D3FC91E0087;	Tue, 19 Nov 2013 16:45:08 +0000 (UTC)
Received: from BL2PRD0510HT002.namprd05.prod.outlook.com (157.56.240.101) by AM1EHSMHS014.bigfish.com (10.3.207.152) with Microsoft SMTP Server (TLS) id 14.16.227.3; Tue, 19 Nov 2013 16:45:08 +0000
Received: from CO1PR05MB443.namprd05.prod.outlook.com (10.141.73.152) by BL2PRD0510HT002.namprd05.prod.outlook.com (10.255.100.37) with Microsoft SMTP Server (TLS) id 14.16.383.1; Tue, 19 Nov 2013 16:45:08 +0000
Received: from CO1PR05MB442.namprd05.prod.outlook.com (10.141.73.146) by CO1PR05MB443.namprd05.prod.outlook.com (10.141.73.152) with Microsoft SMTP Server (TLS) id 15.0.785.10; Tue, 19 Nov 2013 16:45:05 +0000
Received: from CO1PR05MB442.namprd05.prod.outlook.com ([169.254.13.67]) by CO1PR05MB442.namprd05.prod.outlook.com ([169.254.13.146]) with mapi id 15.00.0785.001; Tue, 19 Nov 2013 16:45:04 +0000
From: Ronald Bonica <rbonica@juniper.net>
To: Robert Raszuk <robert@raszuk.net>
Thread-Topic: [spring] IRP Claims related to draft-filsfils-rtgwg-segment-routing-use-cases
Thread-Index: AQHO5TmrRB4uG000XEqFSMlQhRXWJJosqchQgAADR4CAABDOAA==
Date: Tue, 19 Nov 2013 16:45:04 +0000
Message-ID: <d1d11082008e4175bf473c52e7972813@CO1PR05MB442.namprd05.prod.outlook.com>
References: <CEAFA174.41B29%aretana@cisco.com>	<528B171A.9020804@cisco.com> <57d00406c35d47fba874c65b7af9c4ec@CO1PR05MB442.namprd05.prod.outlook.com> <CA+b+ER=75UkOrt5=gN76F-YBaSi574E_6OUMs+hT7HiJ06657w@mail.gmail.com> <b0700b29dfbf48a89ffdd4c020384b2a@CO1PR05MB442.namprd05.prod.outlook.com> <CA+b+ERntS1sxMJHD5FW6R-EvJuS-g1q5h5qyuXfLOEcEho5jeg@mail.gmail.com>
In-Reply-To: <CA+b+ERntS1sxMJHD5FW6R-EvJuS-g1q5h5qyuXfLOEcEho5jeg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.241.15]
x-forefront-prvs: 0035B15214
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Cc: "Alvaro Retana \(aretana\)" <aretana@cisco.com>, "spring@ietf.org" <spring@ietf.org>, Clarence Filsfils <cfilsfil@cisco.com>, "draft-filsfils-rtgwg-segment-routing-use-cases@tools.ietf.org" <draft-filsfils-rtgwg-segment-routing-use-cases@tools.ietf.org>
Subject: Re: [spring] IRP Claims related to draft-filsfils-rtgwg-segment-routing-use-cases
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Stacked Tunnels for Source Routing \(STATUS\)." <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Nov 2013 16:45:21 -0000

Robert,

We agree that is appropriate for a use-case document to say:

1) I have problem P
2) I use technology T to solve problem P

However, we also agree that it is not appropriate for a use-case document t=
o define technology T.

In a use-case document, statement 1) is very concrete, because we understan=
d the nature of problem P. However, statement 2) can only be as solid as ou=
r understanding of technology T.

It seems unlikely that IPR might be associated with that less well understo=
od, second statement. However, only the authors can say for sure.

Not wishing to wallow in the procedural mire, I will back off and listen to=
 what the authors have to say.

                                                 Ron


> -----Original Message-----
> From: rraszuk@gmail.com [mailto:rraszuk@gmail.com] On Behalf Of Robert
> Raszuk
> Sent: Tuesday, November 19, 2013 10:27 AM
> To: Ronald Bonica
> Cc: Clarence Filsfils; Alvaro Retana (aretana); spring@ietf.org; draft-
> filsfils-rtgwg-segment-routing-use-cases@tools.ietf.org
> Subject: Re: [spring] IRP Claims related to draft-filsfils-rtgwg-
> segment-routing-use-cases
>=20
> Hi Ron,
>=20
> I think you are still mixing problem statement with use cases.
>=20
> Problem statement should not talk about solutions nor their
> applications.
>=20
> Use cases is a document which explains how set of solutions can fix
> real problems and why proposed solutions are needed. It does not
> however define in detail the solution.
>=20
> Example:
>=20
> Problem: I need to steer traffic of shortest path via node D.
>=20
> Use case: I use segment routing to shift traffic off the shortest path.
>=20
> Architecture and protocol extension will detail how segment routing
> will accomplish that.
>=20
> For me the distinction is pretty clear.
>=20
> Best,
> R.
>=20
>=20
> On Tue, Nov 19, 2013 at 4:19 PM, Ronald Bonica <rbonica@juniper.net>
> wrote:
> >>
> >> IPR can refer to either solutions or application of the solutions.
> >> Both are valid IPR claims.
> >>
> >
> > Hi Robert,
> >
> > Do we agree that solutions should not appear in a use-case document?
> > (The question is not rhetorical.)
> >
> > If we agree that a solution should not appear in a use-case document,
> how can the document possibly talk about its application?
> >
> >                                                     Ron
> >
> >
> >
>=20



From loa@pi.nu  Tue Nov 19 09:01:26 2013
Return-Path: <loa@pi.nu>
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 AC5AD1AE0E3 for <spring@ietfa.amsl.com>; Tue, 19 Nov 2013 09:01:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.425
X-Spam-Level: 
X-Spam-Status: No, score=-2.425 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.525] 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 wOJ-n0bme6LD for <spring@ietfa.amsl.com>; Tue, 19 Nov 2013 09:01:24 -0800 (PST)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) by ietfa.amsl.com (Postfix) with ESMTP id 8FCE51AE0E0 for <spring@ietf.org>; Tue, 19 Nov 2013 09:01:23 -0800 (PST)
Received: from [172.20.9.41] (unknown [72.29.212.251]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id 8ACE0180203F; Tue, 19 Nov 2013 18:01:16 +0100 (CET)
Message-ID: <528B995B.7050305@pi.nu>
Date: Tue, 19 Nov 2013 12:01:15 -0500
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: Ronald Bonica <rbonica@juniper.net>
References: <CEAFA174.41B29%aretana@cisco.com>	<528B171A.9020804@cisco.com> <57d00406c35d47fba874c65b7af9c4ec@CO1PR05MB442.namprd05.prod.outlook.com> <CA+b+ER=75UkOrt5=gN76F-YBaSi574E_6OUMs+hT7HiJ06657w@mail.gmail.com> <b0700b29dfbf48a89ffdd4c020384b2a@CO1PR05MB442.namprd05.prod.outlook.com> <CA+b+ERntS1sxMJHD5FW6R-EvJuS-g1q5h5qyuXfLOEcEho5jeg@mail.gmail.com> <d1d11082008e4175bf473c52e7972813@CO1PR05MB442.namprd05.prod.outlook.com>
In-Reply-To: <d1d11082008e4175bf473c52e7972813@CO1PR05MB442.namprd05.prod.outlook.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "spring@ietf.org" <spring@ietf.org>, "draft-filsfils-rtgwg-segment-routing-use-cases@tools.ietf.org" <draft-filsfils-rtgwg-segment-routing-use-cases@tools.ietf.org>
Subject: Re: [spring] IRP Claims related to draft-filsfils-rtgwg-segment-routing-use-cases
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Stacked Tunnels for Source Routing \(STATUS\)." <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Nov 2013 17:01:26 -0000

Ron,

The approach I think we are recommended around IPRs in general is that
we should ask for existing IPRs and take the IPR disclosures from IPR
holders as we receive them and not try to second guess what IPR holders
are up to.

I've been involved in a draft that move some IANA registries from place
in the overall IANA registry. My take was originally that there were no
possibilities whatsoever that there would be any IPR, nevertheless the
the working group chairs decided to poll the list for IPRs.

I think the approach is "better safe, than sorry". It is not a problem
for if we get IPR disclosures that the IPR holder can't make stand!
IETF as such don't have an opinion about IPR disclosures.

/Loa

On 2013-11-19 11:45, Ronald Bonica wrote:
> Robert,
>
> We agree that is appropriate for a use-case document to say:
>
> 1) I have problem P
> 2) I use technology T t.o solve problem P
>
> However, we also agree that it is not appropriate for a use-case document to define technology T.
>
> In a use-case document, statement 1) is very concrete, because we understand the nature of problem P. However, statement 2) can only be as solid as our understanding of technology T.
>
> It seems unlikely that IPR might be associated with that less well understood, second statement. However, only the authors can say for sure.
>
> Not wishing to wallow in the procedural mire, I will back off and listen to what the authors have to say.
>
>                                                   Ron
>
>
>> -----Original Message-----
>> From: rraszuk@gmail.com [mailto:rraszuk@gmail.com] On Behalf Of Robert
>> Raszuk
>> Sent: Tuesday, November 19, 2013 10:27 AM
>> To: Ronald Bonica
>> Cc: Clarence Filsfils; Alvaro Retana (aretana); spring@ietf.org; draft-
>> filsfils-rtgwg-segment-routing-use-cases@tools.ietf.org
>> Subject: Re: [spring] IRP Claims related to draft-filsfils-rtgwg-
>> segment-routing-use-cases
>>
>> Hi Ron,
>>
>> I think you are still mixing problem statement with use cases.
>>
>> Problem statement should not talk about solutions nor their
>> applications.
>>
>> Use cases is a document which explains how set of solutions can fix
>> real problems and why proposed solutions are needed. It does not
>> however define in detail the solution.
>>
>> Example:
>>
>> Problem: I need to steer traffic of shortest path via node D.
>>
>> Use case: I use segment routing to shift traffic off the shortest path.
>>
>> Architecture and protocol extension will detail how segment routing
>> will accomplish that.
>>
>> For me the distinction is pretty clear.
>>
>> Best,
>> R.
>>
>>
>> On Tue, Nov 19, 2013 at 4:19 PM, Ronald Bonica <rbonica@juniper.net>
>> wrote:
>>>>
>>>> IPR can refer to either solutions or application of the solutions.
>>>> Both are valid IPR claims.
>>>>
>>>
>>> Hi Robert,
>>>
>>> Do we agree that solutions should not appear in a use-case document?
>>> (The question is not rhetorical.)
>>>
>>> If we agree that a solution should not appear in a use-case document,
>> how can the document possibly talk about its application?
>>>
>>>                                                      Ron
>>>
>>>
>>>
>>
>
>
> _______________________________________________
> spring mailing list
> spring@ietf.org
> https://www.ietf.org/mailman/listinfo/spring
>

-- 


Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64

From rob.shakir@bt.com  Tue Nov 19 02:51:08 2013
Return-Path: <rob.shakir@bt.com>
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 8C3641ADBF7 for <spring@ietfa.amsl.com>; Tue, 19 Nov 2013 02:51:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.425
X-Spam-Level: 
X-Spam-Status: No, score=-2.425 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.525, 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 jG1Cz-dm35rN for <spring@ietfa.amsl.com>; Tue, 19 Nov 2013 02:51:05 -0800 (PST)
Received: from smtpb1.bt.com (smtpb1.bt.com [62.7.242.135]) by ietfa.amsl.com (Postfix) with ESMTP id 601A71AD7BF for <spring@ietf.org>; Tue, 19 Nov 2013 02:51:05 -0800 (PST)
Received: from E07HT04-UKBR.domain1.systemhost.net (193.113.197.162) by EVMED01-UKBR.bt.com (10.216.161.31) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 19 Nov 2013 10:50:52 +0000
Received: from EMV02-UKBR.domain1.systemhost.net ([169.254.1.13]) by E07HT04-UKBR.domain1.systemhost.net ([193.113.197.162]) with mapi; Tue, 19 Nov 2013 10:50:39 +0000
From: <rob.shakir@bt.com>
To: <aretana@cisco.com>, <draft-filsfils-rtgwg-segment-routing-use-cases@tools.ietf.org>
Date: Tue, 19 Nov 2013 10:50:38 +0000
Thread-Topic: IRP Claims related to draft-filsfils-rtgwg-segment-routing-use-cases
Thread-Index: Ac7lFS+W+DHvNn+JQbG2ErVvo1PQwA==
Message-ID: <CEB0F2E7.3BA96%rob.shakir@bt.com>
In-Reply-To: <CEAFA174.41B29%aretana@cisco.com>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.7.130812
acceptlanguage: en-US, en-GB
Content-Type: multipart/alternative; boundary="_000_CEB0F2E73BA96robshakirbtcom_"
MIME-Version: 1.0
X-Mailman-Approved-At: Tue, 19 Nov 2013 10:34:38 -0800
Cc: spring@ietf.org
Subject: Re: [spring] IRP Claims related to draft-filsfils-rtgwg-segment-routing-use-cases
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Stacked Tunnels for Source Routing \(STATUS\)." <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Nov 2013 10:51:08 -0000

--_000_CEB0F2E73BA96robshakirbtcom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

[18/11/2013 15:50, "Alvaro Retana (aretana)" <aretana@cisco.com<mailto:aret=
ana@cisco.com>>]

Hi!

In parallel to the call for adoption of this draft, I want to formally ask =
the authors (no additional contributors are listed in the latest version of=
 the draft) to please respond to this message indicating whether or not you=
 are aware of any relevant IPR.  The draft will not progress (pending the r=
esults of the WG Adoption Call) until we have received a response from each=
 author.

There is no relevant IPR of which I am aware.

Kind regards,
r.

--_000_CEB0F2E73BA96robshakirbtcom_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html><head></head><body style=3D"word-wrap: break-word; -webkit-nbsp-mode:=
 space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-si=
ze: 12px; font-family: Calibri, sans-serif;"><div>[18/11/2013 15:50, "Alvar=
o Retana (aretana)" &lt;<a href=3D"mailto:aretana@cisco.com">aretana@cisco.=
com</a>&gt;]</div><span id=3D"OLK_SRC_BODY_SECTION"><div><br></div><blockqu=
ote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"BORDER-LEFT: #b5c4df=
 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;"><div><meta http-equiv=3D"Conten=
t-Type" content=3D"text/html; charset=3Dutf-8"><div style=3D"word-wrap: bre=
ak-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; c=
olor: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; "><d=
iv>Hi!</div><div><br></div><div>In parallel to the call for adoption of thi=
s draft,&nbsp;I want to formally ask the authors (no additional contributor=
s are listed in the latest version of the draft) to please respond to this =
message indicating whether or not you are aware of any relevant
 IPR. &nbsp;The draft will not progress (pending the results of the WG Adop=
tion Call) until we have received a response from each author.</div></div><=
/div></blockquote></span><div><br></div><div>There is no relevant IPR of wh=
ich I am aware.</div><div><br></div><div>Kind regards,</div><div>r.</div></=
body></html>

--_000_CEB0F2E73BA96robshakirbtcom_--

From jgs@juniper.net  Tue Nov 19 10:35:28 2013
Return-Path: <jgs@juniper.net>
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 99FC11AE126; Tue, 19 Nov 2013 10:35:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 jHfNGUuFbHMN; Tue, 19 Nov 2013 10:35:26 -0800 (PST)
Received: from va3outboundpool.messaging.microsoft.com (va3ehsobe010.messaging.microsoft.com [216.32.180.30]) by ietfa.amsl.com (Postfix) with ESMTP id 5BDB01AE11C; Tue, 19 Nov 2013 10:35:23 -0800 (PST)
Received: from mail131-va3-R.bigfish.com (10.7.14.232) by VA3EHSOBE001.bigfish.com (10.7.40.21) with Microsoft SMTP Server id 14.1.225.22; Tue, 19 Nov 2013 18:35:16 +0000
Received: from mail131-va3 (localhost [127.0.0.1])	by mail131-va3-R.bigfish.com (Postfix) with ESMTP id C747C260204;	Tue, 19 Nov 2013 18:35:16 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT003.namprd05.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -23
X-BigFish: VPS-23(z579ehz98dI9371I103dK1432Izz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h1d1ah1d2ah1fc6h1082kzz8275ch1de098h1033IL8275bh8275dh1de097hz2fh109h2a8h839h944hd25he5bhf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah224fh1d0ch1d2eh1d3fh1dfeh1dffh1e1dh1fe8h1ff5h2052h20b3h2216h22d0h1155h)
Received-SPF: pass (mail131-va3: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=jgs@juniper.net; helo=BL2PRD0510HT003.namprd05.prod.outlook.com ; .outlook.com ; 
X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(377454003)(24454002)(199002)(189002)(51704005)(41574002)(31966008)(46102001)(53806001)(74662001)(74502001)(76482001)(36756003)(76796001)(77096001)(76786001)(33656001)(51856001)(56816003)(74366001)(74876001)(74706001)(83716003)(87936001)(77982001)(79102001)(54316002)(85306002)(56776001)(66066001)(81342001)(87266001)(2656002)(80022001)(65816001)(50986001)(47446002)(63696002)(81542001)(69226001)(54356001)(81816001)(59766001)(82746002)(47736001)(83072001)(80976001)(19580395003)(47976001)(81686001)(83322001)(19580405001)(4396001)(49866001)(42262001); DIR:OUT; SFP:; SCL:1; SRVR:DM2PR05MB526; H:DM2PR05MB527.namprd05.prod.outlook.com; CLIP:66.129.241.14; FPR:; RD:InfoNoRecords; A:1; MX:1; LANG:en; 
Received: from mail131-va3 (localhost.localdomain [127.0.0.1]) by mail131-va3 (MessageSwitch) id 1384886114818353_30319; Tue, 19 Nov 2013 18:35:14 +0000 (UTC)
Received: from VA3EHSMHS022.bigfish.com (unknown [10.7.14.245])	by mail131-va3.bigfish.com (Postfix) with ESMTP id BDDCC2200F1; Tue, 19 Nov 2013 18:35:14 +0000 (UTC)
Received: from BL2PRD0510HT003.namprd05.prod.outlook.com (157.56.240.101) by VA3EHSMHS022.bigfish.com (10.7.99.32) with Microsoft SMTP Server (TLS) id 14.16.227.3; Tue, 19 Nov 2013 18:35:14 +0000
Received: from DM2PR05MB526.namprd05.prod.outlook.com (10.141.99.148) by BL2PRD0510HT003.namprd05.prod.outlook.com (10.255.100.38) with Microsoft SMTP Server (TLS) id 14.16.383.1; Tue, 19 Nov 2013 18:35:13 +0000
Received: from DM2PR05MB527.namprd05.prod.outlook.com (10.141.99.151) by DM2PR05MB526.namprd05.prod.outlook.com (10.141.99.148) with Microsoft SMTP Server (TLS) id 15.0.820.5; Tue, 19 Nov 2013 18:35:12 +0000
Received: from DM2PR05MB527.namprd05.prod.outlook.com ([169.254.6.167]) by DM2PR05MB527.namprd05.prod.outlook.com ([169.254.6.23]) with mapi id 15.00.0820.005; Tue, 19 Nov 2013 18:35:12 +0000
From: John Scudder <jgs@juniper.net>
To: Stefano Previdi <sprevidi@cisco.com>
Thread-Topic: IRP Claims related to draft-filsfils-rtgwg-segment-routing-use-cases
Thread-Index: AQHO5TtFHhlKZZ4m5EGmUvN6dvJ6Wpos4a+A
Date: Tue, 19 Nov 2013 18:35:11 +0000
Message-ID: <798BBF77-D586-4A6D-9408-8743005512A6@juniper.net>
References: <405192AB-8B51-4A5B-86F4-D86A3C8705FA@cisco.com> <8425DDA7-6E3C-450C-BF5F-F174E154A98C@cisco.com>
In-Reply-To: <8425DDA7-6E3C-450C-BF5F-F174E154A98C@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.241.14]
x-forefront-prvs: 0035B15214
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3A365925777D0D489B4AD92472AAD26C@namprd05.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Cc: "<aretana@cisco.com> \(aretana\)" <aretana@cisco.com>, "spring@ietf.org" <spring@ietf.org>, "status@ietf.org" <status@ietf.org>
Subject: Re: [spring] IRP Claims related to draft-filsfils-rtgwg-segment-routing-use-cases
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Stacked Tunnels for Source Routing \(STATUS\)." <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Nov 2013 18:35:28 -0000

Stefano,

Thanks for re-posting. For some reason, the original didn't make it to the =
mailing list, or at least it's not in the archives. I hadn't realized becau=
se it was cc'd direct to me. I'll open a trouble ticket to try to find out =
why the original didn't reach the list.

--John

On Nov 19, 2013, at 10:23 AM, Stefano Previdi (sprevidi) <sprevidi@cisco.co=
m> wrote:

>=20
> re-sending.
>=20
> s.
>=20
>=20
> Begin forwarded message:
>=20
>> From: stefano previdi <sprevidi@cisco.com>
>> Subject: Re: IRP Claims related to draft-filsfils-rtgwg-segment-routing-=
use-cases
>> Date: November 18, 2013 6:57:58 PM GMT+01:00
>> To: "John G. Scudder" <jgs@juniper.net>, "Alvaro Retana (aretana)" <aret=
ana@cisco.com>
>> Cc: spring@ietf.org
>>=20
>> John, Alvaro, All,
>>=20
>> the IPR in the process of being disclosed concerns part of the content=20
>> of the -02 draft (that is more a solution than the description of SR=20
>> use cases, as Hannes pointed out).
>>=20
>> As already anticipated during the spring meeting in Vancouver, we're=20
>> in the process of updating the use-cases draft by moving out sections=20
>> that will become separate drafts.
>>=20
>> Therefore, future versions of the use-cases draft will no longer=20
>> covered by any IPR.
>>=20
>> Thanks.
>>=20
>> s.
>>=20
>>=20
>> On Nov 18, 2013, at 5:08 PM, Stefano Previdi (sprevidi) wrote:
>>=20
>>> Hi,
>>>=20
>>> there is IPR that is in the process of being disclosed.
>>>=20
>>> Thanks.
>>> s.
>>>=20
>>>=20
>>> On Nov 18, 2013, at 4:50 PM, Alvaro Retana (aretana) wrote:
>>>=20
>>>> Hi!
>>>>=20
>>>> In parallel to the call for adoption of this draft, I want to formally=
 ask the authors (no additional contributors are listed in the latest versi=
on of the draft) to please respond to this message indicating whether or no=
t you are aware of any relevant IPR.  The draft will not progress (pending =
the results of the WG Adoption Call) until we have received a response from=
 each author.
>>>>=20
>>>> Thanks!
>>>>=20
>>>> Alvaro.
>>>>=20
>>>=20
>>=20
>=20
>=20
>=20



From rbonica@juniper.net  Tue Nov 19 13:27:54 2013
Return-Path: <rbonica@juniper.net>
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 162791AE1A0; Tue, 19 Nov 2013 13:27:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.601
X-Spam-Level: 
X-Spam-Status: No, score=-102.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 kYs5UXq3hAxP; Tue, 19 Nov 2013 13:27:51 -0800 (PST)
Received: from co1outboundpool.messaging.microsoft.com (co1ehsobe005.messaging.microsoft.com [216.32.180.188]) by ietfa.amsl.com (Postfix) with ESMTP id 8281E1AE168; Tue, 19 Nov 2013 13:27:51 -0800 (PST)
Received: from mail102-co1-R.bigfish.com (10.243.78.238) by CO1EHSOBE008.bigfish.com (10.243.66.71) with Microsoft SMTP Server id 14.1.225.22; Tue, 19 Nov 2013 21:27:44 +0000
Received: from mail102-co1 (localhost [127.0.0.1])	by mail102-co1-R.bigfish.com (Postfix) with ESMTP id E64CA940DD2;	Tue, 19 Nov 2013 21:27:44 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT004.namprd05.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -26
X-BigFish: VPS-26(z579ehz98dI9371I103dK148cI542I1432Izz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h1d1ah1d2ah1fc6hzc2hz8275ch1de098h1033IL8275bh8275dh1de097h186068hz2fh109h2a8h839h944hd24hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah224fh1d07h1d0ch1d2eh1d3fh1de9h1dfeh1dffh1e1dh1fe8h1ff5h2216h22d0h9a9j1155h)
Received-SPF: pass (mail102-co1: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=rbonica@juniper.net; helo=BL2PRD0510HT004.namprd05.prod.outlook.com ; .outlook.com ; 
X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(24454002)(41574002)(13464003)(189002)(199002)(377454003)(52604005)(51704005)(19580395003)(54316002)(80976001)(83072001)(83322001)(19580405001)(56776001)(74366001)(81816001)(85306002)(77096001)(59766001)(77982001)(81342001)(15975445006)(81686001)(81542001)(33646001)(1941001)(69226001)(2656002)(79102001)(63696002)(87266001)(74316001)(46102001)(87936001)(50986001)(76786001)(65816001)(76796001)(66066001)(76576001)(80022001)(56816003)(51856001)(47976001)(74706001)(49866001)(74876001)(47736001)(76482001)(4396001)(74502001)(54356001)(53806001)(31966008)(74662001)(47446002)(24736002); DIR:OUT; SFP:; SCL:1; SRVR:CO1PR05MB524; H:CO1PR05MB442.namprd05.prod.outlook.com; CLIP:66.129.241.18; FPR:; RD:InfoNoRecords; MX:1; A:1; LANG:en; 
Received: from mail102-co1 (localhost.localdomain [127.0.0.1]) by mail102-co1 (MessageSwitch) id 1384896463459706_8471; Tue, 19 Nov 2013 21:27:43 +0000 (UTC)
Received: from CO1EHSMHS019.bigfish.com (unknown [10.243.78.233])	by mail102-co1.bigfish.com (Postfix) with ESMTP id 6BA0E30006B; Tue, 19 Nov 2013 21:27:43 +0000 (UTC)
Received: from BL2PRD0510HT004.namprd05.prod.outlook.com (157.56.240.101) by CO1EHSMHS019.bigfish.com (10.243.66.29) with Microsoft SMTP Server (TLS) id 14.16.227.3; Tue, 19 Nov 2013 21:27:42 +0000
Received: from CO1PR05MB524.namprd05.prod.outlook.com (10.141.72.27) by BL2PRD0510HT004.namprd05.prod.outlook.com (10.255.100.39) with Microsoft SMTP Server (TLS) id 14.16.383.1; Tue, 19 Nov 2013 21:27:38 +0000
Received: from CO1PR05MB442.namprd05.prod.outlook.com (10.141.73.146) by CO1PR05MB524.namprd05.prod.outlook.com (10.141.72.27) with Microsoft SMTP Server (TLS) id 15.0.820.5; Tue, 19 Nov 2013 21:27:35 +0000
Received: from CO1PR05MB442.namprd05.prod.outlook.com ([169.254.13.67]) by CO1PR05MB442.namprd05.prod.outlook.com ([169.254.13.146]) with mapi id 15.00.0785.001; Tue, 19 Nov 2013 21:27:35 +0000
From: Ronald Bonica <rbonica@juniper.net>
To: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>, "Alvaro Retana (aretana)" <aretana@cisco.com>, John Scudder <jgs@juniper.net>, "spring@ietf.org" <spring@ietf.org>, "status@ietf.org" <status@ietf.org>
Thread-Topic: IRP Claims related to draft-filsfils-rtgwg-segment-routing-use-cases
Thread-Index: AQHO5TtFHhlKZZ4m5EGmUvN6dvJ6Wpos4SwA
Date: Tue, 19 Nov 2013 21:27:34 +0000
Message-ID: <b8f5bcedbb9742268893153a5deb59dd@CO1PR05MB442.namprd05.prod.outlook.com>
References: <405192AB-8B51-4A5B-86F4-D86A3C8705FA@cisco.com> <8425DDA7-6E3C-450C-BF5F-F174E154A98C@cisco.com>
In-Reply-To: <8425DDA7-6E3C-450C-BF5F-F174E154A98C@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.241.18]
x-forefront-prvs: 0035B15214
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Subject: Re: [spring] IRP Claims related to draft-filsfils-rtgwg-segment-routing-use-cases
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Stacked Tunnels for Source Routing \(STATUS\)." <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Nov 2013 21:27:54 -0000

Stefano,

Thanks for posting this. That addresses my issue.

                              Ron


> -----Original Message-----
> From: spring [mailto:spring-bounces@ietf.org] On Behalf Of Stefano
> Previdi (sprevidi)
> Sent: Tuesday, November 19, 2013 10:23 AM
> To: Alvaro Retana (aretana); John Scudder; spring@ietf.org;
> status@ietf.org
> Subject: [spring] Fwd: IRP Claims related to draft-filsfils-rtgwg-
> segment-routing-use-cases
>=20
>=20
> re-sending.
>=20
> s.
>=20
>=20
> Begin forwarded message:
>=20
> > From: stefano previdi <sprevidi@cisco.com>
> > Subject: Re: IRP Claims related to
> > draft-filsfils-rtgwg-segment-routing-use-cases
> > Date: November 18, 2013 6:57:58 PM GMT+01:00
> > To: "John G. Scudder" <jgs@juniper.net>, "Alvaro Retana (aretana)"
> > <aretana@cisco.com>
> > Cc: spring@ietf.org
> >
> > John, Alvaro, All,
> >
> > the IPR in the process of being disclosed concerns part of the
> content
> > of the -02 draft (that is more a solution than the description of SR
> > use cases, as Hannes pointed out).
> >
> > As already anticipated during the spring meeting in Vancouver, we're
> > in the process of updating the use-cases draft by moving out sections
> > that will become separate drafts.
> >
> > Therefore, future versions of the use-cases draft will no longer
> > covered by any IPR.
> >
> > Thanks.
> >
> > s.
> >
> >
> > On Nov 18, 2013, at 5:08 PM, Stefano Previdi (sprevidi) wrote:
> >
> >> Hi,
> >>
> >> there is IPR that is in the process of being disclosed.
> >>
> >> Thanks.
> >> s.
> >>
> >>
> >> On Nov 18, 2013, at 4:50 PM, Alvaro Retana (aretana) wrote:
> >>
> >>> Hi!
> >>>
> >>> In parallel to the call for adoption of this draft, I want to
> formally ask the authors (no additional contributors are listed in the
> latest version of the draft) to please respond to this message
> indicating whether or not you are aware of any relevant IPR.  The draft
> will not progress (pending the results of the WG Adoption Call) until
> we have received a response from each author.
> >>>
> >>> Thanks!
> >>>
> >>> Alvaro.
> >>>
> >>
> >
>=20
> _______________________________________________
> spring mailing list
> spring@ietf.org
> https://www.ietf.org/mailman/listinfo/spring
>=20



From aretana@cisco.com  Tue Nov 26 11:09:22 2013
Return-Path: <aretana@cisco.com>
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 CDEDD1ADFC5 for <spring@ietfa.amsl.com>; Tue, 26 Nov 2013 11:09:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.502
X-Spam-Level: 
X-Spam-Status: No, score=-9.502 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.001, 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 BIL_3HJiK05G for <spring@ietfa.amsl.com>; Tue, 26 Nov 2013 11:09:21 -0800 (PST)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) by ietfa.amsl.com (Postfix) with ESMTP id 8C4A41ADF90 for <spring@ietf.org>; Tue, 26 Nov 2013 11:09:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=626; q=dns/txt; s=iport; t=1385492962; x=1386702562; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=6xU6Ca2lvSXWK87lWVsusiOi5Jas2iev60ZNpefEffE=; b=iVONcj0VPTW48TBRQb4CD+xoq955CojP7Cj0Q0v0mXJNe23pdI17X3Me n/eX1cfKqmsQ9z97kUWeGlRfIRVYQrJYBb8lttNt8ABh8fPWIhN+97KM+ CC1nVULj40Sbwge62onjRJtJ246jIYWkHZeR3lqptzXCbK7sS/AkQ/XfP k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AsMFAK3wlFKtJXG8/2dsb2JhbABZgweBC7pqgS4WbQeCLB0dPxIBCDZCJQIEDgWIAb9GF458B4QzA5gUkhKBaoE+gWgjHw
X-IronPort-AV: E=Sophos;i="4.93,776,1378857600";  d="scan'208";a="2423223"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by alln-iport-2.cisco.com with ESMTP; 26 Nov 2013 19:09:21 +0000
Received: from xhc-aln-x03.cisco.com (xhc-aln-x03.cisco.com [173.36.12.77]) by rcdn-core2-1.cisco.com (8.14.5/8.14.5) with ESMTP id rAQJ9L7q000802 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <spring@ietf.org>; Tue, 26 Nov 2013 19:09:21 GMT
Received: from xmb-aln-x15.cisco.com ([169.254.9.147]) by xhc-aln-x03.cisco.com ([173.36.12.77]) with mapi id 14.03.0123.003; Tue, 26 Nov 2013 13:09:20 -0600
From: "Alvaro Retana (aretana)" <aretana@cisco.com>
To: "spring@ietf.org" <spring@ietf.org>
Thread-Topic: [Status] request to move draft-filsfils-rtgwg-segment-routing-use-cases-02 to wg item
Thread-Index: AQHO23E8p83WlqlDLUO90VPM+v9VCJog77WAgBcgLgA=
Date: Tue, 26 Nov 2013 19:09:20 +0000
Message-ID: <CEBA5BD8.42AAB%aretana@cisco.com>
In-Reply-To: <CEA6F54D.40EDD%aretana@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.117.15.4]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <6769108E4AF6C84CA658779305D1F685@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "Stefano Previdi \(sprevidi\)" <sprevidi@cisco.com>
Subject: Re: [spring] [Status] request to move draft-filsfils-rtgwg-segment-routing-use-cases-02 to wg item
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Stacked Tunnels for Source Routing \(STATUS\)." <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Nov 2013 19:09:23 -0000

On 11/11/13 9:00 PM, "Alvaro Retana (aretana)" <aretana@cisco.com> wrote:

>List: This message officially starts the call for adoption.  Please
>indicate your position about adopting this use cases draft.  The call will
>close on Friday, November 22, 2013.

There is clearly interest in using this document as a cornerstone for the
working group's use-case work, but the authors have also indicated that
they are working on a significant revision to cut some of the material out
into separate documents. Therefore we will suspend this adoption poll and
resume it when we see the new revision.

Thanks!

Alvaro.



