Re: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02

2005-12-13 Thread Douglas Otis
On Mon, 2005-12-12 at 13:51 -0600, wayne wrote: Well, I can see coming back some day and trying to create an update to the SPF protocol. I can't see trying to change SPF version 1. The problem with SPF draft is there is no spf2.0/mfrom. This has little to do the IETF, but rather a

Re: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02

2005-12-13 Thread Frank Ellermann
Douglas Otis wrote: The problem with SPF draft is there is no spf2.0/mfrom. One week from draft-ietf-marid-mailfrom-00 to the termination of MARID was a bit short. And after that the next draft was again v=spf1 draft-lentczner-spf-00 (same author). Actually an emergency draft, because the

Re: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02

2005-12-13 Thread wayne
In [EMAIL PROTECTED] Frank Ellermann [EMAIL PROTECTED] writes: Whatever you think, but your complaints about the theoretical upper limit of DNS queries in an attack scenario resulted in some of the most interesting post-MARID changes (Wayne's I-Ds). This is bunk. The DoS limits that are in

Re: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02

2005-12-13 Thread Keith Moore
I have, in the past, argued to the IESG that I did not think the SPF I-D should be marked Experimental because I did not see it being an experiment. It has been out for 2 years now and it is far too widely deployed to make significant changes. Instead, I thought it should be standard track.

Re: Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02

2005-12-13 Thread Douglas Otis
On Dec 13, 2005, at 11:07 AM, wayne wrote: However, his complaints could not have possibly had any impact on the current limits in the SPF spec. The reduction to 111 DNS lookups is not a resounding impact with respect to this concern. Defending this sequential lookup requirement will

Reminder: Call for nominations: IAOC position selected by the IESG

2005-12-13 Thread IETF Chair
The IESG is making a call for volunteers for the IETF Administrative Oversight Committee (IAOC), as described in BCP 101 (RFC 4071) and the approved BCP draft-iab-iesg-iaoc-selection-03.txt. The IESG and the IAB each select one person for a two-year IAOC term in alternate years. This year, the

Last Call: 'PWE3 Frame Check Sequence Retention' to Proposed Standard

2005-12-13 Thread The IESG
The IESG has received a request from the Pseudo Wire Emulation Edge to Edge WG to consider the following document: - 'PWE3 Frame Check Sequence Retention ' draft-ietf-pwe3-fcs-retention-04.txt as a Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final

RFC 4119 on A Presence-based GEOPRIV Location Object Format

2005-12-13 Thread rfc-editor
A new Request for Comments is now available in online RFC libraries. RFC 4119 Title: A Presence-based GEOPRIV Location Object Format Author(s): J. Peterson Status: Standards Track Date: December 2005 Mailbox:[EMAIL PROTECTED]

RFC 4241 on A Model of IPv6/IPv4 Dual Stack Internet Access Service

2005-12-13 Thread rfc-editor
A new Request for Comments is now available in online RFC libraries. RFC 4241 Title: A Model of IPv6/IPv4 Dual Stack Internet Access Service Author(s): Y. Shirasaki, S. Miyakawa, T. Yamasaki, A. Takenouchi Status: