Re: Stephen Farrell's Discuss on draft-ietf-6man-rdnss-rfc6106bis-15: (with DISCUSS)

Suresh Krishnan <suresh.krishnan@ericsson.com> Thu, 19 January 2017 14:38 UTC

Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 413F7129620; Thu, 19 Jan 2017 06:38:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.357
X-Spam-Level:
X-Spam-Status: No, score=-5.357 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-1.156, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 ce_pqI1w4L8I; Thu, 19 Jan 2017 06:38:48 -0800 (PST)
Received: from usplmg20.ericsson.net (usplmg20.ericsson.net [198.24.6.45]) (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 9062F12961E; Thu, 19 Jan 2017 06:38:48 -0800 (PST)
X-AuditID: c618062d-aa3ff70000007359-7d-5880d635d3b9
Received: from EUSAAHC003.ericsson.se (Unknown_Domain [147.117.188.81]) by (Symantec Mail Security) with SMTP id DC.1F.29529.536D0885; Thu, 19 Jan 2017 16:07:35 +0100 (CET)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC003.ericsson.se ([147.117.188.81]) with mapi id 14.03.0319.002; Thu, 19 Jan 2017 09:38:45 -0500
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
To: Fernando Gont <fgont@si6networks.com>
Subject: Re: Stephen Farrell's Discuss on draft-ietf-6man-rdnss-rfc6106bis-15: (with DISCUSS)
Thread-Topic: Stephen Farrell's Discuss on draft-ietf-6man-rdnss-rfc6106bis-15: (with DISCUSS)
Thread-Index: AQHSclK8V+ObW4qCzU6TVXv3hHtouaFAIVCAgAARVgA=
Date: Thu, 19 Jan 2017 14:38:45 +0000
Message-ID: <A413E0CD-E53C-4E68-B63B-ABCA70EA3C4F@ericsson.com>
References: <148483027733.10394.5733573036724815686.idtracker@ietfa.amsl.com> <677f1f83-a6ea-c03d-565d-33719cb0b924@si6networks.com>
In-Reply-To: <677f1f83-a6ea-c03d-565d-33719cb0b924@si6networks.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [147.117.188.11]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <020AE9FC82B55147BB93215401D91392@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrKIsWRmVeSWpSXmKPExsUyuXRPoK75tYYIgwmdfBa7p0xjs9j6fh+b xdeWuewWT1a9YbOY8Wcis8XLs++ZLCa3rWCzmL73GrsDh8fa7qtsHgePfWT02DnrLrvHkiU/ mTw+HOphD2CN4rJJSc3JLEst0rdL4Mp4/VKhYI5Qxf7mnSwNjJ/5uhg5OSQETCR+P2hg7WLk 4hASWM8oMfvxe0YIZzmjxMqGe+wgVWxAVRt2fmYCsUUENCXmPj/CBFLELHCLSeL0hE6gdg4O YYF4iSmH3SBqEiQuN59ihrCtJKbvWcgIYrMIqEqcu7ScBcTmFbCXePRlDgvEsjZGiZNPToM1 cAo4S3yc/g6sgVFATOL7qTVgi5kFxCVuPZnPBHG2gMSSPeeZIWxRiZeP/7FC2EoSH3/PZ4eo 15FYsPsTG4RtLfHoylyoOdoSyxa+ZoY4QlDi5MwnLBMYxWYhWTELSfssJO2zkLTPQtK+gJF1 FSNHaXFBTm66kcEmRmBkHpNg093BeH+65yFGAQ5GJR7egisNEUKsiWXFlbmHGCU4mJVEeDee BQrxpiRWVqUW5ccXleakFh9ilOZgURLnjVt9P1xIID2xJDU7NbUgtQgmy8TBKdXAmHn+m0vs l4zYY01tn+aENenNM54zhzfv08ynKx9dk//G5vDk35czZr5FWTLvE1Yarexg+WFv3XY753Hk 5+z6TwyLVA5can7N2n5nkYb1te7dx6S3P82ZydP8hHNdorJpaH9x2FWf3LO/me8/q4tcIGq9 /qyTesClk28mCkgfvdAwSW16VdvK/0osxRmJhlrMRcWJANG6HNDIAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/idFjpUwSKy5xvvjwlUD9wKjz2Lg>
Cc: 6man WG <ipv6@ietf.org>, Robert Hinden <bob.hinden@gmail.com>, "draft-ietf-6man-rdnss-rfc6106bis@ietf.org" <draft-ietf-6man-rdnss-rfc6106bis@ietf.org>, The IESG <iesg@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>, "Stephen Farrell \(stephen.farrell@cs.tcd.ie\)" <stephen.farrell@cs.tcd.ie>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
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, 19 Jan 2017 14:38:52 -0000

Hi Stephen,

> On Jan 19, 2017, at 8:36 AM, Fernando Gont <fgont@si6networks.com> wrote:
> 
> On 01/19/2017 09:51 AM, Stephen Farrell wrote:
>> Stephen Farrell has entered the following ballot position for
>> draft-ietf-6man-rdnss-rfc6106bis-15: Discuss
>> 
>> When responding, please keep the subject line intact and reply to all
>> email addresses included in the To and CC lines. (Feel free to cut this
>> introductory paragraph, however.)
>> 
>> 
>> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
>> for more information about IESG DISCUSS and COMMENT positions.
>> 
>> 
>> The document, along with other ballot positions, can be found here:
>> https://datatracker.ietf.org/doc/draft-ietf-6man-rdnss-rfc6106bis/
>> 
>> 
>> 
>> ----------------------------------------------------------------------
>> DISCUSS:
>> ----------------------------------------------------------------------
>> 
>> 
>> I think this is the first "configure my DNS" thing to come
>> before the IESG since DPRIVE has gotten an output, so it seems
>> fair to ask now:
>> 
>> Why doesn't the DNS server information include a port now that
>> we have both 53 and 853 as options?  Without that, how is a
>> host supposed to know which to use? Did the WG consider
>> DPRIVE? If so, what was the conclusion? If not, what is the
>> right thing to do? (Add the port no? Define a new DHCPv6 option
>> for DNS/TLS? Something else?)

I think you have a fair point but it was not really within scope of what the WG wanted to accomplish with this document (which is to fix some issues that were discovered during implementation/deployment). 

> 
> FWIW, this is a revision of an existing standard, aimed at fixing known
> problems. Giving how critical it is to IPv6 deployment to convey DNS
> information, I'd personally expect that something like you suggest
> (which is sensible), would be done in a separate document -- e.g., in a
> brand-new option.

Yes. Given that this fixes some important issues like DNS information expiry on lossy links as well as reduction of unnecessary multicast traffic, I would hate to hold this document up. I would much rather have a separate document that extends this option with port info.

Thanks
Suresh