Re: [spring] Alissa Cooper's Discuss on draft-ietf-spring-segment-routing-13: (with DISCUSS and COMMENT)

"Les Ginsberg (ginsberg)" <ginsberg@cisco.com> Thu, 14 December 2017 23:22 UTC

Return-Path: <ginsberg@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 3EF9212714F; Thu, 14 Dec 2017 15:22:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.52
X-Spam-Level:
X-Spam-Status: No, score=-14.52 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, SPF_PASS=-0.001, URIBL_BLOCKED=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 XHYbfnCG3BW1; Thu, 14 Dec 2017 15:22:07 -0800 (PST)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DE5D7127005; Thu, 14 Dec 2017 15:22:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4850; q=dns/txt; s=iport; t=1513293727; x=1514503327; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=9kDwdfp9oIAEyeyDtmpHvu9n5vxfjgmXXHvFMgLChqE=; b=RKs472S8GxfyebJJpV4b16fSXDq+dzkN4qxuN7oq8tV6w3RzCkNCBpFB vEzU1BneAYidBpZqxu37afndXsH73GeM60w/2hMjz2CnCAroI3SBN6pJv ahnqknVLkUi0LmJHk0220pnO8Y/RUG0JVDLR5iLYOiLp/juZv8oqAgzxh w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CwAADMBjNa/5tdJa1dGQEBAQEBAQEBAQEBAQcBAQEBAYM+ZnQnB4N7iiGPB4F9iHyOGhSCAQojhRgCGoRdPxgBAQEBAQEBAQFrKIUjAQEBBCMRRQwEAgEIEQQBAQMCIwMCAgIfERQBCAgCBAENBQiKCgMVEKlEgieHOQ2DGwEBAQEBAQEBAQEBAQEBAQEBAQEBARgFgQ+CUgSCDoFWgWmDK4JqRAEBgToBEgE2gn6CYwWKS48IiRU9Aod7iC+EdYIfhhKLRI0VPohtAhEZAYE6AR85YFYYbxWCY4MIgU54AYgZgSSBFQEBAQ
X-IronPort-AV: E=Sophos;i="5.45,402,1508803200"; d="scan'208";a="44830204"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 14 Dec 2017 23:22:06 +0000
Received: from XCH-RCD-003.cisco.com (xch-rcd-003.cisco.com [173.37.102.13]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id vBENM6nL002960 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 14 Dec 2017 23:22:06 GMT
Received: from xch-aln-001.cisco.com (173.36.7.11) by XCH-RCD-003.cisco.com (173.37.102.13) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Thu, 14 Dec 2017 17:22:05 -0600
Received: from xch-aln-001.cisco.com ([173.36.7.11]) by XCH-ALN-001.cisco.com ([173.36.7.11]) with mapi id 15.00.1320.000; Thu, 14 Dec 2017 17:22:05 -0600
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: Alissa Cooper <alissa@cooperw.in>, The IESG <iesg@ietf.org>
CC: "draft-ietf-spring-segment-routing@ietf.org" <draft-ietf-spring-segment-routing@ietf.org>, "aretana.ietf@gmail.com" <aretana.ietf@gmail.com>, "spring-chairs@ietf.org" <spring-chairs@ietf.org>, "martin.vigoureux@nokia.com" <martin.vigoureux@nokia.com>, "spring@ietf.org" <spring@ietf.org>
Thread-Topic: Alissa Cooper's Discuss on draft-ietf-spring-segment-routing-13: (with DISCUSS and COMMENT)
Thread-Index: AQHTdEIOG0UzK0e0qEeUmrtqvFiUQqNDenmw
Date: Thu, 14 Dec 2017 23:22:05 +0000
Message-ID: <a88e49859d4446deaf8f210d3506fde7@XCH-ALN-001.cisco.com>
References: <151319051482.30109.537791118842316529.idtracker@ietfa.amsl.com>
In-Reply-To: <151319051482.30109.537791118842316529.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: [10.154.160.57]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/El2jt-AqzES8A8DOCINOKctb3lI>
Subject: Re: [spring] Alissa Cooper's Discuss on draft-ietf-spring-segment-routing-13: (with DISCUSS and COMMENT)
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 14 Dec 2017 23:22:09 -0000

Alissa -

I think I am properly understanding your question - but as you reference two non-existent sections in 
https://tools.ietf.org/html/draft-ietf-6man-segment-routing-header-07

<snip>
Section 5.2.2 of draft-ietf-6man-segment-routing-header...
...
Section 5.1.4 of draft-ietf-6man-segment-routing-header
<end snip>

I want to be sure.
Could you provide corrected references and/or the precise text which raises your concern?

Thanx.

    Les

> -----Original Message-----
> From: Alissa Cooper [mailto:alissa@cooperw.in]
> Sent: Wednesday, December 13, 2017 10:42 AM
> To: The IESG <iesg@ietf.org>
> Cc: draft-ietf-spring-segment-routing@ietf.org; aretana.ietf@gmail.com;
> spring-chairs@ietf.org; martin.vigoureux@nokia.com; spring@ietf.org
> Subject: Alissa Cooper's Discuss on draft-ietf-spring-segment-routing-13:
> (with DISCUSS and COMMENT)
> 
> Alissa Cooper has entered the following ballot position for
> draft-ietf-spring-segment-routing-13: Discuss
> 
> When responding, please keep the subject line intact and reply to all email
> addresses included in the To and CC lines. (Feel free to cut this introductory
> paragraph, however.)
> 
> 
> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
> 
> 
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-spring-segment-routing/
> 
> 
> 
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
> 
> I ended up reading draft-ietf-6man-segment-routing-header in tandem with
> this document, and I have a question arising out of that. The trust model for
> SRv6 outlined in this document appears to be one of reliance on the fact that
> an SRH will only ever be inserted and appear within a single administrative
> domain.
> But Section 5.2.2 of draft-ietf-6man-segment-routing-header talks about an
> SRH being inserted by a device outside of the segment routing domain.
> Which is correct? I think this is an important question because the whole
> trust model for the SR information seems to rely on out-of-band trust
> between participating nodes.
> 
> I also think this is important because there is no discussion in this document
> of the impact of the inclusion of the SR metadata on the fingerprinting of the
> device that inserted it. Section 5.1.4 of draft-ietf-6man-segment-routing-
> header sort of alludes to this but seems to equate the capabilities of an
> active attacker (who can conduct a traceroute) with a passive attacker who
> could passively collect topology/fingerprinting information simply by
> observing SRHes flowing by on the network. If the limitation to a single
> administrative domain is meant to prevent such a passive attack (not sure if
> that is really true, but perhaps the document assumes it?), that's another
> reason that the existence of such a limitation needs to be clarified.
> 
> 
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> 
> Per my DISCUSS comment, I think this document needs to include some
> considerations concerning the additional metadata that SRv6 adds to the
> packet.
> This has implications not just for passive observers but also for any node that
> logs the SRH.
>