Re: [Lsr] Benjamin Kaduk's No Objection on draft-ietf-ospf-lls-interface-id-08: (with COMMENT)

"Acee Lindem (acee)" <acee@cisco.com> Thu, 25 October 2018 13:51 UTC

Return-Path: <acee@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 ED306130E5C; Thu, 25 Oct 2018 06:51:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level:
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, 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 O_keWL_JlKvt; Thu, 25 Oct 2018 06:51:44 -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 1145A120072; Thu, 25 Oct 2018 06:51:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1972; q=dns/txt; s=iport; t=1540475504; x=1541685104; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=Pf54eqPyGi1pSB9jnhYxTHD0Uf8AO1rsnpAZ68AuL1E=; b=UxtFNIPxmqrh94QCkx9nGZn8bxV7WyvjgQVsTpxQS9aBEUCvKoXimnVb HTaLtYy/56c32uZNF9681R0hhA60afPvdY7M4d9c6sK0Wub0ptmGaboXZ H9VqBcaL3FDnZpfytKyEYx990WWIAZwNTMkkXELCm85FQ5V4e6ME7hOML k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ADAAC7ydFb/5tdJa1jDgsBAQEBAQEBAQEBAQEHAQEBAQEBgVEEAQEBAQELAYIEZn8oCoNriBiMGIFol0EUgWYLAQEjhEkCF4J5ITQNDQEDAQECAQECbRwMhTsGIxFFEAIBCBoCJgICAjAVEAIEAQ0FgyEBggEPpxyBLoQ+QIUeBYELilsXggCBOAwTgkyDGwIBAgGBKgELBwGDIjGCJgKIdoFqlBYJAoZmihUYgVKEdol7jGqJeAIRFIEmHThkWBEIcBVlAYJBgk+ISoUEOm8BiXUPF4EIgR8BAQ
X-IronPort-AV: E=Sophos;i="5.54,424,1534809600"; d="scan'208";a="386803629"
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; 25 Oct 2018 13:51:43 +0000
Received: from XCH-RTP-011.cisco.com (xch-rtp-011.cisco.com [64.101.220.151]) by rcdn-core-4.cisco.com (8.15.2/8.15.2) with ESMTPS id w9PDpgpq016613 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 25 Oct 2018 13:51:43 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-011.cisco.com (64.101.220.151) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Thu, 25 Oct 2018 09:51:42 -0400
Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1395.000; Thu, 25 Oct 2018 09:51:42 -0400
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Benjamin Kaduk <kaduk@mit.edu>, The IESG <iesg@ietf.org>
CC: "draft-ietf-ospf-lls-interface-id@ietf.org" <draft-ietf-ospf-lls-interface-id@ietf.org>, Yingzhen Qu <yingzhen.ietf@gmail.com>, "aretana.ietf@gmail.com" <aretana.ietf@gmail.com>, "lsr-chairs@ietf.org" <lsr-chairs@ietf.org>, "lsr@ietf.org" <lsr@ietf.org>
Thread-Topic: Benjamin Kaduk's No Objection on draft-ietf-ospf-lls-interface-id-08: (with COMMENT)
Thread-Index: AQHUbF1j4UjYPcg/BUig1Pn6aaXdlKUv+vgA
Date: Thu, 25 Oct 2018 13:51:42 +0000
Message-ID: <58B0C6F5-6153-4117-B214-176A9B68189C@cisco.com>
References: <154047014077.16281.149253858167058600.idtracker@ietfa.amsl.com>
In-Reply-To: <154047014077.16281.149253858167058600.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.116.152.200]
Content-Type: text/plain; charset="utf-8"
Content-ID: <37565EC40E25254E8BF60822207288D6@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Outbound-SMTP-Client: 64.101.220.151, xch-rtp-011.cisco.com
X-Outbound-Node: rcdn-core-4.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/gOW3TsqcwMDmNfmh3tiTSTuvP7U>
Subject: Re: [Lsr] Benjamin Kaduk's No Objection on draft-ietf-ospf-lls-interface-id-08: (with 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: Thu, 25 Oct 2018 13:51:46 -0000

Hi Ben, 

On 10/25/18, 8:22 AM, "Benjamin Kaduk" <kaduk@mit.edu> wrote:

    Benjamin Kaduk has entered the following ballot position for
    draft-ietf-ospf-lls-interface-id-08: No Objection
    
    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-ospf-lls-interface-id/
    
    
    
    ----------------------------------------------------------------------
    COMMENT:
    ----------------------------------------------------------------------
    
    Sending a new type of information to the peer usually involves a privacy
    considerations analysis.  I don't expect there to be anything worrisome
    here, but some text in the document indicating that the analysis has been
    done would be reassuring.

Can you suggest some text? I was thinking:

   Since the scope of the interface ID is limited to the advertising OSPF router 
   uniquely identifying links, there are no privacy concerns associated with its
   advertisement.

Thanks,
Acee