[dhcwg] [Editorial Errata Reported] RFC3495 (4128)
RFC Errata System <rfc-editor@rfc-editor.org> Fri, 10 October 2014 21:15 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A27411AD2EC for <dhcwg@ietfa.amsl.com>; Fri, 10 Oct 2014 14:15:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.688
X-Spam-Level:
X-Spam-Status: No, score=-104.688 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_LETTER=-2, RP_MATCHES_RCVD=-0.786, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
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 X55YQWo7AIFf for <dhcwg@ietfa.amsl.com>; Fri, 10 Oct 2014 14:15:33 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 0091F1AD16B for <dhcwg@ietf.org>; Fri, 10 Oct 2014 14:15:32 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 8FD73181C86; Fri, 10 Oct 2014 14:14:37 -0700 (PDT)
To: burcak@juniper.net, paduffy@cisco.com, brian@innovationslab.net, ted.lemon@nominum.com, volz@cisco.com, tomasz.mrugalski@gmail.com
X-PHP-Originating-Script: 6000:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20141010211437.8FD73181C86@rfc-editor.org>
Date: Fri, 10 Oct 2014 14:14:37 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/wORp0I68fdKRxxMD2qKBYtsW4Eg
Cc: dhcwg@ietf.org, volz@cisco.com, rfc-editor@rfc-editor.org
Subject: [dhcwg] [Editorial Errata Reported] RFC3495 (4128)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Oct 2014 21:15:36 -0000
The following errata report has been submitted for RFC3495, "Dynamic Host Configuration Protocol (DHCP) Option for CableLabs Client Configuration". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=3495&eid=4128 -------------------------------------- Type: Editorial Reported by: Bernie Volz <volz@cisco.com> Section: 5.5. Original Text ------------- The PacketCable architecture requires an MTA to authenticate itself to the TSP's network via the Kerberos protocol. A Kerberos Realm name is required at the MTA to permit a DNS lookup for the address of the TSP's Kerberos Key Distribution Center (KDC) entity. The Kerberos Realm name MUST be encoded per the domain style realm name described in RFC 1510 [5]. This realm name MUST be all capital letters and conform to the syntax described in RFC 1035 [3] section 3.1. The sub-option is encoded as follows: Code Len Kerberos Realm Name +-----+-----+-----+-----+ +-----+ | 6 | n | k1 | k2 |...| kn | +-----+-----+-----+-----+ +-----+ Corrected Text -------------- The PacketCable architecture requires an MTA to authenticate itself to the TSP's network via the Kerberos protocol. A Kerberos Realm name is required at the MTA to permit a DNS lookup for the address of the TSP's Kerberos Key Distribution Center (KDC) entity. The Kerberos Realm name MUST be use a domain style realm name described in RFC 1510 [5]. This realm name MUST be all capital letters and be encoded as described in RFC 1035 [3] section 3.1. The sub-option is encoded as follows: Code Len Kerberos Realm Name +-----+-----+-----+-----+ +-----+ | 6 | n | k1 | k2 |...| kn | +-----+-----+-----+-----+ +-----+ Where k1...kn is the "DNS wire" encoded realm name (see RFC 3315, section 8). Thus, the realm "BASIC.1" is encoded as "RFCCORRECTED_TEXT5BASICRFCCORRECTED_TEXT11RFCCORRECTED_TEXT0". Notes ----- This text is not completely clear about how the realm name is to be encoded - as a 'string' or 'fqdn'. RFC 1510 states: Kerberos realms are encoded as GeneralStrings. Realms shall not contain a character with the code 0 (the ASCII NUL). Most realms will usually consist of several components separated by periods (.), in the style of Internet Domain Names, or separated by slashes (/) in the style of X.500 names. And the reference to RFC 1035 section 3.1 is "conform to the syntax" which isn't the same as use this encoding - though I do agree that section 3.1 is mostly about "DNS wire encoding". It is just the use of "encoded" and "confirm to the syntax" combination that makes this unclear. It is believed that the intended encoding is in DNS wire format. And, this should be clarified. 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. -------------------------------------- RFC3495 (draft-ietf-dhc-packetcable-06) -------------------------------------- Title : Dynamic Host Configuration Protocol (DHCP) Option for CableLabs Client Configuration Publication Date : March 2003 Author(s) : B. Beser, P. Duffy, Ed. Category : PROPOSED STANDARD Source : Dynamic Host Configuration Area : Internet Stream : IETF Verifying Party : IESG
- [dhcwg] [Editorial Errata Reported] RFC3495 (4128) RFC Errata System
- Re: [dhcwg] [Editorial Errata Reported] RFC3495 (… Bernie Volz (volz)
- Re: [dhcwg] [Editorial Errata Reported] RFC3495 (… Karl Auer
- Re: [dhcwg] [Editorial Errata Reported] RFC3495 (… Ted Lemon
- Re: [dhcwg] [Editorial Errata Reported] RFC3495 (… Bernie Volz (volz)
- Re: [dhcwg] [Editorial Errata Reported] RFC3495 (… Ted Lemon
- Re: [dhcwg] [Editorial Errata Reported] RFC3495 (… Ted Lemon
- Re: [dhcwg] [Editorial Errata Reported] RFC3495 (… Bernie Volz (volz)
- Re: [dhcwg] [Editorial Errata Reported] RFC3495 (… Ted Lemon
- Re: [dhcwg] [Editorial Errata Reported] RFC3495 (… Bernie Volz (volz)
- Re: [dhcwg] [Editorial Errata Reported] RFC3495 (… Ted Lemon
- Re: [dhcwg] [Editorial Errata Reported] RFC3495 (… Bernie Volz (volz)
- Re: [dhcwg] [Editorial Errata Reported] RFC3495 (… Ted Lemon
- Re: [dhcwg] [Editorial Errata Reported] RFC3495 (… Robert Elz
- Re: [dhcwg] [Editorial Errata Reported] RFC3495 (… Ted Lemon
- Re: [dhcwg] [Editorial Errata Reported] RFC3495 (… Bernie Volz (volz)
- Re: [dhcwg] [Editorial Errata Reported] RFC3495 (… Ted Lemon
- Re: [dhcwg] [Editorial Errata Reported] RFC3495 (… Bernie Volz (volz)
- Re: [dhcwg] [Editorial Errata Reported] RFC3495 (… Ted Lemon
- Re: [dhcwg] [Editorial Errata Reported] RFC3495 (… Ted Lemon
- Re: [dhcwg] [Editorial Errata Reported] RFC3495 (… Bernie Volz (volz)
- Re: [dhcwg] [Editorial Errata Reported] RFC3495 (… Paul Duffy
- Re: [dhcwg] [Editorial Errata Reported] RFC3495 (… Paul Duffy
- Re: [dhcwg] [Editorial Errata Reported] RFC3495 (… Ted Lemon
- [dhcwg] [Errata Held for Document Update] RFC3495… RFC Errata System