IETF Logo Mail Archive

Re: [Lsr] Benjamin Kaduk's Discuss on draft-ietf-ospf-ospfv3-segment-routing-extensions-20: (with DISCUSS and COMMENT)

Peter Psenak <ppsenak@cisco.com> Tue, 08 January 2019 16:59 UTC

Return-Path: <ppsenak@cisco.com>
X-Original-To: lsr@ietfa.amsl.com
Delivered-To: lsr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 84B45130F05; Tue, 8 Jan 2019 08:59:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.566
X-Spam-Level:
X-Spam-Status: No, score=-14.566 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.065, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, 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 3EDpb0z-TMP1; Tue, 8 Jan 2019 08:59:01 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 28B90130EBF; Tue, 8 Jan 2019 08:58:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=889; q=dns/txt; s=iport; t=1546966739; x=1548176339; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=jn/JZTzI/s/VBIdy554XNi0ZnLXe4o+YFq2o972YO+8=; b=TNKj/7LzIhTcSDGy5UM7murWhEgSAp7ugvW7xRyo41LSzE7ibyXFDZpS PjzyhnkYuRSI3H7yyw/SmQHO1i0PPPbQ/lY11qFVPLrgYhzXUfLciHi+R bwZaWq2zxZI9GZoyOGFTXda+/qBJGuRSOnViROtKmjJpXwlvq/eBPgyyP 4=;
X-IronPort-AV: E=Sophos;i="5.56,454,1539648000"; d="scan'208";a="9321525"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 08 Jan 2019 16:58:56 +0000
Received: from [10.60.140.54] (ams-ppsenak-nitro5.cisco.com [10.60.140.54]) by aer-core-2.cisco.com (8.15.2/8.15.2) with ESMTP id x08GwtbV010326; Tue, 8 Jan 2019 16:58:56 GMT
To: Benjamin Kaduk <kaduk@mit.edu>
References: <154398144445.4943.7198735398003216566.idtracker@ietfa.amsl.com> <5C079200.1030701@cisco.com> <20181217055358.GC94620@kduck.kaduk.org> <69190220-4994-f9c9-4adf-5016abf3a39b@cisco.com> <03e6354b-c606-fc4a-bbf2-3d59fa1cb774@cisco.com> <20181222042939.GW94620@kduck.kaduk.org> <8D31ADF0-FA83-4B23-805E-76145BF914C1@cisco.com> <f3dff5f1-434c-431d-15a3-5fa7462f5572@cisco.com> <20190108143354.GX28515@kduck.kaduk.org> <a014f4fc-f730-a3a6-f169-b5d1fbc133d6@cisco.com> <20190108161620.GY28515@kduck.kaduk.org>
Cc: "Acee Lindem (acee)" <acee@cisco.com>, The IESG <iesg@ietf.org>, "draft-ietf-ospf-ospfv3-segment-routing-extensions@ietf.org" <draft-ietf-ospf-ospfv3-segment-routing-extensions@ietf.org>, "aretana.ietf@gmail.com" <aretana.ietf@gmail.com>, "lsr-chairs@ietf.org" <lsr-chairs@ietf.org>, "lsr@ietf.org" <lsr@ietf.org>
From: Peter Psenak <ppsenak@cisco.com>
Message-ID: <f59eabcb-00dc-7008-d5f9-567d8b232e3b@cisco.com>
Date: Tue, 08 Jan 2019 17:58:55 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <20190108161620.GY28515@kduck.kaduk.org>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Outbound-SMTP-Client: 10.60.140.54, ams-ppsenak-nitro5.cisco.com
X-Outbound-Node: aer-core-2.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/XRE5hyiJSpScfaKZd4c7bdq3TLw>
Subject: Re: [Lsr] Benjamin Kaduk's Discuss on draft-ietf-ospf-ospfv3-segment-routing-extensions-20: (with DISCUSS and COMMENT)
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Link State Routing Working Group <lsr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsr>, <mailto:lsr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsr/>
List-Post: <mailto:lsr@ietf.org>
List-Help: <mailto:lsr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsr>, <mailto:lsr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jan 2019 16:59:04 -0000

Hi Benjamin,

On 08/01/2019 17:16 , Benjamin Kaduk wrote:

>
> Well, there's a few options, and I don't want to try to dictate my
> preferences onto your document.  What seems simplest to me would be to just
> bite the bullet and establish an IANA registry for these AF values, but if
> you wanted to do something else like saying that they are "beyond the scope
> of this specification but may occur in future standards-track work" that
> would also be fine.  I'm just trying to avoid some reader seeing "beyond
> the scope of this specification" and thinking they can do whatever they
> want and pick their own codepoint value to squat on.

would this be fine with you:


"Prefix encoding for other address families is beyond the scope
of this specification. Other address families may be defined in the 
future standard-track IETF specifications."

thanks,
Peter

v2.23.0 | Report a Bug | By Email