RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01

"Templin, Fred L" <Fred.L.Templin@boeing.com> Thu, 04 February 2016 19:37 UTC

Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 56E191ACE31 for <ipv6@ietfa.amsl.com>; Thu, 4 Feb 2016 11:37:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] 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 hmiGs7EkzqtY for <ipv6@ietfa.amsl.com>; Thu, 4 Feb 2016 11:37:03 -0800 (PST)
Received: from blv-mbsout-02.boeing.com (blv-mbsout-02.boeing.com [130.76.32.232]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 082CE1ACE27 for <ipv6@ietf.org>; Thu, 4 Feb 2016 11:37:03 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by blv-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id u14Jb87a009033; Thu, 4 Feb 2016 11:37:08 -0800
Received: from XCH-BLV-202.nw.nos.boeing.com (xch-blv-202.nw.nos.boeing.com [10.57.37.69]) by blv-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id u14Jb0tW008975 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Thu, 4 Feb 2016 11:37:00 -0800
Received: from XCH-BLV-105.nw.nos.boeing.com ([169.254.5.221]) by XCH-BLV-202.nw.nos.boeing.com ([169.254.2.106]) with mapi id 14.03.0235.001; Thu, 4 Feb 2016 11:36:54 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Bob Hinden <bob.hinden@gmail.com>
Subject: RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
Thread-Topic: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
Thread-Index: AQHRX2tT80dfpGCQDUCIhA2edhybgJ8cKO6QgAAMGWCAAIvjAP//enWAgACM6wD//34U0A==
Date: Thu, 04 Feb 2016 19:36:53 +0000
Message-ID: <2134F8430051B64F815C691A62D983183395E0F9@XCH-BLV-105.nw.nos.boeing.com>
References: <9C0F366C-4887-4A63-8422-1C370F9CBD3E@employees.org> <DB69251C-55E5-4577-9C0A-0541A8946940@cisco.com> <2134F8430051B64F815C691A62D983183395DE77@XCH-BLV-105.nw.nos.boeing.com> <2134F8430051B64F815C691A62D983183395DEF3@XCH-BLV-105.nw.nos.boeing.com> <8E7CAC70-9193-43B2-8A47-0C731B5464CA@cisco.com> <2134F8430051B64F815C691A62D983183395DFFF@XCH-BLV-105.nw.nos.boeing.com> <4E0B0B8D-4AE2-47F2-88F0-20589DB48BE1@gmail.com>
In-Reply-To: <4E0B0B8D-4AE2-47F2-88F0-20589DB48BE1@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/hVWLVSiFweKgYD5iqF_A7B09sic>
Cc: IPv6 List <ipv6@ietf.org>, "Fred Baker (fred)" <fred@cisco.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Feb 2016 19:37:04 -0000

Hi Bob,

> -----Original Message-----
> From: Bob Hinden [mailto:bob.hinden@gmail.com]
> Sent: Thursday, February 04, 2016 11:16 AM
> To: Templin, Fred L
> Cc: Bob Hinden; Fred Baker (fred); IPv6 List
> Subject: Re: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
> 
> Fred,
> 
> > On Feb 4, 2016, at 10:58 AM, Templin, Fred L <Fred.L.Templin@boeing.com> wrote:
> >
> > Hi Fred,
> >
> >> -----Original Message-----
> >> From: Fred Baker (fred) [mailto:fred@cisco.com]
> >> Sent: Thursday, February 04, 2016 10:50 AM
> >> To: Templin, Fred L
> >> Cc: Bob Hinden; 6man WG
> >> Subject: Re: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
> >>
> >>
> >>> On Feb 4, 2016, at 10:37 AM, Templin, Fred L <Fred.L.Templin@boeing.com> wrote:
> >>>
> >>> Your text could be modified by simply adding the word "accurate" as follows:
> >>>
> >>> "It defines a method for Packetization Layer Path MTU Discovery (PLPMTUD)
> >>>   designed for use in environments in which delivery of accurate ICMP messages
> >>>   to a host are not assured."
> >>
> >> So you added the word "accurate". Anything else?
> >>
> >> My question would be what makes an ICMP "accurate", and how the host might or might not determine accuracy. As near as I can
> tell,
> >> RFC 1981 says that if a host receives an ICMP Packet Too Big, it should make the packet smaller. If the ICMP has been spoofed,
> unless
> >> the spoofer has done something really egregious, I don't know how the receiving host would know that.
> >
> > ICMP spoofing is exactly the point. But, it is not up to the host to determine
> > whether an ICMP is accurate - it is up to the host to determine whether it is
> > in an environment in which delivery of accurate ICMP messages is not assured.
> >
> >> Given that, I don't think the wording change helps.
> >
> > Without "accurate", the text does not address failure mode 2).
> 
> How is a host supposed to know if it is an “accurate ICMP message”?

Repeating what I said with a necessary correction:

  "But, it is not up to the host to determine
    whether an ICMP is accurate - it is up to the host to determine whether it is
    using a path for which delivery of accurate ICMP message is not assured."

> This is starting to read to me like creating a new specification, not advancing the one we have now.

Not at all. You were only too happy to accept Fred Baker's suggestion; I
have simply modified the aspects of his suggestion that were lacking
and/or inaccurate.

Thanks - Fred
fred.l.templin@boeing.com

> Bob