Re: [AVTCORE] Possible Erratta in RFC2326 relating to 'source' parameter.
worley@ariadne.com (Dale R. Worley) Tue, 30 December 2014 20:35 UTC
Return-Path: <worley@alum.mit.edu>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D7BB11A6F04 for <avt@ietfa.amsl.com>; Tue, 30 Dec 2014 12:35:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.465
X-Spam-Level: *
X-Spam-Status: No, score=1.465 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=no
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 IFtzkTqmZWC0 for <avt@ietfa.amsl.com>; Tue, 30 Dec 2014 12:35:56 -0800 (PST)
Received: from resqmta-po-05v.sys.comcast.net (resqmta-po-05v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:164]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 921061A6F0E for <avt@ietf.org>; Tue, 30 Dec 2014 12:35:56 -0800 (PST)
Received: from resomta-po-06v.sys.comcast.net ([96.114.154.230]) by resqmta-po-05v.sys.comcast.net with comcast id Zwak1p0094yXVJQ01wbwCU; Tue, 30 Dec 2014 20:35:56 +0000
Received: from hobgoblin.ariadne.com ([70.42.157.71]) by resomta-po-06v.sys.comcast.net with comcast id ZwZg1p00V1YiR5A01wZkWz; Tue, 30 Dec 2014 20:33:54 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id sBUKXwE0022477; Tue, 30 Dec 2014 15:33:58 -0500
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id sBUKXwK9022474; Tue, 30 Dec 2014 15:33:58 -0500
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com
To: Julius Friedman <juliusfriedman@gmail.com>
In-Reply-To: <CACFvNHUz=VfYj+nz_WXbEvmzGvmNUiocCM1doPoPNJH+Qsemow@mail.gmail.com> (juliusfriedman@gmail.com)
Sender: worley@ariadne.com
Date: Tue, 30 Dec 2014 15:33:58 -0500
Message-ID: <87a924c1xl.fsf@hobgoblin.ariadne.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1419971756; bh=BsZFdfHV7lRqLrVPUuvshFOIKgYAYN18872J7Uxx+8E=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID; b=RAfTxLG7rqDiqvnHsM+x+RlHaFeeb4pw/IgGEeNI9S8Deh2Io86FcK7p6u10JbeE6 7QozjY4CGW8/ZOyJziBuEfLNTE5xVi8mpgaXtaEV4n2KBk3fl5OiinIOMZpTnvXkli 5vP8LyPKwGQyJ+DzM1GUOjgaCi6N/61aDTiZ2fsmtSmU0TX097LSOLUsFgZLeFGBE2 xSUWBIojGgP3l5cJQVEEFx6DjLc9UqDrAhtOxR/vWTU6HVzCGP7AGQypvK8p7Dh3AT ssRWgm+BEFM30UOXEuWPiDnmWJ3IqcLOgeTrZkogn3q6CjFuZbX1XaGkO5gVr5Dmcc YapJeUrvmtKww==
Archived-At: http://mailarchive.ietf.org/arch/msg/avt/vHiD80XqSX5KX1K9akXqumRAfX0
Cc: avt@ietf.org, mmusic@ietf.org
Subject: Re: [AVTCORE] Possible Erratta in RFC2326 relating to 'source' parameter.
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Dec 2014 20:35:58 -0000
Julius Friedman <juliusfriedman@gmail.com> writes: > Transport = "Transport" ":" > 1\#transport-spec In a few places, RFC 2326 seems to use "\#" in place of "#". There doesn't seem to be any documentation for this. There seems to be other peculiar punctuation as well, including "\$" and "$'$". > Since 'source' is not listed I don't know the syntax, I assumed it to > be an "IPAddress" however the text sates "address" so I imagine if I > found a 'source=1.2.3.4:1554' that would be valid however I want to > make sure since there isn't any syntax specified in the RFC. It's not clear to me that there *is* a "source=" parameter for the Transport header. Yes, there is prose describing source as a datum, but there's no BNF for a corresponding parameter, and a quick search doesn't turn up any instance of "Transport: ...source=..." in any RFC or I-D. However, "source=" is shown in http://heim.ifi.uio.no/~meccano/reflector/smallclient.html > Also I would wonder is there any restriction on specifying a port or > address range also ? e.g. 'source=1.2.3.4/321202/2' Well, I see "parameter = [...] ";" "destination" [ "=" address ]", and address = host host = <A legal Internet host domain name of IP address (in dotted decimal form), as defined by Section 2.1 of RFC 1123 \cite{rfc1123}> so it looks like <address> cannot specifiy an address range or a port. I'd expect the port to be specified by the "client_port" and "server_port" parameters. (BTW, it looks to me like the first "of" in the definition of <host> should be "or".) > I believe there was a similar issue with Rtp-Info headers which was > fixed in 'biz' however this among other issues were not addressed and > I am wondering if any other updates will be made to this RFC before > 2.0 Draft is finalized. An RFC is never "updated", although it can be obsoleted by a later RFC that entirely replaces it. Dale
- [AVTCORE] Possible Erratta in RFC2326 relating to… Julius Friedman
- Re: [AVTCORE] Possible Erratta in RFC2326 relatin… Dale R. Worley
- Re: [AVTCORE] Possible Erratta in RFC2326 relatin… Julius Friedman
- Re: [AVTCORE] Possible Erratta in RFC2326 relatin… Magnus Westerlund