I'm not very comfortable with the appeal text in section 3.4. There
isn't a way to overturn decisions and there is no way to appeal
decisions because the wrong decision was made.
I understand why the current text is there. I understand there are
significant concerns about having either of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Leslie Daigle wrote:
|
| Well, the choice to put this on the ietf-discuss list was deliberate:
| including making sure that a reasonable cross section of the IETF
| would see the discussion. It's not at all clear that such a cross
| section would
Leif Johansson wrote:
Leslie Daigle wrote:
|
| Well, the choice to put this on the ietf-discuss list was deliberate:
| including making sure that a reasonable cross section of the IETF
| would see the discussion. It's not at all clear that such a cross
| section would bother to subscribe to a
Hello Joe,
I'm not the IETF, and I'm not telling anyone what to do,
but I _hope_ the discussion remains on the IETF list.
Regards,
Charlie P.
Joe Touch wrote:
It's unfortunate we don't respect the wishes of the IETF, rather than
telling them what's good for them. IMO, the IETF _is_ the
On Thu December 9 2004 12:23, [EMAIL PROTECTED] wrote:
New Last Call: 'Tags for Identifying Languages' to BCP
Date: 2004-12-08 17:56
From: The IESG [EMAIL PROTECTED]
To: IETF-Announce [EMAIL PROTECTED]
Reply to: [EMAIL PROTECTED]
The IESG has been considering
- 'Tags for
You're missing the point. The topic is important enough to have its own
list, to make sure it stands out from the rash of 2-3 day hot topics that
tend to clutter the list. As it stands I can't filter this traffic (which
I'm tracking) from the run of the mill IETF traffic which I more times
On Fri, 10 Dec 2004 14:46:52 EST, Bruce Lilly said:
Accessibility has not been a problem for this implementor (who,
incidentally, was unaware of this draft until the New
Last Call). ISO 639 language code lists are readily available in
HTML-ized English and French via
--On Wednesday, 08 December, 2004 14:21 +0100 Harald Tveit
Alvestrand [EMAIL PROTECTED] wrote:
--On 8. desember 2004 14:00 +0100 Wijnen, Bert (Bert)
[EMAIL PROTECTED] wrote:
How about
Once funds or in-kind donations have been credited to the
IETF accounts, they shall be
Harald,
This is purely a procedural question, but my interpretation of
the note below and the general support your suggestion has
gotten is that the document that is actually being last-called
is not draft-ietf-iasa-bcp-02.txt, as identified in the Last
Call posted yesterday afternoon, but a
RE: New Last Call: 'Tags for Identifying Languages' to BCP
Date: 2004-12-10 16:37
From: Peter Constable [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Bruce Lilly's message makes several inaccurate statements against the
proposed draft, and misrepresents some of the changes being made. My
RE: New Last Call: 'Tags for Identifying Languages' to BCP
Date: 2004-12-10 20:03
From: Peter Constable [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
Resuming my comments:
Specifically, the draft allows, and RFC 3066 disallows:
subtags more than 8 octets in
Simon == Simon Josefsson [EMAIL PROTECTED] writes:
Simon [EMAIL PROTECTED] (scott bradner) writes:
For IDN, I want to be able to extract the tables from RFC 3454
and use them in my implementation.
For Kerberos, I want to be able to use the ASN.1 schema in my
Bert,
I'm trying to catch up on all of this after nearly two weeks in
which it was impossible to track these various threads. Now it
is merely a hard untangling process.
If you are going to use words equivalent to irrevocable, in
either this context, the ISOC payment one noted by Bernard, or
Lemonade 61.5 Interim Meeting
Location
Oracle, Redwood Shores, CA.
250 Oracle Pkwy
Redwood City, CA 94065-1668
Date
January 19-20, 2005
Start on 1pm Wednesday
Likely finish by noon on Thursday.
Agenda (Draft)
==
- media conversion
- CHANNEL
- quick reconnect
- LEMONADE
A new Request for Comments is now available in online RFC libraries.
RFC 3944
Title: H.350 Directory Services
Author(s): T. Johnson, S. Okubo, S. Campos
Status: Informational
Date: December 2004
Mailbox:[EMAIL PROTECTED],
15 matches
Mail list logo
