Bruce Lilly wrote:
*
* The problem is that 1id-guidelines appears many places; there is one
* version (and, yes, I mean the content of the various documents
* differs; these are not merely mirrors) on the ISI.EDU ftp site in the
* in-notes directory (where the RFCs live), another on
On 15 Mar 2005, at 21:25, The IESG wrote:
The IESG has received a request from an individual submitter to
consider the following document:
- 'Media Type Specifications and Registration Procedures '
draft-freed-media-type-reg-02.txt as a BCP
The IESG plans to make a decision in the next few
On 15 Mar 2005, at 21:25, The IESG wrote:
The IESG has received a request from an individual submitter to
consider the following document:
- 'Media Type Specifications and Registration Procedures '
draft-freed-media-type-reg-02.txt as a BCP
The IESG plans to make a decision in the next
Questions on IMS should probably be directed towards 3gpp mailers, since
that it is where it is being standardized. For SIP questions, you should
direct your queries to sip-implementors@cs.columbia.edu, which is where
general implementation help and QA takes place. For issues related to
sip
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of [EMAIL PROTECTED]
Sent: Tuesday, April 12, 2005 12:57 PM
To: Colin Perkins
Cc: iesg@ietf.org; ietf@ietf.org
Subject: Re: Last Call: 'Media Type Specifications and
Registration Procedures' to BCP
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of [EMAIL PROTECTED]
Sent: Tuesday, April 12, 2005 12:57 PM
To: Colin Perkins
Cc: iesg@ietf.org; ietf@ietf.org
Subject: Re: Last Call: 'Media Type Specifications and
Registration Procedures' to
On 12 Apr 2005, at 18:30, [EMAIL PROTECTED] wrote:
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of [EMAIL PROTECTED]
Sent: Tuesday, April 12, 2005 12:57 PM
To: Colin Perkins
Cc: iesg@ietf.org; ietf@ietf.org
Subject: Re: Last Call: 'Media Type
On 12 Apr 2005, at 17:57, [EMAIL PROTECTED] wrote:
...
The rules for display of text media types assume that such types are,
to
some extent, readable without special purpose viewing software. This
is
certainly true for most types, but some existing types have
restrictions
on their use which are
Date: 2005-04-12 11:58
From: Colin Perkins [EMAIL PROTECTED]
I have reviewed draft-freed-media-type-reg-03.txt, and have a number of
comments intended to align the registration procedures with the current
practice defined RFC 3555. These primarily arise due to the widespread
use
of
On Fri, 8 Apr 2005, Scott W Brim wrote:
On 4/7/2005 10:36, Brian E Carpenter allegedly wrote:
Regardless of the interesting side-discussion about 'voting',
what the toy shows after about a day is:
prefer nroff: 8
prefer xml: 37
neither: 9
I wonder how many of those have
On 12 Apr 2005, at 19:45, Bruce Lilly wrote:
Date: 2005-04-12 11:58
From: Colin Perkins [EMAIL PROTECTED]
I have reviewed draft-freed-media-type-reg-03.txt, and have a number
of
comments intended to align the registration procedures with the
current
practice defined RFC 3555. These primarily
Date:Tue, 12 Apr 2005 19:03:03 +0100
From:Colin Perkins [EMAIL PROTECTED]
Message-ID: [EMAIL PROTECTED]
| Sure, but if the display agent is unaware of the restrictions, it won't
| ever be able to receive the media data. The example I have in mind in
|
On 12 Apr 2005, at 20:51, Robert Elz wrote:
Date:Tue, 12 Apr 2005 19:03:03 +0100
From:Colin Perkins [EMAIL PROTECTED]
Message-ID: [EMAIL PROTECTED]
| Sure, but if the display agent is unaware of the restrictions, it
won't
| ever be able to receive the media data.
Date:Tue, 12 Apr 2005 21:20:28 +0100
From:Colin Perkins [EMAIL PROTECTED]
Message-ID: [EMAIL PROTECTED]
| RFC 3555 allows media types to be defined for transport only via RTP.
| The majority of these registrations are under the audio and video
| top-level
Reading through the comments on voting I am struck by a difference in
the approach people take to what the IETF is for.
* One school of thought is that the reason for starting a working group
is to arrive at a better engineering outcome than is possible
independently.
* Another school of thought
On 12 Apr 2005, at 23:04, Robert Elz wrote:
Date:Tue, 12 Apr 2005 21:20:28 +0100
From:Colin Perkins [EMAIL PROTECTED]
Message-ID: [EMAIL PROTECTED]
| RFC 3555 allows media types to be defined for transport only via
RTP.
| The majority of these registrations are
On Wed, 13 Apr 2005, Robert Elz wrote:
Date:Tue, 12 Apr 2005 21:20:28 +0100
From:Colin Perkins [EMAIL PROTECTED]
Message-ID: [EMAIL PROTECTED]
| RFC 3555 allows media types to be defined for transport only via RTP.
| The majority of these registrations are
Date:Tue, 12 Apr 2005 21:20:28 +0100
From:Colin Perkins [EMAIL PROTECTED]
Message-ID: [EMAIL PROTECTED]
| RFC 3555 allows media types to be defined for transport only via RTP.
| The majority of these registrations are under the audio and video
| top-level
Dear Phillip,
There is a motivation you forgot. It is to take control of your particular
part of the world in using the IANA to lodge your vision and/or your name.
Like a micro TLD Manager.
This goes beyond impressing your commercial/political relations in having
signed an RFC in their area -
Dear Phillip,
There is a motivation you forgot. It is to take control of
your particular
part of the world in using the IANA to lodge your vision
and/or your name.
Like a micro TLD Manager.
Folk greatly overestimate the effectiveness of IANA as a control point.
Why does the IESG
The Voice Profile for Internet Mail WG (vpim) in the Applications Area
has concluded.
The IESG contact persons are Ted Hardie and Scott Hollenbeck.
The mailing list will remain active.
___
IETF-Announce mailing list
IETF-Announce@ietf.org
The IESG has approved the following documents:
- 'Generalized Multi-Protocol Label Switching (GMPLS) Recovery Functional
Specification '
draft-ietf-ccamp-gmpls-recovery-functional-04.txt as a Proposed Standard
- 'Recovery (Protection and Restoration) Terminology for Generalized
22 matches
Mail list logo
