Re: [MMUSIC] draft-ietf-rtcweb-mdns-ice-candidates

Roman Shpount <roman@telurix.com> Wed, 21 October 2020 15:47 UTC

Return-Path: <roman@telurix.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 052AF3A10C3 for <mmusic@ietfa.amsl.com>; Wed, 21 Oct 2020 08:47:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telurix-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 6JeTU8gfpjKF for <mmusic@ietfa.amsl.com>; Wed, 21 Oct 2020 08:47:00 -0700 (PDT)
Received: from mail-ot1-x330.google.com (mail-ot1-x330.google.com [IPv6:2607:f8b0:4864:20::330]) (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 272E63A1059 for <mmusic@ietf.org>; Wed, 21 Oct 2020 08:46:59 -0700 (PDT)
Received: by mail-ot1-x330.google.com with SMTP id k68so2219255otk.10 for <mmusic@ietf.org>; Wed, 21 Oct 2020 08:46:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=sUzsX/qIRPvEGMtRFCuJVRllqD80mYpG6GnOx54o4dk=; b=Y8s/+8Fp32XEr8+knB2A+UGRUYRGHVX5cwnjriFWBKoxLiP7EG+3wHCZBE2ejqcaFu QdyiKV1mISBg4wbxYVaO5Yffbhhy/WeiXHdKDGlchEf0HjLI1plB5IUwAlqCSXGlrGt0 cws5zPB9KZa0wVwrF+iQ2KkleETpTzU/ut3HPWdYFDquKVtRdp2+nbX3BVKr9SRdR3Sy 3sKPX4rIhCCQkx7/Nhy/CDeC/VtJ54oCD5wuyRDN4Gq68Y130gupLIFIDIMau6vHgF9u DzKNzD4ncpPvkmCwQzDaexRKEwa9T5Q1QKG2KTtm+QgZbDj9ofM3eV7bxXfgM38uiKmi nhzQ==
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=sUzsX/qIRPvEGMtRFCuJVRllqD80mYpG6GnOx54o4dk=; b=Kl5UC3T3Z+Yd/yJMx4KhJidyO3FiZFXggHO3IJCazYWHN97ueGOFHSf2I5mz7QG0ol mEV4yhHAkQG7rwYgb3EbZE+iWP+4m4qB4Vx7wjQDt3XQjknj8ERCaQJujWvAhW1lnq39 hwhKeDXg8pbz/iz0QIAcromxeh3de8sLwJQS5KjNrEZ892NG6YFqd3iWGNdykPcfnGs1 yzq4UjhP+eXP626yFFNBi/2Btmw7a0Pe5XRgwL6fm3NRGQ0T7HcC0i/TjO00tEupVC25 5Zw0Q8UbdZqsP/Vy7L8mY0YtE9sKuu4t3zCi8PleYzJmyOZEH4rNqc/S8o2n1AHTKsB2 LFNg==
X-Gm-Message-State: AOAM531cFVpDdVHd08E2emkVUZLDjCG1R9aJPFY/toeo0dRaHoixOxUL Fhn31p+vBQ3WKkybJ1s3RUBGxeNF7pd4aQ==
X-Google-Smtp-Source: ABdhPJwuC+pM3Z6t6XZIPX5G3OHj8fpkP/hlN/MSaXEJrz2efO3NP4NW/pz+ug6WUpjGJ/eGqzhenw==
X-Received: by 2002:a9d:bd1:: with SMTP id 75mr2837318oth.1.1603295218699; Wed, 21 Oct 2020 08:46:58 -0700 (PDT)
Received: from mail-ot1-f42.google.com (mail-ot1-f42.google.com. [209.85.210.42]) by smtp.gmail.com with ESMTPSA id y8sm672047oon.16.2020.10.21.08.46.57 for <mmusic@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 21 Oct 2020 08:46:57 -0700 (PDT)
Received: by mail-ot1-f42.google.com with SMTP id f10so2244300otb.6 for <mmusic@ietf.org>; Wed, 21 Oct 2020 08:46:57 -0700 (PDT)
X-Received: by 2002:a9d:21f5:: with SMTP id s108mr2897414otb.13.1603295216947; Wed, 21 Oct 2020 08:46:56 -0700 (PDT)
MIME-Version: 1.0
References: <CAOJ7v-1VEsXobYaq0UdOkaGLGbnNH40srDX+tg+OYZivGRVhNw@mail.gmail.com> <CAD5OKxupvBC8f4GHY=o2KLxvRoDCqNN5hW+eL5OSthPm0bMkng@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>
In-Reply-To: <dde99284-53ba-12fd-af69-62798a811ec3@cisco.com>
From: Roman Shpount <roman@telurix.com>
Date: Wed, 21 Oct 2020 11:46:45 -0400
X-Gmail-Original-Message-ID: <CAD5OKxv6f0GeL5xqaVuCtzFLE0Rkzse6LdiSty-4zxYqBm_YFQ@mail.gmail.com>
Message-ID: <CAD5OKxv6f0GeL5xqaVuCtzFLE0Rkzse6LdiSty-4zxYqBm_YFQ@mail.gmail.com>
To: Flemming Andreasen <fandreas=40cisco.com@dmarc.ietf.org>
Cc: Youenn Fablet <youenn=40apple.com@dmarc.ietf.org>, Qingsi Wang <qingsi=40google.com@dmarc.ietf.org>, Justin Uberti <juberti=40google.com@dmarc.ietf.org>, mmusic WG <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000e0591c05b230416e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/efMy1yY_hAl6DkbqeHL-7mRqIII>
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: Wed, 21 Oct 2020 15:47:04 -0000

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 listmmusic@ietf.orghttps://www.ietf.org/mailman/listinfo/mmusic
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> mmusic mailing list
>>>>> mmusic@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/mmusic
>>>>>
>>>>
>>>> _______________________________________________
>>>> mmusic mailing listmmusic@ietf.orghttps://www.ietf.org/mailman/listinfo/mmusic
>>>>
>>>>
>>>>
>>
> _______________________________________________
> mmusic mailing listmmusic@ietf.orghttps://www.ietf.org/mailman/listinfo/mmusic
>
>
>
>
> _______________________________________________
> mmusic mailing listmmusic@ietf.orghttps://www.ietf.org/mailman/listinfo/mmusic
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>