[dhcwg] RFC3315 and Hop Limit
Michael Richardson <mcr+ietf@sandelman.ca> Tue, 21 October 2014 21:53 UTC
Return-Path: <mcr@sandelman.ca>
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 59E2A1A87D2 for <dhcwg@ietfa.amsl.com>; Tue, 21 Oct 2014 14:53:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.698
X-Spam-Level:
X-Spam-Status: No, score=0.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_92=0.6, MIME_NO_TEXT=1.999, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, T_TVD_MIME_NO_HEADERS=0.01] autolearn=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 pMW_i6CQUTy1 for <dhcwg@ietfa.amsl.com>; Tue, 21 Oct 2014 14:53:56 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 115B31A87C4 for <dhcwg@ietf.org>; Tue, 21 Oct 2014 14:53:56 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 544E720012 for <dhcwg@ietf.org>; Tue, 21 Oct 2014 17:54:46 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 69F7863A84; Tue, 21 Oct 2014 17:53:54 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 506DB63A82 for <dhcwg@ietf.org>; Tue, 21 Oct 2014 17:53:54 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: dhcwg <dhcwg@ietf.org>
X-Attribution: mcr
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha1"; protocol="application/pgp-signature"
Date: Tue, 21 Oct 2014 17:53:54 -0400
Message-ID: <4117.1413928434@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/SpvLb1ZqG8lJmIEIIXqfbWEuOS0
Subject: [dhcwg] RFC3315 and Hop Limit
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: Tue, 21 Oct 2014 21:53:57 -0000
I could not find any advice in RFC3315 as to what to set the IPv6 HOP Limit to for multicast'ed DHCPv6 messages. I would have thought that the sender should set it to 255, and the sender should validate that it is 255, to be sure that it's onlink. This is what mDNS/Bonjour does, but maybe 3315 predates that thinking. Should 3315bis say something different? (Clearly, it has to be backwards compatible for awhile) -- Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works -= IPv6 IoT consulting =-
- [dhcwg] RFC3315 and Hop Limit Michael Richardson
- Re: [dhcwg] RFC3315 and Hop Limit Ralph Droms
- Re: [dhcwg] RFC3315 and Hop Limit Michael Richardson