Re: [MMUSIC] draft-ietf-rtcweb-mdns-ice-candidates
Justin Uberti <juberti@google.com> Tue, 15 December 2020 18:03 UTC
Return-Path: <juberti@google.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0A573A129E for <mmusic@ietfa.amsl.com>; Tue, 15 Dec 2020 10:03:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.498
X-Spam-Level:
X-Spam-Status: No, score=-17.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 Kx5rkkboYuG7 for <mmusic@ietfa.amsl.com>; Tue, 15 Dec 2020 10:03:33 -0800 (PST)
Received: from mail-io1-xd30.google.com (mail-io1-xd30.google.com [IPv6:2607:f8b0:4864:20::d30]) (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 BB4F23A129D for <mmusic@ietf.org>; Tue, 15 Dec 2020 10:03:33 -0800 (PST)
Received: by mail-io1-xd30.google.com with SMTP id y5so21372808iow.5 for <mmusic@ietf.org>; Tue, 15 Dec 2020 10:03:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=cA9fyqbkG4AbRRyzLXnuhk1kdBv4ZPI4R/Kv/ohRhow=; b=uqb08T+Wa+mrkqrS9oAYlUN5IVcX/IY+g6qiGtaHqIyq0TDbTurHJgGqBGq9E0Z8zq nMNba6xYibKs3yW+dEexRoPzOSu6OjXJkYHAdPtaPncjPJ6TUYKeV7AlO49xV90V1Baq DlXcGZhiIIQ5n6CVkj7TUWPN7MbVIHTnGKgwy0YcB9Xu8CkHOU42fXKtz6RhXTFHJVje vlXIBfzcFmMzkS7B83KC9TDfNPKZyV/UibKZZCTaD9vl1lNnHnfrFiu9CdCOIbB6yPH6 f2hh3c8KuczjF19Kgg9nxjgnEViMb77vVqmR/L6Px9ZM1bCD4g+SCsf25Lvp8LGwDT82 wVDw==
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=cA9fyqbkG4AbRRyzLXnuhk1kdBv4ZPI4R/Kv/ohRhow=; b=V4B+/YIXk4Gcp5efVBhIoFvHrcL+z9NYlF74aOqXSpKA4+ChNmANPJU9CjWZ2LFj27 yIgWoK82OEvlo+VntbxKFOgHASqyt5OgNC0xk76IHxHUyRO+C64RMgSaDJ7dwdxNtHgx BqZRM7EmEQLE9tL7agy3d96FlSprEKOsgev6N0rSKKleRVsf7G1iQju0NaYmOAeGIo31 F44zKAJd+3zHgK2lZt0amb/zxUKx9iR02nVmln8J/hdbL2hnHxt2eufTV59r/AQKG3cY NTkxFsZUvZgaGddrTG5f2pey6PEcsqOvGmQBFsG/U85jfCSCWNuX/P+dnGAbCD6XF1eo zqCA==
X-Gm-Message-State: AOAM530da57apguWsDhOdEHz67Ti1Di0l6RzLJlzuX1n6gVpNVvrajt2 rpoQBJWWJspXemtkN2BQ3Me0UNufT8e0FGaUv3I5dg==
X-Google-Smtp-Source: ABdhPJzsCZH59iYpVSJzq7u1s0pNtHz5WnE7IIzQ7/1M+39BHpROiOsO3eOo5tYGP6B5XHSCMxg1qiiBog47zMwHZOY=
X-Received: by 2002:a6b:dd0a:: with SMTP id f10mr4081925ioc.6.1608055412594; Tue, 15 Dec 2020 10:03:32 -0800 (PST)
MIME-Version: 1.0
References: <CAOJ7v-1VEsXobYaq0UdOkaGLGbnNH40srDX+tg+OYZivGRVhNw@mail.gmail.com> <c13a7ebd-73d3-4429-3f0c-77071dda62c6@cisco.com> <1509C133-A893-4F44-9859-541B1F31F95B@apple.com> <CA+m752+V5r+-CB=4-ckhTWRUdHy+2Ap1UxRk-2mafDOhFhtGnA@mail.gmail.com> <8f1951af-d0a3-1f05-c3a8-a2a907a8320c@cisco.com> <CAOJ7v-1Aj2jSxPqFzVqvDZz1CP9=KpVGUxpAg16i+63iT5gsNg@mail.gmail.com> <CAOJ7v-3OQDEy_OYnDeU0KWw88m6W0pR_or9CYPiEJuAnEX0W-w@mail.gmail.com> <e14ba43d-ba21-609f-223e-d1f703fb9770@cisco.com> <CA+m752LWz=SkCHGwzBXzMkEyWb3R5A20OVAsjGiGbE8g=6dciA@mail.gmail.com> <7111cec3-35de-7067-6d4f-b62063224d53@cisco.com> <597A03E6-DBD1-4EA1-BFE3-F24FCF028CFC@apple.com> <dde99284-53ba-12fd-af69-62798a811ec3@cisco.com> <CAD5OKxv6f0GeL5xqaVuCtzFLE0Rkzse6LdiSty-4zxYqBm_YFQ@mail.gmail.com> <CAOJ7v-2c7p6+K6aZfyeBNB71X-1aBNFCZtnfb1A-TCtb3ma7-A@mail.gmail.com> <a489fb7e-1d70-e79a-d4a9-683f43b7e691@cisco.com> <CAOJ7v-2tEZkzrdFyQ_64bY+O8XXGkPRUk75Ejnwn36P=KHv+Hw@mail.gmail.com> <4a30a974-fbef-5b79-d91d-43f0ab3abca9@cisco.com> <8C5F94F4-5226-4875-AE25-07D0551566B8@apple.com> <AM0PR07MB386020B236D6C7676DBB150193C70@AM0PR07MB3860.eurprd07.prod.outlook.com> <CAD5OKxuznrD2JtWSo3rKpQFAOhzLpy=HjMvsCs5UVsRi9EDZ4g@mail.gmail.com>
In-Reply-To: <CAD5OKxuznrD2JtWSo3rKpQFAOhzLpy=HjMvsCs5UVsRi9EDZ4g@mail.gmail.com>
From: Justin Uberti <juberti@google.com>
Date: Tue, 15 Dec 2020 10:03:20 -0800
Message-ID: <CAOJ7v-15k4z=aJjkwNo+BOL-13tpr_neD_oUYOfDpLzC_N0j3w@mail.gmail.com>
To: Roman Shpount <roman@telurix.com>
Cc: Christer Holmberg <christer.holmberg@ericsson.com>, Youenn Fablet <youenn@apple.com>, Flemming Andreasen <fandreas@cisco.com>, mmusic WG <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a6172d05b68493f2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/q2Y85xUZMwZneesuklAFMif14Xo>
Subject: Re: [MMUSIC] draft-ietf-rtcweb-mdns-ice-candidates
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Dec 2020 18:03:37 -0000
Treating mdns-ice-candidates as an extension spec seems like the cleanest path to me. We can simply adjust the draft metadata to say that it updates sip-sdp, and then I suppose we'll need a section that directly indicates how sip-sdp is being extended. On Mon, Dec 14, 2020 at 11:57 AM Roman Shpount <roman@telurix.com> wrote: > Hi, > > We have added the following language in ICE-SIP-SDP specifically related > to this issue: > > An agent generating local candidates MUST NOT use FQDN addresses. An > agent processing remote candidates MUST ignore candidate lines that include > candidates with FQDN or IP address versions that are not supported or > recognized. The procedures for generation and handling of FQDN candidates, > as well as how agents indicate support for such procedures, need to be > specified in an extension specification. > > So, the simplest thing would be to treat mdns-ice as an extension > specification. > > Another option is to write an extension specification for a generic > FQND candidate handling. > _____________ > Roman Shpount > > > On Mon, Dec 14, 2020 at 2:12 PM Christer Holmberg <christer.holmberg= > 40ericsson.com@dmarc.ietf.org> wrote: > >> Hi, >> >> >> >> I don’t think you can override ICE-SIP-SDP. You can update ICE-SIP-SDP in >> the mdns draft, though. >> >> >> >> Regards, >> >> >> >> Christer >> >> >> >> *From:* mmusic <mmusic-bounces@ietf.org> *On Behalf Of *Youenn Fablet >> *Sent:* maanantai 14. joulukuuta 2020 17.57 >> *To:* Flemming Andreasen <fandreas@cisco.com> >> *Cc:* Justin Uberti <juberti=40google.com@dmarc.ietf.org>; mmusic WG < >> mmusic@ietf.org> >> *Subject:* Re: [MMUSIC] draft-ietf-rtcweb-mdns-ice-candidates >> >> >> >> The remaining issue so far is how to integrate mDNS ICE candidate within >> the ICE SIP SDP spec. >> >> Issue is tracked at >> https://github.com/rtcweb-wg/mdns-ice-candidates/issues/98 >> <https://protect2.fireeye.com/v1/url?k=d3f714f2-8c6c2c10-d3f75469-86073b36ea28-1104717675e6365a&q=1&e=f1f29775-cad2-4330-81ed-4c95d3733118&u=https%3A%2F%2Fgithub.com%2Frtcweb-wg%2Fmdns-ice-candidates%2Fissues%2F98> >> >> Either the mDNS ICE candidate overrides ICE-SIP-SDP or ICE-SIP-SDP is >> updated and could refer to the mDNS ICE candidate spec. >> >> We lean towards the former and welcome any feedback on the best way to >> proceed. >> >> >> >> Thanks, >> >> Y >> >> >> >> On 14 Dec 2020, at 16:17, Flemming Andreasen <fandreas@cisco.com> wrote: >> >> >> >> Thanks Justin >> >> We submitted a milestone update a little while back and are just waiting >> for the AD go-ahead. In the meantime, it would be good to have any >> remaining issues discussed on the mailing list as well. >> >> Cheers >> >> -- Flemming >> >> On 12/11/20 11:01 PM, Justin Uberti wrote: >> >> Youenn and Qingsi have resolved several issues over the past week. There >> are a few remaining issues to discuss, but I think we can have this ready >> for last call within the month, perhaps earlier. >> >> >> >> On Mon, Oct 26, 2020 at 5:20 PM Flemming Andreasen <fandreas@cisco.com> >> wrote: >> >> Going back to the original question: What do the authors view as a >> realistic timeframe for getting the draft ready for publication ? >> >> Thanks >> >> -- Flemming >> >> On 10/22/20 1:54 AM, Justin Uberti wrote: >> >> This is currently supported in Safari iOS, and we are working to bring >> this to Chrome Android as well. >> >> >> >> On Wed, Oct 21, 2020 at 8:47 AM Roman Shpount <roman@telurix.com> wrote: >> >> I would like to see if there any implementations of this draft on mobile >> networks. I think this draft's interactions with mobile network deployment >> scenarios, such as 464XLAT, should be examined in detail before this draft >> is ready for publication. Also, mDNS is not currently supported on Android, >> which represents a significant portion of this draft use case, making some >> of the implementation details a bit fuzzy. My main concern here is if the >> mDNS name which is associated with one IP address always resolves to the >> same IP address with the same address family when resolved on the same >> network. >> >> >> >> Best Regards, >> >> _____________ >> Roman Shpount >> >> >> >> >> >> On Wed, Oct 21, 2020 at 11:04 AM Flemming Andreasen <fandreas= >> 40cisco.com@dmarc.ietf.org> wrote: >> >> By publication we mean that the draft is considered to be in the final >> ready state with no known issues, whether technical or editorial. At that >> point, the Working Group chairs will do (another) thorough review of the >> document, and if it looks ready then ask for publication of the document, >> which means it will be sent to the responsible Area Director for review, >> and subsequently to the IESG for further review and eventually it's >> published as an RFC. >> >> Thanks >> >> -- Flemming >> >> On 10/21/20 10:48 AM, Youenn Fablet wrote: >> >> I am also fuzzy about what it means to publish the draft. >> >> It seems to me the document is ready for another version to be published. >> >> To produce the final version that we expect to go to validation, we >> should probably finish resolving the 8 remaining issues and update the spec >> according the resolutions of these 8 issues. >> >> >> >> On 21 Oct 2020, at 16:33, Flemming Andreasen <fandreas@cisco.com> wrote: >> >> >> >> It all depends on how mature the draft is, especially in terms of its >> technical content. Also, we will need a few reviewers to look closely at >> the draft to see if there are any issues the authors may not have thought >> of. >> >> Cheers >> >> -- Flemming >> >> >> On 10/20/20 10:55 PM, Qingsi Wang wrote: >> >> Hi Flemming, >> >> >> >> I'm sorry for not being familiar with the process. In addition to >> editorial revisions and addressing comments, are there other prerequisites >> for publication? >> >> >> >> Thanks, >> >> Qingsi >> >> >> >> On Tue, Oct 20, 2020 at 7:47 PM Flemming Andreasen <fandreas@cisco.com> >> wrote: >> >> Thanks Justin. What do the authors view as a realistic timeframe for >> getting the draft ready for publication ? >> >> Cheers >> >> -- Flemming >> >> On 10/19/20 8:08 PM, Justin Uberti wrote: >> >> New draft posted (now with -mmusic name) and waiting for approval. >> >> >> >> On Thu, Oct 15, 2020 at 12:40 PM Justin Uberti <juberti@google.com> >> wrote: >> >> This fell off my radar, will update the draft shortly though. >> >> >> >> On Fri, Sep 18, 2020 at 9:13 AM Flemming Andreasen <fandreas= >> 40cisco.com@dmarc.ietf.org> wrote: >> >> It looks like we have at least 5 people interested in and willing to >> contribute to the work. Based on this, the chairs will work with our AD on >> getting a new milestone added. >> >> I see that the current draft has expired though - can we get an updated >> version submitted first ? >> >> Thanks >> >> -- Flemming (as MMUSIC co-chair) >> >> >> On 9/2/20 2:57 PM, Qingsi Wang wrote: >> >> I am interested and willing to contribute to this document too. >> >> >> >> Best, >> >> Qingsi >> >> >> >> On Wed, Sep 2, 2020 at 11:51 AM Youenn Fablet <youenn= >> 40apple.com@dmarc.ietf.org> wrote: >> >> I am interested and willing to contribute to the document. >> >> The proposal being implemented by various parties, having this document >> be reviewed and ironed out as much as possible is valuable. >> >> >> >> Thanks, >> >> Y >> >> >> >> On 2 Sep 2020, at 20:09, Flemming Andreasen <fandreas@cisco.com> wrote: >> >> >> >> So far I've only seen 2 people expressing an interest in this document. >> >> Is anybody else interested, and if so, are you willing to contribute >> and/or review the document ? >> >> Thanks >> >> -- Flemming (as MMUSIC co-chair) >> >> On 7/31/20 12:16 AM, Roman Shpount wrote: >> >> I am strongly in favor of adopting this draft to MMUSIC and getting it >> completed. >> >> _____________ >> Roman Shpount >> >> >> >> >> >> On Thu, Jul 30, 2020 at 7:33 PM Justin Uberti <juberti= >> 40google.com@dmarc.ietf.org> wrote: >> >> Hi all, >> >> >> >> With the closure of rtcweb, we have been advised to find a new forum for >> https://tools.ietf.org/html/draft-ietf-rtcweb-mdns-ice-candidates-04, >> and MMUSIC seems like the best home for it. >> >> >> >> I believe this document is in fairly good shape and should be ready for >> last call soon. Any objections to taking it on in this working group? >> >> >> >> Justin >> >> _______________________________________________ >> mmusic mailing list >> mmusic@ietf.org >> https://www.ietf.org/mailman/listinfo/mmusic >> >> >> >> _______________________________________________ >> >> mmusic mailing list >> >> mmusic@ietf.org >> >> https://www.ietf.org/mailman/listinfo/mmusic >> >> >> >> >> >> _______________________________________________ >> mmusic mailing list >> mmusic@ietf.org >> https://www.ietf.org/mailman/listinfo/mmusic >> >> >> >> _______________________________________________ >> >> mmusic mailing list >> >> mmusic@ietf.org >> >> https://www.ietf.org/mailman/listinfo/mmusic >> >> >> >> >> >> >> >> _______________________________________________ >> >> mmusic mailing list >> >> mmusic@ietf.org >> >> https://www.ietf.org/mailman/listinfo/mmusic >> >> >> >> >> >> >> _______________________________________________ >> >> mmusic mailing list >> >> mmusic@ietf.org >> >> https://www.ietf.org/mailman/listinfo/mmusic >> >> >> >> _______________________________________________ >> mmusic mailing list >> mmusic@ietf.org >> https://www.ietf.org/mailman/listinfo/mmusic >> >> >> >> >> >> _______________________________________________ >> >> mmusic mailing list >> >> mmusic@ietf.org >> >> https://www.ietf.org/mailman/listinfo/mmusic >> >> >> >> >> _______________________________________________ >> mmusic mailing list >> mmusic@ietf.org >> https://www.ietf.org/mailman/listinfo/mmusic >> >
- [MMUSIC] draft-ietf-rtcweb-mdns-ice-candidates Justin Uberti
- Re: [MMUSIC] draft-ietf-rtcweb-mdns-ice-candidates Sean DuBois
- Re: [MMUSIC] draft-ietf-rtcweb-mdns-ice-candidates Justin Uberti
- Re: [MMUSIC] draft-ietf-rtcweb-mdns-ice-candidates Sean DuBois
- Re: [MMUSIC] draft-ietf-rtcweb-mdns-ice-candidates Roman Shpount
- Re: [MMUSIC] draft-ietf-rtcweb-mdns-ice-candidates Flemming Andreasen
- Re: [MMUSIC] draft-ietf-rtcweb-mdns-ice-candidates Youenn Fablet
- Re: [MMUSIC] draft-ietf-rtcweb-mdns-ice-candidates Qingsi Wang
- Re: [MMUSIC] draft-ietf-rtcweb-mdns-ice-candidates Nils Ohlmeier
- Re: [MMUSIC] draft-ietf-rtcweb-mdns-ice-candidates Flemming Andreasen
- Re: [MMUSIC] draft-ietf-rtcweb-mdns-ice-candidates Justin Uberti
- Re: [MMUSIC] draft-ietf-rtcweb-mdns-ice-candidates Justin Uberti
- Re: [MMUSIC] draft-ietf-rtcweb-mdns-ice-candidates Flemming Andreasen
- Re: [MMUSIC] draft-ietf-rtcweb-mdns-ice-candidates Qingsi Wang
- Re: [MMUSIC] draft-ietf-rtcweb-mdns-ice-candidates Flemming Andreasen
- Re: [MMUSIC] draft-ietf-rtcweb-mdns-ice-candidates Youenn Fablet
- Re: [MMUSIC] draft-ietf-rtcweb-mdns-ice-candidates Flemming Andreasen
- Re: [MMUSIC] draft-ietf-rtcweb-mdns-ice-candidates Roman Shpount
- Re: [MMUSIC] draft-ietf-rtcweb-mdns-ice-candidates Justin Uberti
- Re: [MMUSIC] draft-ietf-rtcweb-mdns-ice-candidates Flemming Andreasen
- Re: [MMUSIC] draft-ietf-rtcweb-mdns-ice-candidates Justin Uberti
- Re: [MMUSIC] draft-ietf-rtcweb-mdns-ice-candidates Flemming Andreasen
- Re: [MMUSIC] draft-ietf-rtcweb-mdns-ice-candidates Youenn Fablet
- Re: [MMUSIC] draft-ietf-rtcweb-mdns-ice-candidates Christer Holmberg
- Re: [MMUSIC] draft-ietf-rtcweb-mdns-ice-candidates Roman Shpount
- [MMUSIC] Question about draft-ietf-rtcweb-mdns-ic… Roman Shpount
- Re: [MMUSIC] Question about draft-ietf-rtcweb-mdn… Qingsi Wang
- Re: [MMUSIC] Question about draft-ietf-rtcweb-mdn… Roman Shpount
- Re: [MMUSIC] Question about draft-ietf-rtcweb-mdn… Youenn Fablet
- Re: [MMUSIC] Question about draft-ietf-rtcweb-mdn… Roman Shpount
- Re: [MMUSIC] draft-ietf-rtcweb-mdns-ice-candidates Justin Uberti
- Re: [MMUSIC] draft-ietf-rtcweb-mdns-ice-candidates Christer Holmberg
- Re: [MMUSIC] draft-ietf-rtcweb-mdns-ice-candidates Roman Shpount
- Re: [MMUSIC] draft-ietf-rtcweb-mdns-ice-candidates Christer Holmberg