IETF Logo Mail Archive

Re: [MMUSIC] SCTP AppID

Martin Thomson <martin.thomson@gmail.com> Thu, 06 March 2014 14:14 UTC

Return-Path: <martin.thomson@gmail.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 445A01A036B for <mmusic@ietfa.amsl.com>; Thu, 6 Mar 2014 06:14:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 0ZusUxJAGVxA for <mmusic@ietfa.amsl.com>; Thu, 6 Mar 2014 06:14:36 -0800 (PST)
Received: from mail-we0-x234.google.com (mail-we0-x234.google.com [IPv6:2a00:1450:400c:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id 532931A0380 for <mmusic@ietf.org>; Thu, 6 Mar 2014 06:14:22 -0800 (PST)
Received: by mail-we0-f180.google.com with SMTP id p61so3137355wes.25 for <mmusic@ietf.org>; Thu, 06 Mar 2014 06:14:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=yCyfAuqbZXPpCWjD2Spo+t+yhanznKb5TqcUENXZCHM=; b=qaNiOdpTtKC02DShCeH+qWZknpxiV9DQGApYkjfNNKez8uDJmMyBLmL45OoCjBta8r K5Zh0TGOmQwZi3XsRaYh8+EeU2dJobeRulfKTUMOlnlShIN12ruOV/JsjtIrzwFCKhLQ YJM6jla+MU5XIhwrN1eYwAwGkua4WttZRzM6Q4KdrIR8lX1nTBMTWE7SincO8InmLaoT Z32PE6Z8shqLc9MQmFI8OZ58/F0nGB4zaegfbHkznSut6OGE1PS//VarCwcsC0s8k4nK I4QYPBi5/gdJ4eddA/ztDPawJWpm2+I/1YYr9jlPO6zg93kxqr8UZHow37Lb03v7/91z drlg==
MIME-Version: 1.0
X-Received: by 10.194.170.167 with SMTP id an7mr10435084wjc.39.1394115258028; Thu, 06 Mar 2014 06:14:18 -0800 (PST)
Received: by 10.227.10.196 with HTTP; Thu, 6 Mar 2014 06:14:17 -0800 (PST)
In-Reply-To: <C1D662DF-E3E3-45CD-991F-8090CD7130E0@ericsson.com>
References: <53185B8E.2070808@nteczone.com> <C8EB64C0-3140-477C-9373-BD36B4B1A64B@ericsson.com> <53187415.2000108@nteczone.com> <C1D662DF-E3E3-45CD-991F-8090CD7130E0@ericsson.com>
Date: Thu, 06 Mar 2014 14:14:17 +0000
Message-ID: <CABkgnnWOVf-72jeLbo74dbpxwhiYwgOjsfte2Cx3Voi_YRxdTg@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Salvatore Loreto <salvatore.loreto@ericsson.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/5PJwdrvmvpjL0jskxZo37PpwH6M
Cc: mmusic mailing list <mmusic@ietf.org>
Subject: Re: [MMUSIC] SCTP AppID
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Thu, 06 Mar 2014 14:14:38 -0000

On 6 March 2014 13:36, Salvatore Loreto <salvatore.loreto@ericsson.com> wrote:
> I understood Martin was only proposing to look at how ALPN defines and handles the registry
> and do something similar not using it. Am I wrong?

Yes, you are wrong.

My intent was to say that you should be using the registry in an
unadulterated form.

ALPN is being used now in a number of places to identify protocols.
We've more or less unilaterally decided in httpbis that this means the
entire protocol stack.  I'm thinking that the protocol we're
identifying here is the following stack of protocols:

Data channel protocol (the combination of the data chennel
establishment protocol and the use of the text and binary PPIDs).
SCTP
DTLS
UDP
IP

Yes, there are cases where there are other users, or protocols perched
on top of this tower.  Those could also be identified with an ALPN
identifier too, if they wanted to.

One such higher-level protocol is the combination of this glorious
protocol tower with SRTP.  That's another ALPN identifier.

v2.46.0 | Report a Bug | By Email | System Status