Re: Last Call: <draft-arkko-trip-registry-update-00.txt> (Update to the TRIP IANA Registry Rules Regarding Postal Addresses) to Informational RFC
Ben Campbell <ben@nostrum.com> Mon, 03 December 2018 14:17 UTC
Return-Path: <ben@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82CD8123FFD; Mon, 3 Dec 2018 06:17:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.878
X-Spam-Level:
X-Spam-Status: No, score=-1.878 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
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 gWfU-UQadnqB; Mon, 3 Dec 2018 06:17:09 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 40E19130E2F; Mon, 3 Dec 2018 06:17:09 -0800 (PST)
Received: from [10.80.113.142] (mobile-166-177-121-255.mycingular.net [166.177.121.255]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id wB3EH6TP039184 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 3 Dec 2018 08:17:08 -0600 (CST) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host mobile-166-177-121-255.mycingular.net [166.177.121.255] claimed to be [10.80.113.142]
Content-Type: multipart/alternative; boundary="Apple-Mail-8AD73BC7-770D-45A2-879B-811C726C4C7D"
Mime-Version: 1.0 (1.0)
Subject: Re: Last Call: <draft-arkko-trip-registry-update-00.txt> (Update to the TRIP IANA Registry Rules Regarding Postal Addresses) to Informational RFC
From: Ben Campbell <ben@nostrum.com>
X-Mailer: iPad Mail (16B92)
In-Reply-To: <CADnDZ8_aUXGv+1NKaEhtzRG5usry-WEhA8rH+pN_kGtobO5KBg@mail.gmail.com>
Date: Mon, 03 Dec 2018 08:17:01 -0600
Cc: ietf <ietf@ietf.org>, draft-arkko-trip-registry-update@ietf.org, iesg@ietf.org
Content-Transfer-Encoding: 7bit
Message-Id: <4A2603BC-697E-411F-98AA-8D2344EA59A8@nostrum.com>
References: <154361542734.27535.10383183340180057481.idtracker@ietfa.amsl.com> <CADnDZ8_aUXGv+1NKaEhtzRG5usry-WEhA8rH+pN_kGtobO5KBg@mail.gmail.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Q7v-Wa78n5ypB7DcJAt9GIJN168>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Dec 2018 14:17:16 -0000
I think you are correct on this point. I suspect this was just an oversight; at least it was on my part. If the authors agree, we will make that change now and restart the IETF last call as standards track. Thanks for catching this early in the last call period. Ben. > On Dec 3, 2018, at 1:43 AM, Abdussalam Baryun <abdussalambaryun@gmail.com> wrote: > > The draft should be standard track to update RFC3219 standard. IMHO, while this draft is informational > it cannot update a standard RFC. I a not sure if this has been done in the past, but if it was done I disagree with such RFCs. > > I think that the IANA consideration section is part of the standard, and I don't consider it just information that may not affect the standard. I think updating it may affect any standard/technology. > > Best Regards, > AB > >> On Sat, Dec 1, 2018 at 12:04 AM The IESG <iesg-secretary@ietf.org> wrote: >> >> The IESG has received a request from an individual submitter to consider the >> following document: - 'Update to the TRIP IANA Registry Rules Regarding >> Postal Addresses' >> <draft-arkko-trip-registry-update-00.txt> as Informational RFC >> >> The IESG plans to make a decision in the next few weeks, and solicits final >> comments on this action. Please send substantive comments to the >> ietf@ietf.org mailing lists by 2018-12-28. Exceptionally, comments may be >> sent to iesg@ietf.org instead. In either case, please retain the beginning of >> the Subject line to allow automated sorting. >> >> Abstract >> >> >> This memo updates the IANA registry rules for the Telephony Routing >> over IP (TRIP) protocol, by no longer requiring that postal addresses >> be included in contact information. >> >> This memo updates RFC 3219. >> >> >> >> >> The file can be obtained via >> https://datatracker.ietf.org/doc/draft-arkko-trip-registry-update/ >> >> IESG discussion can be tracked via >> https://datatracker.ietf.org/doc/draft-arkko-trip-registry-update/ballot/ >> >> >> No IPR declarations have been submitted directly on this I-D. >> >> >> >>
- Re: Last Call: <draft-arkko-trip-registry-update-… Russ Housley
- Re: Last Call: <draft-arkko-trip-registry-update-… Paul Wouters
- Re: Last Call: <draft-arkko-trip-registry-update-… Russ Housley
- Re: Last Call: <draft-arkko-trip-registry-update-… Jari Arkko
- Re: Last Call: <draft-arkko-trip-registry-update-… Abdussalam Baryun
- Re: Last Call: <draft-arkko-trip-registry-update-… Ben Campbell
- Re: Last Call: <draft-arkko-trip-registry-update-… Jari Arkko