Re: Alissa Cooper's No Objection on draft-ietf-bfd-yang-16: (with COMMENT)

"Reshad Rahman (rrahman)" <> Wed, 25 July 2018 14:33 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id D7A07130DF6; Wed, 25 Jul 2018 07:33:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Status: No, score=-14.511 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, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id gWRj-Nwwt5Pe; Wed, 25 Jul 2018 07:33:25 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 66286126BED; Wed, 25 Jul 2018 07:33:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=4644; q=dns/txt; s=iport; t=1532529205; x=1533738805; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=1ciX2LmUdZdi3jX2W+yS6XNZDa80JNVpH2X0Ji7cd8s=; b=B53OutY7pFcWeXtnIKb21/FxIiI3pPmh2+8K4yR37N0TtbkSsoXDstJQ b0nev6XxSSSYLRfzobU08IJf1HgtsasiXQ+levKUxot19dioo7nw0VIQm EzdZ3omkjwKxk0QUtsnYw5Pb5VcWuV03UGx44l73qRsLC0b0jtLry9/OZ o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.51,401,1526342400"; d="scan'208";a="418360378"
Received: from ([]) by with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 25 Jul 2018 14:33:24 +0000
Received: from ( []) by (8.15.2/8.15.2) with ESMTPS id w6PEXOj4023520 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 25 Jul 2018 14:33:24 GMT
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1320.4; Wed, 25 Jul 2018 09:33:23 -0500
Received: from ([]) by ([]) with mapi id 15.00.1320.000; Wed, 25 Jul 2018 09:33:23 -0500
From: "Reshad Rahman (rrahman)" <>
To: Alissa Cooper <>, The IESG <>
CC: "" <>, Jeffrey Haas <>, "" <>, "" <>
Subject: Re: Alissa Cooper's No Objection on draft-ietf-bfd-yang-16: (with COMMENT)
Thread-Topic: Alissa Cooper's No Objection on draft-ietf-bfd-yang-16: (with COMMENT)
Thread-Index: AQHUH6RxGxy8bwmG4ke2wgqkz+XacaSgGlyA
Date: Wed, 25 Jul 2018 14:33:23 +0000
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/10.b.0.180311
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
Content-ID: <>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <>
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: "RTG Area: Bidirectional Forwarding Detection DT" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 25 Jul 2018 14:33:28 -0000

Hi Alissa,

Regarding your comment below on 2.12, I looked at the 4 IANA modules @ iana-if-type, iana-crypt-hash, iana-routing-types and iana-hardware (from the 4 RFCs you listed below) and they all seem to be using ICANN. I will modify the address in draft-ietf-bfd-yang to the address below.


Postal: ICANN
12025 Waterfront Drive, Suite 300
Los Angeles, CA 90094-2536
United States of America

On 2018-07-19, 5:07 PM, "Alissa Cooper" <> wrote:

    Alissa Cooper has entered the following ballot position for
    draft-ietf-bfd-yang-16: 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
    for more information about IESG DISCUSS and COMMENT positions.
    The document, along with other ballot positions, can be found here:
    Looking forward to the discussion of my original DISCUSS in NETMOD. Here it was:
    I will apologize in advance because this document may be sort of a casualty of
    this DISCUSS. I should have raised my point below at least two years ago if not
    four years ago when the first iana-* YANG module was registered, but the
    thought did not occur to me until now.
    It gives me some pause to see the name "iana" embedded in the file name, module
    name, namespace, and prefix of the module being defined in Sec. 2.12. I realize
    there is precedent here, but I question whether tying these kinds of modules
    specifically to IANA as the protocol parameter registry operator by name puts
    them on the most stable deployment footing under all possible circumstances. I
    am personally pleased as punch with the service we get from IANA, but that
    doesn't mean "IANA" will always be the name of the registry operator. The more
    modules that get created with this embedding, the more of them that may need to
    change in the unlikely event that the name of the registry operator changes.
    Lots of RFCs would need to change too, but embedding the name extends the
    potential problem to the modules themselves.
    It wasn't clear to me whether there is some ops-area-wide convention around the
    embedding of "iana" in the names of modules to be maintained by IANA. I don't
    see this specifically referenced in RFC 7950 or RFC 6020. So I'd like to
    discuss whether a different naming convention could be established and used in
    this document and others going forward.
    Some further questions on Sec. 2.12:
    Looking back at the other RFCs that have defined YANG modules to be maintained
    by IANA (7224, 7317, 8294, 8348), they use two different postal addresses for
    ICANN. Why? Furthermore, is "ICANN" really the right contact name, or should it
    be PTI?