IETF Logo Mail Archive

Re: [Status] Chartering next steps

John E Drake <jdrake@juniper.net> Fri, 20 September 2013 20:18 UTC

Return-Path: <jdrake@juniper.net>
X-Original-To: status@ietfa.amsl.com
Delivered-To: status@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2CA5621F9E43 for <status@ietfa.amsl.com>; Fri, 20 Sep 2013 13:18:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.906
X-Spam-Level:
X-Spam-Status: No, score=-2.906 tagged_above=-999 required=5 tests=[AWL=-0.308, 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 vXavI7f9HRkf for <status@ietfa.amsl.com>; Fri, 20 Sep 2013 13:18:31 -0700 (PDT)
Received: from db9outboundpool.messaging.microsoft.com (mail-db9lp0251.outbound.messaging.microsoft.com [213.199.154.251]) by ietfa.amsl.com (Postfix) with ESMTP id 404B321F9E3B for <status@ietf.org>; Fri, 20 Sep 2013 13:18:30 -0700 (PDT)
Received: from mail177-db9-R.bigfish.com (10.174.16.249) by DB9EHSOBE014.bigfish.com (10.174.14.77) with Microsoft SMTP Server id 14.1.225.22; Fri, 20 Sep 2013 20:18:29 +0000
Received: from mail177-db9 (localhost [127.0.0.1]) by mail177-db9-R.bigfish.com (Postfix) with ESMTP id B055B440247; Fri, 20 Sep 2013 20:18:29 +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: -21
X-BigFish: VPS-21(zz98dI9371Ic89bhc857h4015Izz1f42h208ch1ee6h1de0h1fdah2073h1202h1e76h1d1ah1d2ah1fc6hzz8275ch1d7338h1de098h1033IL17326ah18c673h1de097h186068h8275bh8275dhz2fh2a8h839hd24hf0ah1288h12a5h12bdh137ah1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah1bceh1d07h1d0ch1d2eh1d3fh1de9h1dfeh1dffh1e1dh1fe8h1ff5h20f0h9a9j1155h)
Received-SPF: pass (mail177-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:(377454003)(24454002)(189002)(199002)(164054003)(15202345003)(76796001)(76786001)(76576001)(56816003)(77096001)(33646001)(15975445006)(19580405001)(83322001)(19580395003)(74366001)(56776001)(4396001)(53806001)(65816001)(80022001)(46102001)(51856001)(76482001)(54316002)(54356001)(16236675002)(50986001)(47976001)(47736001)(49866001)(63696002)(81342001)(19609705001)(79102001)(77982001)(59766001)(69226001)(19300405004)(74502001)(47446002)(80976001)(31966008)(81816001)(74316001)(81686001)(74876001)(83072001)(74662001)(66066001)(81542001)(74706001)(24736002); DIR:OUT; SFP:; SCL:1; SRVR:BY2PR05MB142; H:BY2PR05MB142.namprd05.prod.outlook.com; CLIP:66.129.232.2; FPR:; RD:InfoNoRecords; MX:1; A:1; LANG:en;
Received: from mail177-db9 (localhost.localdomain [127.0.0.1]) by mail177-db9 (MessageSwitch) id 1379708260592136_5923; Fri, 20 Sep 2013 20:17:40 +0000 (UTC)
Received: from DB9EHSMHS016.bigfish.com (unknown [10.174.16.243]) by mail177-db9.bigfish.com (Postfix) with ESMTP id 8A8EF40287; Fri, 20 Sep 2013 20:17:40 +0000 (UTC)
Received: from BL2PRD0510HT005.namprd05.prod.outlook.com (157.56.240.101) by DB9EHSMHS016.bigfish.com (10.174.14.26) with Microsoft SMTP Server (TLS) id 14.16.227.3; Fri, 20 Sep 2013 20:17:40 +0000
Received: from BY2PR05MB142.namprd05.prod.outlook.com (10.242.39.144) by BL2PRD0510HT005.namprd05.prod.outlook.com (10.255.100.40) with Microsoft SMTP Server (TLS) id 14.16.359.1; Fri, 20 Sep 2013 20:17:38 +0000
Received: from BY2PR05MB142.namprd05.prod.outlook.com (10.242.39.144) by BY2PR05MB142.namprd05.prod.outlook.com (10.242.39.144) with Microsoft SMTP Server (TLS) id 15.0.775.9; Fri, 20 Sep 2013 20:17:36 +0000
Received: from BY2PR05MB142.namprd05.prod.outlook.com ([169.254.12.132]) by BY2PR05MB142.namprd05.prod.outlook.com ([169.254.12.190]) with mapi id 15.00.0775.005; Fri, 20 Sep 2013 20:17:36 +0000
From: John E Drake <jdrake@juniper.net>
To: Sriganesh Kini <sriganesh.kini@ericsson.com>, Lou Berger <lberger@labn.net>
Thread-Topic: [Status] Chartering next steps
Thread-Index: AQHOtePWSMVrThVEyk6+j+CSjXdeu5nOp9oAgABT+4CAABQL8A==
Date: Fri, 20 Sep 2013 20:17:35 +0000
Message-ID: <aa748c6b240642b9bdfecf836e918a48@BY2PR05MB142.namprd05.prod.outlook.com>
References: <523C1538.1030701@cisco.com> <523C5514.8060700@labn.net> <CAOndX-sGXvqrUdnzw+3cnY5MbH9qUBAcM_CUD0C8+D+hC+0ing@mail.gmail.com>
In-Reply-To: <CAOndX-sGXvqrUdnzw+3cnY5MbH9qUBAcM_CUD0C8+D+hC+0ing@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [66.129.232.2]
x-forefront-prvs: 09752BC779
Content-Type: multipart/alternative; boundary="_000_aa748c6b240642b9bdfecf836e918a48BY2PR05MB142namprd05pro_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Cc: "Stewart Bryant (stbryant)" <stbryant@cisco.com>, "status@ietf.org" <status@ietf.org>, "rtg-ads@tools.ietf.org" <rtg-ads@tools.ietf.org>
Subject: Re: [Status] Chartering next steps
X-BeenThere: status@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Stacked Tunnels for Source Routing \(STATUS\)." <status.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/status>, <mailto:status-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/status>
List-Post: <mailto:status@ietf.org>
List-Help: <mailto:status-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/status>, <mailto:status-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Sep 2013 20:18:38 -0000

Snipped, comment inline.

Yours Irrespectively,

John

From: status-bounces@ietf.org [mailto:status-bounces@ietf.org] On Behalf Of Sriganesh Kini
Sent: Friday, September 20, 2013 12:01 PM
To: Lou Berger
Cc: rtg-ads@tools.ietf.org; status@ietf.org; Stewart Bryant (stbryant)
Subject: Re: [Status] Chartering next steps



On Fri, Sep 20, 2013 at 7:00 AM, Lou Berger <lberger@labn.net<mailto:lberger@labn.net>> wrote:
Stewart,
        A comment and a question:
- You say:
  any path without requiring state to be maintained by transited nodes
I think it would be worth clarifying that no "per-path state" is
required to be maintained. The extensions eluded to below will certainly
control/install state per node, just not per path.

That is an important distinction. Maybe worthwhile to be explicit that this is applicable both to control and data plane state.


- You say:
  any node in the SPRING region is trusted to steer a packet
  through any of the other nodes within the region.
To me this limits "steering", and perhaps steering identifiers, to the
node level. Is steering at the interface/link level now excluded?  The
text should be clear that this is in scope.

This could be worded as "steer a packet along an explicit path". That should cover both.


[JD]  We should probably use the RFC 3031 terminology so we should say “steer a packet along an explicit route through the SPRING region”.



Thanks,
Lou

v2.41.0 | Report a Bug | By Email | System Status