Re: [dhcwg] I-D Action: draft-ietf-dhc-rfc3315bis-09.txt - questions about Solicit Prefix Delegation

"Bernie Volz (volz)" <> Sat, 15 July 2017 06:45 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 50FA712EB69 for <>; Fri, 14 Jul 2017 23:45:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -14.521
X-Spam-Status: No, score=-14.521 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, 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 BIt5L7Z2RDjE for <>; Fri, 14 Jul 2017 23:45:27 -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 ACEDC129AAD for <>; Fri, 14 Jul 2017 23:45:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=33366; q=dns/txt; s=iport; t=1500101126; x=1501310726; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=DTK9MAGiAHuadGIJxw2+9x5Df64agiIksjGt0K9M+dE=; b=IpZYkNapoSyfS5JkZIaYmHPeGNKSTLE7LrYlrlWi7XU2kEIuafQT03iY tB7l66bNv4a6zraJ0BdGbxZvsXl1R+ADSppI8Yk60cE1/NQac9ZsuqW5w g7n8r0Y+ZMfAJ5ZMqp2V1nk1YRoI5n8rBpWwGUh5z4gB+UsBE3zinBF3U U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.40,362,1496102400"; d="scan'208,217";a="273917732"
Received: from ([]) by with ESMTP/TLS/DHE-RSA-AES256-SHA; 15 Jul 2017 06:45:25 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id v6F6jP0g000975 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Sat, 15 Jul 2017 06:45:25 GMT
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1210.3; Sat, 15 Jul 2017 01:45:24 -0500
Received: from ([]) by ([]) with mapi id 15.00.1210.000; Sat, 15 Jul 2017 01:45:24 -0500
From: "Bernie Volz (volz)" <>
To: Ted Lemon <>, Alexandre Petrescu <>
CC: =?utf-8?B?VsOtemRhbCBBbGXFoQ==?= <>, dhcwg <>
Thread-Topic: [dhcwg] I-D Action: draft-ietf-dhc-rfc3315bis-09.txt - questions about Solicit Prefix Delegation
Date: Sat, 15 Jul 2017 06:45:24 +0000
Message-ID: <>
References: <> <> <> <> <> <> <> <> <> <> <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/f.23.0.170610
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_B5F9980A3BF04069939A75683E01D643ciscocom_"
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [dhcwg] I-D Action: draft-ietf-dhc-rfc3315bis-09.txt - questions about Solicit Prefix Delegation
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sat, 15 Jul 2017 06:45:29 -0000

I agree with Ted.

And, it does appear that kernels will default to 1 for a hop limit with multicast:

“By default, IP multicast datagrams are sent with a hop limit of one, which prevents the datagrams from being forwarded beyond a single subnetwork.”

Thus, it is the multicast destination (ff02::1:2 for DHCPv6 packets) that controls the (default) hop limit.

Also note that 2460bis has:

      Hop Limit           8-bit unsigned integer.  Decremented by 1 by

                          each node that forwards the packet.  When

                          forwarding, the packet is discarded if Hop

                          Limit was zero when received or is decremented

                          to zero.  A node that is the destination of a

                          packet should not discard a packet with hop

                          limit equal to zero, it should process the

                          packet normally.

RFC 2460 only has the 1st sentence, so it was clarified as to what a node that receives a packet should do if the hop count is 0 – process it.

  *   Bernie

From: Ted Lemon <>
Date: Saturday, July 15, 2017 at 6:36 AM
To: Alexandre Petrescu <>
Cc: Vízdal Aleš <>cz>, "" <>rg>, Bernie Volz <>
Subject: Re: [dhcwg] I-D Action: draft-ietf-dhc-rfc3315bis-09.txt - questions about Solicit Prefix Delegation

