Re: [MBONED] Éric Vyncke's No Objection on draft-ietf-mboned-driad-amt-discovery-10: (with COMMENT)

"Holland, Jake" <jholland@akamai.com> Tue, 17 December 2019 23:04 UTC

Return-Path: <jholland@akamai.com>
X-Original-To: mboned@ietfa.amsl.com
Delivered-To: mboned@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A6DD4120128; Tue, 17 Dec 2019 15:04:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=akamai.com
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 u5ypCNufNK2l; Tue, 17 Dec 2019 15:04:30 -0800 (PST)
Received: from mx0a-00190b01.pphosted.com (mx0a-00190b01.pphosted.com [IPv6:2620:100:9001:583::1]) (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 86A231200B1; Tue, 17 Dec 2019 15:04:30 -0800 (PST)
Received: from pps.filterd (m0050093.ppops.net [127.0.0.1]) by m0050093.ppops.net-00190b01. (8.16.0.42/8.16.0.42) with SMTP id xBHN02eh028938; Tue, 17 Dec 2019 23:04:28 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=jan2016.eng; bh=Egb8+zO01pKkDPm90lTYY8QqmvxAxNeUDKsecsj6ZBA=; b=b0iiXihib+OwEgU6onb5pYD+vCkPgnB5fwMd9YeqN7ci7ZDDGdF3Ky+mBTXMNZO+JgvV KV1YC/iJPC1L+sPezKe/T104cL/wmN+O207veZO2WVm+iN4NTNbiyQe5zxRqquvWerbv cSvO+xPRLTSeu9JAU3l1K4hiIUvDGBgV4nJEljTWi0lJKN/Hu3FHcqmX4/3HE30efBi6 k9Lnv4piMjShmQ85M0YY09XMxvPvZfJaOX8SMjlOOIiEkgppagkf0BAeDy+YS4Exv1Q3 Tl/2FsnPJpW4UWZmM28KlOTCBZWeOkzGvUUbOEGtaozpdaXGF7wdD/J06CCxeZFa5MBu oA==
Received: from prod-mail-ppoint8 (prod-mail-ppoint8.akamai.com [96.6.114.122] (may be forged)) by m0050093.ppops.net-00190b01. with ESMTP id 2wvqvupe2b-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 17 Dec 2019 23:04:28 +0000
Received: from pps.filterd (prod-mail-ppoint8.akamai.com [127.0.0.1]) by prod-mail-ppoint8.akamai.com (8.16.0.27/8.16.0.27) with SMTP id xBHMlY9I014752; Tue, 17 Dec 2019 18:04:27 -0500
Received: from email.msg.corp.akamai.com ([172.27.165.113]) by prod-mail-ppoint8.akamai.com with ESMTP id 2wvuy1nb9q-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Tue, 17 Dec 2019 18:04:27 -0500
Received: from ustx2ex-dag1mb6.msg.corp.akamai.com (172.27.165.124) by ustx2ex-dag1mb1.msg.corp.akamai.com (172.27.165.119) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 17 Dec 2019 17:04:26 -0600
Received: from ustx2ex-dag1mb6.msg.corp.akamai.com ([172.27.165.124]) by ustx2ex-dag1mb6.msg.corp.akamai.com ([172.27.165.124]) with mapi id 15.00.1473.005; Tue, 17 Dec 2019 15:04:26 -0800
From: "Holland, Jake" <jholland@akamai.com>
To: Éric Vyncke <evyncke@cisco.com>, The IESG <iesg@ietf.org>
CC: "draft-ietf-mboned-driad-amt-discovery@ietf.org" <draft-ietf-mboned-driad-amt-discovery@ietf.org>, "mboned-chairs@ietf.org" <mboned-chairs@ietf.org>, "mboned@ietf.org" <mboned@ietf.org>
Thread-Topic: [MBONED] Éric Vyncke's No Objection on draft-ietf-mboned-driad-amt-discovery-10: (with COMMENT)
Thread-Index: AQHVtRTSSAQJ9cKQpEyAczn/EUfrAae+8n2A
Date: Tue, 17 Dec 2019 23:04:26 +0000
Message-ID: <1BA9032C-767B-4280-A1EC-0CE76CAAC412@akamai.com>
References: <157661285538.26445.14640422767755463731.idtracker@ietfa.amsl.com>
In-Reply-To: <157661285538.26445.14640422767755463731.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.20.0.191208
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.82.210]
Content-Type: text/plain; charset="utf-8"
Content-ID: <BB458B38C9826848A3835CD1E7DAEEA7@akamai.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-12-17_04:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1911140001 definitions=main-1912170182
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.95,18.0.572 definitions=2019-12-17_04:2019-12-17,2019-12-17 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 adultscore=0 priorityscore=1501 malwarescore=0 spamscore=0 mlxscore=0 suspectscore=0 bulkscore=0 phishscore=0 clxscore=1015 lowpriorityscore=0 mlxlogscore=999 impostorscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-1910280000 definitions=main-1912170183
Archived-At: <https://mailarchive.ietf.org/arch/msg/mboned/e7GfJfBZMjHE9WZwOoSI6wjgC2I>
Subject: Re: [MBONED] Éric Vyncke's No Objection on draft-ietf-mboned-driad-amt-discovery-10: (with COMMENT)
X-BeenThere: mboned@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mail List for the Mboned Working Group <mboned.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mboned>, <mailto:mboned-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mboned/>
List-Post: <mailto:mboned@ietf.org>
List-Help: <mailto:mboned-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mboned>, <mailto:mboned-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Dec 2019 23:04:34 -0000

