From nobody Thu Feb 6 10:36:38 2020 Return-Path: X-Original-To: dnssd@ietf.org Delivered-To: dnssd@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 85353120809; Thu, 6 Feb 2020 10:36:24 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: Tommy Pauly via Datatracker To: Cc: draft-ietf-dnssd-prireq.all@ietf.org, last-call@ietf.org, dnssd@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.117.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: Tommy Pauly Message-ID: <158101418447.5086.13358929809191152425@ietfa.amsl.com> Date: Thu, 06 Feb 2020 10:36:24 -0800 Archived-At: Subject: [dnssd] Tsvart last call review of draft-ietf-dnssd-prireq-04 X-BeenThere: dnssd@ietf.org X-Mailman-Version: 2.1.29 List-Id: "Discussion of extensions to DNS-based service discovery for routed networks." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Feb 2020 18:36:25 -0000 Reviewer: Tommy Pauly Review result: Ready with Nits This document has been reviewed as part of the transport area review team's ongoing effort to review key IETF documents. These comments were written primarily for the transport area directors, but are copied to the document's authors and WG to allow them to address any issues raised and also to the IETF discussion list for information. When done at the time of IETF Last Call, the authors should consider this review as part of the last-call comments they receive. Please always CC tsv-art@ietf.org if you reply to or forward this review. Thanks for the well-written document! As an informational overview of privacy attacks to be concerned about in service discovery (particularly DNS-SD over mDNS), this document doesn’t define any new protocol behavior, but provides useful guidance for future work. >From a transport perspective, the most relevant section is the operational considerations in sections 3.4.2 and 4.3, which notes that privacy-preserving mechanism that increase the amount of traffic can cause unnecessary load on the network. This can in turn lead to congestion and general performance degradation, within the multicast scope in which some discovery mechanism is being used. This consideration seems appropriate, and any future documents that go on to propose a privacy-preserving discovery mechanism should have similar considerations on the impact on network congestion, and avoiding amplification attacks. I also think this is the first time I’ve seen a smartwatch on a stick figure drawn in ASCII art. Any interest in SVG drawings? =) Nits: Abstract I’d suggest hyphenating “privacy-respecting” in this sentence: We analyze the requirements of a privacy respecting discovery service. Section 1 Perhaps write out Multicast DNS (mDNS) upon first introduction In the third paragraph, the same phrase “DNS-SD over mDNS” is used with duplicate references as in the first paragraph. These references seem a bit redundant. Section 3.1.3 Extra apostrophe in “David' is here.” In the thought bubble Section 3.2.5 “A sometimes heard argument is that…” sounds a bit awkward. Perhaps “An argument is sometimes made that…” Section 3.3.1 The questions, (“Can we trust the information we receive?”) changes the voice used in the document, and it may not be immediately clear who the “we” is. I would suggest rephrasing this to be specific about which parties need to question which information. Section 3.3.2 The term ‘The “Discover” operation’ is used with quotes and capitalization, however the term has not been used prior in the document or formally introduced. I would suggest either adding a reference if this is a particular term, or else making the phrasing more generic, such as “The process of service discovery…” Sections 4.1 and 4.2 The formatting of the numbered lists has some issues (duplicated numbers). From nobody Fri Feb 7 07:50:06 2020 Return-Path: X-Original-To: dnssd@ietf.org Delivered-To: dnssd@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A1921208F3; Fri, 7 Feb 2020 07:50:01 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: Robert Sparks via Datatracker To: Cc: draft-ietf-dnssd-prireq.all@ietf.org, last-call@ietf.org, dnssd@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.117.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: Robert Sparks Message-ID: <158109060108.11593.18381186607321338415@ietfa.amsl.com> Date: Fri, 07 Feb 2020 07:50:01 -0800 Archived-At: Subject: [dnssd] Genart last call review of draft-ietf-dnssd-prireq-04 X-BeenThere: dnssd@ietf.org X-Mailman-Version: 2.1.29 List-Id: "Discussion of extensions to DNS-based service discovery for routed networks." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Feb 2020 15:50:01 -0000 Reviewer: Robert Sparks Review result: Ready with Nits This is a combined genart and secdir last-call review. Please treat these comments just like any other last call comments. Document: draft-ietf-dnssd-prireq-04 Reviewer: Robert Sparks Review Date: 2020-02-07 IETF LC End Date: 2020-02-12 IESG Telechat date: Not scheduled for a telechat Summary: Ready (but with nits) for publication as an Informational RFC This document provides a set of high-level requirements for a DNS-SD privacy exptension, and discussion motivating those requirements. Comment: It might be good to call out in the discussion that while it is intended to be thorough, it's not possible to be exhaustive. Nits (editorial, in document order): The last sentence of the first paragraph of the introduction is complex. Consider breaking it apart. In the introduction at "When analyzing these scenarios in Section 3.2", did you mean Section 3.1? In the first sentence of 3.2 at "the scenarios in Section 2", did you mean Section 3.1? At the first sentence in 3.4.4, at "online" did you mean "on-link"? The statement in the second paragraph of section 4 is perhaps too strong. Consider changing "will lead" to "are intended to lead". The item numbering in sections 4.1 and 4.2 are messsed up. The intent of the next to last paragraph in 4.1 and the last paragraph in 4.2 could be made more clear. I suggest something like: "When listing and resolving services in current DNS-SD deployments". From nobody Fri Feb 7 07:51:21 2020 Return-Path: X-Original-To: dnssd@ietf.org Delivered-To: dnssd@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2CDA9120907; Fri, 7 Feb 2020 07:51:19 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: Robert Sparks via Datatracker To: Cc: draft-ietf-dnssd-prireq.all@ietf.org, last-call@ietf.org, dnssd@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.117.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: Robert Sparks Message-ID: <158109067912.11622.15617540846660389050@ietfa.amsl.com> Date: Fri, 07 Feb 2020 07:51:19 -0800 Archived-At: Subject: [dnssd] Secdir last call review of draft-ietf-dnssd-prireq-04 X-BeenThere: dnssd@ietf.org X-Mailman-Version: 2.1.29 List-Id: "Discussion of extensions to DNS-based service discovery for routed networks." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Feb 2020 15:51:19 -0000 Reviewer: Robert Sparks Review result: Ready This is a combined genart and secdir last-call review. Please treat these comments just like any other last call comments. Document: draft-ietf-dnssd-prireq-04 Reviewer: Robert Sparks Review Date: 2020-02-07 IETF LC End Date: 2020-02-12 IESG Telechat date: Not scheduled for a telechat Summary: Ready (but with nits) for publication as an Informational RFC This document provides a set of high-level requirements for a DNS-SD privacy exptension, and discussion motivating those requirements. Comment: It might be good to call out in the discussion that while it is intended to be thorough, it's not possible to be exhaustive. Nits (editorial, in document order): The last sentence of the first paragraph of the introduction is complex. Consider breaking it apart. In the introduction at "When analyzing these scenarios in Section 3.2", did you mean Section 3.1? In the first sentence of 3.2 at "the scenarios in Section 2", did you mean Section 3.1? At the first sentence in 3.4.4, at "online" did you mean "on-link"? The statement in the second paragraph of section 4 is perhaps too strong. Consider changing "will lead" to "are intended to lead". The item numbering in sections 4.1 and 4.2 are messsed up. The intent of the next to last paragraph in 4.1 and the last paragraph in 4.2 could be made more clear. I suggest something like: "When listing and resolving services in current DNS-SD deployments". From nobody Sat Feb 8 22:46:45 2020 Return-Path: X-Original-To: dnssd@ietfa.amsl.com Delivered-To: dnssd@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C69021200E3 for ; Sat, 8 Feb 2020 22:46:43 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.6 X-Spam-Level: X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable 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 WVmcFyauZkTc for ; Sat, 8 Feb 2020 22:46:42 -0800 (PST) Received: from mx36-out10.antispamcloud.com (mx36-out10.antispamcloud.com [209.126.121.30]) (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 473AE1200E0 for ; Sat, 8 Feb 2020 22:46:42 -0800 (PST) Received: from xse504.mail2web.com ([66.113.197.250] helo=xse.mail2web.com) by mx12.antispamcloud.com with esmtp (Exim 4.92) (envelope-from ) id 1j0g6Y-0001cL-VG for dnssd@ietf.org; Sun, 09 Feb 2020 07:30:08 +0100 Received: from xsmtp22.mail2web.com (unknown [10.100.68.61]) by xse.mail2web.com (Postfix) with ESMTPS id 48FfKQ1D06znMB for ; Sat, 8 Feb 2020 22:30:02 -0800 (PST) Received: from [10.5.2.49] (helo=xmail11.myhosting.com) by xsmtp22.mail2web.com with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from ) id 1j0g6U-0007rK-1X for dnssd@ietf.org; Sat, 08 Feb 2020 22:30:02 -0800 Received: (qmail 17332 invoked from network); 9 Feb 2020 06:30:01 -0000 Received: from unknown (HELO [192.168.1.103]) (Authenticated-user:_huitema@huitema.net@[172.58.43.97]) (envelope-sender ) by xmail11.myhosting.com (qmail-ldap-1.03) with ESMTPA for ; 9 Feb 2020 06:30:01 -0000 To: Tommy Pauly , tsv-art@ietf.org Cc: draft-ietf-dnssd-prireq.all@ietf.org, last-call@ietf.org, dnssd@ietf.org References: <158101418447.5086.13358929809191152425@ietfa.amsl.com> From: Christian Huitema Autocrypt: addr=huitema@huitema.net; prefer-encrypt=mutual; keydata= mQENBFIRX8gBCAC26usy/Ya38IqaLBSu33vKD6hP5Yw390XsWLaAZTeQR64OJEkoOdXpvcOS HWfMIlD5s5+oHfLe8jjmErFAXYJ8yytPj1fD2OdSKAe1TccUBiOXT8wdVxSr5d0alExVv/LO I/vA2aU1TwOkVHKSapD7j8/HZBrqIWRrXUSj2f5n9tY2nJzG9KRzSG0giaJWBfUFiGb4lvsy IaCaIU0YpfkDDk6PtK5YYzuCeF0B+O7N9LhDu/foUUc4MNq4K3EKDPb2FL1Hrv0XHpkXeMRZ olpH8SUFUJbmi+zYRuUgcXgMZRmZFL1tu6z9h6gY4/KPyF9aYot6zG28Qk/BFQRtj7V1ABEB AAG0J0NocmlzdGlhbiBIdWl0ZW1hIDxodWl0ZW1hQGh1aXRlbWEubmV0PokBOQQTAQIAIwUC UhFfyAIbLwcLCQgHAwIBBhUIAgkKCwQWAgMBAh4BAheAAAoJEJNDCbJVyA1yhbYH/1ud6x6m VqGIp0JcZUfSQO8w+TjugqxCyGNn+w/6Qb5O/xENxNQ4HaMQ5uSRK9n8WKKDDRSzwZ4syKKf wbkfj05vgFxrjCynVbm1zs2X2aGXh+PxPL/WHUaxzEP7KjYbLtCUZDRzOOrm+0LMktngT/k3 6+EZoLEM52hwwpIAzJoscyEz7QfqMOZtFm6xQnlvDQeIrHx0KUvwo/vgDLK3SuruG1CSHcR0 D24kEEUa044AIUKBS3b0b8AR7f6mP2NcnLpdsibtpabi9BzqAidcY/EjTaoea46HXALk/eJd 6OLkLE6UQe1PPzQC4jB7rErX2BxnSkHDw50xMgLRcl5/b1a5AQ0EUhFfyAEIAKp7Cp8lqKTV CC9QiAf6QTIjW+lie5J44Ad++0k8gRgANZVWubQuCQ71gxDWLtxYfFkEXjG4TXV/MUtnOliG 5rc2E+ih6Dg61Y5PQakm9OwPIsOx+2R+iSW325ngln2UQrVPgloO83QiUoi7mBJPbcHlxkhZ bd3+EjFxSLIQogt29sTcg2oSh4oljUpz5niTt69IOfZx21kf29NfDE+Iw56gfrxI2ywZbu5o G+d0ZSp0lsovygpk4jK04fDTq0vxjEU5HjPcsXC4CSZdq5E2DrF4nOh1UHkHzeaXdYR2Bn1Y wTePfaHBFlvQzI+Li/Q6AD/uxbTM0vIcsUxrv3MNHCUAEQEAAYkCPgQYAQIACQUCUhFfyAIb LgEpCRCTQwmyVcgNcsBdIAQZAQIABgUCUhFfyAAKCRC22tOSFDh1UOlBB/94RsCJepNvmi/c YiNmMnm0mKb6vjv43OsHkqrrCqJSfo95KHyl5Up4JEp8tiJMyYT2mp4IsirZHxz/5lqkw9Az tcGAF3GlFsj++xTyD07DXlNeddwTKlqPRi/b8sppjtWur6Pm+wnAHp0mQ7GidhxHccFCl65w uT7S/ocb1MjrTgnAMiz+x87d48n1UJ7yIdI41Wpg2XFZiA9xPBiDuuoPwFj14/nK0elV5Dvq 4/HVgfurb4+fd74PV/CC/dmd7hg0ZRlgnB5rFUcFO7ywb7/TvICIIaLWcI42OJDSZjZ/MAzz BeXm263lHh+kFxkh2LxEHnQGHCHGpTYyi4Z3dv03HtkH/1SI8joQMQq00Bv+RdEbJXfEExrT u4gtdZAihwvy97OPA2nCdTAHm/phkzryMeOaOztI4PS8u2Ce5lUB6P/HcGtK/038KdX5MYST Fn8KUDt4o29bkv0CUXwDzS3oTzPNtGdryBkRMc9b+yn9+AdwFEH4auhiTQXPMnl0+G3nhKr7 jvzVFJCRif3OAhEm4vmBNDE3uuaXFQnbK56GJrnqVN+KX5Z3M7X3fA8UcVCGOEHXRP/aubiw Ngawj0V9x+43kUapFp+nF69R53UI65YtJ95ec4PTO/Edvap8h1UbdEOc4+TiYwY1TBuIKltY 1cnrjgAWUh/Ucvr++/KbD9tD6C8= Message-ID: Date: Sat, 8 Feb 2020 22:30:03 -0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1 MIME-Version: 1.0 In-Reply-To: <158101418447.5086.13358929809191152425@ietfa.amsl.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Content-Language: en-US X-Originating-IP: 66.113.197.250 X-Spampanel-Domain: xsmtpout.mail2web.com X-Spampanel-Username: 66.113.197.0/24 Authentication-Results: antispamcloud.com; auth=pass smtp.auth=66.113.197.0/24@xsmtpout.mail2web.com X-Spampanel-Outgoing-Class: unsure X-Spampanel-Outgoing-Evidence: Combined (0.13) X-Recommended-Action: accept X-Filter-ID: Mvzo4OR0dZXEDF/gcnlw0S9sfM/nP8gxoqs1zeWkeM2pSDasLI4SayDByyq9LIhV0x/Wfl+G+r1U GZK7iOCbvETNWdUk1Ol2OGx3IfrIJKywOmJyM1qr8uRnWBrbSAGDoeDwbaJnZ2TaZhv/Bk6d8Jj9 EvBvwu01uVCaGVBWGqus95ABN462tE4kWHH2UKlL2rBNMmEsKEibQwSU1xBeOHButNDpi1WUXRkr He1vFsYm1aGKgRFqmjZjxZofiz4rVsp2VMbDAtRNxMUM7IoK/ryme9ldZJ7uNXfg/GfS8fUvP/L5 rCqHDsKZM+xa1iwJX+gRCHfMVnsAk591zk0uilUI+ZL4xWiN8NS6C+dmX6OEdA4u1aThyWrQ/ou2 +v/lmX4Em37yFgrCB6NHRn1g+f3uncIqYSL3lhh5c81YyJqFoLZMmkWsaurVZfvqROaDnDtHb8z5 dpPkEuJ8Snwqla7jUnW3hy14Yji8fo+4xCnSRo4Rcu5Z37rMuDjCny5fE9ykbJ7I9co1MAEE3ruN Xsm8UJsAPvDcVSKtDCYkioPY5Qx4fJOk03R5fJtf/Dv/dkIzS7m4GUpXCY1Y3j3ilS53T+wO6abg 4E3AqpZHyzzs3e8/YuGKFerbT2aiZ9FStFXZH8PaMIUYFYxlY5EWWzRSiP6TDH7tws6a5dofrizv 5pWb82qAoDl3ILGSF0vmDvI0DEihOd7XzCAIcFZdY11677oPXF7r5zsW33ZNlirOC6HI6/h+rh4v 4bH4tTksCDRZgQnFYkq0SOLrmvxpFzzAXPU1UvCyITFs2AML0PrYCox+niJHsRaLDgEXSzVjHHAS JNUmoOHSoqgqxfHmWRWcrRhLeB34s3hUb32GO+3NXs3OQhG4P447qC6cEbou08QV3No+S2msRDep v5w/kkG0v17AmegcpQ0tml/sN9lmMy/o83jVXTcfb9k0nLWblJy7uxV6dw8jzlsaNZe6hynMJcjx DydxsJEju76A7X1QIVydqXpZ6MHhiKws9Iiut28r9wo4SqUIg8Yh9hAM0n3LLzx/F2gT3wl8JQJv Bho= X-Report-Abuse-To: spam@quarantine11.antispamcloud.com Archived-At: Subject: Re: [dnssd] Tsvart last call review of draft-ietf-dnssd-prireq-04 X-BeenThere: dnssd@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of extensions to DNS-based service discovery for routed networks." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Feb 2020 06:46:44 -0000 Thanks for the review, Tommy. We will fix the nits in the next revision. -- Christian Huitema On 2/6/2020 10:36 AM, Tommy Pauly via Datatracker wrote: > Reviewer: Tommy Pauly > Review result: Ready with Nits > > This document has been reviewed as part of the transport area review team's > ongoing effort to review key IETF documents. These comments were written > primarily for the transport area directors, but are copied to the document's > authors and WG to allow them to address any issues raised and also to the IETF > discussion list for information. > > When done at the time of IETF Last Call, the authors should consider this > review as part of the last-call comments they receive. Please always CC > tsv-art@ietf.org if you reply to or forward this review. > > Thanks for the well-written document! As an informational overview of privacy > attacks to be concerned about in service discovery (particularly DNS-SD over > mDNS), this document doesn’t define any new protocol behavior, but provides > useful guidance for future work. > > >From a transport perspective, the most relevant section is the operational > considerations in sections 3.4.2 and 4.3, which notes that privacy-preserving > mechanism that increase the amount of traffic can cause unnecessary load on the > network. This can in turn lead to congestion and general performance > degradation, within the multicast scope in which some discovery mechanism is > being used. This consideration seems appropriate, and any future documents that > go on to propose a privacy-preserving discovery mechanism should have similar > considerations on the impact on network congestion, and avoiding amplification > attacks. > > I also think this is the first time I’ve seen a smartwatch on a stick figure > drawn in ASCII art. Any interest in SVG drawings? =) > > Nits: > > Abstract > I’d suggest hyphenating “privacy-respecting” in this sentence: > > We analyze the requirements of a privacy respecting > discovery service. > > Section 1 > Perhaps write out Multicast DNS (mDNS) upon first introduction > > In the third paragraph, the same phrase “DNS-SD over mDNS” is used with > duplicate references as in the first paragraph. These references seem a bit > redundant. > > Section 3.1.3 > Extra apostrophe in “David' is here.” In the thought bubble > > Section 3.2.5 > “A sometimes heard argument is that…” sounds a bit awkward. Perhaps “An > argument is sometimes made that…” > > Section 3.3.1 > The questions, (“Can we trust the information we receive?”) changes the voice > used in the document, and it may not be immediately clear who the “we” is. I > would suggest rephrasing this to be specific about which parties need to > question which information. > > Section 3.3.2 > The term ‘The “Discover” operation’ is used with quotes and capitalization, > however the term has not been used prior in the document or formally > introduced. I would suggest either adding a reference if this is a particular > term, or else making the phrasing more generic, such as “The process of service > discovery…” > > Sections 4.1 and 4.2 > The formatting of the numbered lists has some issues (duplicated numbers). > From nobody Sat Feb 8 23:40:11 2020 Return-Path: X-Original-To: dnssd@ietfa.amsl.com Delivered-To: dnssd@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA9F51200CD for ; Sat, 8 Feb 2020 23:40:09 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.6 X-Spam-Level: X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable 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 Yy4h_zkW2aPN for ; Sat, 8 Feb 2020 23:40:09 -0800 (PST) Received: from mx36-out10.antispamcloud.com (mx36-out10.antispamcloud.com [209.126.121.30]) (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 326641200B3 for ; Sat, 8 Feb 2020 23:40:09 -0800 (PST) Received: from xse168.mail2web.com ([66.113.196.168] helo=xse.mail2web.com) by mx37.antispamcloud.com with esmtp (Exim 4.92) (envelope-from ) id 1j0g5f-0008Jw-JK for dnssd@ietf.org; Sun, 09 Feb 2020 07:29:12 +0100 Received: from xsmtp22.mail2web.com (unknown [10.100.68.61]) by xse.mail2web.com (Postfix) with ESMTPS id 48FfJN5XmGz13Hd for ; Sat, 8 Feb 2020 22:29:08 -0800 (PST) Received: from [10.5.2.49] (helo=xmail11.myhosting.com) by xsmtp22.mail2web.com with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from ) id 1j0g5c-000751-LH for dnssd@ietf.org; Sat, 08 Feb 2020 22:29:08 -0800 Received: (qmail 16872 invoked from network); 9 Feb 2020 06:29:08 -0000 Received: from unknown (HELO [192.168.1.103]) (Authenticated-user:_huitema@huitema.net@[172.58.43.97]) (envelope-sender ) by xmail11.myhosting.com (qmail-ldap-1.03) with ESMTPA for ; 9 Feb 2020 06:29:08 -0000 To: Robert Sparks , secdir@ietf.org Cc: draft-ietf-dnssd-prireq.all@ietf.org, "last-call@ietf.org" , dnssd@ietf.org References: <158109067912.11622.15617540846660389050@ietfa.amsl.com> From: Christian Huitema Autocrypt: addr=huitema@huitema.net; prefer-encrypt=mutual; keydata= mQENBFIRX8gBCAC26usy/Ya38IqaLBSu33vKD6hP5Yw390XsWLaAZTeQR64OJEkoOdXpvcOS HWfMIlD5s5+oHfLe8jjmErFAXYJ8yytPj1fD2OdSKAe1TccUBiOXT8wdVxSr5d0alExVv/LO I/vA2aU1TwOkVHKSapD7j8/HZBrqIWRrXUSj2f5n9tY2nJzG9KRzSG0giaJWBfUFiGb4lvsy IaCaIU0YpfkDDk6PtK5YYzuCeF0B+O7N9LhDu/foUUc4MNq4K3EKDPb2FL1Hrv0XHpkXeMRZ olpH8SUFUJbmi+zYRuUgcXgMZRmZFL1tu6z9h6gY4/KPyF9aYot6zG28Qk/BFQRtj7V1ABEB AAG0J0NocmlzdGlhbiBIdWl0ZW1hIDxodWl0ZW1hQGh1aXRlbWEubmV0PokBOQQTAQIAIwUC UhFfyAIbLwcLCQgHAwIBBhUIAgkKCwQWAgMBAh4BAheAAAoJEJNDCbJVyA1yhbYH/1ud6x6m VqGIp0JcZUfSQO8w+TjugqxCyGNn+w/6Qb5O/xENxNQ4HaMQ5uSRK9n8WKKDDRSzwZ4syKKf wbkfj05vgFxrjCynVbm1zs2X2aGXh+PxPL/WHUaxzEP7KjYbLtCUZDRzOOrm+0LMktngT/k3 6+EZoLEM52hwwpIAzJoscyEz7QfqMOZtFm6xQnlvDQeIrHx0KUvwo/vgDLK3SuruG1CSHcR0 D24kEEUa044AIUKBS3b0b8AR7f6mP2NcnLpdsibtpabi9BzqAidcY/EjTaoea46HXALk/eJd 6OLkLE6UQe1PPzQC4jB7rErX2BxnSkHDw50xMgLRcl5/b1a5AQ0EUhFfyAEIAKp7Cp8lqKTV CC9QiAf6QTIjW+lie5J44Ad++0k8gRgANZVWubQuCQ71gxDWLtxYfFkEXjG4TXV/MUtnOliG 5rc2E+ih6Dg61Y5PQakm9OwPIsOx+2R+iSW325ngln2UQrVPgloO83QiUoi7mBJPbcHlxkhZ bd3+EjFxSLIQogt29sTcg2oSh4oljUpz5niTt69IOfZx21kf29NfDE+Iw56gfrxI2ywZbu5o G+d0ZSp0lsovygpk4jK04fDTq0vxjEU5HjPcsXC4CSZdq5E2DrF4nOh1UHkHzeaXdYR2Bn1Y wTePfaHBFlvQzI+Li/Q6AD/uxbTM0vIcsUxrv3MNHCUAEQEAAYkCPgQYAQIACQUCUhFfyAIb LgEpCRCTQwmyVcgNcsBdIAQZAQIABgUCUhFfyAAKCRC22tOSFDh1UOlBB/94RsCJepNvmi/c YiNmMnm0mKb6vjv43OsHkqrrCqJSfo95KHyl5Up4JEp8tiJMyYT2mp4IsirZHxz/5lqkw9Az tcGAF3GlFsj++xTyD07DXlNeddwTKlqPRi/b8sppjtWur6Pm+wnAHp0mQ7GidhxHccFCl65w uT7S/ocb1MjrTgnAMiz+x87d48n1UJ7yIdI41Wpg2XFZiA9xPBiDuuoPwFj14/nK0elV5Dvq 4/HVgfurb4+fd74PV/CC/dmd7hg0ZRlgnB5rFUcFO7ywb7/TvICIIaLWcI42OJDSZjZ/MAzz BeXm263lHh+kFxkh2LxEHnQGHCHGpTYyi4Z3dv03HtkH/1SI8joQMQq00Bv+RdEbJXfEExrT u4gtdZAihwvy97OPA2nCdTAHm/phkzryMeOaOztI4PS8u2Ce5lUB6P/HcGtK/038KdX5MYST Fn8KUDt4o29bkv0CUXwDzS3oTzPNtGdryBkRMc9b+yn9+AdwFEH4auhiTQXPMnl0+G3nhKr7 jvzVFJCRif3OAhEm4vmBNDE3uuaXFQnbK56GJrnqVN+KX5Z3M7X3fA8UcVCGOEHXRP/aubiw Ngawj0V9x+43kUapFp+nF69R53UI65YtJ95ec4PTO/Edvap8h1UbdEOc4+TiYwY1TBuIKltY 1cnrjgAWUh/Ucvr++/KbD9tD6C8= Message-ID: <1619adeb-50f7-cdc1-c08c-159bbcdd8ec5@huitema.net> Date: Sat, 8 Feb 2020 22:29:08 -0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1 MIME-Version: 1.0 In-Reply-To: <158109067912.11622.15617540846660389050@ietfa.amsl.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: en-US X-Originating-IP: 66.113.196.168 X-Spampanel-Domain: xsmtpout.mail2web.com X-Spampanel-Username: 66.113.196.168/32 Authentication-Results: antispamcloud.com; auth=pass smtp.auth=66.113.196.168/32@xsmtpout.mail2web.com X-Spampanel-Outgoing-Class: unsure X-Spampanel-Outgoing-Evidence: Combined (0.11) X-Recommended-Action: accept X-Filter-ID: Mvzo4OR0dZXEDF/gcnlw0S9sfM/nP8gxoqs1zeWkeM2pSDasLI4SayDByyq9LIhV2Ahkt42yLPuK dJjhmGk4mUTNWdUk1Ol2OGx3IfrIJKywOmJyM1qr8uRnWBrbSAGDoeDwbaJnZ2TaZhv/Bk6d8Jj9 EvBvwu01uVCaGVBWGqugBaoNm8oDyL0LmAHzhgXj2rBNMmEsKEibQwSU1xBeOHButNDpi1WUXRkr He1vFsYm1aGKgRFqmjZjxZofiz4rc0IkROma4leeWKFOaFAwGLyme9ldZJ7uNXfg/GfS8fUvP/L5 rCqHDsKZM+xa1iwJX+gRCHfMVnsAk591zk0uilUI+ZL4xWiN8NS6C+dmX6OEdA4u1aThyWrQ/ou2 +v/lmX4Em37yFgrCB6NHRn1g+f3uncIqYSL3lhh5c81YyJqFoLZMmkWsaurVZfvqROaDnDtHb8z5 dpPkEuJ8Snwqla7jUnW3hy14Yji8fo+4xCnSRo4Rcu5Z37rMuDjCny5fE9ykbJ7I9co1MAEE3ruN Xsm8UJsAPvDcVSKtDCYkioPY5Qx4fJOk03R5fJtf/Dv/dkIzS7m4GUpXCY1Y3j3ilVfN5RapG9NU WVOzh+N93wT3GZ3OdHboSQb7BQZPpeqB4iuGcpbD/CgZeW9Iz59+5RUqj4bWJUsnFWTvDBzA8uHE GL9QaZb82ijJkSLDW7QUU6OiDfGh9fXfL9G8dOLAlhg66gs5OuzYxJgw5atIxeNDvjI/CYe5WPy0 +t1RP0az//59ESTA+QacOFAcwBhhSZxMPnetLBJMh51NiRRoHIBzQQ9wtnP2nuL9HrZxYbjemiK7 x42VjdzChZMe6O/Did+/hGXTmfhE+Dx2/NyzMXprgxLCo9qHqV1uAwmVdHlFvOnCUbNPgcPcQwzM gKHyQxUo+ql2ySTkvEFH/23XMww2BnTTFGX5/yI4Ky+1ZJcbGqc5H4PEZHeoI/d6LWFf332z7LMw LGdoi9FMQ5j9dQUvMi1YKAun15JQSJLyCT5k+MTObVKxHy/dols381l9r9ft9daDonlwd6LnuX+J u10= X-Report-Abuse-To: spam@quarantine11.antispamcloud.com Archived-At: Subject: Re: [dnssd] [Last-Call] Secdir last call review of draft-ietf-dnssd-prireq-04 X-BeenThere: dnssd@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of extensions to DNS-based service discovery for routed networks." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Feb 2020 07:40:10 -0000 Thanks for the review, Robert. We will fix the nits in the next revision. -- Christian Huitema On 2/7/2020 7:51 AM, Robert Sparks via Datatracker wrote: > Reviewer: Robert Sparks > Review result: Ready > > This is a combined genart and secdir last-call review. > Please treat these comments just like any other last call comments. > > Document: draft-ietf-dnssd-prireq-04 > Reviewer: Robert Sparks > Review Date: 2020-02-07 > IETF LC End Date: 2020-02-12 > IESG Telechat date: Not scheduled for a telechat > > Summary: Ready (but with nits) for publication as an Informational RFC > > This document provides a set of high-level requirements for a DNS-SD > privacy exptension, and discussion motivating those requirements. > > Comment: > It might be good to call out in the discussion that while it is intended > to be thorough, it's not possible to be exhaustive. > > Nits (editorial, in document order): > > The last sentence of the first paragraph of the introduction is complex. > Consider breaking it apart. > > In the introduction at "When analyzing these scenarios in Section 3.2", > did you mean Section 3.1? > > In the first sentence of 3.2 at "the scenarios in Section 2", did you > mean Section 3.1? > > At the first sentence in 3.4.4, at "online" did you mean "on-link"? > > The statement in the second paragraph of section 4 is perhaps too strong. > Consider changing "will lead" to "are intended to lead". > > The item numbering in sections 4.1 and 4.2 are messsed up. > > The intent of the next to last paragraph in 4.1 and the last paragraph in 4.2 > could be made more clear. I suggest something like: "When listing and resolving > services in current DNS-SD deployments". > > > From nobody Mon Feb 10 08:04:46 2020 Return-Path: X-Original-To: dnssd@ietf.org Delivered-To: dnssd@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 719FE1200B4; Mon, 10 Feb 2020 00:39:12 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: Tianran Zhou via Datatracker To: Cc: draft-ietf-dnssd-prireq.all@ietf.org, last-call@ietf.org, dnssd@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.117.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: Tianran Zhou Message-ID: <158132395239.4159.4997095650392562087@ietfa.amsl.com> Date: Mon, 10 Feb 2020 00:39:12 -0800 Archived-At: Subject: [dnssd] Opsdir last call review of draft-ietf-dnssd-prireq-04 X-BeenThere: dnssd@ietf.org X-Mailman-Version: 2.1.29 List-Id: "Discussion of extensions to DNS-based service discovery for routed networks." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Feb 2020 08:39:13 -0000 Reviewer: Tianran Zhou Review result: Ready I have reviewed this document as part of the Operational directorate's ongoing effort to review all IETF documents being processed by the IESG. These comments were written with the intent of improving the operational aspects of the IETF drafts. Comments that are not addressed in last call may be included in AD reviews during the IESG review. Document editors and WG chairs should treat these comments just like any other last call comments. In general, this document is clear to me. I did not see any special operational or network management related issue. The problems and requirements are well discussed in this informational document. There are some obvious nits. For example, the number of the items in section 4.1 and 4.2. From nobody Tue Feb 11 11:27:54 2020 Return-Path: X-Original-To: dnssd@ietfa.amsl.com Delivered-To: dnssd@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C702120A62; Tue, 11 Feb 2020 11:27:48 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.001 X-Spam-Level: X-Spam-Status: No, score=-2.001 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_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=futurewei.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 stHaHgsAcNgh; Tue, 11 Feb 2020 11:27:45 -0800 (PST) Received: from NAM11-DM6-obe.outbound.protection.outlook.com (mail-dm6nam11on2132.outbound.protection.outlook.com [40.107.223.132]) (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 DA223120A63; Tue, 11 Feb 2020 11:27:44 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=OR6LQTQnqXGrfXa1vzCa+mDbAAMLqZLdU2lmhtW9xm0aP7Xij7Cw2rqa9Qb2UExg8zXRo4J/GD5jI/VCezinxhE3la9Cc/BjwI74hp7KwKwPNKkPbkknumDE0UBl4sobn2POX96FgusfAmjhxX4iOYv+GVFgysirIJZ1+SMr6YoWjIOINqYfm08PhOWe54AnPaBA0St2qBwTWfN8YyzFAMbX59s15xiGcfJw3Kmv7vWe5v4T3R96qFuEkHYwhPV0to8nrDcY5vjDjwxGo3mLIqq0hlBOZ4ANvO4lE1Go+XtXgpv2LQMjUGXQamzeLLSj6ilHoEWeGpCFO1hbKn/MDQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=TrMFxj4nar1DIrV+OLKUDNSVSiJg99mPJzwGAVBSQPI=; b=c9dDauy71RXmSs7mAzKc1pKCxi0VT3LuxjxCTwKB318hF0YxKy5pwnsMZoEyTZ5gcaK0PGDUN6RgSZzeQVYddh3p32DXbni5PqjogK9GuGdHHe1/ObH+18N7COoHSWghogknvWRuMFUcGRfATJPMxSDQ8n6oIxg8GAEEpEiPvgvKp+d0FAkj1QTF1k3XC0fz8kY/IqTNdp2pCD13xUBGS44Q2mX9akUPV69lszse/8vst4DdaLjFnfjIJZ/R0Cojl9+shl1YUZWijYh0L5kzFtFPIIb/n8rk+mJOMOhXuOAURJ0VeklzJafObAPP6+WGdG0C7xuiCYoBvKxr5v3RpA== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=futurewei.com; dmarc=pass action=none header.from=futurewei.com; dkim=pass header.d=futurewei.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Futurewei.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=TrMFxj4nar1DIrV+OLKUDNSVSiJg99mPJzwGAVBSQPI=; b=jl+//pwoXzasBSGtinW8iJe5LMsD2JDMfjT9NMvsDVPW4wqDinpZuVNfYSjYt8aQBCPbZw6wwBZp78CcsaZcQ5tqblm5GcK/zxm+tH+Rbkan8/EEDVdghTh1p3HTXcGqs/7TUjW69dIsQTGZikPZxWBTqZEz4WfR8Kq/0MVLwA4= Received: from BN6PR1301MB2083.namprd13.prod.outlook.com (10.174.89.151) by BN6PR1301MB2132.namprd13.prod.outlook.com (10.174.89.16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2729.14; Tue, 11 Feb 2020 19:27:41 +0000 Received: from BN6PR1301MB2083.namprd13.prod.outlook.com ([fe80::3102:fae9:7c48:cbe]) by BN6PR1301MB2083.namprd13.prod.outlook.com ([fe80::3102:fae9:7c48:cbe%4]) with mapi id 15.20.2729.021; Tue, 11 Feb 2020 19:27:41 +0000 From: Linda Dunbar To: "dnssd@ietf.org" , RTGWG Thread-Topic: Solicit feedback on the problems of DNS for Cloud Resources described by the draft-ietf-rtgwg-net2cloud-problem-statement Thread-Index: AdXhDgZ3FNT4wyuhTVyPeuEWPmJf/g== Date: Tue, 11 Feb 2020 19:27:41 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=linda.dunbar@futurewei.com; x-originating-ip: [199.187.220.18] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: 2b98ed61-1485-496a-5aee-08d7af287639 x-ms-traffictypediagnostic: BN6PR1301MB2132: x-microsoft-antispam-prvs: x-ms-oob-tlc-oobclassifiers: OLM:10000; x-forefront-prvs: 0310C78181 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(39840400004)(396003)(136003)(376002)(366004)(346002)(199004)(189003)(966005)(110136005)(186003)(2906002)(71200400001)(7696005)(5660300002)(316002)(478600001)(26005)(8936002)(86362001)(66446008)(76116006)(66946007)(81166006)(81156014)(66556008)(66476007)(64756008)(6506007)(55016002)(33656002)(9686003)(44832011)(8676002)(450100002)(52536014); DIR:OUT; SFP:1102; SCL:1; SRVR:BN6PR1301MB2132; H:BN6PR1301MB2083.namprd13.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; received-spf: None (protection.outlook.com: futurewei.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam: BCL:0; x-microsoft-antispam-message-info: CNj/0mKt75Zkp1lr8hXUMau60V9ZCcy5bQpgPE/YbOBkFMRGuBOKOrgE+K8hNFLmlyUhg40pnBDFT870ih+jtxNtBHuABEaXDgdoV9yPV7E7cROCLOPgKj40KFNr3IwH2vTwV/xyPkqOZam1fLB01pd71WP3yoEOWTXL6CbZHu4ofjqvXfYO+g7YdpgONYCf2c14nYOkdVOv6Uk4YbCQZ02uGjwRYAH1pG6tnhSHWeodgKgP0KKbEfoCff/OCA2+fWeEuiaQfz9bkepRshPFkmLtMlNTPyRWW6CJ+sfK865LFmkUOdeQsdUGpVOelp8ffwVH9v4cMeVsOU8Q2nM2FsmDDSYmtkBkV+5ACARW/1vpId3C7fOlJXYxCSA4Z9Vpv9J0Pmvq9fHm7Ja9wEWxMVAF1RalOzq0rDbx2gXKUHCdmmVuAmZU8ysl7NcUfOoUDYL5pce591qCQ0lbCeC3+eXxAGp5Qw58t/7G0tCw2DrC/uWiDhagQolcKm7+FOY4lJ00RwYJqSLIgAHLSQIjKw== x-ms-exchange-antispam-messagedata: gWQEC4LdMyJ4ZKVVS1Qun+prsZNcLl+UF6bzVMzBGoOTNW5Z2HYVWPXHZJWWX4+P3hvLUBIQ4f+GAN1T36FbBU3rT+MBLn29MgYyxt/jISr2wv/KKEexwD1fVg/zmE5HQp/6XE9JQfrcS72jiC4Ktg== x-ms-exchange-transport-forked: True Content-Type: multipart/alternative; boundary="_000_BN6PR1301MB2083B6F88FDE9A0A4EA2384985180BN6PR1301MB2083_" MIME-Version: 1.0 X-OriginatorOrg: Futurewei.com X-MS-Exchange-CrossTenant-Network-Message-Id: 2b98ed61-1485-496a-5aee-08d7af287639 X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Feb 2020 19:27:41.0868 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 0fee8ff2-a3b2-4018-9c75-3a1d5591fedc X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: mSr5mqHsep+P2Plcb2MpHfFyqP1PN92pcmqnXCqYNWVsaVe1Zzy837m9MvWATurhe72bY9cudDk+Ph1Z/uwrbw== X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR1301MB2132 Archived-At: Subject: [dnssd] Solicit feedback on the problems of DNS for Cloud Resources described by the draft-ietf-rtgwg-net2cloud-problem-statement X-BeenThere: dnssd@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of extensions to DNS-based service discovery for routed networks." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Feb 2020 19:27:49 -0000 --_000_BN6PR1301MB2083B6F88FDE9A0A4EA2384985180BN6PR1301MB2083_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable DNS experts, https://datatracker.ietf.org/doc/draft-ietf-rtgwg-net2cloud-problem-stateme= nt/ describes the problems that enterprises face today when interconnecting= their branch offices with dynamic workloads in third party data centers (a= .k.a. Cloud DCs). There can be many problems associated with network connecting to or among C= louds, many of which probably are out of the IETF scope. The objective of t= his document is to identify some of the problems that need additional work = in IETF Routing area. Other problems are out of the scope of this document. During IETF 106, we received comments that the document should cover the pr= oblems associated with DNS service by different Cloud Operators for Enterpr= ise to utilize Cloud Resources even though DNS is not within the scope of I= ETF routing area. We greatly appreciate DNS experts to provide comments to= our description. 3.4 DNS for Cloud Resources DNS name resolution is essential for on-premises and cloud-based resources.= For customers with hybrid workloads, which include on-premises and cloud-b= ased resources, extra steps are necessary to configure DNS to work seamless= ly across both environments. Cloud operators have their own DNS to resolve resources within their Cloud = DCs and to well-known public domains. Cloud's DNS can be configured to forw= ard queries to customer managed authoritative DNS servers hosted on-premise= s, and to respond to DNS queries forwarded by on-premises DNS servers. For enterprises utilizing Cloud services by different cloud operators, it i= s necessary to establish policies and rules on how/where to forward DNS que= ries to. When applications in one Cloud need to communication with applicat= ions hosted in another Cloud, there could be DNS queries from one Cloud DC = being forwarded to the enterprise's on premise DNS, which in turn be forwar= ded to the DNS service in another Cloud. Needless to say, configuration can= be complex depending on the application communication patterns. Thank you very much. Linda Dunbar --_000_BN6PR1301MB2083B6F88FDE9A0A4EA2384985180BN6PR1301MB2083_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

