Displaying 20 results from an estimated 22 matches for "bradner".
Did you mean:
bradler
2001 Feb 25
0
RTP Payload for Vorbis Audio: draft-moffitt-vorbis-rtp-00.txt
...5 Open Issues
Some of these are discussed in RFC2736, in particular the need for "Out of
band signalling" of codec parameters.
6 Security Considerations
Spelling error "Becase" -> "Because"
8 References:
Your reference to RFC2119 of 1 Introduction got lost.
[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", RFC 2119, BCP 14, March 1997.
[1] in 6 Security Considerations will then be [2]:
[2] Schulzrinne, H., Casner, S., Frederick, R., and V. Jacobson,
"RTP: A transport protocol for real-time applications,&qu...
2003 Feb 11
1
RFC-to-be: <draft-walleij-ogg-mediatype-08.txt> (fwd)
...used in applications. The
IANA has assigned it in their namespace, so start adding it at will.
See mail below.
Linus
---------- Forwarded message ----------
Date: Mon, 10 Feb 2003 12:23:47 -0800
From: IANA <iana@iana.org>
To: triad@df.lth.se
Cc: Allison Mankin <mankin@psg.com>, Scott Bradner <sob@harvard.edu>
Subject: RFC-to-be: <draft-walleij-ogg-mediatype-08.txt>
Authors,
We have completed the IANA Actions for RFC-to-be
<draft-walleij-ogg-mediatype-08.txt>.
Please see the following for the registration of the
MIME Media Type application/ogg:
<http://www.iana....
2004 Aug 06
1
RTP Profile Revision
...ng cost of
the authentication itself may be too high. In a multicast
environment, pruning of specific sources may be implemented in future
versions of IGMP [7] and in multicast routing protocols to allow a
receiver to select which sources are allowed to reach it.
7. References
1. Bradner, S., "The Internet Standards Process -- Revision 3", BCP
9, RFC 2026, October 1996.
2. ITU-T Recommendation G.722.1, available online from the ITU
bookstore at http://www.itu.int.
3. Schulzrinne, H., Casner, S., Frederick, R. and V. Jacobson, "RTP:
A Transpo...
2004 Aug 06
0
First draft for Speex RTP profile - Please send your comments
...of
the authentication itself may be too high. In a multicast
environment, pruning of specific sources may be implemented in future
versions of IGMP [7] and in multicast routing protocols to allow a
receiver to select which sources are allowed to reach it.
<p>7. References
1. Bradner, S., "The Internet Standards Process -- Revision 3", BCP
9, RFC 2026, October 1996.
2. ITU-T Recommendation G.722.1, available online from the ITU
bookstore at http://www.itu.int.
3. Schulzrinne, H., Casner, S., Frederick, R. and V. Jacobson, "RTP:
A Transpo...
2004 Aug 06
0
RTP Profile Revision v5
...tances a receiver may
be overloaded simply by the receipt of too many packets, either
desired or undesired. Network-layer authentication may be used to
discard packets from undesired sources, but the processing cost of
the authentication itself may be too high.
7. References
1. Bradner, S., "The Internet Standards Process -- Revision 3", BCP
9, RFC 2026, October 1996.
2. Schulzrinne, H., Casner, S., Frederick, R. and V. Jacobson, "RTP:
A Transport Protocol for real-time applications", RFC 1889,
January 1996. (Updated by a Work in Progres...
2004 Aug 06
0
Comments on New RTP Profile Document
...tances a receiver may
be overloaded simply by the receipt of too many packets, either
desired or undesired. Network-layer authentication may be used to
discard packets from undesired sources, but the processing cost of
the authentication itself may be too high.
8. References
1. Bradner, S., "The Internet Standards Process -- Revision 3", BCP
9, RFC 2026, October 1996.
2. Schulzrinne, H., Casner, S., Frederick, R. and V. Jacobson, "RTP:
A Transport Protocol for real-time applications", RFC 1889,
January 1996. (Updated by a Work in Progres...
2004 Aug 06
3
Updated Speex RTP Internet Draft
...ay
be overloaded simply by the receipt of too many packets, either
desired or undesired. Network-layer authentication may be used to
discard packets from undesired sources, but the processing cost of
the authentication itself may be too high.
<p>8. Normative References
1. Bradner, S., "The Internet Standards Process -- Revision 3", BCP
9, RFC 2026, October 1996.
2. Schulzrinne, H., Casner, S., Frederick, R. and V. Jacobson, "RTP:
A Transport Protocol for real-time applications", RFC 1889,
January 1996.
3. Freed, N. and N. B...
2004 Aug 06
1
linux.conf.au and streaming (was Re: patch for libspeex)
...tances a receiver may
be overloaded simply by the receipt of too many packets, either
desired or undesired. Network-layer authentication may be used to
discard packets from undesired sources, but the processing cost of
the authentication itself may be too high.
8. References
1. Bradner, S., "The Internet Standards Process -- Revision 3", BCP
9, RFC 2026, October 1996.
2. Schulzrinne, H., Casner, S., Frederick, R. and V. Jacobson, "RTP:
A Transport Protocol for real-time applications", RFC 1889,
January 1996. (Updated by a Work in Progres...
2004 Aug 06
0
draft-herlein-speex-rtp-profile-01
...ay
be overloaded simply by the receipt of too many packets, either
desired or undesired. Network-layer authentication may be used to
discard packets from undesired sources, but the processing cost of
the authentication itself may be too high.
<p>8. Normative References
1. Bradner, S., "The Internet Standards Process -- Revision 3", BCP
9, RFC 2026, October 1996.
2. Schulzrinne, H., Casner, S., Frederick, R. and V. Jacobson, "RTP:
A Transport Protocol for real-time applications", RFC 1889,
January 1996.
3. Freed, N. and N. B...
2004 Aug 06
0
Updated Speex RTP Internet Draft
...e receipt of too many packets, either
> desired or undesired. Network-layer authentication may be used to
> discard packets from undesired sources, but the processing cost of
> the authentication itself may be too high.
>
>
> 8. Normative References
>
> 1. Bradner, S., "The Internet Standards Process -- Revision 3", BCP
> 9, RFC 2026, October 1996.
>
> 2. Schulzrinne, H., Casner, S., Frederick, R. and V. Jacobson, "RTP:
> A Transport Protocol for real-time applications", RFC 1889,
> January 1996.
&...
2004 Aug 06
5
linux.conf.au and streaming (was Re: patch for libspeex)
On Tue, Dec 17, 2002 at 11:55:21PM -0800, Greg Herlein wrote:
> If such a thing happens, discussion of the RTP profile draft
> would be most welcome - please get responses back to the
> list!
Now, if this were finalised before the conference then we could do
a demo and use it for broadcasting the lectures streams around the
world... What is currently the best way of doing this?
I'm
2008 Dec 23
6
Security advice, please
My LAN is behind a Netgear router, which does NAT. On the CentOS server I
have fail2ban running. This morning my router reported 3 different IPs
attempting to send UDP packets to port 38950, Since each address is only seen
4-5 times, I presume that fail2ban took over after that.
GRC reports that ports are stealthed (port 143 was open, but is now closed),
but then:
Unsolicited Packets:
2016 May 26
3
Channel Mapping Family for Ambisonics
...| 254 | This Document Section 3.1 |
+-------+---------------------------+
6. Acknowledgments
Thanks to Timothy Terriberry and Marcin Gorzel for their guidance and
valuable contributions to this document.
7. References
7.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>.
[RFC6716] Valin, JM., Vos, K., and T. Terriberry, "Definition of the...
2016 May 16
2
Channel Mapping Family for Ambisonics
Tim,
Would you mind giving me a more specific example of the sort of document
that you think this should look like? I'd like to write up something that
is somewhat final.
On Mon, May 2, 2016 at 9:30 PM, Michael Graczyk <mgraczyk at google.com> wrote:
> On Fri, Apr 29, 2016 at 4:32 PM, Timothy B. Terriberry
> <tterribe at xiph.org> wrote:
> > As a general point,
2016 May 27
2
Channel Mapping Family for Ambisonics
...| 2 | This Document Section 3.1 |
+-------+---------------------------+
6. Acknowledgments
Thanks to Timothy Terriberry and Marcin Gorzel for their guidance and
valuable contributions to this document.
7. References
7.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>.
[RFC6716] Valin, JM., Vos, K., and T. Terriberry, "Definition of the...
2007 Jun 07
1
draft-ietf-avt-rtp-speex-01.txt
...>
>
>
>
>
>
>
> Herlein, et al. Expires December 7, 2007 [Page 17]
>
> Internet-Draft Speex June 2007
>
>
> 9. References
>
> 9.1. Normative References
>
> [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
> Requirement Levels", BCP 14, RFC 2119, March 1997.
>
> [RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V.
> Jacobson, "RTP: A Transport Protocol for Real-Time
> Appli...
2007 May 29
0
draft-ietf-avt-rtp-speex-01.txt
...is document; Simon Morlat, Roger
Hardiman, Phil Kerr.
Herlein, et al. Expires November 30, 2007 [Page 17]
Internet-Draft Speex May 2007
9. References
9.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V.
Jacobson, "RTP: A Transport Protocol for Real-Time
Applications", STD 64, RF...
2007 May 30
5
draft-ietf-avt-rtp-speex-01.txt
Do not forget to add the "Copying conditions" to the RFC.
Check http://wiki.debian.org/NonFreeIETFDocuments
That page contains a section titled "Template for RFC authors to
release additional rights". To follow that guideline a
section like the following should be added:
x. Copying conditions
The author(s) agree to grant third parties the irrevocable
right to
2007 Jun 07
0
draft-ietf-avt-rtp-speex-01.txt
...is document; Simon Morlat, Roger
Hardiman, Phil Kerr.
Herlein, et al. Expires December 7, 2007 [Page 17]
Internet-Draft Speex June 2007
9. References
9.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V.
Jacobson, "RTP: A Transport Protocol for Real-Time
Applications", STD 64, RF...
2007 May 15
4
draft-ietf-avt-rtp-speex-01.txt
...his document; Simon Morlat, Roger
Hardiman, Phil Kerr
Herlein, et al. Expires October 24, 2007 [Page 15]
Internet-Draft Speex April 2007
8. References
8.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V.
Jacobson, "RTP: A Transport Protocol for Real-Time
Applications", STD 64, RF...