[homenet] [Technical Errata Reported] RFC7788 (4718)
RFC Errata System <rfc-editor@rfc-editor.org> Fri, 24 June 2016 01:33 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 612A312D648 for <homenet@ietfa.amsl.com>; Thu, 23 Jun 2016 18:33:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.328
X-Spam-Level:
X-Spam-Status: No, score=-108.328 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.426, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 mMiGpO2OlwEO for <homenet@ietfa.amsl.com>; Thu, 23 Jun 2016 18:33:25 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8BCB812D189 for <homenet@ietf.org>; Thu, 23 Jun 2016 18:33:25 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 74F1BB80D98; Thu, 23 Jun 2016 18:33:25 -0700 (PDT)
To: markus.stenberg@iki.fi, cyrus@openwrt.org, pierre.pfister@darou.fr, suresh.krishnan@ericsson.com, terry.manderson@icann.org, ray@bellis.me.uk, mark@townsley.net
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20160624013325.74F1BB80D98@rfc-editor.org>
Date: Thu, 23 Jun 2016 18:33:25 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/mAbJ99Ue-p9hbCmgJaRvwSVNd8U>
Cc: homenet@ietf.org, rdroms.ietf@gmail.com, rfc-editor@rfc-editor.org
Subject: [homenet] [Technical Errata Reported] RFC7788 (4718)
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jun 2016 01:33:28 -0000
The following errata report has been submitted for RFC7788, "Home Networking Control Protocol". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=7788&eid=4718 -------------------------------------- Type: Technical Reported by: Ralph Droms <rdroms.ietf@gmail.com> Section: GLOBAL Original Text ------------- 7.4. Multicast DNS Proxy The designated Multicast DNS (mDNS) [RFC6762] proxy on a Common Link is elected based on the capabilities described in Section 4. [...] The elected router MUST provide an mDNS proxy on the given link and announce it as described in Section 8. [...] 8. Naming and Service Discovery [...] Each HNCP router SHOULD provide and announce an auto-generated or user-configured name for each internal Common Link (Section 6.1) for which it is the designated DHCPv4, stateful DHCPv6 server, mDNS proxy, or for which it provides forward or reverse DNS services on behalf of connected devices. [...] 10.1. HNCP-Version TLV [...] M-capability: Priority value used for electing the on-link mDNS [RFC6762] proxy. It MUST be set to 0 if the router is not capable of proxying mDNS, otherwise it SHOULD be set to 4 but MAY be set to any value from 1 to 7 to indicate a non-default priority Corrected Text -------------- 7.4. Multicast DNS Hybrid Proxy The designated Multicast DNS (mDNS) [RFC6762] Hybrid Proxy [draft-ietf-dnssd-hybrid-03] on a Common Link is elected based on the capabilities described in Section 4. [...] The elected router MUST provide an mDNS Hybrid Proxy on the given link and announce it as described in Section 8. [...] 8. Naming and Service Discovery [...] Each HNCP router SHOULD provide and announce an auto-generated or user-configured name for each internal Common Link (Section 6.1) for which it is the designated DHCPv4, stateful DHCPv6 server, mDNS Hybrid Proxy, or for which it provides forward or reverse DNS services on behalf of connected devices. [...] 10.1. HNCP-Version TLV [...] M-capability: Priority value used for electing the on-link mDNS Hybrid Proxy. It MUST be set to 0 if the router is not capable of providing an mDNS Hybrid Proxy service, otherwise it SHOULD be set to 4 but MAY be set to any value from 1 to 7 to indicate a non-default priority Notes ----- RFC 7788 refers to "Multicast DNS (mDNS) proxy" and gives a citation for RFC 6762. RFC 6762, "Multicast DNS," defines multicast DNS and mentions (without an explicit definition) a "Multicast DNS Proxy" service. This proxy service is also known as "Bonjour Sleep Proxy" [https://en.wikipedia.org/wiki/Bonjour_Sleep_Proxy] However, the intent of RFC 7788 is to specify the operation and advertisement of the multicast DNS Hybrid Proxy Service, as defined in draft-ietf-dnssd-hybrid-03, "Hybrid Unicast/Multicast DNS-Based Service Discovery." This errata corrects the mentions of "mDNS proxy" in RFC 7788 to "Hybrid Proxy." draft-ietf-dnssd-hybrid-03 should also be added to the Normative References. Instructions: ------------- This erratum is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party (IESG) can log in to change the status and edit the report, if necessary. -------------------------------------- RFC7788 (draft-ietf-homenet-hncp-10) -------------------------------------- Title : Home Networking Control Protocol Publication Date : April 2016 Author(s) : M. Stenberg, S. Barth, P. Pfister Category : PROPOSED STANDARD Source : Home Networking Area : Internet Stream : IETF Verifying Party : IESG
- [homenet] [Technical Errata Reported] RFC7788 (47… RFC Errata System