DNS experts,

 

https://datatracker.ietf.org/doc/dra= ft-ietf-rtgwg-net2cloud-problem-statement/ describes the problems that = enterprises face today when interconnecting their branch offices with dynamic workloads in third party data centers (a= .k.a. Cloud DCs).

There can be many problems associated with network c= onnecting to or among Clouds, many of which probably are out of the IETF sc= ope. The objective of this document is to identify some of the problems tha= t need additional work in IETF Routing area. Other problems are out of the scope of this document.

 

During IETF 106, we received comments that the docum= ent should cover the problems associated with DNS service by different Clou= d Operators for Enterprise to utilize Cloud Resources even though DNS is no= t within the scope of IETF routing area.  We greatly appreciate DNS experts to provide comments to our d= escription.

 

 

3.4 DNS for Cloud Resources

DNS name resolution is essential for on-premises and= cloud-based resources. For customers with hybrid workloads, which include = on-premises and cloud-based resources, extra steps are necessary to configu= re DNS to work seamlessly across both environments.

Cloud operators have their own DNS to resolve resour= ces within their Cloud DCs and to well-known public domains. Cloud’s = DNS can be configured to forward queries to customer managed authoritative = DNS servers hosted on-premises, and to respond to DNS queries forwarded by on-premises DNS servers.  

For enterprises utilizing Cloud services by differen= t cloud operators, it is necessary to establish policies and rules on how/w= here to forward DNS queries to. When applications in one Cloud need to comm= unication with applications hosted in another Cloud, there could be DNS queries from one Cloud DC being forwa= rded to the enterprise’s on premise DNS, which in turn be forwarded t= o the DNS service in another Cloud. Needless to say, configuration can be c= omplex depending on the application communication patterns.

 

 

Thank you very much.

 

Linda Dunbar

