Re: [Teas] Stephen Farrell's No Objection on draft-ietf-teas-rsvp-te-srlg-collect-06: (with COMMENT)

"Matt Hartley (mhartley)" <mhartley@cisco.com> Thu, 16 June 2016 00:08 UTC

Return-Path: <mhartley@cisco.com>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B37012D9E4; Wed, 15 Jun 2016 17:08:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.947
X-Spam-Level:
X-Spam-Status: No, score=-15.947 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 Dm8YCxXu4aTW; Wed, 15 Jun 2016 17:08:45 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F257A12D58D; Wed, 15 Jun 2016 17:08:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1052; q=dns/txt; s=iport; t=1466035725; x=1467245325; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=clMJzrZl+4geGZXIBLraVs6pBaPBbvF9MQvMsHVoNWk=; b=FirbCghoAaVSqBkv1tU7g5sk2hpE4cU9f6W5KhjUQowcCB5EqQjS/85R 4zfJEavPuJong/JQ0MJqU3pnCrj6b1qen6t7uIApeb0YxiQtPasB8RPYL 4OXVDcuf5NXK1GUty20c6oa9tTlnmcCd+fj8Bx+n/34IvNhtz5TLOIZji Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AXAgC97WFX/5tdJa1dgz6BWbhXgg+BeoYXAoEuOBQBAQEBAQEBZSeETAEBBDo/EAIBCC0JBQsyJQIEAQ0NiCi/VwEBAQEBAQEBAQEBAQEBAQEBAQEBARyGJ4RNhH+FHAWYaQGOIY8pj3MBHjaCOoE1iXcBfgEBAQ
X-IronPort-AV: E=Sophos;i="5.26,478,1459814400"; d="scan'208";a="113416713"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-9.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 16 Jun 2016 00:08:44 +0000
Received: from XCH-ALN-002.cisco.com (xch-aln-002.cisco.com [173.36.7.12]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id u5G08iJ7002183 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 16 Jun 2016 00:08:44 GMT
Received: from xch-rcd-001.cisco.com (173.37.102.11) by XCH-ALN-002.cisco.com (173.36.7.12) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Wed, 15 Jun 2016 19:08:43 -0500
Received: from xch-rcd-001.cisco.com ([173.37.102.11]) by XCH-RCD-001.cisco.com ([173.37.102.11]) with mapi id 15.00.1104.009; Wed, 15 Jun 2016 19:08:43 -0500
From: "Matt Hartley (mhartley)" <mhartley@cisco.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, The IESG <iesg@ietf.org>
Thread-Topic: [Teas] Stephen Farrell's No Objection on draft-ietf-teas-rsvp-te-srlg-collect-06: (with COMMENT)
Thread-Index: AQHRx1pRouh8MVXt1k+/94WnQoh/cp/rNr9A
Date: Thu, 16 Jun 2016 00:08:43 +0000
Message-ID: <ab2b0abf825f4b5abb1aac41fb7543d6@XCH-RCD-001.cisco.com>
References: <20160615230443.26078.47168.idtracker@ietfa.amsl.com>
In-Reply-To: <20160615230443.26078.47168.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [161.44.213.200]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/nvVusIKoXHnG7V4oJeKfCCDF-DU>
Cc: "Matt Hartley (mhartley)" <mhartley@cisco.com>, "teas-chairs@ietf.org" <teas-chairs@ietf.org>, "draft-ietf-teas-rsvp-te-srlg-collect@ietf.org" <draft-ietf-teas-rsvp-te-srlg-collect@ietf.org>, "teas@ietf.org" <teas@ietf.org>, "vbeeram@juniper.net" <vbeeram@juniper.net>
Subject: Re: [Teas] Stephen Farrell's No Objection on draft-ietf-teas-rsvp-te-srlg-collect-06: (with COMMENT)
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jun 2016 00:08:46 -0000

Stephen,

> "It is recommended that domain/layer boundary policies take the
> implications of releasing SRLG information into consideration and behave
> accordingly during LSP signaling." Eh, that's a bit opaque for me at
> least.  Can you say a bit more about what those implications might be and
> how one might take them into account, and why that doesn't need to be
> mentioned in the document?  I'm asking since there is a bit of a breach of
> the blood-brain barrier going on here (as is ack'd in the draft) and while
> it's hard to envisage that much going wrong if providers expose this
> information, I guess there might easily be something too subtle for this
> particular reader:-)

There's no intent here to tell anyone how they ought to run their network. What I was really trying to do when I wrote this was to say, "You should probably think about this before you do it". This is also talked about a bit at the end of section 1. Would it help to re-iterate what's there in this section?

Cheers

Matt