Hi Éric,

Thanks for the review and comments.  Some responses below.

On 2019-12-17, 12:01, "Éric Vyncke via Datatracker" <noreply@ietf.org> wrote:
> Thank you for the work put into this document. Quite an achievement for a
> single author !

In many ways I suspect it was easier as a single author ;)

> -- Section 2.4.2 --
> At the end, the text
>         "its default settings MUST NOT permit more
>    than 10 queries for any 100-millisecond period (though this MAY be
>    overridable by administrative configuration)."
> should probably use a "SHOULD NOT" rather than a "MUST NOT" as it "MAY" be
> overridden.

Sure, that's fine by me.  I've changed this locally and it will be in the
-11 version.

> The last paragraph is a little unclear whether the AMT gateway should wait
> until all DNS replies are received before initiating AMT connection.

(I noticed another case of RFC 8085 mistakenly being used here instead of
RFC 8305, now also fixed locally, and did a search for any others.)

I thought this point was pretty well covered by RFC 8305, but if you
think it's helpful I could add a note about this detail at the end of the
paragraph:

OLD:
   under the algorithm restrictions and guidelines given in [RFC8085]
   for the "Establishment of one connection, which cancels all other
   attempts" phase.

NEW:
   under the algorithm restrictions and guidelines given in [RFC8305]
   for the "Establishment of one connection, which cancels all other
   attempts" phase.  As described in Section 3 of [RFC8305], DNS
   resolution is treated as asynchronous, and connection initiation does
   not wait for lagging DNS responses.

FWIW, I'm slightly negative on adding this. I think this is one of
several details about Happy Eyeballs algorithms that are mostly not
explicitly spelled out in this doc, but rather implied by reference
to RFC 8305.

However, if you think this is a particularly useful detail to highlight,
I'm willing to add the above text or similar.

> -- Section 2.5.3 --
> The whole section about tunnel stability has little to do, IMHO, with
> neither the title of the document "DNS Reverse IP AMT Discovery" nor with
> the abstract. The content is useful and should perhaps be moved to another
> companion document. I understand that this is a little late in the process
> so let's change the abstract at least. Note: I considered balloting a DISCUSS
> on this issue.

I see what you mean, and after having written them up, it occurred to me
that a number of the sub-sections in section 2 maybe could have been
structured as a companion document instead.  But I ended up deciding that
the advice on when to restart discovery was worthwhile to include.

I think updating the abstract is a good solution, thanks for the suggestion.

Does this work?

OLD:
   This document updates RFC 7450 (Automatic Multicast Tunneling, or
   AMT) by extending the relay discovery process to use a new DNS
   resource record named AMTRELAY when discovering AMT relays for
   source-specific multicast channels.  The reverse IP DNS zone for a
   multicast sender's IP address is configured to use AMTRELAY resource
   records to advertise a set of AMT relays that can receive and forward
   multicast traffic from that sender over an AMT tunnel.

NEW:
   This document updates RFC 7450 (Automatic Multicast Tunneling, or
   AMT) by modifying the relay discovery process.  A new DNS resource
   record named AMTRELAY is defined for publishing AMT relays for
   source-specific multicast channels.  The reverse IP DNS zone for a
   multicast sender's IP address is configured to use AMTRELAY resource
   records to advertise a set of AMT relays that can receive and forward
   multicast traffic from that sender over an AMT tunnel.  Other minor
   extensions and clarifications to the relay discovery process are also
   defined.


> -- Section 3.1.1 --
> Please expand CMTS & OLT used in figure 3

These terms don't fit in the image very well, but I can add them to the
definitions section, unless you have a better suggestion?

NEW (section 1.3):
   |            |                                                      |
   |       CMTS | Cable Modem Termination System                       |
   |            |                                                      |
   |        OLT | Optical Line Terminal                                |


> -- Section 3.1.2 --
> Unsure whether this is a common use-case in 2019 but it is OK (I hope that my
> ISP was mcast-capable...).

AFAICT support is mixed, and often has caveats, especially for interdomain
multicast.  I hope this improves, but I think improved support for the
transition technologies like AMT might be critical to making that happen. 

> -- Section 4.1 --
> Should the code 260 be allocated by IANA? I would rather use 'TBD' in the
> document and ask for IANA allocation for 'TBD'

This was the case for the -00 version:
https://tools.ietf.org/html/draft-ietf-mboned-driad-amt-discovery-00#section-5

However, the codepoint was provisionally assigned by IANA last February,
under the guidelines in RFC 6895:
https://tools.ietf.org/html/rfc6895#section-3.1.1

So it's already in the registry as 260, and will become reasonably permanent
if this doc becomes an RFC:
https://www.iana.org/assignments/dns-parameters/dns-parameters.xhtml


> == NITS ==
> 
> -- Section 2.1 --
> s/The sender/The multicast source/ ?

I think this would make it slightly less correct.  I think "the multicast
source" refers to a device sending multicast traffic (or sometimes maybe its
IP address).  "The sender" at the beginning of paragraph 2 refers to an
entity that both controls the RR in the DNS zone and also operates a device
producing multicast traffic.

> -- Section 4.2.2 --
> Please use the canonical format for IPv6 address. I know this is cosmetic but
> it hurts my eyes ;-)

I think you meant 4.3.2, and this is just DB8 -> db8, correct?  Or was there
more?

OLD:
       10     IN AMTRELAY  10 0 2 2001:DB8::15

NEW:
       10     IN AMTRELAY  10 0 2 2001:db8::15