Alexandre, it appears to me that you are asking the DHC working group to make a change to the DHCPv6 spec in order to solve a problem you don't know exists in an IPv6 layer 2 implementation.   I think that this is wrong-headed on two fronts.   First, you are speculating that the problem exists.  Find out whether the problem exists, don't speculate.   Second, the problem is not in DHCP, if it does exist--it is in an IP implementation.   So fix the implementation--don't ask for a change to the DHCP spec.

On Fri, Jul 14, 2017 at 9:50 PM, Alexandre Petrescu <<>> wrote:

Le 14/07/2017 à 21:26, Vízdal Aleš a écrit :

On 14 Jul 2017, at 21:15, Alexandre Petrescu <<>> wrote:
Le 14/07/2017 à 20:35, Ted Lemon a écrit : So are the DHCP clients you are talking about setting the IP header hop count to
 0/1, or the DHCP header hop-count field to 0/1?   That is, what
 is the behavior you are concerned about, and why do you think it
 might cause a problem in this case?

Some clients I am talking about issue DHCP Solicit with Hop Limit field in the IPv6 base header (not DHCP UDP header) with value 1.

This Solicit is sent on a cellular network.  The cellular network encapsulates at some point in IPv4, and further decapsulates.  The
 encapsulation protocol is called "GTPU" by some non-wireshark packet dump format, with fields like "TEID", "GTP_TPDU_MSG".  This
 cellular network does not offer IPv4 access to end user, it only offers IPv6.

There is no GTP RFC.

GTP aka GPRS Tunnelling Protocol has been specified by 3GPP.

It starts at the eNodeB and terminates at the PGW where the DHCP server/relay would sit.

You see, I am also told that my "MT" ("Mobile Terminal"?) terminates
GTP.  I guess both are possible (terminate some times at eNodeB and
other times at MT).

Or otherwise the expression "terminate at" may have different meanings
to different people.
There is an RFC for "Generic Packet Tunnelling in IPv6".  This RFC
 says that encap/decap decrements the Hop Limit.

This raises a potential speculation that the network drops an incoming packet that has Hop Limit 1.

It may be that the GTP encapsulation (no RFC) does not decrement the Hop Limit of a packet-to-be-encapsulated.  In this case there is no problem with DHCP Solicit having Hop Limit 1.

It shall keep the packet as-is, since it is not visible from user/data-plane point of view.

I dont understand that.  Not sure what you mean by user-data planes.

The IP Hop Limit is in the IP header.  Some IP tunnelling mechanisms do
touch the Hop Limit of the encapsulated packet.  Why would GTP be
different than the other IP tunnelling mechanisms?
I suggest a deep dive into 3GPP specs ...

It is certainly advantageous to understand the 3GPP specs.

But I'd rather consider putting that into an Internet Draft.



On Fri, Jul 14, 2017 at 8:32 PM, Alexandre Petrescu <<> <<>>> wrote: Le 13/07/2017 à 23:14, Ted Lemon a écrit : On Jul 13, 2017 16:01, "Alexandre Petrescu" <<> <<>> <<> <<>>>> wrote: My oppinion is to
 make DHCP spec Hop Limit > 1.  In order to make sure that the encap/decap of DHCP Solicit in IPv4 GTP happening on a cellular link does not drop it to 0 upon decap. If a link local sourced multicast with a hop limit of one is dropped between sender and receiver, ip is broken on that link, ne c'est pas? If that link is a real link then yes - ip is broken on that link. But if the link is a virtual link - like when on a tunnel - then it may be that tunnel works or no. Alex

_______________________________________________ dhcwg mailing list<>

Zásady komunikace, které společnost T-Mobile Czech Republic a.s. užívá při sjednávání smluv, jsou uvedeny zde<>.

Není-li v zásadách uvedeno jinak, nepředstavuje tato zpráva konečný
návrh na uzavření či změnu smlouvy ani přijetí takového návrhu. The communication principles which T-Mobile Czech Republic a.s. applies when negotiating contracts are defined here<>.

Unless otherwise stated in the principles, this message does not
constitute the final offer to contract or an amendment of a contract
 or acceptance of such offer.