--_000_BN6PR1301MB2083B6F88FDE9A0A4EA2384985180BN6PR1301MB2083_-- From nobody Tue Feb 11 12:37:48 2020 Return-Path: X-Original-To: dnssd@ietfa.amsl.com Delivered-To: dnssd@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B0782120B40; Tue, 11 Feb 2020 12:37:46 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.998 X-Spam-Level: X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 D6cDtDEAYB1g; Tue, 11 Feb 2020 12:37:43 -0800 (PST) Received: from mail-lf1-x135.google.com (mail-lf1-x135.google.com [IPv6:2a00:1450:4864:20::135]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 85D59120B35; Tue, 11 Feb 2020 12:37:42 -0800 (PST) Received: by mail-lf1-x135.google.com with SMTP id 203so7987911lfa.12; Tue, 11 Feb 2020 12:37:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=hMdwqYdhc1Zyi9hREW4QOkJ81CxQW6d3TaxQq4kABtE=; b=H9gfb/5Asayk7tUTRU45a3f6SgYlvEMDQBQ9NeTyt6Febnw7YIKAc9FGCG5gm30DlX aaq2mvACXceWosd4lY2RPeZl+u6m5k95lUqYYcaZnxzvympm+oNrLmysoP9RtLVY/54J jrkhCjmesHCierCWlkTFwxoTyudVg0IBFeped8hbhoR6Ysbj5yq+VecrMCLMfgWsxS18 dbLLNmd9dSJMzsnCV5mtkWMLHkoqxmPmfeHmquzoS/4BZ7gzy5ukuvCwLqQdAbsYbxEM rrOtrsvTrMXKOYeU96yg7LsLvITreUC5j7P5mSYX606XLyF2FPizcnznFEEhLT/P8+Wz f1nA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=hMdwqYdhc1Zyi9hREW4QOkJ81CxQW6d3TaxQq4kABtE=; b=pa4ZEa0wgetIbcsfleD6Z5KdPLfKMGBHbfKnHapKLDrIs9ME8JhQ3HP6cX0S8TQMxa 9bgZPfB6UK6huMUxAbsN3+2jOFNHrhdiv/Z6xJJiWu+bJvFiAqTiN/b/67wXhxQSizKU r5ekQwTba4PyiKZLhm+RcF6QmbWckU/BPmIkHaYjL+9BO1D2cwdj7i0c2q5Ak4V+qxvf f53/mNLo+53tdnnF0Ix0/b7mMsf0xoOWbdlYhqGDPhcbPUYQ6Z2TWiK+3gePYhadyM81 F+2T06hoUevcq9uq9Ru0I7J8E1YE+OJmFtmy4Kthcwi+ACcdSk0kes+hFI+hap8rw+Sc uOsQ== X-Gm-Message-State: APjAAAXuuchpCEuDC0Duxx/qCl/vTg6TIjrkQ+3VRBFyudS5afEiJ/st Aly1cncRdFwNELOORqldehAn79fTI5FopyBob8VTEB9K X-Google-Smtp-Source: APXvYqwL9Q8fTJ1Kj4HxegiVKjAaKdkBw88RMAFesppPSSjXrAp8uVVhIWvl77xDNirXH65Fbvx5FCKkj9dziF9x1O4= X-Received: by 2002:a19:5f05:: with SMTP id t5mr4650152lfb.149.1581453460546; Tue, 11 Feb 2020 12:37:40 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: David Schinazi Date: Tue, 11 Feb 2020 12:37:29 -0800 Message-ID: To: Linda Dunbar Cc: "dnssd@ietf.org" , RTGWG Content-Type: multipart/alternative; boundary="000000000000bea7e4059e52d31d" Archived-At: Subject: Re: [dnssd] Solicit feedback on the problems of DNS for Cloud Resources described by the draft-ietf-rtgwg-net2cloud-problem-statement X-BeenThere: dnssd@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of extensions to DNS-based service discovery for routed networks." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Feb 2020 20:37:47 -0000 --000000000000bea7e4059e52d31d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Linda, I think you may have the wrong IETF list. DNSSD is about DNS Service Discovery (RFC 6763), not general-purpose DNS. I think you want dnsop@ietf.org David On Tue, Feb 11, 2020 at 11:28 AM Linda Dunbar wrote: > DNS experts, > > > > > https://datatracker.ietf.org/doc/draft-ietf-rtgwg-net2cloud-problem-state= ment/ > describes the problems that enterprises face today when interconnecting > their branch offices with dynamic workloads in third party data centers > (a..k.a. Cloud DCs). > > There can be many problems associated with network connecting to or among > Clouds, many of which probably are out of the IETF scope. The objective o= f > this document is to identify some of the problems that need additional wo= rk > in IETF Routing area. Other problems are out of the scope of this documen= t. > > > > During IETF 106, we received comments that the document should cover the > problems associated with DNS service by different Cloud Operators for > Enterprise to utilize Cloud Resources even though DNS is not within the > scope of IETF routing area. We greatly appreciate DNS experts to provide > comments to our description. > > > > > 3.4 DNS for Cloud Resources > > DNS name resolution is essential for on-premises and cloud-based > resources. For customers with hybrid workloads, which include on-premises > and cloud-based resources, extra steps are necessary to configure DNS to > work seamlessly across both environments. > > Cloud operators have their own DNS to resolve resources within their Clou= d > DCs and to well-known public domains. Cloud=E2=80=99s DNS can be configur= ed to > forward queries to customer managed authoritative DNS servers hosted > on-premises, and to respond to DNS queries forwarded by on-premises DNS > servers. > > For enterprises utilizing Cloud services by different cloud operators, it > is necessary to establish policies and rules on how/where to forward DNS > queries to. When applications in one Cloud need to communication with > applications hosted in another Cloud, there could be DNS queries from one > Cloud DC being forwarded to the enterprise=E2=80=99s on premise DNS, whic= h in turn > be forwarded to the DNS service in another Cloud. Needless to say, > configuration can be complex depending on the application communication > patterns. > > > > > > Thank you very much. > > > > Linda Dunbar > _______________________________________________ > dnssd mailing list > dnssd@ietf.org > https://www.ietf.org/mailman/listinfo/dnssd > --000000000000bea7e4059e52d31d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Linda,

I think you may have the wron= g=C2=A0IETF list.
DNSSD is about DNS Service Discovery (RFC=C2=A0= 6763),
not general-purpose DNS. I think you want dnsop@ietf.org

David

On= Tue, Feb 11, 2020 at 11:28 AM Linda Dunbar <linda.dunbar@futurewei.com> wrote:

DNS experts,

=C2=A0

https://datatracke= r.ietf.org/doc/draft-ietf-rtgwg-net2cloud-problem-statement/ describes = the problems that enterprises face today when interconnecting their branch offices with dynamic workloads in third party data centers (a= ..k.a. Cloud DCs).

There can be many problems associated with network c= onnecting to or among Clouds, many of which probably are out of the IETF sc= ope. The objective of this document is to identify some of the problems tha= t need additional work in IETF Routing area. Other problems are out of the scope of this document.<= /p>

=C2=A0

During IETF 106, we received comments that the docum= ent should cover the problems associated with DNS service by different Clou= d Operators for Enterprise to utilize Cloud Resources even though DNS is no= t within the scope of IETF routing area.=C2=A0 We greatly appreciate DNS experts to provide comments to our d= escription.

=C2=A0

=C2=A0

3.4 DNS for Cloud Resources

DNS name resolution is essential for on-premises and= cloud-based resources. For customers with hybrid workloads, which include = on-premises and cloud-based resources, extra steps are necessary to configu= re DNS to work seamlessly across both environments.

Cloud operators have their own DNS to resolve resour= ces within their Cloud DCs and to well-known public domains. Cloud=E2=80=99= s DNS can be configured to forward queries to customer managed authoritativ= e DNS servers hosted on-premises, and to respond to DNS queries forwarded by on-premises DNS servers.=C2=A0=C2=A0

For enterprises utilizing Cloud services by differen= t cloud operators, it is necessary to establish policies and rules on how/w= here to forward DNS queries to. When applications in one Cloud need to comm= unication with applications hosted in another Cloud, there could be DNS queries from one Cloud DC being forwa= rded to the enterprise=E2=80=99s on premise DNS, which in turn be forwarded= to the DNS service in another Cloud. Needless to say, configuration can be= complex depending on the application communication patterns.

=C2=A0

=C2=A0

Thank you very much.

=C2=A0

Linda Dunbar

_______________________________________________
dnssd mailing list
dnssd@ietf.org
https://www.ietf.org/mailman/listinfo/dnssd
--000000000000bea7e4059e52d31d-- From nobody Wed Feb 12 01:11:03 2020 Return-Path: X-Original-To: dnssd@ietfa.amsl.com Delivered-To: dnssd@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 47E741200B1 for ; Wed, 12 Feb 2020 01:11:01 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.601 X-Spam-Level: X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable 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 h83LYFacZsCf for ; Wed, 12 Feb 2020 01:11:00 -0800 (PST) Received: from mx36-out10.antispamcloud.com (mx36-out10.antispamcloud.com [209.126.121.30]) (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 30BBB120044 for ; Wed, 12 Feb 2020 01:10:51 -0800 (PST) Received: from xse93.mail2web.com ([66.113.196.93] helo=xse.mail2web.com) by mx105.antispamcloud.com with esmtp (Exim 4.92) (envelope-from ) id 1j1miw-0002k4-Ol for dnssd@ietf.org; Wed, 12 Feb 2020 08:46:26 +0100 Received: from xsmtp21.mail2web.com (unknown [10.100.68.60]) by xse.mail2web.com (Postfix) with ESMTPS id 48HWsm5fm2z1T7m for ; Tue, 11 Feb 2020 23:46:04 -0800 (PST) Received: from [10.5.2.49] (helo=xmail11.myhosting.com) by xsmtp21.mail2web.com with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from ) id 1j1mii-0003ij-M5 for dnssd@ietf.org; Tue, 11 Feb 2020 23:46:04 -0800 Received: (qmail 17103 invoked from network); 12 Feb 2020 07:46:04 -0000 Received: from unknown (HELO [192.168.1.103]) (Authenticated-user:_huitema@huitema.net@[172.58.43.97]) (envelope-sender ) by xmail11.myhosting.com (qmail-ldap-1.03) with ESMTPA for ; 12 Feb 2020 07:46:04 -0000 To: Tianran Zhou , ops-dir@ietf.org Cc: draft-ietf-dnssd-prireq.all@ietf.org, last-call@ietf.org, dnssd@ietf.org References: <158132395239.4159.4997095650392562087@ietfa.amsl.com> From: Christian Huitema Autocrypt: addr=huitema@huitema.net; prefer-encrypt=mutual; keydata= mQENBFIRX8gBCAC26usy/Ya38IqaLBSu33vKD6hP5Yw390XsWLaAZTeQR64OJEkoOdXpvcOS HWfMIlD5s5+oHfLe8jjmErFAXYJ8yytPj1fD2OdSKAe1TccUBiOXT8wdVxSr5d0alExVv/LO I/vA2aU1TwOkVHKSapD7j8/HZBrqIWRrXUSj2f5n9tY2nJzG9KRzSG0giaJWBfUFiGb4lvsy IaCaIU0YpfkDDk6PtK5YYzuCeF0B+O7N9LhDu/foUUc4MNq4K3EKDPb2FL1Hrv0XHpkXeMRZ olpH8SUFUJbmi+zYRuUgcXgMZRmZFL1tu6z9h6gY4/KPyF9aYot6zG28Qk/BFQRtj7V1ABEB AAG0J0NocmlzdGlhbiBIdWl0ZW1hIDxodWl0ZW1hQGh1aXRlbWEubmV0PokBOQQTAQIAIwUC UhFfyAIbLwcLCQgHAwIBBhUIAgkKCwQWAgMBAh4BAheAAAoJEJNDCbJVyA1yhbYH/1ud6x6m VqGIp0JcZUfSQO8w+TjugqxCyGNn+w/6Qb5O/xENxNQ4HaMQ5uSRK9n8WKKDDRSzwZ4syKKf wbkfj05vgFxrjCynVbm1zs2X2aGXh+PxPL/WHUaxzEP7KjYbLtCUZDRzOOrm+0LMktngT/k3 6+EZoLEM52hwwpIAzJoscyEz7QfqMOZtFm6xQnlvDQeIrHx0KUvwo/vgDLK3SuruG1CSHcR0 D24kEEUa044AIUKBS3b0b8AR7f6mP2NcnLpdsibtpabi9BzqAidcY/EjTaoea46HXALk/eJd 6OLkLE6UQe1PPzQC4jB7rErX2BxnSkHDw50xMgLRcl5/b1a5AQ0EUhFfyAEIAKp7Cp8lqKTV CC9QiAf6QTIjW+lie5J44Ad++0k8gRgANZVWubQuCQ71gxDWLtxYfFkEXjG4TXV/MUtnOliG 5rc2E+ih6Dg61Y5PQakm9OwPIsOx+2R+iSW325ngln2UQrVPgloO83QiUoi7mBJPbcHlxkhZ bd3+EjFxSLIQogt29sTcg2oSh4oljUpz5niTt69IOfZx21kf29NfDE+Iw56gfrxI2ywZbu5o G+d0ZSp0lsovygpk4jK04fDTq0vxjEU5HjPcsXC4CSZdq5E2DrF4nOh1UHkHzeaXdYR2Bn1Y wTePfaHBFlvQzI+Li/Q6AD/uxbTM0vIcsUxrv3MNHCUAEQEAAYkCPgQYAQIACQUCUhFfyAIb LgEpCRCTQwmyVcgNcsBdIAQZAQIABgUCUhFfyAAKCRC22tOSFDh1UOlBB/94RsCJepNvmi/c YiNmMnm0mKb6vjv43OsHkqrrCqJSfo95KHyl5Up4JEp8tiJMyYT2mp4IsirZHxz/5lqkw9Az tcGAF3GlFsj++xTyD07DXlNeddwTKlqPRi/b8sppjtWur6Pm+wnAHp0mQ7GidhxHccFCl65w uT7S/ocb1MjrTgnAMiz+x87d48n1UJ7yIdI41Wpg2XFZiA9xPBiDuuoPwFj14/nK0elV5Dvq 4/HVgfurb4+fd74PV/CC/dmd7hg0ZRlgnB5rFUcFO7ywb7/TvICIIaLWcI42OJDSZjZ/MAzz BeXm263lHh+kFxkh2LxEHnQGHCHGpTYyi4Z3dv03HtkH/1SI8joQMQq00Bv+RdEbJXfEExrT u4gtdZAihwvy97OPA2nCdTAHm/phkzryMeOaOztI4PS8u2Ce5lUB6P/HcGtK/038KdX5MYST Fn8KUDt4o29bkv0CUXwDzS3oTzPNtGdryBkRMc9b+yn9+AdwFEH4auhiTQXPMnl0+G3nhKr7 jvzVFJCRif3OAhEm4vmBNDE3uuaXFQnbK56GJrnqVN+KX5Z3M7X3fA8UcVCGOEHXRP/aubiw Ngawj0V9x+43kUapFp+nF69R53UI65YtJ95ec4PTO/Edvap8h1UbdEOc4+TiYwY1TBuIKltY 1cnrjgAWUh/Ucvr++/KbD9tD6C8= Message-ID: Date: Tue, 11 Feb 2020 23:46:07 -0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1 MIME-Version: 1.0 In-Reply-To: <158132395239.4159.4997095650392562087@ietfa.amsl.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: en-US X-Originating-IP: 66.113.196.93 X-Spampanel-Domain: xsmtpout.mail2web.com X-Spampanel-Username: 66.113.196.93/32 Authentication-Results: antispamcloud.com; auth=pass smtp.auth=66.113.196.93/32@xsmtpout.mail2web.com X-Spampanel-Outgoing-Class: unsure X-Spampanel-Outgoing-Evidence: Combined (0.11) X-Recommended-Action: accept X-Filter-ID: Mvzo4OR0dZXEDF/gcnlw0QHHUXH8HYgJuwhvgiygxCWpSDasLI4SayDByyq9LIhV0yneV02lvIlO /ObN6AbMtkTNWdUk1Ol2OGx3IfrIJKywOmJyM1qr8uRnWBrbSAGDoeDwbaJnZ2TaZhv/Bk6d8Jj9 EvBvwu01uVCaGVBWGqtKznFym0KMr/YMrqrwOBZr2rBNMmEsKEibQwSU1xBeOHButNDpi1WUXRkr He1vFsZaZad0VL/QynhFAlbT36L827A0We4Px3ZtIg26LaXLKAZ6weYgSzquK2hxskqXvy8woCTx LKweTbuJ+19zsyHVGVmhMAaQ/AfCRwRe7yHm5oY+NYmsSGn+svMubxnbgm1cr18FZBEPC2/c16Xd 7sC9aC4xteE1WLqGS9YoqrsZ2DyteN0e+ECCv9/f+GPymkgDVo7QBKA4MctKq4ifYPcXFRL2K3LA EfDXVOdt7wDbusYnuEVWSxKMHbU0zkNM3EElFDaoLuOPKc8gc82pKfhB7T02ZXdoQxMs//iOE4Fl hiCv9TR+UxzLZWL8hwGBjhoI3W+YcuHfP5PkZb5A+wE5qGdpH54Oa3V8I76VOEvlwPpZ90pncljT Sb0eCPh6fGVZkhHczxXNtf1osmsghZuHkhEFUcH9bKaci2tvjLWIKY80XlUdA3qPwTt9U9q2PxqH gbVpRK3T9+h2PwMALJBCkSE1fOcjG8Kq+0xIREFjgbdCp3Zd9clP8wSiJZWbJCg35R5vCGCRun6Y x0PkyFKG6l+/cYVtI5x5PLoACr4TKTXg724gFzhHYUe+7aKm0vV0kNe81TibgjBJY64S+aRHTi+J 2sBvM/O0p+zizleC4lU8fDj1CnRx+r4b/1Q/PZ8OMlKhaMBXBEUx5kqFnVjvvOnCUbNPgcPcQwzM gKHyQxUo+ql2ySTkvEFH/23XMww2BnTTFGX5/yI4Ky+1ZJcbGqc5H4PEZHeoI/d6LWFf332z7LMw LGdoi9FMQ5j9dQUvMi1YKAun15JQSJLyCT5k+MTObVKxHy/dols381l9r9ft9daDonlwd6LnuX+J u10= X-Report-Abuse-To: spam@quarantine11.antispamcloud.com Archived-At: Subject: Re: [dnssd] Opsdir last call review of draft-ietf-dnssd-prireq-04 X-BeenThere: dnssd@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of extensions to DNS-based service discovery for routed networks." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Feb 2020 09:11:01 -0000 Thanks for the review, Tianran On 2/10/2020 12:39 AM, Tianran Zhou via Datatracker wrote: > Reviewer: Tianran Zhou > Review result: Ready > > I have reviewed this document as part of the Operational directorate's ongoing > effort to review all IETF documents being processed by the IESG. These > comments were written with the intent of improving the operational aspects of > the IETF drafts. Comments that are not addressed in last call may be included > in AD reviews during the IESG review. Document editors and WG chairs should > treat these comments just like any other last call comments. > > In general, this document is clear to me. I did not see any special operational > or network management related issue. The problems and requirements are well > discussed in this informational document. > > There are some obvious nits. For example, the number of the items in section > 4.1 and 4.2. > > From nobody Thu Feb 13 09:32:00 2020 Return-Path: X-Original-To: dnssd@ietf.org Delivered-To: dnssd@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2CB54120168; Thu, 13 Feb 2020 09:31:59 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: Samita Chakrabarti via Datatracker To: Cc: draft-ietf-dnssd-prireq.all@ietf.org, last-call@ietf.org, dnssd@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.117.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: Samita Chakrabarti Message-ID: <158161511905.20519.9851954062722453601@ietfa.amsl.com> Date: Thu, 13 Feb 2020 09:31:59 -0800 Archived-At: Subject: [dnssd] Iotdir last call review of draft-ietf-dnssd-prireq-04 X-BeenThere: dnssd@ietf.org X-Mailman-Version: 2.1.29 List-Id: "Discussion of extensions to DNS-based service discovery for routed networks." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Feb 2020 17:31:59 -0000 Reviewer: Samita Chakrabarti Review result: Ready with Nits I have reviewed draft-ietf-dnssd-prireq-04. The document is informative and clear with a few editorial nits on section 4.1 through 4.3. I have reviewed from the IoT devices perspective and most likely for the consumer devices that might be present in the public network and are using shared network technologies (wireless or wired). The threat model are applicable to them. Section 3.1 describes implications for wearable and server related privacy issue. Perhaps a small paragraph might be added in this section or in the introduction calling out possible privacy and security threats on personal IoT devices in the public places ( that might act as a dns-sd client). At the same time, considering limited processing capabilities, battery saving concern considerations, privacy related extra processing of messages from the dns-sd server should not be mandated for the IoT devices. Depending on the device capabilities, the feature can be configurable and the user can turn on/off at their need; additionally some iot devices may not care about the privacy at all. So, a few additional lines on IoT implications for the threat model and yet flexibility of implementation of the dns-sd IOT client may be mentioned in the document to clarify the IoT devices in the shared wireless/wired medium. From nobody Thu Feb 13 09:47:23 2020 Return-Path: X-Original-To: dnssd@ietfa.amsl.com Delivered-To: dnssd@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC1E4120058 for ; Thu, 13 Feb 2020 09:47:21 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 c8REqsqGWUzC for ; Thu, 13 Feb 2020 09:47:19 -0800 (PST) Received: from mail-pf1-x431.google.com (mail-pf1-x431.google.com [IPv6:2607:f8b0:4864:20::431]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 76F951207FC for ; Thu, 13 Feb 2020 09:47:19 -0800 (PST) Received: by mail-pf1-x431.google.com with SMTP id q8so3423305pfh.7 for ; Thu, 13 Feb 2020 09:47:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=zWhsjF/jxtkoPFR0f2JKDHUm9cHqApR8uoYs/0RgD+Q=; b=fFTDzYsJqmPcl9YbLiXSzgacjQJmzwUiWO1eRJFGKQCd+WPYUv5yb6cnkqYBJN+lde U1wTb0OViKJkD3nmCNbOWxb1wDf5p8ovTXU6/Xhlngm9nX7WthVgtmEcVXddkJ+WZfuF Op7VywNwRcAKQFUMksiLtiT560fVF3iJQIbEpr56ppOY9Fl0bSSWwwaHkrozs4wXsfu4 Jq+yhCjidxuYdY+uM9FRBiuCdSUj7AtVopjcLeM2lDxYo7ugRGdI9lXM4wjCeshDiRyH jMDdY6fqVMzywf7aM0UbO7Xdy/qB4J/rT1N7HtTW/1ZWqbq6qH32VR00C8F224DMIGhJ ZThQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=zWhsjF/jxtkoPFR0f2JKDHUm9cHqApR8uoYs/0RgD+Q=; b=U2+q/eBEiucFyXNcLScbLFM2EzKzMsqpSIeRcDuQwSxvxKn8pIC/b9nycL/C7LpyqI njEtVUZZIokYUyrP4ygw1xJyXLlWPl7Eow5eLQdMgGQSlnJ7IB2mxaTC5zJ3X/BmauIG Qpv0tWBSoYkBXzMA5FlgQXueEMHAg72+NJysy8uglH8poU0kmaADzTf4/UCtkl1B0CdM Qv2obLLC0kqBYrVWSQUe3hD95iF2tJRz7xe5U1OU3h2v7OVr2jBXFr5ZuvVTn3FN3U7O aMBe1QnJs/Y6TgDilFs/8cSwRzS6f5BbuX5YCH6j0ropxS48H1ErHEkK2PWshyPeN1Wl vo9g== X-Gm-Message-State: APjAAAUK7yKpTXmR0hFscH2BBuoNcORTNOdyzxg2GZRFHEEQCwivbQUy VfTAUN7RHdyv3YpXVg+Bvb58Kg== X-Google-Smtp-Source: APXvYqznZPi5yomeLpuW2wyQr728bc2jWCCE3FpxXdMYZF7lzg+kpKK57jvbo+BlrcpAeRrbE6fZFA== X-Received: by 2002:a63:a807:: with SMTP id o7mr14942985pgf.407.1581616038962; Thu, 13 Feb 2020 09:47:18 -0800 (PST) Received: from [172.16.140.189] ([144.178.28.13]) by smtp.gmail.com with ESMTPSA id y127sm3861247pfg.22.2020.02.13.09.47.17 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 13 Feb 2020 09:47:18 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.60.0.2.5\)) From: Ted Lemon In-Reply-To: <158161511905.20519.9851954062722453601@ietfa.amsl.com> Date: Thu, 13 Feb 2020 09:47:17 -0800 Cc: draft-ietf-dnssd-prireq.all@ietf.org, last-call@ietf.org, DNSSD Content-Transfer-Encoding: quoted-printable Message-Id: References: <158161511905.20519.9851954062722453601@ietfa.amsl.com> To: Samita Chakrabarti X-Mailer: Apple Mail (2.3608.60.0.2.5) Archived-At: Subject: Re: [dnssd] Iotdir last call review of draft-ietf-dnssd-prireq-04 X-BeenThere: dnssd@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of extensions to DNS-based service discovery for routed networks." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Feb 2020 17:47:22 -0000 100% agree with your first point. Regarding your second point, one of the classic use cases for dns-sd = privacy is a pacemaker. This is a battery-operated device, but the user = should not have to broadcast the fact that they have a pacemaker = installed whenever they are walking around out in the world. So if you think that the requirements really do not address the power = consumption issue, that is something that should be added to the = document as a requirement, rather than saying that in such cases privacy = can be optional. > On Feb 13, 2020, at 9:31 AM, Samita Chakrabarti via Datatracker = wrote: >=20 > Reviewer: Samita Chakrabarti > Review result: Ready with Nits >=20 > I have reviewed draft-ietf-dnssd-prireq-04. >=20 > The document is informative and clear with a few editorial nits on = section 4.1 > through 4.3. >=20 > I have reviewed from the IoT devices perspective and most likely for = the > consumer devices that might be present in the public network and are = using > shared network technologies (wireless or wired). The threat model are > applicable to them. Section 3.1 describes implications for wearable = and server > related privacy issue. Perhaps a small paragraph might be added in = this > section or in the introduction calling out possible privacy and = security > threats on personal IoT devices in the public places ( that might act = as a > dns-sd client). >=20 > At the same time, considering limited processing capabilities, battery = saving > concern considerations, privacy related extra processing of messages = from the > dns-sd server should not be mandated for the IoT devices. Depending on = the > device capabilities, the feature can be configurable and the user can = turn > on/off at their need; additionally some iot devices may not care = about the > privacy at all. >=20 > So, a few additional lines on IoT implications for the threat model = and yet > flexibility of implementation of the dns-sd IOT client may be = mentioned in the > document to clarify the IoT devices in the shared wireless/wired = medium. >=20 >=20 > _______________________________________________ > dnssd mailing list > dnssd@ietf.org > https://www.ietf.org/mailman/listinfo/dnssd From nobody Thu Feb 13 10:37:29 2020 Return-Path: X-Original-To: dnssd@ietfa.amsl.com Delivered-To: dnssd@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46F03120251 for ; Thu, 13 Feb 2020 10:37:22 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.601 X-Spam-Level: X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable 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 QZUHuenBOioF for ; Thu, 13 Feb 2020 10:37:21 -0800 (PST) Received: from mx43-out1.antispamcloud.com (mx43-out1.antispamcloud.com [138.201.61.189]) (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 C5D28120809 for ; Thu, 13 Feb 2020 10:37:20 -0800 (PST) Received: from xse49.mail2web.com ([66.113.196.49] helo=xse.mail2web.com) by mx177.antispamcloud.com with esmtp (Exim 4.92) (envelope-from ) id 1j2JLj-000jpL-8M for dnssd@ietf.org; Thu, 13 Feb 2020 19:37:16 +0100 Received: from xsmtp22.mail2web.com (unknown [10.100.68.61]) by xse.mail2web.com (Postfix) with ESMTPS id 48JQFm61gNz1ml5 for ; Thu, 13 Feb 2020 10:36:28 -0800 (PST) Received: from [10.5.2.15] (helo=xmail05.myhosting.com) by xsmtp22.mail2web.com with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from ) id 1j2JLg-0002t6-NS for dnssd@ietf.org; Thu, 13 Feb 2020 10:36:28 -0800 Received: (qmail 30950 invoked from network); 13 Feb 2020 18:36:28 -0000 Received: from unknown (HELO [192.168.1.103]) (Authenticated-user:_huitema@huitema.net@[172.58.43.97]) (envelope-sender ) by xmail05.myhosting.com (qmail-ldap-1.03) with ESMTPA for ; 13 Feb 2020 18:36:28 -0000 To: Samita Chakrabarti , iot-directorate@ietf.org Cc: draft-ietf-dnssd-prireq.all@ietf.org, last-call@ietf.org, dnssd@ietf.org References: <158161511905.20519.9851954062722453601@ietfa.amsl.com> From: Christian Huitema Autocrypt: addr=huitema@huitema.net; prefer-encrypt=mutual; keydata= mQENBFIRX8gBCAC26usy/Ya38IqaLBSu33vKD6hP5Yw390XsWLaAZTeQR64OJEkoOdXpvcOS HWfMIlD5s5+oHfLe8jjmErFAXYJ8yytPj1fD2OdSKAe1TccUBiOXT8wdVxSr5d0alExVv/LO I/vA2aU1TwOkVHKSapD7j8/HZBrqIWRrXUSj2f5n9tY2nJzG9KRzSG0giaJWBfUFiGb4lvsy IaCaIU0YpfkDDk6PtK5YYzuCeF0B+O7N9LhDu/foUUc4MNq4K3EKDPb2FL1Hrv0XHpkXeMRZ olpH8SUFUJbmi+zYRuUgcXgMZRmZFL1tu6z9h6gY4/KPyF9aYot6zG28Qk/BFQRtj7V1ABEB AAG0J0NocmlzdGlhbiBIdWl0ZW1hIDxodWl0ZW1hQGh1aXRlbWEubmV0PokBOQQTAQIAIwUC UhFfyAIbLwcLCQgHAwIBBhUIAgkKCwQWAgMBAh4BAheAAAoJEJNDCbJVyA1yhbYH/1ud6x6m VqGIp0JcZUfSQO8w+TjugqxCyGNn+w/6Qb5O/xENxNQ4HaMQ5uSRK9n8WKKDDRSzwZ4syKKf wbkfj05vgFxrjCynVbm1zs2X2aGXh+PxPL/WHUaxzEP7KjYbLtCUZDRzOOrm+0LMktngT/k3 6+EZoLEM52hwwpIAzJoscyEz7QfqMOZtFm6xQnlvDQeIrHx0KUvwo/vgDLK3SuruG1CSHcR0 D24kEEUa044AIUKBS3b0b8AR7f6mP2NcnLpdsibtpabi9BzqAidcY/EjTaoea46HXALk/eJd 6OLkLE6UQe1PPzQC4jB7rErX2BxnSkHDw50xMgLRcl5/b1a5AQ0EUhFfyAEIAKp7Cp8lqKTV CC9QiAf6QTIjW+lie5J44Ad++0k8gRgANZVWubQuCQ71gxDWLtxYfFkEXjG4TXV/MUtnOliG 5rc2E+ih6Dg61Y5PQakm9OwPIsOx+2R+iSW325ngln2UQrVPgloO83QiUoi7mBJPbcHlxkhZ bd3+EjFxSLIQogt29sTcg2oSh4oljUpz5niTt69IOfZx21kf29NfDE+Iw56gfrxI2ywZbu5o G+d0ZSp0lsovygpk4jK04fDTq0vxjEU5HjPcsXC4CSZdq5E2DrF4nOh1UHkHzeaXdYR2Bn1Y wTePfaHBFlvQzI+Li/Q6AD/uxbTM0vIcsUxrv3MNHCUAEQEAAYkCPgQYAQIACQUCUhFfyAIb LgEpCRCTQwmyVcgNcsBdIAQZAQIABgUCUhFfyAAKCRC22tOSFDh1UOlBB/94RsCJepNvmi/c YiNmMnm0mKb6vjv43OsHkqrrCqJSfo95KHyl5Up4JEp8tiJMyYT2mp4IsirZHxz/5lqkw9Az tcGAF3GlFsj++xTyD07DXlNeddwTKlqPRi/b8sppjtWur6Pm+wnAHp0mQ7GidhxHccFCl65w uT7S/ocb1MjrTgnAMiz+x87d48n1UJ7yIdI41Wpg2XFZiA9xPBiDuuoPwFj14/nK0elV5Dvq 4/HVgfurb4+fd74PV/CC/dmd7hg0ZRlgnB5rFUcFO7ywb7/TvICIIaLWcI42OJDSZjZ/MAzz BeXm263lHh+kFxkh2LxEHnQGHCHGpTYyi4Z3dv03HtkH/1SI8joQMQq00Bv+RdEbJXfEExrT u4gtdZAihwvy97OPA2nCdTAHm/phkzryMeOaOztI4PS8u2Ce5lUB6P/HcGtK/038KdX5MYST Fn8KUDt4o29bkv0CUXwDzS3oTzPNtGdryBkRMc9b+yn9+AdwFEH4auhiTQXPMnl0+G3nhKr7 jvzVFJCRif3OAhEm4vmBNDE3uuaXFQnbK56GJrnqVN+KX5Z3M7X3fA8UcVCGOEHXRP/aubiw Ngawj0V9x+43kUapFp+nF69R53UI65YtJ95ec4PTO/Edvap8h1UbdEOc4+TiYwY1TBuIKltY 1cnrjgAWUh/Ucvr++/KbD9tD6C8= Message-ID: Date: Thu, 13 Feb 2020 10:36:27 -0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1 MIME-Version: 1.0 In-Reply-To: <158161511905.20519.9851954062722453601@ietfa.amsl.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: en-US X-Originating-IP: 66.113.196.49 X-Spampanel-Domain: xsmtpout.mail2web.com X-Spampanel-Username: 66.113.196.49/32 Authentication-Results: antispamcloud.com; auth=pass smtp.auth=66.113.196.49/32@xsmtpout.mail2web.com X-Spampanel-Outgoing-Class: unsure X-Spampanel-Outgoing-Evidence: Combined (0.15) X-Recommended-Action: accept X-Filter-ID: Mvzo4OR0dZXEDF/gcnlw0QHHUXH8HYgJuwhvgiygxCWpSDasLI4SayDByyq9LIhVUZbR67CQ7/vm /hHDJU4RXkTNWdUk1Ol2OGx3IfrIJKywOmJyM1qr8uRnWBrbSAGDoeDwbaJnZ2TaZhv/Bk6d8Jj9 EvBvwu01uVCaGVBWGquMGjp8gKynRFO2CQGaTIUu2rBNMmEsKEibQwSU1xBeOHButNDpi1WUXRkr He1vFsZaZad0VL/QynhFAlbT36L8fRK6OI+YnimtEVKoqAOiWQZ6weYgSzquK2hxskqXvy8woCTx LKweTbuJ+19zsyHVGVmhMAaQ/AfCRwRe7yHm5oY+NYmsSGn+svMubxnbgm1cr18FZBEPC2/c16Xd 7sC9aC4xteE1WLqGS9YoqrsZ2DyteN0e+ECCv9/f+GPymkgDVo7QBKA4MctKq4ifYPcXFRL2K3LA EfDXVOdt7wDbusYnuEVWSxKMHbU0zkNM3EElFDaoLuOPKc8gc82pKfhB7T02ZXdoQxMs//iOE4Fl hiCv9TR+UxzLZWL8hwGBjhoI3W+YcuHfP5PkZb5A+wE5qGdpH54Oa3V8I76VOEvlwB+XPdEXquZ7 t0MUOMrNUB0nGQsoW6B+lTGeIbefyd01CyHyYbVvauedtRZUmh9JJ1L74velDeb146pzABnFuTck 6Q9V9YO5wBS5yaTKclLkOJvldYwsT+DOapjRlvdsyRg66gs5OuzYxJgw5atIxePaw4mGPOB1lCDk b7ANR1sPedc4GNTVcd2XLjoUZfm6kjzAXPU1UvCyITFs2AML0Pqy7jcUucXawQsftzoPgEckHHAS JNUmoOHSoqgqxfHmWfZIwxxhwvMcWh0MGcvUtQhr8aoZwvk//YyD5tCrcU3z1vEjHyvS2QZiR+AZ YvfxEvZFKu+ZM2mB1CpThxyaBpbeNHk15VolAGHS5rCXQKDyCQUljhSWDhWh87HBSLhNUo4qiB0X MVQG2R7iUfOzATaF5R3hQJk8CwyURYKQ0Ye0iR3bHfnMCIEU+nrglojKwJanfcoq9IsR6l/OZb9V MEM= X-Report-Abuse-To: spam@quarantine11.antispamcloud.com Archived-At: Subject: Re: [dnssd] [Last-Call] Iotdir last call review of draft-ietf-dnssd-prireq-04 X-BeenThere: dnssd@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of extensions to DNS-based service discovery for routed networks." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Feb 2020 18:37:28 -0000 Thanks for the review, Samita. We will try to add some precisions about IoT devices in the next version of the draft. On 2/13/2020 9:31 AM, Samita Chakrabarti via Datatracker wrote: > Reviewer: Samita Chakrabarti > Review result: Ready with Nits > > I have reviewed draft-ietf-dnssd-prireq-04. > > The document is informative and clear with a few editorial nits on section 4.1 > through 4.3. > > I have reviewed from the IoT devices perspective and most likely for the > consumer devices that might be present in the public network and are using > shared network technologies (wireless or wired). The threat model are > applicable to them. Section 3.1 describes implications for wearable and server > related privacy issue. Perhaps a small paragraph might be added in this > section or in the introduction calling out possible privacy and security > threats on personal IoT devices in the public places ( that might act as a > dns-sd client). > > At the same time, considering limited processing capabilities, battery saving > concern considerations, privacy related extra processing of messages from the > dns-sd server should not be mandated for the IoT devices. Depending on the > device capabilities, the feature can be configurable and the user can turn > on/off at their need; additionally some iot devices may not care about the > privacy at all. > > So, a few additional lines on IoT implications for the threat model and yet > flexibility of implementation of the dns-sd IOT client may be mentioned in the > document to clarify the IoT devices in the shared wireless/wired medium. > > From nobody Thu Feb 13 10:45:18 2020 Return-Path: X-Original-To: dnssd@ietfa.amsl.com Delivered-To: dnssd@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7CF601201CE for ; Thu, 13 Feb 2020 10:45:15 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.6 X-Spam-Level: X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, 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 AxDfA1c7PrCh for ; Thu, 13 Feb 2020 10:45:14 -0800 (PST) Received: from mx36-out10.antispamcloud.com (mx36-out10.antispamcloud.com [209.126.121.30]) (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 132731201AA for ; Thu, 13 Feb 2020 10:45:14 -0800 (PST) Received: from xse334.mail2web.com ([66.113.197.80] helo=xse.mail2web.com) by mx62.antispamcloud.com with esmtp (Exim 4.92) (envelope-from ) id 1j2JU7-0007kv-7F for dnssd@ietf.org; Thu, 13 Feb 2020 19:45:12 +0100 Received: from xsmtp21.mail2web.com (unknown [10.100.68.60]) by xse.mail2web.com (Postfix) with ESMTPS id 48JQRp21xSzLJ9 for ; Thu, 13 Feb 2020 10:45:10 -0800 (PST) Received: from [10.5.2.18] (helo=xmail08.myhosting.com) by xsmtp21.mail2web.com with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from ) id 1j2JU6-0005ie-59 for dnssd@ietf.org; Thu, 13 Feb 2020 10:45:10 -0800 Received: (qmail 18111 invoked from network); 13 Feb 2020 18:45:09 -0000 Received: from unknown (HELO [192.168.1.103]) (Authenticated-user:_huitema@huitema.net@[172.58.43.97]) (envelope-sender ) by xmail08.myhosting.com (qmail-ldap-1.03) with ESMTPA for ; 13 Feb 2020 18:45:09 -0000 To: Ted Lemon , Samita Chakrabarti Cc: draft-ietf-dnssd-prireq.all@ietf.org, last-call@ietf.org, DNSSD References: <158161511905.20519.9851954062722453601@ietfa.amsl.com> From: Christian Huitema Autocrypt: addr=huitema@huitema.net; prefer-encrypt=mutual; keydata= mQENBFIRX8gBCAC26usy/Ya38IqaLBSu33vKD6hP5Yw390XsWLaAZTeQR64OJEkoOdXpvcOS HWfMIlD5s5+oHfLe8jjmErFAXYJ8yytPj1fD2OdSKAe1TccUBiOXT8wdVxSr5d0alExVv/LO I/vA2aU1TwOkVHKSapD7j8/HZBrqIWRrXUSj2f5n9tY2nJzG9KRzSG0giaJWBfUFiGb4lvsy IaCaIU0YpfkDDk6PtK5YYzuCeF0B+O7N9LhDu/foUUc4MNq4K3EKDPb2FL1Hrv0XHpkXeMRZ olpH8SUFUJbmi+zYRuUgcXgMZRmZFL1tu6z9h6gY4/KPyF9aYot6zG28Qk/BFQRtj7V1ABEB AAG0J0NocmlzdGlhbiBIdWl0ZW1hIDxodWl0ZW1hQGh1aXRlbWEubmV0PokBOQQTAQIAIwUC UhFfyAIbLwcLCQgHAwIBBhUIAgkKCwQWAgMBAh4BAheAAAoJEJNDCbJVyA1yhbYH/1ud6x6m VqGIp0JcZUfSQO8w+TjugqxCyGNn+w/6Qb5O/xENxNQ4HaMQ5uSRK9n8WKKDDRSzwZ4syKKf wbkfj05vgFxrjCynVbm1zs2X2aGXh+PxPL/WHUaxzEP7KjYbLtCUZDRzOOrm+0LMktngT/k3 6+EZoLEM52hwwpIAzJoscyEz7QfqMOZtFm6xQnlvDQeIrHx0KUvwo/vgDLK3SuruG1CSHcR0 D24kEEUa044AIUKBS3b0b8AR7f6mP2NcnLpdsibtpabi9BzqAidcY/EjTaoea46HXALk/eJd 6OLkLE6UQe1PPzQC4jB7rErX2BxnSkHDw50xMgLRcl5/b1a5AQ0EUhFfyAEIAKp7Cp8lqKTV CC9QiAf6QTIjW+lie5J44Ad++0k8gRgANZVWubQuCQ71gxDWLtxYfFkEXjG4TXV/MUtnOliG 5rc2E+ih6Dg61Y5PQakm9OwPIsOx+2R+iSW325ngln2UQrVPgloO83QiUoi7mBJPbcHlxkhZ bd3+EjFxSLIQogt29sTcg2oSh4oljUpz5niTt69IOfZx21kf29NfDE+Iw56gfrxI2ywZbu5o G+d0ZSp0lsovygpk4jK04fDTq0vxjEU5HjPcsXC4CSZdq5E2DrF4nOh1UHkHzeaXdYR2Bn1Y wTePfaHBFlvQzI+Li/Q6AD/uxbTM0vIcsUxrv3MNHCUAEQEAAYkCPgQYAQIACQUCUhFfyAIb LgEpCRCTQwmyVcgNcsBdIAQZAQIABgUCUhFfyAAKCRC22tOSFDh1UOlBB/94RsCJepNvmi/c YiNmMnm0mKb6vjv43OsHkqrrCqJSfo95KHyl5Up4JEp8tiJMyYT2mp4IsirZHxz/5lqkw9Az tcGAF3GlFsj++xTyD07DXlNeddwTKlqPRi/b8sppjtWur6Pm+wnAHp0mQ7GidhxHccFCl65w uT7S/ocb1MjrTgnAMiz+x87d48n1UJ7yIdI41Wpg2XFZiA9xPBiDuuoPwFj14/nK0elV5Dvq 4/HVgfurb4+fd74PV/CC/dmd7hg0ZRlgnB5rFUcFO7ywb7/TvICIIaLWcI42OJDSZjZ/MAzz BeXm263lHh+kFxkh2LxEHnQGHCHGpTYyi4Z3dv03HtkH/1SI8joQMQq00Bv+RdEbJXfEExrT u4gtdZAihwvy97OPA2nCdTAHm/phkzryMeOaOztI4PS8u2Ce5lUB6P/HcGtK/038KdX5MYST Fn8KUDt4o29bkv0CUXwDzS3oTzPNtGdryBkRMc9b+yn9+AdwFEH4auhiTQXPMnl0+G3nhKr7 jvzVFJCRif3OAhEm4vmBNDE3uuaXFQnbK56GJrnqVN+KX5Z3M7X3fA8UcVCGOEHXRP/aubiw Ngawj0V9x+43kUapFp+nF69R53UI65YtJ95ec4PTO/Edvap8h1UbdEOc4+TiYwY1TBuIKltY 1cnrjgAWUh/Ucvr++/KbD9tD6C8= Message-ID: Date: Thu, 13 Feb 2020 10:45:09 -0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Language: en-US X-Originating-IP: 66.113.197.80 X-Spampanel-Domain: xsmtpout.mail2web.com X-Spampanel-Username: 66.113.197.0/24 Authentication-Results: antispamcloud.com; auth=pass smtp.auth=66.113.197.0/24@xsmtpout.mail2web.com X-Spampanel-Outgoing-Class: unsure X-Spampanel-Outgoing-Evidence: Combined (0.15) X-Recommended-Action: accept X-Filter-ID: Mvzo4OR0dZXEDF/gcnlw0QHHUXH8HYgJuwhvgiygxCWpSDasLI4SayDByyq9LIhVK9prosleN3yI FHT1CgO2zUTNWdUk1Ol2OGx3IfrIJKywOmJyM1qr8uRnWBrbSAGDoeDwbaJnZ2TaZhv/Bk6d8Jj9 EvBvwu01uVCaGVBWGqvkLnuS+XYHUT8QRJrvghfu2rBNMmEsKEibQwSU1xBeOHButNDpi1WUXRkr He1vFsYm1aGKgRFqmjZjxZofiz4rBXfTi7gDmaugbDBQV1VSRryme9ldZJ7uNXfg/GfS8fUvP/L5 rCqHDsKZM+xa1iwJX+gRCHfMVnsAk591zk0uilUI+ZL4xWiN8NS6C+dmX6OEdA4u1aThyWrQ/ou2 +v/lmX4Em37yFgrCB6NHRn1g+f3uncIqYSL3lhh5c81YyJqFoLZMmkWsaurVZfvqROaDnDtHb8z5 dpPkEuJ8Snwqla7jUnW3hy14Yji8fo+4xCnSRo4Rcu5Z37rMuDjCny5fE9ykbJ7I9co1MAEE3ruN Xsm8UJsAPvDcVSKtDCYkioPY5Qx4fJOk03R5fJtf/Dv/dkIzS7m4GUpXCY1Y3j3ilUzW4cMJiJyc Gks9WKBuupO0P9vl2nz+rVVSok0CBMGw14xPbUivFNWp6nCDOfUYccgbFBW5YxM/YOomoTsuFSR8 g2fGU86cSswil+kDetUfttbLHdNhiUq2jBEvMVLlZ4GThCScvU0cCIiHSQbmcVJ5KU/AfPaxwF20 1uuZdk7jWDvBhuNO4tpnc980Bg7nrU/bHjDx3g9K/ll+sxTNAqQgNr912iD9Qi/sgiqno0FwXPWl FdaGOH191uXjgjQN/bk/tOvsMDZmQNfeGxdXg4Hd0dcpOBA0Wd48n1CerqZ683g9ueTJOU6a76yp yxjdeg8YhWenlMfuvb1mNY5/IPiuedK/Z3MvnAyDmuOaA5CGZRWsGw8ac2InzcAP/gmxwNpms+rB 6wJM+NNhN3aT35NSU/fjw6KbqLw80r1gDO3m6U0LjBzYuQztdAThgtWSU3qCINKqlAdh+ePAcEwD s/8= X-Report-Abuse-To: spam@quarantine11.antispamcloud.com Archived-At: Subject: Re: [dnssd] [Last-Call] Iotdir last call review of draft-ietf-dnssd-prireq-04 X-BeenThere: dnssd@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of extensions to DNS-based service discovery for routed networks." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Feb 2020 18:45:15 -0000 On 2/13/2020 9:47 AM, Ted Lemon wrote: > 100% agree with your first point. > > Regarding your second point, one of the classic use cases for dns-sd pr= ivacy is a pacemaker. This is a battery-operated device, but the user sh= ould not have to broadcast the fact that they have a pacemaker installed = whenever they are walking around out in the world. > > So if you think that the requirements really do not address the power c= onsumption issue, that is something that should be added to the document = as a requirement, rather than saying that in such cases privacy can be op= tional. We tried to address that in the section 3.4, Operational Considerations. Samita, do you think we should have some specific text there? I am always worried about forcing a trade-off between privacy and power consumption. There may be devices such as sensors in buildings for which the privacy considerations are minimum, but there are clear requirements for any "wearable" device. Ted's example of a pacemaker is an obvious one, but even something benign as "smart jewelry" would have obvious implications. -- Christian Huitema From nobody Mon Feb 17 18:38:33 2020 Return-Path: X-Original-To: dnssd@ietfa.amsl.com Delivered-To: dnssd@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96A72120020 for ; Mon, 17 Feb 2020 07:45:19 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=uni.lu 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 LGQ6f-fB5UUT for ; Mon, 17 Feb 2020 07:45:16 -0800 (PST) Received: from smtp2.uni.lu (smtp2.uni.lu [IPv6:2001:a18:a:c5::e]) (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 507FE120018 for ; Mon, 17 Feb 2020 07:45:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=uni.lu; i=@uni.lu; q=dns/txt; s=DKIM; t=1581954316; x=1613490316; h=subject:references:to:from:message-id:date:mime-version: in-reply-to:content-transfer-encoding; bh=02EeI7KbWOcnq11WUpYEEuW1WNTWURdTlwZzJ/TAJfg=; b=D3sf8yMfKvc59ij5z9PBlvZdXKbLtvPc4FsAM00DvvqMqi3P/ha1ashr BsoUNAgExI8KswvHcKv49ysZDAQpmjNWAfdKpwdKvCE//woSKgWhbHrlE o1tCLakXv0Yzpht9NqOdmTLa/62BKjZtzQ6f6nFNG8C1Yja6T5f1MmpMI SRn3NloZFtmx2I43JDVH/Tr2XE9jEt2RlKe7uKth4iwkmUrLKEL41k6Uu 2xiIuL4PEyiJybS80x5S6fYfNy7o+OUCDQiMPJE6W78DH4IWLtMNIM5kV v30BQdXQcoF77WZgMGdA6IWMwto+rEK0H2Q6ok0aQ/nvqVf42NdSNiY8C w==; IronPort-SDR: dZFoKB+mzhgqTVR2DEEanpIccTuCdwkkTfKe/QrJkp+Mbo50W8ed6VaBdaOtdvxitM1C0CFx35 r8nXSVGarwTQ== X-IronPort-AV: E=Sophos;i="5.70,453,1574118000"; d="scan'208";a="27619812" References: <8da51e40-e2a0-fd39-df6a-6440b2e91c41@uni.lu> To: DNSSD From: Daniel KAISER X-Forwarded-Message-Id: <8da51e40-e2a0-fd39-df6a-6440b2e91c41@uni.lu> Message-ID: <89ebac8b-8446-a0c1-0a96-d719c5d4654f@uni.lu> Date: Mon, 17 Feb 2020 16:45:08 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.4.2 MIME-Version: 1.0 In-Reply-To: <8da51e40-e2a0-fd39-df6a-6440b2e91c41@uni.lu> Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-Originating-IP: [10.244.9.68] X-ClientProxiedBy: Quinn2017.uni.lux (2001:a18:a:90::75) To lydia2017.uni.lux (2001:a18:a:90::6f) Archived-At: Subject: [dnssd] last call reviews of draft-ietf-dnssd-prireq-04 X-BeenThere: dnssd@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of extensions to DNS-based service discovery for routed networks." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Feb 2020 15:45:20 -0000 Dear all, I have addressed each feedback item in the last call reviews and pushed a PR to our git repo: https://github.com/huitema/dnssd-privreq/pull/12 kind regards, Daniel From nobody Wed Feb 19 07:56:48 2020 Return-Path: X-Original-To: dnssd@ietfa.amsl.com Delivered-To: dnssd@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5F1612022C; Wed, 19 Feb 2020 07:56:33 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -14.501 X-Spam-Level: X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=JsiQ01gm; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=KU+ILcXe 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 mpe2efGBUf4g; Wed, 19 Feb 2020 07:56:32 -0800 (PST) Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EFC94120154; Wed, 19 Feb 2020 07:56:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2982; q=dns/txt; s=iport; t=1582127792; x=1583337392; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=MC6e69rtyqU3DepSR1fyXgyJsNLQAso5l1aaEwM0ROs=; b=JsiQ01gmjbulOqu8AcO157JrpU00pPm6hl7wEotMXNDK18T0GeGoSOkP 6spo6W9vRMcwX1KjfuX1PoDJlM78gWmTje9Oc03BnZri77haW0g88FdCp 5nCEGgBTUvL+9y6Ws9CtxpvK3Inii6nAy9lgoHZJX2uUZO/yonzw1skzk 0=; IronPort-PHdr: =?us-ascii?q?9a23=3AQ5YIKxQnoz8fxTOs2Q5Lqcg6+9psv++ubAcI9p?= =?us-ascii?q?oqja5Pea2//pPkeVbS/uhpkESXBdfA8/wRje3QvuigQmEG7Zub+FE6OJ1XH1?= =?us-ascii?q?5g640NmhA4RsuMCEn1NvnvOiEkDcJJV1JN9HCgOk8TE8H7NBXf?= X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CiBQC9WU1e/5NdJa1mHAEBAQEBBwE?= =?us-ascii?q?BEQEEBAEBgXuBVFAFbFggBAsqhBSDRgOKcYI6JZgRglIDVAkBAQEMAQEYCwo?= =?us-ascii?q?CBAEBhEACF4FtJDgTAgMNAQEFAQEBAgEFBG2FNwyFZwEBAQMBARAREQwBASw?= =?us-ascii?q?CCQEPAgEIGAICJgICAiULFRACBAENBSKDBAGCSgMuAQ6iYQKBOYhidYEygn8?= =?us-ascii?q?BAQWFOxiCDAMGgQ4qjCQagUE/gTgMFIIeLj6CZAEBgSIaERgXgnkygiyQY55?= =?us-ascii?q?CcAqCO5ZgHJsrjm+bRQIEAgQFAg4BAQWBaSKBWHAVOyoBgkFQGA2OHYNzhRS?= =?us-ascii?q?FP3SBKYsngkMBAQ?= X-IronPort-AV: E=Sophos;i="5.70,461,1574121600"; d="scan'208";a="455325230" Received: from rcdn-core-11.cisco.com ([173.37.93.147]) by alln-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 19 Feb 2020 15:56:31 +0000 Received: from XCH-RCD-001.cisco.com (xch-rcd-001.cisco.com [173.37.102.11]) by rcdn-core-11.cisco.com (8.15.2/8.15.2) with ESMTPS id 01JFuUCA006559 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 19 Feb 2020 15:56:30 GMT Received: from xhs-rcd-001.cisco.com (173.37.227.246) by XCH-RCD-001.cisco.com (173.37.102.11) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 19 Feb 2020 09:56:30 -0600 Received: from xhs-rtp-002.cisco.com (64.101.210.229) by xhs-rcd-001.cisco.com (173.37.227.246) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 19 Feb 2020 09:56:29 -0600 Received: from NAM11-BN8-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Wed, 19 Feb 2020 10:56:29 -0500 ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Tugpsy/gI+khiXegEZCqB77cNwa+cSENkEC26F3SZ9/zHZle7Viz63SfdybiWekmSALQdKlF7wmEn5/2ZnTWo/8Tl10JUlC0db40W5y6/Nsknji68RlLU1IlFM8tUuMx5kNAaQsZUnYBZZKbEmgTnmYU/wRbydwuCmaGE2WYYAM6duok2S0T3Vnl7qb3q5Vcf2i8QF63Zf7p0uo/+8CbyPrHqFk2IWbp6Q1yKzz0qZS0kTUumt2Fc8SVHJGhJQU4l0Yae43sHpaHiL+jRcrhjeen9s8Br3dZs3pya1ycbskM0Pyx+H3dSXsj/zEvvx7jfy2fopWTJQ731TunGP7IDg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=MC6e69rtyqU3DepSR1fyXgyJsNLQAso5l1aaEwM0ROs=; b=EACMngI0kiB+wgFnVHyeJ24RThih6R8s7NVOpHvJO/WGL6u1avJkGewAEjTm/h1H8VZGoxRYDqL4vacgeOMNkJplCHF7xWBiSLabAcmXEqmAGvj8NNm1coZF3WzrWQ14BvezBzbsCE8CcjD66Ti98pqp4TqZWApKzlNxIrnsmeH0cfzmB4CGuCDOAvgF1h5wEu6A68ynKOBB5r2btadU4n/T1UpjgMkhnxxAcCDXNqJKyBAylisssHp7NhH47dq6D9pSIzQMD4u6cjUA0hsJfGiQLX+vv9fUtuw/M8HmAqkKr8qkuB4U/pxjBO210vc5Nmazx8NwUV9OS1bLt6n3fA== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=MC6e69rtyqU3DepSR1fyXgyJsNLQAso5l1aaEwM0ROs=; b=KU+ILcXebMkmyzFZDcgIes4Mkjm5mVfnhPe6OokKfP5k9moKWk473sGjhtzjPOqZPeUwUQ8kuzuU6RRsSRKSmKr7U9ouMS53yZfa5JpCpgmIPqEAhRODnWUcfQ2rZzKmbS6Ka44OMpm4CxlsrrzizSQDNS1lxsML4PXZvcgQAaE= Received: from DM5PR11MB1753.namprd11.prod.outlook.com (10.175.88.141) by DM5PR11MB0074.namprd11.prod.outlook.com (10.164.154.24) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2729.31; Wed, 19 Feb 2020 15:56:29 +0000 Received: from DM5PR11MB1753.namprd11.prod.outlook.com ([fe80::680d:e22e:72d5:67ca]) by DM5PR11MB1753.namprd11.prod.outlook.com ([fe80::680d:e22e:72d5:67ca%3]) with mapi id 15.20.2729.032; Wed, 19 Feb 2020 15:56:28 +0000 From: "Eric Vyncke (evyncke)" To: Christian Huitema , Samita Chakrabarti , "iot-directorate@ietf.org" CC: "draft-ietf-dnssd-prireq.all@ietf.org" , "last-call@ietf.org" , "dnssd@ietf.org" Thread-Topic: [Last-Call] Iotdir last call review of draft-ietf-dnssd-prireq-04 Thread-Index: AQHV4pOLoWNXcboSwEycv2RebvIkgqgZc9mAgAlSDQA= Date: Wed, 19 Feb 2020 15:56:28 +0000 Message-ID: <97B94441-77A4-4497-AEC4-F4E29F637F08@cisco.com> References: <158161511905.20519.9851954062722453601@ietfa.amsl.com> In-Reply-To: Accept-Language: fr-BE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/10.22.0.200209 authentication-results: spf=none (sender IP is ) smtp.mailfrom=evyncke@cisco.com; x-originating-ip: [2001:420:c0c1:36:f842:aaed:6557:3770] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: ad029280-fe62-4077-18c2-08d7b554483a x-ms-traffictypediagnostic: DM5PR11MB0074: x-microsoft-antispam-prvs: x-ms-oob-tlc-oobclassifiers: OLM:8882; x-forefront-prvs: 0318501FAE x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(346002)(376002)(366004)(396003)(39860400002)(136003)(189003)(199004)(66946007)(66476007)(66446008)(66556008)(64756008)(2616005)(5660300002)(6512007)(186003)(4326008)(2906002)(6486002)(81166006)(316002)(81156014)(966005)(8676002)(6506007)(76116006)(53546011)(36756003)(8936002)(110136005)(91956017)(33656002)(86362001)(478600001)(71200400001)(54906003); DIR:OUT; SFP:1101; SCL:1; SRVR:DM5PR11MB0074; H:DM5PR11MB1753.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam: BCL:0; x-microsoft-antispam-message-info: QHCv+rN4SMky1YmKwMPqF+3yq/VTzzZ3kUHPkxFvjCpiarq4NQ2vM7TSCFrbHPc0Mo2qJY87YCGN8KVlcuqvTJ53EGuJEZoPQOzuz6Jg9s4G2CAmIZ+aT6qZ9bcsETtxyMrUvdZqf+X5tj7jO9FXHUPAwVd6ClCnoJEz55HNohdvbzRSz/iKUR5SryrfSWnzGF+KkSVNKU0tA3Ph2B6r5Je+iqel9IJIR1++CzJk4309pIq8iAkaI9fZa7K2dE3fukVtbGyaQqG+Egc0FNYNaHU0lWvFhj8OxOQsvFR7erZGQ7Twaun7pkRcYlX2wtMbXgK9l88mf1MNyMH6IagBZv3pDeYMKuuYUzhIJxZXA5T+vbC4otuPVp1kH9pqLdoTdIiIWlwiPE57DkZwti9mE2p9JjJSHV+H9lpBGVj5pKFrw6BZxct2zl1Px/k6OfeFNeogZFyh5WnqMXdHwJZN+j94/vs0EyGZIDtAYwzDVQNcgOeZzonlvfKrBpACK+kqLEvVCjA+dTUQRET6coymDQ== x-ms-exchange-antispam-messagedata: Z90rl5sj61DTe8jV2Ga9MlmkrOhjeWUGWVTMXE7qazezXb6/pPX4a0yxt981dAs+seu2b4WkHRY40IoHPa5vKYxRgHO+jS2Q/1Xk/CrTyH2P2M0Sk19BAl9/T0kCzMzHaCtWPEbBCGdRHuoyHiuf2PhdHR8LCjJ33u2Gu9Fkxo1R4kK+EnxFHT6iMuKt0kqHjJ+74PeeZmdVDdKZC7xxkw== x-ms-exchange-transport-forked: True Content-Type: text/plain; charset="utf-8" Content-ID: <43CB379D46DC8F40A16175B6229EC0D9@namprd11.prod.outlook.com> Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-MS-Exchange-CrossTenant-Network-Message-Id: ad029280-fe62-4077-18c2-08d7b554483a X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Feb 2020 15:56:28.9202 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: 8ym4X0yyj2+7FnfGQ9E//0MvxTz7wntaNK+ZDDySSbUj5Niup+3yJ84vAKMljgPnRPxcG47WfKFCKO35WkRH+w== X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR11MB0074 X-OriginatorOrg: cisco.com X-Outbound-SMTP-Client: 173.37.102.11, xch-rcd-001.cisco.com X-Outbound-Node: rcdn-core-11.cisco.com Archived-At: Subject: Re: [dnssd] [Last-Call] Iotdir last call review of draft-ietf-dnssd-prireq-04 X-BeenThere: dnssd@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of extensions to DNS-based service discovery for routed networks." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Feb 2020 15:56:40 -0000 W1NvcnJ5IGZvciBiZWxhdGVkIHJlcGx5LCBJIHdhcyBvbiB2YWNhdGlvbnNdDQoNClRoYW5rIHlv dSBTYW1pdGEgZm9yIHlvdXIgcmV2aWV3IGFuZCB0aGFuayB5b3UgQ2hyaXN0aWFuIGFuZCBUZWQg Zm9yIHlvdXIgcmVwbGllcw0KDQotw6lyaWMNCg0K77u/T24gMTMvMDIvMjAyMCwgMTk6MzcsICJs YXN0LWNhbGwgb24gYmVoYWxmIG9mIENocmlzdGlhbiBIdWl0ZW1hIiA8bGFzdC1jYWxsLWJvdW5j ZXNAaWV0Zi5vcmcgb24gYmVoYWxmIG9mIGh1aXRlbWFAaHVpdGVtYS5uZXQ+IHdyb3RlOg0KDQog ICAgVGhhbmtzIGZvciB0aGUgcmV2aWV3LCBTYW1pdGEuIFdlIHdpbGwgdHJ5IHRvIGFkZCBzb21l IHByZWNpc2lvbnMgYWJvdXQNCiAgICBJb1QgZGV2aWNlcyBpbiB0aGUgbmV4dCB2ZXJzaW9uIG9m IHRoZSBkcmFmdC4NCiAgICANCiAgICBPbiAyLzEzLzIwMjAgOTozMSBBTSwgU2FtaXRhIENoYWty YWJhcnRpIHZpYSBEYXRhdHJhY2tlciB3cm90ZToNCiAgICA+IFJldmlld2VyOiBTYW1pdGEgQ2hh a3JhYmFydGkNCiAgICA+IFJldmlldyByZXN1bHQ6IFJlYWR5IHdpdGggTml0cw0KICAgID4NCiAg ICA+IEkgaGF2ZSByZXZpZXdlZCBkcmFmdC1pZXRmLWRuc3NkLXByaXJlcS0wNC4NCiAgICA+DQog ICAgPiBUaGUgZG9jdW1lbnQgaXMgaW5mb3JtYXRpdmUgYW5kIGNsZWFyIHdpdGggYSBmZXcgZWRp dG9yaWFsIG5pdHMgb24gc2VjdGlvbiA0LjENCiAgICA+IHRocm91Z2ggNC4zLg0KICAgID4NCiAg ICA+IEkgaGF2ZSByZXZpZXdlZCBmcm9tIHRoZSBJb1QgZGV2aWNlcyBwZXJzcGVjdGl2ZSAgYW5k IG1vc3QgbGlrZWx5IGZvciB0aGUNCiAgICA+IGNvbnN1bWVyIGRldmljZXMgdGhhdCBtaWdodCBi ZSBwcmVzZW50IGluIHRoZSBwdWJsaWMgbmV0d29yayBhbmQgYXJlIHVzaW5nDQogICAgPiBzaGFy ZWQgbmV0d29yayB0ZWNobm9sb2dpZXMgKHdpcmVsZXNzIG9yIHdpcmVkKS4gVGhlIHRocmVhdCBt b2RlbCBhcmUNCiAgICA+IGFwcGxpY2FibGUgdG8gdGhlbS4gU2VjdGlvbiAzLjEgZGVzY3JpYmVz IGltcGxpY2F0aW9ucyBmb3Igd2VhcmFibGUgYW5kICBzZXJ2ZXINCiAgICA+IHJlbGF0ZWQgcHJp dmFjeSBpc3N1ZS4gIFBlcmhhcHMgYSBzbWFsbCBwYXJhZ3JhcGggbWlnaHQgYmUgYWRkZWQgaW4g dGhpcw0KICAgID4gc2VjdGlvbiBvciBpbiB0aGUgaW50cm9kdWN0aW9uIGNhbGxpbmcgb3V0IHBv c3NpYmxlIHByaXZhY3kgYW5kIHNlY3VyaXR5DQogICAgPiB0aHJlYXRzIG9uIHBlcnNvbmFsIElv VCBkZXZpY2VzIGluIHRoZSBwdWJsaWMgcGxhY2VzICggdGhhdCBtaWdodCBhY3QgYXMgYQ0KICAg ID4gZG5zLXNkIGNsaWVudCkuDQogICAgPg0KICAgID4gQXQgdGhlIHNhbWUgdGltZSwgY29uc2lk ZXJpbmcgbGltaXRlZCBwcm9jZXNzaW5nIGNhcGFiaWxpdGllcywgYmF0dGVyeSBzYXZpbmcNCiAg ICA+IGNvbmNlcm4gY29uc2lkZXJhdGlvbnMsIHByaXZhY3kgcmVsYXRlZCBleHRyYSBwcm9jZXNz aW5nIG9mIG1lc3NhZ2VzIGZyb20gdGhlDQogICAgPiBkbnMtc2Qgc2VydmVyIHNob3VsZCBub3Qg YmUgbWFuZGF0ZWQgZm9yIHRoZSBJb1QgZGV2aWNlcy4gRGVwZW5kaW5nIG9uIHRoZQ0KICAgID4g ZGV2aWNlIGNhcGFiaWxpdGllcywgdGhlIGZlYXR1cmUgY2FuIGJlIGNvbmZpZ3VyYWJsZSBhbmQg dGhlIHVzZXIgY2FuIHR1cm4NCiAgICA+IG9uL29mZiAgYXQgdGhlaXIgbmVlZDsgYWRkaXRpb25h bGx5IHNvbWUgaW90IGRldmljZXMgbWF5IG5vdCBjYXJlIGFib3V0IHRoZQ0KICAgID4gcHJpdmFj eSBhdCBhbGwuDQogICAgPg0KICAgID4gU28sIGEgZmV3IGFkZGl0aW9uYWwgbGluZXMgb24gSW9U IGltcGxpY2F0aW9ucyBmb3IgdGhlIHRocmVhdCBtb2RlbCBhbmQgeWV0DQogICAgPiBmbGV4aWJp bGl0eSBvZiBpbXBsZW1lbnRhdGlvbiBvZiB0aGUgZG5zLXNkIElPVCBjbGllbnQgbWF5IGJlIG1l bnRpb25lZCBpbiB0aGUNCiAgICA+IGRvY3VtZW50IHRvIGNsYXJpZnkgdGhlIElvVCBkZXZpY2Vz IGluIHRoZSBzaGFyZWQgd2lyZWxlc3Mvd2lyZWQgbWVkaXVtLg0KICAgID4NCiAgICA+DQogICAg DQogICAgLS0gDQogICAgbGFzdC1jYWxsIG1haWxpbmcgbGlzdA0KICAgIGxhc3QtY2FsbEBpZXRm Lm9yZw0KICAgIGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vbGFzdC1jYWxs DQogICAgDQoNCg== From nobody Wed Feb 19 07:57:49 2020 Return-Path: X-Original-To: dnssd@ietfa.amsl.com Delivered-To: dnssd@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2281C120805; Wed, 19 Feb 2020 07:57:33 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -14.501 X-Spam-Level: X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=RhDUAs+w; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=h5YTaK/6 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 QDTd0eCw923S; Wed, 19 Feb 2020 07:57:31 -0800 (PST) Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 043261201CE; Wed, 19 Feb 2020 07:57:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1626; q=dns/txt; s=iport; t=1582127850; x=1583337450; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=uFASJcL2dQZU9N8qCI3N5YmN5vUXSk+WmzPr/wVnX4E=; b=RhDUAs+w2VXRKv64Q2i/V2JSpxAVrpSF/oN6V2bD8Mvi+wZxIDZk0NHW ec6fxz7ZND6bpoqAB/TbHRIpjCJAebkenqksbU7of1W5tT7Ay9D0gjEOS giNlrTz19H0lOFJA+QzUVoKZSGf9zMxNjHgqACm6ugEDNl4Oq5COIrpEY E=; IronPort-PHdr: =?us-ascii?q?9a23=3Axkwd6h9S5vZuL/9uRHGN82YQeigqvan1NQcJ65?= =?us-ascii?q?0hzqhDabmn44+8ZB7E/fs4iljPUM2b8P9Ch+fM+4HYEW0bqdfk0jgZdYBUER?= =?us-ascii?q?oMiMEYhQslVcObGEvwL/PCZC0hF8MEX1hgrDm2?= X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CgBQBsWk1e/4sNJK1mHAEBAQEBBwE?= =?us-ascii?q?BEQEEBAEBgXuBVFAFbFggBAsqhBSDRgOKcII6mDaCUgNUCQEBAQwBARgLCgI?= =?us-ascii?q?EAQGEQAIXgW0kOBMCAw0BAQUBAQECAQUEbYU3DIVnAgEDAQEQEREMAQEsCwE?= =?us-ascii?q?PAgEIDgwCJgICAiULFRACBAENBQkZgwQBgkoDLgEOomkCgTmIYnWBMoJ/AQE?= =?us-ascii?q?FhTsYggwJgQ4qjCQagUE/gTgMFIIeLj6CWQsBAQGBZBeCeTKCLI1cgwefMgq?= =?us-ascii?q?CO5IuhDIcmyuOb4Z0lFECBAIEBQIOAQEFgWkigVIGcBU7KgGCQQlHGA2OHYN?= =?us-ascii?q?zhRSFP3QCgSeNagEB?= X-IronPort-AV: E=Sophos;i="5.70,461,1574121600"; d="scan'208";a="719712517" Received: from alln-core-6.cisco.com ([173.36.13.139]) by rcdn-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 19 Feb 2020 15:57:29 +0000 Received: from XCH-ALN-001.cisco.com (xch-aln-001.cisco.com [173.36.7.11]) by alln-core-6.cisco.com (8.15.2/8.15.2) with ESMTPS id 01JFvUEu006530 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 19 Feb 2020 15:57:30 GMT Received: from xhs-rcd-002.cisco.com (173.37.227.247) by XCH-ALN-001.cisco.com (173.36.7.11) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 19 Feb 2020 09:57:29 -0600 Received: from xhs-rcd-001.cisco.com (173.37.227.246) by xhs-rcd-002.cisco.com (173.37.227.247) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 19 Feb 2020 09:57:28 -0600 Received: from NAM12-MW2-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-001.cisco.com (173.37.227.246) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Wed, 19 Feb 2020 09:57:28 -0600 ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=IoW8LqkvCgvhZOt/xaatSz5SAnkgBHydj9a0HoMRdlcO/l6BWOP6QmEgm19+BRwWJfIp8kXf+78WDvohLeFJxBywyxWidUFCJwgt1a4Q3SvB4MKLIDsXxM8ZtVYO7YaAX+prx6dr7IRWA7Xfk0Q8xn9tIhOVIof9nkebW2KgFy5SEm47UqtVdSMDhTUjYiAWYZkfhRUGOixIYqEJCsebUKAO81DBwRcwosVMnANisnmNuQDbDAl5Bck6owCmcGP7HgasnXm7qd2WjYbbm+wu5j4jZS4JNjROZD3ZPVZ/1mlzYJr9HtQomswGGiDxFWHaydWWYR2Kmo9WnmZ807OYkQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=uFASJcL2dQZU9N8qCI3N5YmN5vUXSk+WmzPr/wVnX4E=; b=UTrAQ05K0a8Q1KuLnnxnqwXIOjcrJUucVDrpKx9mhcxJV8VFAsK/1kAQ3vRAOI/0W2b/GCw90TGAQUR4w7QUcRX72V2my7RlXyhY4EynptRR0qhxVOgKAT1pFczNOcjf6ZzNMm+E7Q/hW+NYspVWhYJx5JycQq1tpQ6L81alwdgjojvt9MTB+3Nt9RWaRr02hdRZl8nJO8xiFUP7VWl+XfCtwmP0qiwtoIPrAiAu/TFGMmTBgwhYVIwUQAy9oWV1o3wxFtff3giYQpCKwMoQwXdDfAUp+hlKT3WSPbyRe4ZWBdzb+bn8q0d6xy6kHMOYRT9iVxCmE8NrqnAn9cWxSw== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=uFASJcL2dQZU9N8qCI3N5YmN5vUXSk+WmzPr/wVnX4E=; b=h5YTaK/6P9UFtydk1ZDlcXv44ru9lH+rDhDSYxhh+ObNCWYSwjT/p/QXnv5FG7zmRtnO6binevvyXr/HgheVilrFlTMWJwkbuBDimr9wfmNFDbFjs+/XLprChSkOa056vCYnbGJBwIYOuMX9l488gvKBNC+07fpefMKXcHE2KwY= Received: from DM5PR11MB1753.namprd11.prod.outlook.com (10.175.88.141) by DM5PR11MB0009.namprd11.prod.outlook.com (10.164.154.10) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2729.25; Wed, 19 Feb 2020 15:57:27 +0000 Received: from DM5PR11MB1753.namprd11.prod.outlook.com ([fe80::680d:e22e:72d5:67ca]) by DM5PR11MB1753.namprd11.prod.outlook.com ([fe80::680d:e22e:72d5:67ca%3]) with mapi id 15.20.2729.032; Wed, 19 Feb 2020 15:57:27 +0000 From: "Eric Vyncke (evyncke)" To: Bob Halley , "int-dir@ietf.org" CC: "draft-ietf-dnssd-prireq.all@ietf.org" , "dnssd@ietf.org" Thread-Topic: [Int-dir] Intdir last call review of draft-ietf-dnssd-prireq-04 Thread-Index: AQHV16GlIvcuJkTrj0mp3A7gb425qKgi3BCA Date: Wed, 19 Feb 2020 15:57:27 +0000 Message-ID: References: <158041171662.10182.4141705117062266648@ietfa.amsl.com> In-Reply-To: <158041171662.10182.4141705117062266648@ietfa.amsl.com> Accept-Language: fr-BE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/10.22.0.200209 authentication-results: spf=none (sender IP is ) smtp.mailfrom=evyncke@cisco.com; x-originating-ip: [2001:420:c0c1:36:f842:aaed:6557:3770] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: 80e98880-13c7-4989-3203-08d7b5546b46 x-ms-traffictypediagnostic: DM5PR11MB0009: x-microsoft-antispam-prvs: x-ms-oob-tlc-oobclassifiers: OLM:7691; x-forefront-prvs: 0318501FAE x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(136003)(396003)(346002)(39860400002)(366004)(376002)(189003)(199004)(2616005)(81166006)(81156014)(33656002)(8676002)(86362001)(110136005)(2906002)(8936002)(5660300002)(36756003)(54906003)(186003)(6512007)(4326008)(6506007)(66574012)(316002)(66446008)(66946007)(6486002)(71200400001)(4744005)(478600001)(64756008)(66556008)(966005)(91956017)(76116006)(66476007); DIR:OUT; SFP:1101; SCL:1; SRVR:DM5PR11MB0009; H:DM5PR11MB1753.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam: BCL:0; x-microsoft-antispam-message-info: R8ls/1H3/aOLRAo4VXIV8nq4FIocPTJ0XZZBoAdBBBYwRSvA+YQMrEpFpAxnIZpkAXWxiKVoV6UT/2UT0sJxMgT5s7yxtYzh1Koj/Q8jNCGES7q11QQ12cISr7aSC4hciMuF8FIknn47JvimRy2KXqvWiIXHSYBSl4TQOc9KkzNW58t9Wp+KzbwclhmAq2M0jJ3tfwHe5OijdH1lisbtVLr98vrSysfp3M3+hOW4uJtvW26kD4PL+IQXAUSc5d0zGq4edElk8lYf2NBi2YIYoopUKHwvc8cVrUbvqUZGLyAWx4LB3aa4b4crFOs2whpiFLk2rj+bolwELJSfMaa/Z/B8ay2EqrSUOxzxv5URb4wSG8sPpqBlo/BqEySiNI95liM1GXlp3LpuwLwcTVqTrD8BVt6l3XvEG0VfPwFxDPuotKOjBsCgC4HZ3u9wLuuMu5sxvbe31uOSiDCZXzaX2fg31zGXJBbixCf8gFTKzWxPHhCyad/zsb4LdcjiDq7+LGpZVbL2ECD4h43w5aNpfQ== x-ms-exchange-antispam-messagedata: VBewwVAo3mcbFspBZFnvKB7tUelBqkiOlcU884neZjKMp/FgcWMgp7pTb94bcsBJxgNOMliRw9mZdfb7LLNHOp9ObPeGRDHKmdUzheL6uKsfkGNPzyUalSa/y5liJIliaY5nmSCIlehOKqqo3hqDVP3c6v3pJE5fGxWG+iINICxOoW1jUN0y8WVrZOStXbSO30ZlWv1kHOYlgbuf4NSYjA== x-ms-exchange-transport-forked: True Content-Type: text/plain; charset="utf-8" Content-ID: <6DAE80EBA22938479E36F1239A34B24F@namprd11.prod.outlook.com> Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-MS-Exchange-CrossTenant-Network-Message-Id: 80e98880-13c7-4989-3203-08d7b5546b46 X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Feb 2020 15:57:27.7337 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: jTcPFwpHf4OFaZgzbzapdYzmk6MwyBfusb/ODxDoIkKAn3zfjUqv7FhRTCxK3JfD77IeV3Y1YGWYQPcptoqFfg== X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR11MB0009 X-OriginatorOrg: cisco.com X-Outbound-SMTP-Client: 173.36.7.11, xch-aln-001.cisco.com X-Outbound-Node: alln-core-6.cisco.com Archived-At: Subject: Re: [dnssd] [Int-dir] Intdir last call review of draft-ietf-dnssd-prireq-04 X-BeenThere: dnssd@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of extensions to DNS-based service discovery for routed networks." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Feb 2020 15:57:38 -0000 VGhhbmsgeW91IHZlcnkgbXVjaCBCb2IgZm9yIHRoZSByZXZpZXchDQoNCkkgYWxzbyBsaWtlZCB0 aGUgQVNDSUkgYXJ0IGFuZCB0aGUgY2hvaWNlIG9mIGZpcnN0IG5hbWVzIDstKQ0KDQotw6lyaWMN Cg0K77u/T24gMzAvMDEvMjAyMCwgMjA6MTUsICJJbnQtZGlyIG9uIGJlaGFsZiBvZiBCb2IgSGFs bGV5IHZpYSBEYXRhdHJhY2tlciIgPGludC1kaXItYm91bmNlc0BpZXRmLm9yZyBvbiBiZWhhbGYg b2Ygbm9yZXBseUBpZXRmLm9yZz4gd3JvdGU6DQoNCiAgICBSZXZpZXdlcjogQm9iIEhhbGxleQ0K ICAgIFJldmlldyByZXN1bHQ6IFJlYWR5DQogICAgDQogICAgSSBhbSBhbiBhc3NpZ25lZCBJTlQg ZGlyZWN0b3JhdGUgcmV2aWV3ZXIgZm9yIGRyYWZ0LWlldGYtZG5zc2QtcHJpcmVxLiAgVGhlc2UN CiAgICBjb21tZW50cyB3ZXJlIHdyaXR0ZW4gcHJpbWFyaWx5IGZvciB0aGUgYmVuZWZpdCBvZiB0 aGUgSW50ZXJuZXQgQXJlYSBEaXJlY3RvcnMuDQogICAgRG9jdW1lbnQgZWRpdG9ycyBhbmQgc2hl cGhlcmQocykgc2hvdWxkIHRyZWF0IHRoZXNlIGNvbW1lbnRzIGp1c3QgbGlrZSB0aGV5DQogICAg d291bGQgdHJlYXQgY29tbWVudHMgZnJvbSBhbnkgb3RoZXIgSUVURiBjb250cmlidXRvcnMgYW5k IHJlc29sdmUgdGhlbSBhbG9uZw0KICAgIHdpdGggYW55IG90aGVyIExhc3QgQ2FsbCBjb21tZW50 cyB0aGF0IGhhdmUgYmVlbiByZWNlaXZlZC4gRm9yIG1vcmUgZGV0YWlscyBvbg0KICAgIHRoZSBJ TlQgRGlyZWN0b3JhdGUsIHNlZSBodHRwOi8vd3d3LmlldGYub3JnL2llc2cvZGlyZWN0b3JhdGUu aHRtbC4NCiAgICANCiAgICBUaGUgZHJhZnQgZG9lcyBhIHZlcnkgZ29vZCBqb2IgZXhwbGFpbmlu ZyB0aGUgcHJvYmxlbSBzcGFjZSBhbmQgaXRzDQogICAgY29tcGxleGl0aWVzLiAgVGhlIGd1aWRh bmNlIGl0IG9mZmVycyBmb3IgZnV0dXJlIGV4dGVuc2lvbnMgaXMgc291bmQuDQogICAgDQogICAg L0JvYg0KICAgIA0KICAgIFAuUy4gSSBsaWtlZCB0aGUgQVNDSUkgYXJ0Lg0KICAgIA0KICAgIA0K ICAgIF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQogICAg SW50LWRpciBtYWlsaW5nIGxpc3QNCiAgICBJbnQtZGlyQGlldGYub3JnDQogICAgaHR0cHM6Ly93 d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9pbnQtZGlyDQogICAgDQoNCg== From nobody Wed Feb 19 09:30:40 2020 Return-Path: X-Original-To: dnssd@ietf.org Delivered-To: dnssd@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C47912008D; Wed, 19 Feb 2020 09:30:38 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: IETF Meeting Session Request Tool To: Cc: lflynn@amsl.com, dnssd@ietf.org, dnssd-chairs@ietf.org, evyncke@cisco.com X-Test-IDTracker: no X-IETF-IDTracker: 6.118.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <158213343847.17742.5906792269751080675.idtracker@ietfa.amsl.com> Date: Wed, 19 Feb 2020 09:30:38 -0800 Archived-At: Subject: [dnssd] dnssd - Update to a Meeting Session Request for IETF 107 X-BeenThere: dnssd@ietf.org X-Mailman-Version: 2.1.29 List-Id: "Discussion of extensions to DNS-based service discovery for routed networks." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Feb 2020 17:30:38 -0000 An update to a meeting session request has just been submitted by Liz Flynn, on behalf of the dnssd working group. --------------------------------------------------------- Working Group Name: Extensions for Scalable DNS Service Discovery Area Name: Internet Area Session Requester: Liz Flynn Number of Sessions: 1 Length of Session(s): 2 Hours Number of Attendees: 75 Conflicts to Avoid: Chair Conflict: dnsop doh dprive homenet quic tls babel intarea httpbis 6man v6ops Technology Overlap: mls core anima pearg Key Participant Conflict: 6tisch rats roll lake People who must be present: Stephen Farrell Eric Vyncke Barbara Stark David Schinazi Resources Requested: Special Requests: dnssd and homenet would like to do a single joint 2 hour meeting. We'll figure out how to divide the time. --------------------------------------------------------- From nobody Fri Feb 21 06:18:37 2020 Return-Path: X-Original-To: dnssd@ietf.org Delivered-To: dnssd@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 38206120033; Fri, 21 Feb 2020 06:18:35 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: dnssd@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.118.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: dnssd@ietf.org Message-ID: <158229471514.29053.10772609447240040025@ietfa.amsl.com> Date: Fri, 21 Feb 2020 06:18:35 -0800 Archived-At: Subject: [dnssd] I-D Action: draft-ietf-dnssd-prireq-05.txt X-BeenThere: dnssd@ietf.org X-Mailman-Version: 2.1.29 List-Id: "Discussion of extensions to DNS-based service discovery for routed networks." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Feb 2020 14:18:35 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Extensions for Scalable DNS Service Discovery WG of the IETF. Title : DNS-SD Privacy and Security Requirements Authors : Christian Huitema Daniel Kaiser Filename : draft-ietf-dnssd-prireq-05.txt Pages : 19 Date : 2020-02-21 Abstract: DNS-SD (DNS Service Discovery) normally discloses information about devices offering and requesting services. This information includes host names, network parameters, and possibly a further description of the corresponding service instance. Especially when mobile devices engage in DNS Service Discovery at a public hotspot, serious privacy problems arise. We analyze the requirements of a privacy-respecting discovery service. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-dnssd-prireq/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-dnssd-prireq-05 https://datatracker.ietf.org/doc/html/draft-ietf-dnssd-prireq-05 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-dnssd-prireq-05 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Tue Feb 25 12:12:04 2020 Return-Path: X-Original-To: dnssd@ietfa.amsl.com Delivered-To: dnssd@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AED683A11AB for ; Tue, 25 Feb 2020 12:12:02 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.097 X-Spam-Level: X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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=gmail.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 I-TH5H9vP35i for ; Tue, 25 Feb 2020 12:12:01 -0800 (PST) Received: from mail-lf1-x12b.google.com (mail-lf1-x12b.google.com [IPv6:2a00:1450:4864:20::12b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E78C83A11A8 for ; Tue, 25 Feb 2020 12:12:00 -0800 (PST) Received: by mail-lf1-x12b.google.com with SMTP id y17so144637lfe.8 for ; Tue, 25 Feb 2020 12:12:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to:cc; bh=UAMYfN3xeaEf33fY4QMXDFcgUAOHNBa0wpYhd6kSArg=; b=kmkRwPVnkCXbr1mxUmyXbVqSLdC7T1BCpu+q9TuX6598Pw0EO+0X4RG2DCrEETREWq CaP6CsXY93S99g6J5OaRdAIEyKaHUoELN0neyakPZFN4F28UBMArw+VZUqOHj7KI6tzr QBWJ2/pg2ZqBTLYm+9OGfK+Le33Gm1dJquMyCDVmFbSuuOBi9PyProociuxy8bv/l7uM t/3Euxi8gjPSmc8COxKZp9y3nv2otXQXQNv5gIG+VDmPgJf2plGVG+S2xuj26xfmw9FU ZCVmE9ftdv+jbgXzYhlxBtOJjW8jGYSXOad7tXLWtZidsMe2MjGgIss+HgnFTeOZcejZ O1lw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=UAMYfN3xeaEf33fY4QMXDFcgUAOHNBa0wpYhd6kSArg=; b=kD1rX2Fc4McpVxs/1mjCfdDUBtpTQlcMAOFz77qc0wTYsGkBZTt09MTcD6Q11Scxd5 JDSFhv3BbkQFr/zFNmeohK/pcwLk+jqqBXcRzlu1aO2ZttbZI2PheJfudEMTwb5bSu3k K5CFTEh58+KZORIB7yGIq6AihKeNGcOgsKv+zmF0J4Q65rm3Lyqu9D4314gQDmn3o5Rm ryhMvgWtYCnILEQgRRc1iNuu5fBv8fQMZo3N+DoWQCUUqC/tRzMOuDrx8lHwJBX5gC2C 1GTcW8Xp0wzhiTaUTGhd9jtNs2akn5kBu+8Ad7HSOzLBKfCW4k+RKiJSHo+aprt42zrn bBbw== X-Gm-Message-State: APjAAAVkQdDX0JUgUpyjJp1a4nGr6qddCUp5VrKF8Hmvpky07TG78qNz qmCTBmgzolFyt9HI20K1Jiu13SRADhnowGh72JS2ggzd X-Google-Smtp-Source: APXvYqxrBKYvbtPepthYkZ/a4FBGzXvDYiZj2MopFBAFL3P6q9qrCD3gWV2OdmbKn466tA3cziiHQmMLQXBFofmJQ3A= X-Received: by 2002:a05:6512:3136:: with SMTP id p22mr297537lfd.120.1582661518301; Tue, 25 Feb 2020 12:11:58 -0800 (PST) MIME-Version: 1.0 From: David Schinazi Date: Tue, 25 Feb 2020 12:11:47 -0800 Message-ID: To: DNSSD Cc: Barbara Stark Content-Type: multipart/alternative; boundary="000000000000991d5f059f6c19af" Archived-At: Subject: [dnssd] DNSSD @ IETF 107 - Call for Agenda Items X-BeenThere: dnssd@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of extensions to DNS-based service discovery for routed networks." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Feb 2020 20:12:03 -0000 --000000000000991d5f059f6c19af Content-Type: text/plain; charset="UTF-8" Hi everyone, According to the IETF 107 Preliminary Agenda, https://datatracker.ietf.org/meeting/107/agenda DNSSD will have a 2-hour session shared with HOMENET on Thursday 2020-03-26 morning 10-12am PDT. Please send us your agenda requests ASAP. Note that the other sessions for this time slot are: - art cbor Concise Binary Object Representation Maintenance and Extensions - irtf gaia Global Access to the Internet for All - irtf icnrg Information-Centric Networking - rtg spring Source Packet Routing in Networking - sec privacypass privacy-passBOF - tsv tsvwg Transport Area Working Group Please let us know immediately if you have severe conflicts with any of those. Thanks, David --000000000000991d5f059f6c19af Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi everyone,

According to the IETF = 107 Preliminary Agenda,
https://datatracker.ietf.org/meeting/107/agenda
<= /div>
DNSSD will have a 2-hour session shared with HOMENET
on= Thursday 2020-03-26 morning 10-12am PDT.

Please s= end us your agenda requests ASAP.

Note that the ot= her sessions for this time slot are:
- art cbor Concise Binary Ob= ject Representation Maintenance and Extensions=C2=A0
- irtf gaia = Global Access to the Internet for All
- irtf icnrg Information-Centric= Networking
- rtg spring Source Packet Routing in Networking
- se= c privacypass privacy-passBOF
- tsv tsvwg Transport Area Working Group=
Please let us know immediately if you have severe conflicts = with any of those.

Thanks,
David
--000000000000991d5f059f6c19af-- From nobody Tue Feb 25 17:06:49 2020 Return-Path: X-Original-To: dnssd@ietf.org Delivered-To: dnssd@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0059D3A03FA; Tue, 25 Feb 2020 17:06:33 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: Barry Leiba via Datatracker To: "The IESG" Cc: draft-ietf-dnssd-prireq@ietf.org, dnssd-chairs@ietf.org, dnssd@ietf.org, David Schinazi , dschinazi.ietf@gmail.com X-Test-IDTracker: no X-IETF-IDTracker: 6.118.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: Barry Leiba Message-ID: <158267919299.11026.3193133978474704307.idtracker@ietfa.amsl.com> Date: Tue, 25 Feb 2020 17:06:32 -0800 Archived-At: Subject: [dnssd] Barry Leiba's Yes on draft-ietf-dnssd-prireq-05: (with COMMENT) X-BeenThere: dnssd@ietf.org X-Mailman-Version: 2.1.29 List-Id: "Discussion of extensions to DNS-based service discovery for routed networks." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Feb 2020 01:06:33 -0000 Barry Leiba has entered the following ballot position for draft-ietf-dnssd-prireq-05: Yes 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-dnssd-prireq/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- It’s useful to have this analysis; thanks. Just some editorial comments below. Please consider them; none needs any explicit response. Please take specific note of the last one, about the references. General: “i.e.” and “e.g.” always need a comma after them. — Section 1 — There are cases when nodes connected to a network want to provide or consume services without exposing their identity to the other parties Nit: “their identities” (or “a node… wants… its identity”) Consider for example a traveler Nit: “Consider, for example, a traveler” Disclosing Information In this document "disclosing information" is also focused on disclosure by data conveyed via messages on the service discovery protocol layer. Do you mean “disclosure of data” (not “by”)? — Section 2 — All these attackers can either be passive, i.e. they just listen to network traffic they have access to, or active, i.e. they additionally can craft and send (malicious) packets. Style: You decide, of course, but I find this easier to read with parentheses, rather than “i.e.”s: SUGGEST All these attackers can either be passive (they just listen to network traffic they have access to) or active (they additionally can craft and send malicious packets). END on-link An on-link attacker is on the same network link as victim devices engaging in service discovery; thus, the external attacker is in the same multicast domain. The second line should say “on-link attacker”. MITM A Man in the Middle (MITM) attacker either controls (parts of) a network link or can trick two parties to send traffic via him; Nit: “Man-in-the-Middle” needs hyphens when it modifies “attacker”. Style: I know that “him” matches “Man”, so maybe we should leave it as is. Still, it jarred me. I would say “via the attacker.” — Section 3.1.1 — I love the ASCII-art stick figures. :-) just for tracking people or as a preliminary to targeted attacks. “preliminary” isn’t a noun. Maybe “preliminary step”, or maybe “preamble”? Or you could remove “as a”, and it would work. Yes, I think the last is the best fix here. — Section 3.1.2 — such as for example an airport's lounge. Nit: “for example” needs to be set off with commas before and after it. — Section 3.1.3 — to further attacks, from theft to device specific hacking. Nit: hyphenate “device-specific”. "fingerprint" of the person, allowing identification. Style: I would say “facilitating identification”, or maybe “risking identification”. — Section 3.2 — This is mainly relevant for unicast based discovery Nit: hyphenate “unicast-based”. — Section 3.2.4 — o Some attributes like the paper size available in a printer, Fruit flies like a banana? The attributes are not paticularly fond of anything: “Some attributes, such as the paper size available in a printer,” Combinations of attributes have more information power than specific attributes Style: I would say, “than individual attributes” Information contained in TXT records does not only breach privacy Nit: make it “…records not only breaches privacy” Further, TXT records often contain version information about services allowing potential attackers You need a comma after “services” — otherwise, the meaning isn’t quite as you want it. — Section 3.2.5 — An argument is sometimes made that devices providing services can be identified by observing the local traffic, and that trying to hide the presence of the service is futile. However, Given what you say below this, I think it would help to emphasize the point here, so may I suggest this?: NEW An argument is sometimes made that devices providing services can be identified by observing the local traffic, and that trying to hide the presence of the service is futile. However, there are good reasons for the doscovery service layer to avoid unnecessary exposure: END — Section 3.2.6 — services, such as for example some private messaging services. “such as” already means “for example”, so you don’t need both. I would just remove “for example”. — Section 3.4.1 — can perform, the proxy may have some way to wake the device, as implied in RFC6762 [RFC6762] 6762 is 50 pages-ish; do you mind adding a section to the citation to help the reader find the implication? — Section 3.4.2 — Further it may cause an unnecessary level of power consumption which is particularly problematic Nit: this needs a comma after “further” and another after “consumption”. unauthorized observers, while also managing to do that efficiently. You’re missing an antecedent to “that”. I think you need to say, “to do its job efficiently,” or something like that. — Section 3.4.3 — establishment requires active participation of the user, such as entering a password or PIN. I submit that “clicking OK” is also active participation. Maybe “more significant participation” is better? — Section 4 — lead to a solution that does not transmit privacy violating DNS-SD Nit: hyphenate “privacy-violating”. mechanisms should be used on deeper layer network protocols and on how to actually connect to services in a privacy preserving way, Nit: hyphenate “deeper-layer” and “privacy-preserving”. — Section 4.2 — 4. Avoid disclosure of information about the services they offer to unauthorized clients. This sounds like it’s talking about services that they offer to unauthorized clients. I don’t actually think readers will misunderstand it, but they might trip over it. Maybe move “to unauthorized clients” after “disclosure”? That way, you can make the same change in bullet 3 and keep them parallel and clear. — Section 4.3 — Further, it would increase power consumption which is critical for IoT devices. Increased power consumption isn’t what’s critical; just the opposite. Maybe “which is damaging to IoT devices.” — Section 7 — Do with this comment what you will: I’m one who believes that Informational documents do have Normative References. Those are the references that are critical to the understanding of the document. Clearly, the DNSSD and mDNS documents are in that category, and I think there are others. You needn’t reply on this, and you needn’t do it if you disagree, but I think it would be best to identify the key documents that readers of this need to be familiar with, and move them into Normative References. From nobody Tue Feb 25 21:02:17 2020 Return-Path: X-Original-To: dnssd@ietfa.amsl.com Delivered-To: dnssd@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 144243A0D83 for ; Tue, 25 Feb 2020 21:02:05 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 Dy8ySBrW4thq for ; Tue, 25 Feb 2020 21:02:03 -0800 (PST) Received: from mx36-out10.antispamcloud.com (mx36-out10.antispamcloud.com [209.126.121.30]) (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 EFA323A0D33 for ; Tue, 25 Feb 2020 21:02:02 -0800 (PST) Received: from xse432.mail2web.com ([66.113.197.178] helo=xse.mail2web.com) by mx170.antispamcloud.com with esmtp (Exim 4.92) (envelope-from ) id 1j6oWs-000J1E-0x for dnssd@ietf.org; Wed, 26 Feb 2020 05:42:39 +0100 Received: from xsmtp21.mail2web.com (unknown [10.100.68.60]) by xse.mail2web.com (Postfix) with ESMTPS id 48S37b0Cr6z529Z for ; Tue, 25 Feb 2020 20:42:35 -0800 (PST) Received: from [10.5.2.31] (helo=xmail09.myhosting.com) by xsmtp21.mail2web.com with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from ) id 1j6oWo-0000E9-Se for dnssd@ietf.org; Tue, 25 Feb 2020 20:42:34 -0800 Received: (qmail 24489 invoked from network); 26 Feb 2020 04:42:34 -0000 Received: from unknown (HELO [192.168.1.103]) (Authenticated-user:_huitema@huitema.net@[172.58.46.215]) (envelope-sender ) by xmail09.myhosting.com (qmail-ldap-1.03) with ESMTPA for ; 26 Feb 2020 04:42:34 -0000 To: Barry Leiba , The IESG Cc: draft-ietf-dnssd-prireq@ietf.org, dnssd-chairs@ietf.org, dnssd@ietf.org, David Schinazi References: <158267919299.11026.3193133978474704307.idtracker@ietfa.amsl.com> From: Christian Huitema Autocrypt: addr=huitema@huitema.net; prefer-encrypt=mutual; keydata= mQENBFIRX8gBCAC26usy/Ya38IqaLBSu33vKD6hP5Yw390XsWLaAZTeQR64OJEkoOdXpvcOS HWfMIlD5s5+oHfLe8jjmErFAXYJ8yytPj1fD2OdSKAe1TccUBiOXT8wdVxSr5d0alExVv/LO I/vA2aU1TwOkVHKSapD7j8/HZBrqIWRrXUSj2f5n9tY2nJzG9KRzSG0giaJWBfUFiGb4lvsy IaCaIU0YpfkDDk6PtK5YYzuCeF0B+O7N9LhDu/foUUc4MNq4K3EKDPb2FL1Hrv0XHpkXeMRZ olpH8SUFUJbmi+zYRuUgcXgMZRmZFL1tu6z9h6gY4/KPyF9aYot6zG28Qk/BFQRtj7V1ABEB AAG0J0NocmlzdGlhbiBIdWl0ZW1hIDxodWl0ZW1hQGh1aXRlbWEubmV0PokBOQQTAQIAIwUC UhFfyAIbLwcLCQgHAwIBBhUIAgkKCwQWAgMBAh4BAheAAAoJEJNDCbJVyA1yhbYH/1ud6x6m VqGIp0JcZUfSQO8w+TjugqxCyGNn+w/6Qb5O/xENxNQ4HaMQ5uSRK9n8WKKDDRSzwZ4syKKf wbkfj05vgFxrjCynVbm1zs2X2aGXh+PxPL/WHUaxzEP7KjYbLtCUZDRzOOrm+0LMktngT/k3 6+EZoLEM52hwwpIAzJoscyEz7QfqMOZtFm6xQnlvDQeIrHx0KUvwo/vgDLK3SuruG1CSHcR0 D24kEEUa044AIUKBS3b0b8AR7f6mP2NcnLpdsibtpabi9BzqAidcY/EjTaoea46HXALk/eJd 6OLkLE6UQe1PPzQC4jB7rErX2BxnSkHDw50xMgLRcl5/b1a5AQ0EUhFfyAEIAKp7Cp8lqKTV CC9QiAf6QTIjW+lie5J44Ad++0k8gRgANZVWubQuCQ71gxDWLtxYfFkEXjG4TXV/MUtnOliG 5rc2E+ih6Dg61Y5PQakm9OwPIsOx+2R+iSW325ngln2UQrVPgloO83QiUoi7mBJPbcHlxkhZ bd3+EjFxSLIQogt29sTcg2oSh4oljUpz5niTt69IOfZx21kf29NfDE+Iw56gfrxI2ywZbu5o G+d0ZSp0lsovygpk4jK04fDTq0vxjEU5HjPcsXC4CSZdq5E2DrF4nOh1UHkHzeaXdYR2Bn1Y wTePfaHBFlvQzI+Li/Q6AD/uxbTM0vIcsUxrv3MNHCUAEQEAAYkCPgQYAQIACQUCUhFfyAIb LgEpCRCTQwmyVcgNcsBdIAQZAQIABgUCUhFfyAAKCRC22tOSFDh1UOlBB/94RsCJepNvmi/c YiNmMnm0mKb6vjv43OsHkqrrCqJSfo95KHyl5Up4JEp8tiJMyYT2mp4IsirZHxz/5lqkw9Az tcGAF3GlFsj++xTyD07DXlNeddwTKlqPRi/b8sppjtWur6Pm+wnAHp0mQ7GidhxHccFCl65w uT7S/ocb1MjrTgnAMiz+x87d48n1UJ7yIdI41Wpg2XFZiA9xPBiDuuoPwFj14/nK0elV5Dvq 4/HVgfurb4+fd74PV/CC/dmd7hg0ZRlgnB5rFUcFO7ywb7/TvICIIaLWcI42OJDSZjZ/MAzz BeXm263lHh+kFxkh2LxEHnQGHCHGpTYyi4Z3dv03HtkH/1SI8joQMQq00Bv+RdEbJXfEExrT u4gtdZAihwvy97OPA2nCdTAHm/phkzryMeOaOztI4PS8u2Ce5lUB6P/HcGtK/038KdX5MYST Fn8KUDt4o29bkv0CUXwDzS3oTzPNtGdryBkRMc9b+yn9+AdwFEH4auhiTQXPMnl0+G3nhKr7 jvzVFJCRif3OAhEm4vmBNDE3uuaXFQnbK56GJrnqVN+KX5Z3M7X3fA8UcVCGOEHXRP/aubiw Ngawj0V9x+43kUapFp+nF69R53UI65YtJ95ec4PTO/Edvap8h1UbdEOc4+TiYwY1TBuIKltY 1cnrjgAWUh/Ucvr++/KbD9tD6C8= Message-ID: <640b12c8-a4be-0c0a-6760-e7fa02364fb7@huitema.net> Date: Tue, 25 Feb 2020 20:42:39 -0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.5.0 MIME-Version: 1.0 In-Reply-To: <158267919299.11026.3193133978474704307.idtracker@ietfa.amsl.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Content-Language: en-US X-Originating-IP: 66.113.197.178 X-Spampanel-Domain: xsmtpout.mail2web.com X-Spampanel-Username: 66.113.197.0/24 Authentication-Results: antispamcloud.com; auth=pass smtp.auth=66.113.197.0/24@xsmtpout.mail2web.com X-Spampanel-Outgoing-Class: unsure X-Spampanel-Outgoing-Evidence: Combined (0.15) X-Recommended-Action: accept X-Filter-ID: Mvzo4OR0dZXEDF/gcnlw0eYBE/I2+wvb5IJ3WTuccampSDasLI4SayDByyq9LIhVUZbR67CQ7/vm /hHDJU4RXkTNWdUk1Ol2OGx3IfrIJKywOmJyM1qr8uRnWBrbSAGDoeDwbaJnZ2TaZhv/Bk6d8Jj9 EvBvwu01uVCaGVBWGqtdvLx5KYAWSN549sC5h70a2rBNMmEsKEibQwSU1xBeOHButNDpi1WUXRkr He1vFsZaZad0VL/QynhFAlbT36L8Bo/amW5kihSpmXVC8ht5WQZ6weYgSzquK2hxskqXvy8woCTx LKweTbuJ+19zsyHVGVmhMAaQ/AfCRwRe7yHm5oY+NYmsSGn+svMubxnbgm1cr18FZBEPC2/c16Xd 7sC9aC4xteE1WLqGS9YoqrsZ2DyteN0e+ECCv9/f+GPymkgDVo7QBKA4MctKq4ifYPcXFRL2K3LA EfDXVOdt7wDbusYnuEVWSxKMHbU0zkNM3EElFDaoLuOPKc8gc82pKfhB7T02ZXdoQxMs//iOE4Fl hiCv9TR+UxzLZWL8hwGBjhoI3W+YcuHfP5PkZb5A+wE5qGdpH54Oa3V8I76VOEvlwLCanpZsarZa LIRpEqA8mZECoO4gCQkfvynnCsTu+Y7qY55nZvlhWdT03ric3ufdO7reFVMZHeVGIiZUgGBcYb32 ie80q3LAG2MiIaIREzT1xNjuO97khcUFBr/guEWv1bdCp3Zd9clP8wSiJZWbJCj+xRrjVmRxpGtS cvUmgj1LuUBMDB4bqTTFWoXNjuPDO12jZAOanSBpz6Rja2u/0jJLGJAvVDcbFpoDcCeICPWuh+Xw USsu3r8c/nSA6bEnnvysta6u1iHEyuS7GD1uvcq2dHZOyIPu+ID36td2YpU6JOYIJd4MvQ0Nf4Ec bvHO1diDanHV9KirFAIIecsyj+YNTo81GR+jDXFsz/ZQnbbTizvwlZsrbltGiZoUh+c+5pFVgpT1 b21uZVckGp0ccOa2XhkGbmsUNPNkere1WheNsVXmhO8BzADiszcWR9bz/SDtF09JpSbuuCeiIDK0 C/0= X-Report-Abuse-To: spam@quarantine11.antispamcloud.com Archived-At: Subject: Re: [dnssd] Barry Leiba's Yes on draft-ietf-dnssd-prireq-05: (with COMMENT) X-BeenThere: dnssd@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of extensions to DNS-based service discovery for routed networks." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Feb 2020 05:02:12 -0000 Thanks for the review, Barry. We will address your comments in the next revision of the draft. I am not enthusiastic about "normative references in informational documents". I will wait for Eric's advice on that one, assuming that he will carry the IESG consensus on that topic. -- Christian Huitema On 2/25/2020 5:06 PM, Barry Leiba via Datatracker wrote: > Barry Leiba has entered the following ballot position for > draft-ietf-dnssd-prireq-05: Yes > > 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-dnssd-prireq/ > > > > ---------------------------------------------------------------------- > COMMENT: > ---------------------------------------------------------------------- > > It’s useful to have this analysis; thanks. Just some editorial comments below. > Please consider them; none needs any explicit response. Please take specific > note of the last one, about the references. > > General: “i.e.” and “e.g.” always need a comma after them. > > — Section 1 — > > There are cases when nodes connected to a network want to provide or > consume services without exposing their identity to the other parties > > Nit: “their identities” (or “a node… wants… its identity”) > > Consider for example a traveler > > Nit: “Consider, for example, a traveler” > > Disclosing Information In this document "disclosing information" is > also focused on disclosure by data conveyed via messages on the > service discovery protocol layer. > > Do you mean “disclosure of data” (not “by”)? > > — Section 2 — > > All these attackers can either be passive, i.e. > they just listen to network traffic they have access to, or active, > i.e. they additionally can craft and send (malicious) packets. > > Style: You decide, of course, but I find this easier to read with parentheses, > rather than “i.e.”s: > > SUGGEST > All these attackers can either be passive (they > just listen to network traffic they have access to) or active > (they additionally can craft and send malicious packets). > END > > on-link An on-link attacker is on the same network link as victim > devices engaging in service discovery; thus, the external attacker > is in the same multicast domain. > > The second line should say “on-link attacker”. > > MITM A Man in the Middle (MITM) attacker either controls (parts of) > a network link or can trick two parties to send traffic via him; > > Nit: “Man-in-the-Middle” needs hyphens when it modifies “attacker”. > Style: I know that “him” matches “Man”, so maybe we should leave it as is. > Still, it jarred me. I would say “via the attacker.” > > — Section 3.1.1 — > I love the ASCII-art stick figures. :-) > > just for tracking people or as a preliminary to targeted attacks. > > “preliminary” isn’t a noun. Maybe “preliminary step”, or maybe “preamble”? Or > you could remove “as a”, and it would work. Yes, I think the last is the best > fix here. > > — Section 3.1.2 — > > such as > for example an airport's lounge. > > Nit: “for example” needs to be set off with commas before and after it. > > — Section 3.1.3 — > > to further attacks, from theft to device specific hacking. > > Nit: hyphenate “device-specific”. > > "fingerprint" of the person, allowing identification. > > Style: I would say “facilitating identification”, or maybe “risking > identification”. > > — Section 3.2 — > > This is mainly relevant for unicast based discovery > > Nit: hyphenate “unicast-based”. > > — Section 3.2.4 — > > o Some attributes like the paper size available in a printer, > > Fruit flies like a banana? The attributes are not paticularly fond of > anything: “Some attributes, such as the paper size available in a printer,” > > Combinations of attributes have more information power than specific > attributes > > Style: I would say, “than individual attributes” > > Information contained in TXT records does not only breach privacy > > Nit: make it “…records not only breaches privacy” > > Further, TXT records often contain version information about services > allowing potential attackers > > You need a comma after “services” — otherwise, the meaning isn’t quite as you > want it. > > — Section 3.2.5 — > > An argument is sometimes made that devices providing services can be > identified by observing the local traffic, and that trying to hide > the presence of the service is futile. However, > > Given what you say below this, I think it would help to emphasize the point > here, so may I suggest this?: > > NEW > An argument is sometimes made that devices providing services can be > identified by observing the local traffic, and that trying to hide > the presence of the service is futile. However, there are good > reasons for the doscovery service layer to avoid unnecessary exposure: > END > > — Section 3.2.6 — > > services, such as for example some private messaging services. > > “such as” already means “for example”, so you don’t need both. I would just > remove “for example”. > > — Section 3.4.1 — > > can perform, the proxy may have some way to wake the device, as > implied in RFC6762 [RFC6762] > > 6762 is 50 pages-ish; do you mind adding a section to the citation to help the > reader find the implication? > > — Section 3.4.2 — > > Further it may cause an unnecessary level > of power consumption which is particularly problematic > > Nit: this needs a comma after “further” and another after “consumption”. > > unauthorized observers, while also managing to do that efficiently. > > You’re missing an antecedent to “that”. I think you need to say, “to do its > job efficiently,” or something like that. > > — Section 3.4.3 — > > establishment requires active participation of the user, such as > entering a password or PIN. > > I submit that “clicking OK” is also active participation. Maybe “more > significant participation” is better? > > — Section 4 — > > lead to a solution that does not transmit privacy violating DNS-SD > > Nit: hyphenate “privacy-violating”. > > mechanisms should be used on deeper layer network protocols and on > how to actually connect to services in a privacy preserving way, > > Nit: hyphenate “deeper-layer” and “privacy-preserving”. > > — Section 4.2 — > > 4. Avoid disclosure of information about the services they offer to > unauthorized clients. > > This sounds like it’s talking about services that they offer to unauthorized > clients. I don’t actually think readers will misunderstand it, but they might > trip over it. Maybe move “to unauthorized clients” after “disclosure”? That > way, you can make the same change in bullet 3 and keep them parallel and clear. > > — Section 4.3 — > > Further, it would > increase power consumption which is critical for IoT devices. > > Increased power consumption isn’t what’s critical; just the opposite. Maybe > “which is damaging to IoT devices.” > > — Section 7 — > Do with this comment what you will: I’m one who believes that Informational > documents do have Normative References. Those are the references that are > critical to the understanding of the document. Clearly, the DNSSD and mDNS > documents are in that category, and I think there are others. You needn’t > reply on this, and you needn’t do it if you disagree, but I think it would be > best to identify the key documents that readers of this need to be familiar > with, and move them into Normative References. > > > From nobody Wed Feb 26 08:49:08 2020 Return-Path: X-Original-To: dnssd@ietfa.amsl.com Delivered-To: dnssd@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B3743A0BC1; Wed, 26 Feb 2020 08:49:00 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.399 X-Spam-Level: X-Spam-Status: No, score=-1.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 KRIGIkbfZmta; Wed, 26 Feb 2020 08:48:59 -0800 (PST) Received: from mail-io1-f50.google.com (mail-io1-f50.google.com [209.85.166.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 711F33A0BB7; Wed, 26 Feb 2020 08:48:59 -0800 (PST) Received: by mail-io1-f50.google.com with SMTP id z16so4028678iod.11; Wed, 26 Feb 2020 08:48:59 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=GOLuCR2MOYEmTK09QvtLGQbIgjEcGl4mW7HHMBJ7svM=; b=IAumAL89uTe0OexL3hGUmh2eTPLx9K/1fZCe2Zc/s9waO0nHnph5vrBd72qVjGO/xL uI9tfZL2A9k0qwcIihYvK0C4qwW4nVprkfMDgPYFrF/fQkhmNC7SXczqtrd9427CC6/2 jsTJ0d4PmfD2vazDzu0WbwPSDoyQcEkYJ0qYeUNqKg1VBBWYE6WmMU/ZSHOH7RX/LFDR R4ACpfUDymFi27bhWGg8Gr4DupMhjEEBLYaYRBgQ+YuSFvtL3OVtH0vmen3fdRU+U0mC pIsrfM0yy7iQsndQk9mSV6vIFIZW15cKjy8GXie/l6aLibNmw5gIDcNt6RNxeGI7YEGR 6bjQ== X-Gm-Message-State: APjAAAUdbGGqii2NyyKQ9G4JKhQpYleOWHE1B6/A5C6gpwSEga7ftMl5 A+vXzeDjJtdo4Lx5RuUs5DwdlY2q9VgC2rqairCOS8qo X-Google-Smtp-Source: APXvYqynJ/5fM8X/OeDJ3gfRlXD2FLm52xCF2vV/HD+0jUyXrjy/0O5q+XWw4JT1tMHksYRtV1kg+WCwiYQtHMVpUSQ= X-Received: by 2002:a5d:9ed4:: with SMTP id a20mr5418815ioe.187.1582735738676; Wed, 26 Feb 2020 08:48:58 -0800 (PST) MIME-Version: 1.0 References: <158267919299.11026.3193133978474704307.idtracker@ietfa.amsl.com> <640b12c8-a4be-0c0a-6760-e7fa02364fb7@huitema.net> In-Reply-To: <640b12c8-a4be-0c0a-6760-e7fa02364fb7@huitema.net> From: Barry Leiba Date: Wed, 26 Feb 2020 08:48:46 -0800 Message-ID: To: Christian Huitema Cc: The IESG , draft-ietf-dnssd-prireq@ietf.org, dnssd-chairs@ietf.org, dnssd@ietf.org, David Schinazi Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Archived-At: Subject: Re: [dnssd] Barry Leiba's Yes on draft-ietf-dnssd-prireq-05: (with COMMENT) X-BeenThere: dnssd@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of extensions to DNS-based service discovery for routed networks." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Feb 2020 16:49:01 -0000 Thanks, Christian, and I appreciate your quick response. > I am not enthusiastic about "normative references in informational > documents". I will wait for Eric's advice on that one, assuming that he > will carry the IESG consensus on that topic. =C3=89ric and I will discuss it. Meanwhile, I'll note that the IESG said this in 2006: https://www.ietf.org/about/groups/iesg/statements/normative-i= nformative-references/ "Normative references specify documents that must be read to understand or implement the technology in the new RFC, or whose technology must be present for the technology in the new RFC to work." and "Note 3: The normative/informative distinction is relevant in any document that amounts to a technical specification, even if its intended status is Experimental or Informational." Barry From nobody Thu Feb 27 04:55:36 2020 Return-Path: X-Original-To: dnssd@ietf.org Delivered-To: dnssd@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 53E353A0528; Thu, 27 Feb 2020 04:55:26 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit From: =?utf-8?q?Mirja_K=C3=BChlewind_via_Datatracker?= To: "The IESG" Cc: draft-ietf-dnssd-prireq@ietf.org, dnssd-chairs@ietf.org, dnssd@ietf.org, David Schinazi , dschinazi.ietf@gmail.com X-Test-IDTracker: no X-IETF-IDTracker: 6.118.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: =?utf-8?q?Mirja_K=C3=BChlewind?= Message-ID: <158280812633.2047.3057396160621969333.idtracker@ietfa.amsl.com> Date: Thu, 27 Feb 2020 04:55:26 -0800 Archived-At: Subject: [dnssd] =?utf-8?q?Mirja_K=C3=BChlewind=27s_No_Objection_on_draft?= =?utf-8?q?-ietf-dnssd-prireq-05=3A_=28with_COMMENT=29?= X-BeenThere: dnssd@ietf.org X-Mailman-Version: 2.1.29 List-Id: "Discussion of extensions to DNS-based service discovery for routed networks." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Feb 2020 12:55:27 -0000 Mirja Kühlewind has entered the following ballot position for draft-ietf-dnssd-prireq-05: No Objection 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-dnssd-prireq/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- nit sec 2: "on-link An on-link attacker is [...]; thus, the external attacker is in the same multicast domain." s/external attacker/on-link attacker/ I agree with Barry that at least RFC6763 and RFC7558 should be normative references. From nobody Thu Feb 27 09:05:06 2020 Return-Path: X-Original-To: dnssd@ietfa.amsl.com Delivered-To: dnssd@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 927DA3A0C9D; Thu, 27 Feb 2020 09:05:04 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -9.6 X-Spam-Level: X-Spam-Status: No, score=-9.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=MrtJzbmJ; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=OloMv8tM 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 NBH4jts-VxpJ; Thu, 27 Feb 2020 09:05:02 -0800 (PST) Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 47E823A0CD6; Thu, 27 Feb 2020 09:05:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2218; q=dns/txt; s=iport; t=1582823102; x=1584032702; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=BFMf00Se3NWpSi3n2obZ7KNgTZ7FXKicGTSWOn+LPns=; b=MrtJzbmJVHFgIl0lIuTXh1sTqcXTc7R8lJJS8bTc+OVNgTMxJYXFZkcs Z+I1ntYuKMLjiMp0eqkoJa/lNV3vnBXD2CUA0NsF5EsmiR9GaBRCFq9g8 4/W2Gfv6rtuzQ7H4uqCqnYl7IsksepU9ePwnoezusatm/s0T7budBkbcR A=; IronPort-PHdr: =?us-ascii?q?9a23=3ANYt0BBPQKQ35QTmugbcl6mtXPHoupqn0MwgJ65?= =?us-ascii?q?Eul7NJdOG58o//OFDEu60/l0fHCIPc7f8My/HbtaztQyQh2d6AqzhDFf4ETB?= =?us-ascii?q?oZkYMTlg0kDtSCDBj2Mu/sZC83NM9DT1RiuXq8NBsdFQ=3D=3D?= X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DyAQBR9lde/5pdJa1mGwEBAQEBAQE?= =?us-ascii?q?FAQEBEQEBAwMBAQGBe4FUKScFbFggBAsqhBSDRgOKZ4I6JYljjjGCUgNUCQE?= =?us-ascii?q?BAQwBASUIAgQBAYRAAheBcSQ4EwIDDQEBBQEBAQIBBQRthTcMhWMBAQEBAgE?= =?us-ascii?q?SEREMAQE3AQsEAgEIEQMBAgMCJgICAh8RFQgIAgQBDQUigwQBgkoDDiABDqR?= =?us-ascii?q?0AoE5iGJ1gTKCfwEBBYUODQuCDAMGgQ4qjCUagUE/gREnDBSCTD6CG0kBAYF?= =?us-ascii?q?lgxEygiyQKjuecUQKgjySL4Q2HIJJiBuETot8jnCBTYldkB0CBAIEBQIOAQE?= =?us-ascii?q?FgWkigVhwFWUBgg0BAQExUBgNjh0MF4EEAQiCQ4UUhUF0gSmOCgEB?= X-IronPort-AV: E=Sophos;i="5.70,492,1574121600"; d="scan'208";a="449979747" Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 27 Feb 2020 17:04:57 +0000 Received: from XCH-RCD-005.cisco.com (xch-rcd-005.cisco.com [173.37.102.15]) by rcdn-core-3.cisco.com (8.15.2/8.15.2) with ESMTPS id 01RH4v3U017335 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 27 Feb 2020 17:04:57 GMT Received: from xhs-aln-002.cisco.com (173.37.135.119) by XCH-RCD-005.cisco.com (173.37.102.15) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 27 Feb 2020 11:04:56 -0600 Received: from xhs-aln-003.cisco.com (173.37.135.120) by xhs-aln-002.cisco.com (173.37.135.119) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 27 Feb 2020 11:04:56 -0600 Received: from NAM12-BN8-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-003.cisco.com (173.37.135.120) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Thu, 27 Feb 2020 11:04:56 -0600 ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=UeQZSCs+oZ45ReZUMfAv3anCstiJiBig4d5yP+uhK/K04+5V72SNVQ+Ra+iqveVUWnWQLI+IO+Wqtj0Gssr90WnKD4kWc/Hsjy1vI4oa9fVF3umRqY47lFKHYpEx9jq/CJ+eubTdgi8ldPY7CXBfjZS2QaCH9X2hXN62AcRgBDkMNemhnjJqjzey5YtfVag7g9OmK/hEis6WuBTadRdS9xFktzUJ+8X30phHbLzn4mbIlXMc0VCOECj5TKKooj6JvR3dRkx6CWRUSqdKOdPl6+yLRJnLEbpuoQGuPuuKfPevGYaFLP8vCuG5daKEtOF6Ar3hfPPQXRk/laXlKHjMCQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=BFMf00Se3NWpSi3n2obZ7KNgTZ7FXKicGTSWOn+LPns=; b=dCtMD5uciktahCcYwPUrWAwSvw+O2pXxcc+pcq5sMW7mYzWJHKEMVFATthtWR3MU9DJGXz9wMfnUku6t1j48KSlo8JH4tqQ+iAiewOX6zagTiOVeee00wjCXxOjX5fBcmR9xwn0Yd+3UhkB3xjg3XCfCRkVYs4gg8tyFXfRnn7HDBJaQmDCK0gSqW7bDT2tLoovcRNwe1OFSoCVOizlP1+APXyVgQBZzxil7borKL50LnoLdls5rSEI5uFLfLKOXCb6C4RXxQDvJb/BCc00qQHAJ2RIXjLBF3EaEpoGuiYZYxoWWSyvb/fgamM9UFzlUR7XJfHLO0muPVm2uUBmTEg== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=BFMf00Se3NWpSi3n2obZ7KNgTZ7FXKicGTSWOn+LPns=; b=OloMv8tM2AI9Cchvnu7NGODhj8KnWoJKs6hR7rjqQLYR6sVOVMjA5RJBFQBP4nEV151HsvQrIKYkTgD8qkv+eKYXYu1ilGKHX+vgrYgGpab8HF6dnatYd2eJ1RVTij4HhuwImloPOp0mdQDWrct4MhaOjU68dZvqyXdTrW6iFVc= Received: from DM5PR11MB1753.namprd11.prod.outlook.com (2603:10b6:3:10d::13) by DM5PR11MB1449.namprd11.prod.outlook.com (2603:10b6:4:8::20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2772.15; Thu, 27 Feb 2020 17:04:55 +0000 Received: from DM5PR11MB1753.namprd11.prod.outlook.com ([fe80::680d:e22e:72d5:67ca]) by DM5PR11MB1753.namprd11.prod.outlook.com ([fe80::680d:e22e:72d5:67ca%3]) with mapi id 15.20.2772.012; Thu, 27 Feb 2020 17:04:55 +0000 From: "Eric Vyncke (evyncke)" To: Barry Leiba , Christian Huitema CC: David Schinazi , "dnssd@ietf.org" , "dnssd-chairs@ietf.org" , The IESG , "draft-ietf-dnssd-prireq@ietf.org" Thread-Topic: [dnssd] Barry Leiba's Yes on draft-ietf-dnssd-prireq-05: (with COMMENT) Thread-Index: AQHV7EEKFaVl9iPQbU6zmL9hygbGrqgs5daAgADK4ACAAaebAA== Date: Thu, 27 Feb 2020 17:04:55 +0000 Message-ID: References: <158267919299.11026.3193133978474704307.idtracker@ietfa.amsl.com> <640b12c8-a4be-0c0a-6760-e7fa02364fb7@huitema.net> In-Reply-To: Accept-Language: fr-BE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/10.22.0.200209 authentication-results: spf=none (sender IP is ) smtp.mailfrom=evyncke@cisco.com; x-originating-ip: [2001:420:c0c1:36:40c5:de2c:de59:d774] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: c3770acb-adc7-49ae-a694-08d7bba72b37 x-ms-traffictypediagnostic: DM5PR11MB1449: x-microsoft-antispam-prvs: x-ms-oob-tlc-oobclassifiers: OLM:10000; x-forefront-prvs: 03264AEA72 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(39860400002)(366004)(396003)(136003)(346002)(376002)(189003)(199004)(186003)(6486002)(2906002)(81166006)(8676002)(6512007)(8936002)(33656002)(86362001)(110136005)(54906003)(316002)(81156014)(91956017)(76116006)(66946007)(64756008)(66556008)(66446008)(66476007)(6506007)(53546011)(5660300002)(4326008)(36756003)(71200400001)(2616005)(478600001)(966005); DIR:OUT; SFP:1101; SCL:1; SRVR:DM5PR11MB1449; H:DM5PR11MB1753.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam: BCL:0; x-microsoft-antispam-message-info: 5tz8R4q7pllr0HrBRACPpgupbx/Wcc7sVjUxkuxV+QCnDqMFxYU9lKRFutANmncNLFTIol+WqqKc4Gsn4QJTTPlAvDq6BkADLBmS1S/Jpxl90S3maxG+C7hfJy94i+4K3jrX9klqL9n5sS5XHX5m3v7n83C/RLI4NFpgFP3QHVcyr5Wza1dP3jGV8caRzgRR1L/I0pWe5I2WhhVwRRgj1u1KGlLn5xVkFckiWEIPX1moC2x3st4Czt4D2yHJJKYNY/2mIkzkF9e+siY9A+9HynDxro8GnzsM5iGs3t00+f0ywjNuzwWdCjSgwGyynEDSlg/NHVwdr5iTLZ4yb3Tayq+pTPzIVsXpMFNyrAyrWWlqoo/kAEHMcMSi5FSeizXztVQGi0UZrMtUmips3Y2cg22H7p8PAmlyYW0hEOI/XzXgmXjxTqvo0cM5dEeXhX4gOX5+Ugm3j/bvFBYwM6chQgaVsJeFQ0FcchlUtm2Gr4n4WVqGiLlPMtX7mXxVMggcGx0lq1f/+O4J33CM+7uZfw== x-ms-exchange-antispam-messagedata: 4Jp5NfSzeAZEB5oqh4KYhoGs4rKMoS0zuDedpuUVh3k+kJWKxUV+CwuzDbktmNd5t36Sf4/sHrYRTzzO0RdMXuP8kee1zQMNa1fKne0lPGMoQO8A8SV0UUND24kMJEKxQvYKkuFlPvRK/n1D2ShxHXni2ZA7XpQqIHi/F+uZleR59q8sD0ElkVD2q7+DnuvW2/r1byXVcz85Fa0wE+7lyw== x-ms-exchange-transport-forked: True Content-Type: text/plain; charset="utf-8" Content-ID: Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-MS-Exchange-CrossTenant-Network-Message-Id: c3770acb-adc7-49ae-a694-08d7bba72b37 X-MS-Exchange-CrossTenant-originalarrivaltime: 27 Feb 2020 17:04:55.4154 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: GSwYWnr2KTS+sFNDQRzyWMoZfxQWD7CdeqLEuoui6tlJlhEwl6HypDrRC8B6dl/2zHsqRBJBvnXab+Y7phhf/g== X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR11MB1449 X-OriginatorOrg: cisco.com X-Outbound-SMTP-Client: 173.37.102.15, xch-rcd-005.cisco.com X-Outbound-Node: rcdn-core-3.cisco.com Archived-At: Subject: Re: [dnssd] Barry Leiba's Yes on draft-ietf-dnssd-prireq-05: (with COMMENT) X-BeenThere: dnssd@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Discussion of extensions to DNS-based service discovery for routed networks." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Feb 2020 17:05:05 -0000 Q2hyaXN0aWFuLCBEYW5pZWwsDQoNCkJhc2VkIG9uIHRoZSBJRVNHIHN0YXRlbWVudCBiZWxvdywg cGxlYXNlIHVwZGF0ZSB0aGUgZG9jdW1lbnQgKGFmdGVyIHRoZSB0ZWxlY2hhdCkgdG8gaW5jbHVk ZSB0aG9zZSByZWZlcmVuY2VzIGFzIG5vcm1hdGl2ZS4NCg0KVGhhbmsgeW91DQoNCi3DqXJpYw0K DQrvu78tLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogaWVzZyA8aWVzZy1ib3VuY2Vz QGlldGYub3JnPiBvbiBiZWhhbGYgb2YgQmFycnkgTGVpYmEgPGJhcnJ5bGVpYmFAY29tcHV0ZXIu b3JnPg0KRGF0ZTogV2VkbmVzZGF5LCAyNiBGZWJydWFyeSAyMDIwIGF0IDE3OjQ5DQpUbzogQ2hy aXN0aWFuIEh1aXRlbWEgPGh1aXRlbWFAaHVpdGVtYS5uZXQ+DQpDYzogRGF2aWQgU2NoaW5hemkg PGRzY2hpbmF6aS5pZXRmQGdtYWlsLmNvbT4sICJkbnNzZEBpZXRmLm9yZyIgPGRuc3NkQGlldGYu b3JnPiwgImRuc3NkLWNoYWlyc0BpZXRmLm9yZyIgPGRuc3NkLWNoYWlyc0BpZXRmLm9yZz4sIFRo ZSBJRVNHIDxpZXNnQGlldGYub3JnPiwgImRyYWZ0LWlldGYtZG5zc2QtcHJpcmVxQGlldGYub3Jn IiA8ZHJhZnQtaWV0Zi1kbnNzZC1wcmlyZXFAaWV0Zi5vcmc+DQpTdWJqZWN0OiBSZTogW2Ruc3Nk XSBCYXJyeSBMZWliYSdzIFllcyBvbiBkcmFmdC1pZXRmLWRuc3NkLXByaXJlcS0wNTogKHdpdGgg Q09NTUVOVCkNCg0KICAgIFRoYW5rcywgQ2hyaXN0aWFuLCBhbmQgSSBhcHByZWNpYXRlIHlvdXIg cXVpY2sgcmVzcG9uc2UuDQogICAgDQogICAgPiBJIGFtIG5vdCBlbnRodXNpYXN0aWMgYWJvdXQg Im5vcm1hdGl2ZSByZWZlcmVuY2VzIGluIGluZm9ybWF0aW9uYWwNCiAgICA+IGRvY3VtZW50cyIu IEkgd2lsbCB3YWl0IGZvciBFcmljJ3MgYWR2aWNlIG9uIHRoYXQgb25lLCBhc3N1bWluZyB0aGF0 IGhlDQogICAgPiB3aWxsIGNhcnJ5IHRoZSBJRVNHIGNvbnNlbnN1cyBvbiB0aGF0IHRvcGljLg0K ICAgIA0KICAgIMOJcmljIGFuZCBJIHdpbGwgZGlzY3VzcyBpdC4gIE1lYW53aGlsZSwgSSdsbCBu b3RlIHRoYXQgdGhlIElFU0cgc2FpZA0KICAgIHRoaXMgaW4gMjAwNjogaHR0cHM6Ly93d3cuaWV0 Zi5vcmcvYWJvdXQvZ3JvdXBzL2llc2cvc3RhdGVtZW50cy9ub3JtYXRpdmUtaW5mb3JtYXRpdmUt cmVmZXJlbmNlcy8NCiAgICANCiAgICAiTm9ybWF0aXZlIHJlZmVyZW5jZXMgc3BlY2lmeSBkb2N1 bWVudHMgdGhhdCBtdXN0IGJlIHJlYWQgdG8NCiAgICB1bmRlcnN0YW5kIG9yIGltcGxlbWVudCB0 aGUgdGVjaG5vbG9neSBpbiB0aGUgbmV3IFJGQywgb3Igd2hvc2UNCiAgICB0ZWNobm9sb2d5IG11 c3QgYmUgcHJlc2VudCBmb3IgdGhlIHRlY2hub2xvZ3kgaW4gdGhlIG5ldyBSRkMgdG8gd29yay4i DQogICAgDQogICAgYW5kDQogICAgDQogICAgIk5vdGUgMzogVGhlIG5vcm1hdGl2ZS9pbmZvcm1h dGl2ZSBkaXN0aW5jdGlvbiBpcyByZWxldmFudCBpbiBhbnkNCiAgICBkb2N1bWVudCB0aGF0IGFt b3VudHMgdG8gYSB0ZWNobmljYWwgc3BlY2lmaWNhdGlvbiwgZXZlbiBpZiBpdHMNCiAgICBpbnRl bmRlZCBzdGF0dXMgaXMgRXhwZXJpbWVudGFsIG9yIEluZm9ybWF0aW9uYWwuIg0KICAgIA0KICAg IEJhcnJ5DQogICAgDQogICAgDQoNCg== From nobody Fri Feb 28 14:39:31 2020 Return-Path: X-Original-To: dnssd@ietf.org Delivered-To: dnssd@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 33EBF3A1F30; Fri, 28 Feb 2020 14:35:26 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "\"IETF Secretariat\"" To: , Cc: evyncke@cisco.com, dnssd@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.119.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <158292932619.19931.18070956926986553296@ietfa.amsl.com> Date: Fri, 28 Feb 2020 14:35:26 -0800 Archived-At: Subject: [dnssd] dnssd - Requested session has been scheduled for IETF 107 X-BeenThere: dnssd@ietf.org X-Mailman-Version: 2.1.29 List-Id: "Discussion of extensions to DNS-based service discovery for routed networks." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Feb 2020 22:35:33 -0000 Dear Barbara Stark, The session(s) that you have requested have been scheduled. Below is the scheduled session information followed by the original request. dnssd Session 1 (2:00 requested) Thursday, 26 March 2020, Morning Session I 1000-1200 Room Name: Georgia B size: 150 --------------------------------------------- Special Note: Joint with HOMENET iCalendar: https://datatracker.ietf.org/meeting/107/sessions/dnssd.ics Request Information: --------------------------------------------------------- Working Group Name: Extensions for Scalable DNS Service Discovery Area Name: Internet Area Session Requester: Barbara Stark Number of Sessions: 1 Length of Session(s): 2 Hours Number of Attendees: 75 Conflicts to Avoid: Chair Conflict: dnsop doh dprive homenet quic tls babel intarea httpbis 6man v6ops Technology Overlap: mls core anima pearg Key Participant Conflict: 6tisch rats roll lake People who must be present: Stephen Farrell Eric Vyncke Barbara Stark David Schinazi Resources Requested: Special Requests: dnssd and homenet would like to do a single joint 2 hour meeting. We'll figure out how to divide the time. ---------------------------------------------------------