Return-Path: X-Original-To: rtcweb@ietfa.amsl.com Delivered-To: rtcweb@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0FCBB12D0FF for ; Tue, 12 Jul 2016 05:45:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 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_LOW=-0.7, 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 vEQshoO_KI86 for ; Tue, 12 Jul 2016 05:45:08 -0700 (PDT) Received: from mail-yw0-x229.google.com (mail-yw0-x229.google.com [IPv6:2607:f8b0:4002:c05::229]) (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 9A84812D739 for ; Tue, 12 Jul 2016 05:45:07 -0700 (PDT) Received: by mail-yw0-x229.google.com with SMTP id i12so12218918ywa.1 for ; Tue, 12 Jul 2016 05:45:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=maqDqHOBuNIB55ZkCQ7jPRARJx875SXcKVhrLaSvBt8=; b=fsft5lprq9Mg8PaUCcp/1DeeQqK886KSnfFL8ieUGevulCbQyu4Evia8vh5oGb+62h gVk/yRSSY5tFhVKf3YVSSy27i7CP3XPeD1CtRxWAycgtI6XSsgFPa49UCZcnYzOa5nrx e892fikqXWHNoVoCFkNxmyugo6CS7U4tujhjmAXyw3D+nQzISuzN28Qj6vcRVPe+WBqc JGrD4p7SQ5ViBQMCv9ncbyme5SZknKh8JNs2pzD49DGsZaaDQO0UAvRfxZ4qcGv7djBs HubOYC3kLsIuwu49dAZlL8cypECDpjkorbl3jktvoiTqQWW0BGfnFxBaOtkK7hGuzgSa lbbw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=maqDqHOBuNIB55ZkCQ7jPRARJx875SXcKVhrLaSvBt8=; b=h/dJqLKsc/NreMCxlhYMcImBBqz8seG7ujsrAu1SuHttPNFjwOksuVvZh6f1CW7XWm jtTIRrUzA+U11iGIqpvUhj3ZTyjzZz4QtuetZkDli8eRER9INJ9gDj8ed7zLvKCcXt3K OgJEWUmbXqh9x3pqrkk8jUp13nT8wwsKnOpaVGb4OmmJo1J/VAto3zzve1u2xGpNe/b+ Y8L54M1jxKWRhWIgfZeU7eviPk4QmcSj2JW4jxCXlPcc8VTlup4WSUmObmHKgxKwmSrn 2e6CkyMI/DnnTSn9RMnzYLjU3pIW6rCwCJP9RoOaCl3g4oxdCJaLXSfChlLcwfTrH5EH fiHQ== X-Gm-Message-State: ALyK8tJ1AiDGNz4svIOYdADK5u0zjyvSCG0Two1tziVCW0xK37zi/b1N4gG3EsggiEXDshU5RE71nSNJ7euioA== X-Received: by 10.129.93.214 with SMTP id r205mr1261847ywb.15.1468327506749; Tue, 12 Jul 2016 05:45:06 -0700 (PDT) MIME-Version: 1.0 Received: by 10.129.121.3 with HTTP; Tue, 12 Jul 2016 05:45:06 -0700 (PDT) In-Reply-To: References: <3F93402D-B1B1-4FD5-8242-076A5604E551@edvina.net> From: Suhas Nandakumar Date: Tue, 12 Jul 2016 18:15:06 +0530 Message-ID: To: "Olle E. Johansson" Content-Type: multipart/alternative; boundary=001a114d6e0c742e2c05376fa3ba Archived-At: Cc: "rtcweb@ietf.org" Subject: Re: [rtcweb] draft-ietf-rtcweb-sdp-02 submitted X-BeenThere: rtcweb@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Real-Time Communication in WEB-browsers working group list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Jul 2016 12:45:10 -0000 --001a114d6e0c742e2c05376fa3ba Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hello Olle Thanks for the review. I will go through the other comments in a while but wanted to share one thought on the ptime feedback JSEP-15 says - If this m=3D section is for media with configurable frame sizes, e.g. audio, an "a=3Dmaxptime" line, indicating the smallest of the maximum supported frame sizes out of all codecs included above, as specified in [RFC4566] , Section 6." The current set of examples try to follow JSEP specification to the closest in how the SDP is constructed barring few open issues on handing certain attributes Please let us know your thoughts on various ptimes across codecs is something that should go in JSEP spec SDP rules as well ? Thanks Suhas On Tue, Jul 12, 2016 at 5:40 PM, Olle E. Johansson wrote: > > On 12 Jul 2016, at 09:55, Olle E. Johansson wrote: > > > General: > > I would like to see some examples using the current IP protocol, not the = legacy IPv4, > > as well as dual stack examples. > > > - An IPv6 only web browser offering an IPv4 through a relay ice candidate > > - A dual stack client > > - A full IPv6 exchange - maybe switch one of the examples using IPv4 to I= Pv6 > > just to show the syntax of address and port number > > > In addition I think an offer/answer with different packetization times, > like > alaw/30 ms, Opus/60 ms or something similar. Yes, I=E2=80=99m going down = a rat > hole, > but it will come up and we=E2=80=99d better document a proposal for how t= o handle > this. > > If one wants to be messy you can add DTMF or CNG to an offer/answer using > alaw at 8000 hz and Opus at 48000 making it necessary to have multiple DT= MF > and CNG for that media stream. But that may be out of scope for this > particular > document, even though it may add clarity. > > /O > --001a114d6e0c742e2c05376fa3ba Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello Olle

=C2=A0 Thanks for the review= . I will go through the other comments in a while but wanted to share one t= hought on the ptime feedback

JSEP-15 says
  • If this = m=3D section is for media with configurable frame sizes, e.g. audio, an &qu= ot;a=3Dmaxptime" line, indicating the smallest of the maximum supporte= d frame sizes out of all codecs included above, as specified in=C2=A0[RFC4566], Section 6."
    • The current set of examples tr= y to follow JSEP specification to the closest in how the SDP is constructed= barring few open issues on handing certain attributes
    <= div>=
    Please let us know your thoughts =C2=A0on various pti= mes across codecs is something that should go in JSEP spec SDP rules as wel= l ?

    Thanks
    Suhas

    On Tue, Jul 12, 2016 at 5:4= 0 PM, Olle E. Johansson <oej@edvina.net> wrote:
    On 12 Jul 2016, at 09:55, Olle E. Joha= nsson <oej@edvina.ne= t> wrote:


    General:
    I would like to see some examples using the current=
 IP protocol, not the legacy IPv4,
    as well as dual stack examples.
    = 

    - An IPv6 only =
web browser offering an IPv4 through a relay ice candidate
    - A dual stack clien=
t
    - A full IPv6 excha=
nge - maybe switch one of the examples using IPv4 to IPv6
      just to show the syntax of address and po=
rt number

    In addition I think an o= ffer/answer with different packetization times, like
    alaw/30 ms, Opus/6= 0 ms or something similar. Yes, I=E2=80=99m going down a rat hole,
    but it will come up and we=E2=80=99d better document a proposal for how t= o handle this.

    If one wants to be messy you can ad= d DTMF or CNG to an offer/answer using
    alaw at 8000 hz and Opus a= t 48000 making it necessary to have multiple DTMF
    and CNG for tha= t media stream. But that may be out of scope for this particular
    = document, even though it may add clarity.

    /O

    --001a114d6e0c742e2c05376fa3ba--