Hi,
Several drafts posted on the morning of Feb. 1 are returning '404 not found'
errors. These 5 were posted in sequence, at 10:36 AM PT:
http://www.ietf.org/internet-drafts/draft-bjorklund-netconf-yang-01.txt
http://www.ietf.org/internet-drafts/draft-ietf-ltans-ers-scvp-06.txt
I have been selected as the General Area Review Team (Gen-ART)
reviewer for this draft (for background on Gen-ART, please see
http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html).
Please resolve these comments along with any other Last Call
comments you may receive.
Document:
So there's something else besides key name that is used to identify
keys. Great, so that means these hashed key names are unnecessary. No
need to do HMAC-SHA256 to generate a random string, throw away 3/4 of
that result and come up with something that is unusable.
Let's get rid of this stuff
There is nothing in the document that says you must index keys only by
key id. I don't really understand the problem here, there is other
context associated with a key besides a name that can be used for
indexing. The key name provides a fixed length unique identifier for
the key. EAP
-Original Message-
From: Dan Harkins [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 05, 2008 12:23 PM
To: Joseph Salowey (jsalowey)
Cc: Dan Harkins; ietf@ietf.org; [EMAIL PROTECTED]
Subject: RE: [HOKEY] Last Call: draft-ietf-hokey-erx (EAP
Extensions for EAP
On 5 feb 2008, at 10:43, Iljitsch van Beijnum wrote:
So ietf.org needs one or more nameservers with records.
I need to study up on DNS tools, because it does...
But somehow I couldn't get at www.ietf.org running IPv6-only. Maybe
someone else can explain this?
I assume that others have come across this problem as well,
but I haven't seen anything mentioned about it on this list or the IETF
sites.
I receive over 500 non-spam emails every day (peaks can reach 1000).
These include emails from about 15 IETF lists,
about 25 other standardization lists,
Now that the root servers have IPv6 glue records, we're one step
closer to being able to successfully run IPv6-only for a bit in
Philadelphia. (What's the status of the preparations for that, by the
way? I'm still happy to volunteer.)
(Don't forget to download the new named.root file from
At 8:35 AM +0200 2/5/08, Yaakov Stein wrote:
Would it be possible to post information that would help here ?
What is constant and can be relied upon ?
The List-ID: mail header, RFC 2919. It should hopefully be on every
IETF mailing list, and should remain relatively* constant.
*Some changed
FYI, Richard Stiennon at ZDNet noticed that the root servers will be
IPv6-accessible and refers to it as the Birth of IPv6:
http://blogs.zdnet.com/threatchaos/?p=527
He was pointing over to the BBC article about this:
http://news.bbc.co.uk/1/hi/technology/7221758.stm
(I thought the
Yaakov Stein wrote:
What is constant and can be relied upon ?
List-Id is designed to be constant and reliable.
Two examples (this list and apps.discuss):
List-Id: IETF-Discussion ietf.ietf.org
List-Id: general discussion of application-layer protocols discuss.ietf.org
Frank
Yaakov Stein wrote:
Would it be possible to post information that would help here ?
What is constant and can be relied upon ?
The List-Id works pretty well for me, for example this IETF discussion,
announce, and ID announce mailing lists are filtered by procmail using:
:0:
* ^List-Id:
I can answer a few questions that will help.
AMS installed the default configuration of mailman and then
imported each mailing list's individual configuration file as
provided by NSS.
It should be the case now that all IETF hosted mailing lists are in
the domain ietf.org. The mail server
Hi,
On 2008-02-05 07:35 Yaakov Stein said the following:
I assume that others have come across this problem as well,
but I haven't seen anything mentioned about it on this list or the IETF
sites.
I receive over 500 non-spam emails every day (peaks can reach 1000).
These include emails
The IAOC and the Internet Society are very pleased to announce that
Alcatel-Lucent will be be the Host for IETF 72 in Dublin and has agreed
to be the Welcome Reception Sponsor as well. [www.alcatel-lucent.com]
Alcatel-Lucent is pleased to host the 72nd meeting of the IETF in
Dublin, Ireland.
Andy,
You need to report these things to [EMAIL PROTECTED]
Apparently there were some issues immediately after the cut-over
through part of Friday, 1 February. Based on reports received at
the time AMS addressed the issues, at least there have not been any
reports since last Friday.
The
2008/2/4 Dan York [EMAIL PROTECTED]:
FYI, Richard Stiennon at ZDNet noticed that the root servers will be
IPv6-accessible and refers to it as the Birth of IPv6:
http://blogs.zdnet.com/threatchaos/?p=527
He was pointing over to the BBC article about this:
In reading this draft (-09 version) I came up with a few questions and
comments:
Section 3 -
Section 3 is a bit confusing it seems that much of the text is section
3.1 (detailed description of exchanges) should go into section 3.0
because it seems that much of the process should be the same for
The IAOC and the Internet Society are very pleased to announce that
Alcatel-Lucent will be be the Host for IETF 72 in Dublin and has agreed to
be the Welcome Reception Sponsor as well. [www.alcatel-lucent.com]
Alcatel-Lucent is pleased to host the 72nd meeting of the IETF in
Dublin, Ireland.
19 matches
Mail list logo
