Re: [bfcpbis] Eric Rescorla's Discuss on draft-ietf-bfcpbis-rfc4583bis-26: (with DISCUSS and COMMENT)

Eric Rescorla <ekr@rtfm.com> Mon, 03 December 2018 14:55 UTC

Return-Path: <ekr@rtfm.com>
X-Original-To: bfcpbis@ietfa.amsl.com
Delivered-To: bfcpbis@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33030130E99 for <bfcpbis@ietfa.amsl.com>; Mon, 3 Dec 2018 06:55:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.358
X-Spam-Level:
X-Spam-Status: No, score=-3.358 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-1.459, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-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 3OAjMtrwIPXk for <bfcpbis@ietfa.amsl.com>; Mon, 3 Dec 2018 06:55:48 -0800 (PST)
Received: from mail-lj1-x230.google.com (mail-lj1-x230.google.com [IPv6:2a00:1450:4864:20::230]) (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 66B33130E7F for <bfcpbis@ietf.org>; Mon, 3 Dec 2018 06:55:46 -0800 (PST)
Received: by mail-lj1-x230.google.com with SMTP id c19-v6so11663321lja.5 for <bfcpbis@ietf.org>; Mon, 03 Dec 2018 06:55:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=024fXe9z52WIEnET8TsM/xR6WKMkQdDqu7cBQ4BKX4o=; b=E+9dhA6MulI2xxV4t0Hw0pbE0cN7NipE8W8wC8awBaTUx4joTBQDGBHwtSJ0bAf6Uq /Itsk+CQCSj+VyJzLIYDyfzwh6VF5ScDm8hzgL/QIJkCyK3reMVdt5N3oPKeK6qBW0LL JQ0NjM2RqMIZngkijU04EG4vz27IVj//V4khCm1L0d4KmBXE9TP0ykFy29r90p+H+23N 8fliTjKhJ7n/jOyRfHTobpTE3FnH9LFutH3lU0fShWaj3JqE2OxX6fG+zipZCh/BW8Fv pKDexruzcGTyEg6Mp/2+LHROwJND/Yl3F/WzLnCZwfcrf/nPVPApWiImHjSBCcEN5eM5 3yTw==
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=024fXe9z52WIEnET8TsM/xR6WKMkQdDqu7cBQ4BKX4o=; b=Oatk0c8eSkfWMjtiptnaV3X7drw3k4f/VvTTi0Kp1g3WM1IAlKMdQcuI8tPVkjGrJ6 7RKtqSl5fAc+bQi/0+LB6dF5WB7EK2yjAHdKe7NZ6b+4/hYqNqGncGTLpjktxzdclQGj XLgirQjBp5rGbAVrTHY5daMt5cxzCJ78fCbL4EhERofUvwIjzUJb/9AHEFCOew0wbler xyS2Ke+TvZC5isFZ9v5Tyz4Ladbcn74wCnn0Ku1hM9L5+YXQtWGGzsUfAEzHCP5M/s8t /liMyNXY0ypMfkJ0+qJmmnrGV2n36hKSvFaYW/vTgCzMbXdzXJQmoQ2worlLbqaoOICJ AB6w==
X-Gm-Message-State: AA+aEWatIXwG90RGb9wdRhgj2SHVG4PDlzU59zM9C4oIkmYTv8gzmq/C 33WT/R66mHDdkPb745utdgDsLBnQGi6sVTXd2L0s/Q==
X-Google-Smtp-Source: AFSGD/W5Ms+nDrR60yW4FDGclZJrtDQrSipOdUAdVuxPxmTryK2tEO6GZeXs4g+0IMeyBmRh5gFSmhu3RFGgJyoTQZM=
X-Received: by 2002:a2e:5418:: with SMTP id i24-v6mr11169979ljb.51.1543848944576; Mon, 03 Dec 2018 06:55:44 -0800 (PST)
MIME-Version: 1.0
References: <154040901414.6834.17243795717657341259.idtracker@ietfa.amsl.com> <8032FEDB-0F35-4CCA-A0E7-BE86AEC0CBD8@ericsson.com> <CABcZeBP0pB7YZwz2Hm=ZJf4HBMC_nJ_M4bD=xbFto9iM8dfU+g@mail.gmail.com> <E3F4852A-F79E-48AC-A153-60B8C1A3443B@ericsson.com> <CABcZeBPo6o-TjFGXvJ-EfKke30z6=ue5KrSNgTAZYCu=ABD+2g@mail.gmail.com> <41F47CD9-01AC-4865-B511-FABDF455395F@ericsson.com>
In-Reply-To: <41F47CD9-01AC-4865-B511-FABDF455395F@ericsson.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Mon, 03 Dec 2018 06:55:07 -0800
Message-ID: <CABcZeBNw-wP3CnWO9FJ=WqGXticAU4zaKqXs3RUEQcZrZakjHQ@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Cc: IESG <iesg@ietf.org>, Mary Barnes <mary.ietf.barnes@gmail.com>, bfcpbis@ietf.org, draft-ietf-bfcpbis-rfc4583bis@ietf.org, bfcpbis-chairs@ietf.org
Content-Type: multipart/alternative; boundary="000000000000edcae9057c1f57cb"
Archived-At: <https://mailarchive.ietf.org/arch/msg/bfcpbis/4aL9KXviY49oCjoEnVYPrJPe5Rs>
Subject: Re: [bfcpbis] Eric Rescorla's Discuss on draft-ietf-bfcpbis-rfc4583bis-26: (with DISCUSS and COMMENT)
X-BeenThere: bfcpbis@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: BFCPBIS working group discussion list <bfcpbis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bfcpbis>, <mailto:bfcpbis-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bfcpbis/>
List-Post: <mailto:bfcpbis@ietf.org>
List-Help: <mailto:bfcpbis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bfcpbis>, <mailto:bfcpbis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Dec 2018 14:55:52 -0000

On Mon, Dec 3, 2018 at 6:33 AM Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> Hi,
>
> ---
>
> >>>>> S 5.5.
> >>>>>      'bfcpver' attribute in offers and answers.  The attribute
> value, if
> >>>>>      present, MUST be in accordance with the definition of the
> Version
> >>>>>      field in [I-D.ietf-bfcpbis-rfc4582bis].  If the attribute is not
> >>>>>      present, endpoints MUST assume a default value in accordance
> with
> >>>>>      [I-D.ietf-bfcpbis-rfc4582bis]: when used over a reliable
> transport
> >>>>>      the default attribute value is "1", and when used over an
> unreliable
> >>>>
> >>>> Just for clarity: UDP over TURN-TCP is an unreliable transport, right?
> >>>
> >>> I would assume so, but I guess that question is not BFCP specific?
> >>>
> >>> Sorry, what I mean is "does BFCP count it as an unreliable transport".
> I agree it is unreliable.
> >>
> >> Do you think we need to add some text about it?
> >>
> >> Related to that, if ICE is used, if both UDP and TCP candidates are
> offered, endpoints might not know what kind of transport will eventually
> >> be selected. Perhaps there should be a note about that?
> >>
> >> Something like:
> >>
> >> "Note: When ICE is used, where the candidates represent both reliable
> and unreliable transports, the ICE process will determine what type of
> transport will eventually be used."
> >
> > Well, ICE can flip-flop the transport, so I think if you have anything
> other than ICE-TCP (which is to say anyone who uses ICE) then you have to
> assume it's unreliable
>
> My point was that when you send the offer, and set the 'bfcpver' attribute
> value, if you use ICE you may not yet know whether the transport will
> eventually be reliable or unreliable (if you offer candidates for both
> reliable and unreliable transports).
>
> I guess we could say that the attribute value must match the transport
> indicated in the 'm' line. That way things will be correct if the remote
> peer does not support ICE.
>

i don't really know what this attribute is used for so it's hard for me to
say.

Can you explain what it does?

-Ekr

Regards,
>
> Christer
>
>
>
>