Re: [MMUSIC] Finding a max length of "a=mid" attribute

Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com> Wed, 03 March 2021 21:43 UTC

Return-Path: <sergio.garcia.murillo@gmail.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 180EC3A1BA3 for <mmusic@ietfa.amsl.com>; Wed, 3 Mar 2021 13:43:47 -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, RCVD_IN_DNSWL_NONE=-0.0001, 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 aNy8x06CeGjm for <mmusic@ietfa.amsl.com>; Wed, 3 Mar 2021 13:43:44 -0800 (PST)
Received: from mail-wr1-x432.google.com (mail-wr1-x432.google.com [IPv6:2a00:1450:4864:20::432]) (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 3B0E33A1BA1 for <mmusic@ietf.org>; Wed, 3 Mar 2021 13:43:44 -0800 (PST)
Received: by mail-wr1-x432.google.com with SMTP id h98so25328833wrh.11 for <mmusic@ietf.org>; Wed, 03 Mar 2021 13:43:44 -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=rw83oap3bV7s63vNeCRMozuvloryhmrZbe5sErYLbkY=; b=XShHjh9QbD7ac7oOhqQDX4KaJpBlz143KE8+jZI9/zgDOWS5e/98vg3V9kXNj3Frkz h9G4OTsSwK/1Q/RYctdO0JF6R6gn/IFg4oNfgUOiDmUI5ayvlHUcaQy1X1FhTp9SY7At B3ErGn2dF6eMurqF+qs7nwzCufM3cA1EF65NBxLK9JZAVARP4r4CAxz7aPv3SSXsLyGB ZKWhwEgRXnhyT/eKjMTbl/btQcdKx0f2/0pLs5M/w7pHIfYs5MfTJdHB3BxhtEBodtA2 xi9o8ArQwwKbs27LZnKQ0veDJVrHnkf+hAwziZhTJRrz3EFLexqRJ/xlf+92siqvwY+2 Xj5Q==
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=rw83oap3bV7s63vNeCRMozuvloryhmrZbe5sErYLbkY=; b=RL11w5X9QCUB0GKxY4lTHkKT1C2yaUoJzqs1LUp4q79koeAO+DoqeaBg3/96IKRPJb 6dIysEcPPGA2Em5M1mfr2X7pJPh6Jnq56kMnM1xZ0+I7mV/E3pBilu7NAldR36tUkAFW 9llC/T+jJtM9s3/4dStf0XXgWYMaPdfGOAj8wgLPhyCNgUamhF48eCFakFS+eZ8Dt6uN o6FJIgwafmKkI8+cK260X3Gj2tv4m6/xvKHZVkrc/hCV0sWIPTob6XpzouI+kS0JFEzN 2EjSHlBOczdl8K/MFp/2leWIGY2ZHBxY3EID7FjFTPrdfq1S9AzGDNfXtz123WLGY5Y0 6nrA==
X-Gm-Message-State: AOAM532iZuijyns0tc522PxMor8wm1nxq43ADIDrNGgl3krWv7TDvO3/ touVAVBw9ZX4qCilxtGN0wMpQOTDqwYY8ZTot7E=
X-Google-Smtp-Source: ABdhPJxWK13lrMx8VvIZFol0Az5yl+J8p0CNwFVWN5HnbIrFDqDuE9WA7GA1BVEILPuSS/aZ4tIZvfD7iD0pR2ZHxes=
X-Received: by 2002:adf:fd91:: with SMTP id d17mr797411wrr.0.1614807821441; Wed, 03 Mar 2021 13:43:41 -0800 (PST)
MIME-Version: 1.0
References: <463c848c-d171-7184-d65b-9ea95438d442@alum.mit.edu> <CANKS34fmzw3TNJVJhkUQvWv+EM2SCuEZcp7JgyZbN-p7iqMxfg@mail.gmail.com> <bfd34ef4-d081-c1e9-9985-da1e1b794c58@alvestrand.no>
In-Reply-To: <bfd34ef4-d081-c1e9-9985-da1e1b794c58@alvestrand.no>
From: Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>
Date: Wed, 03 Mar 2021 22:43:31 +0100
Message-ID: <CA+ag07budQbg1qKa+rR939sQ2CP2aAmnd8jDL93e1_B=QuonQA@mail.gmail.com>
To: Harald Alvestrand <harald@alvestrand.no>
Cc: mmusic@ietf.org
Content-Type: multipart/alternative; boundary="00000000000093df9e05bca8be6f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/iWfWd1A4stSohYXa2HmKy6WfC8A>
Subject: Re: [MMUSIC] Finding a max length of "a=mid" attribute
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, 03 Mar 2021 21:43:47 -0000

If length is >16, shouldn't the 2 byte header extension be used instead?
that would allow mid values up to 256 bytes.

Best regards
Sergio


El mié., 3 mar. 2021 22:40, Harald Alvestrand <harald@alvestrand.no>
escribió:

>
> On 3/3/21 4:06 PM, Nils Ohlmeier wrote:
> >> Am 3/3/21 um 06:31 schrieb Paul Kyzivat <pkyzivat@alum.mit.edu>:
> >>
> >> On 3/3/21 3:51 AM, Harald Alvestrand wrote:
> >>> I'm searching for the source of a max length limit on the "a=mid"
> attribute.
> >>> I couldn't find it in RFC 5888 (grouping framework) or RFC 8843
> (BUNDLE).
> >>> Does anyone remember where it's supposed to be?
> >>> (I have code that will insist that it should be 16 bytes or less, but
> I'm trying to verify that this is the correct limit.)
> >> Its defined as a token (from RFC4566/8866). And that is:
> >>
> >>   token = 1*(token-char)
> >>
> >> There is no upper limit on the length. You can't impose a limit for
> implementation convenience. But practically speaking it is limited by the
> length of the message body that contains it, so you could code using an
> offset+length into the message buffer.
> > While the SDP side might be able to handle really long MID values I
> > doubt the RTP header extension allow or support that. Maybe your 16
> > byte length limitation comes from the RTP side?
>
> I found that it is impossible to encode an 1-byte RTP header extension
> longer than 16 bytes (the length is a 4-bit field with a bias value of
> 1). So in practice, it's an RTP restriction.
>
> I think Postel once advised that one should always have length limits -
> "if you don't have a length limit, you just have an implementation
> defined limit, and that's worse".
>
> So the next question (now that we've settled that the standards don't
> impose one) is: Should the standards specify a limit?
>
> And the third question: if asked to handle a BUNDLEd connection where
> the MID is > 16 bytes, is it reasonable to just ignore the over-long MID
> value?
>
>
>
>
> >
> > Best
> >    Nils
> >
> > _______________________________________________
> > 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
>