Hi,
My reading of this thread of comments is that there is no reason to
change anything regarding the document. I will therefore progress this
document towards approval.
Regards
Magnus Westerlund
Brian E Carpenter skrev:
> On 2007-10-05 05:38, ken carlberg wrote:
>>
>>> I don't recall when was
On 15-okt-2007, at 18:28, Hallam-Baker, Phillip wrote:
I think that whole conversation is missing the point. While one
conference with one and a half thousand participants has a
significant carbon footprint the more significant issue is the net
impact of Internet technology. We can do far m
> > i'm aware of that line, but that does not really meet my observations.
>
> You asked that we revise the RFC to be compatible with POSIX.
> I observed that the RFC is not incompatible with POSIX. Now you
> are asserting that isn't what you were really asking?
>
> > if the above POSIX
Douglas Otis wrote:
>> In theory IANA could publish one _spf.arpa "v=spf1 mx a -all"
>> record, and everybody could use it with "v=spf1 redirect=_spf.arpa".
>> That one SPF record can (kind of) reference an unlimited number of
>> MX records doesn't depend on SPF's local-part macro.
> This
Pete,
Thanks , we are reviewing to see if the example reflects existing
implementations
Roni Even
> -Original Message-
> From: Pete Cordell [mailto:[EMAIL PROTECTED]
> Sent: Monday, October 08, 2007 4:22 PM
> To: ietf@ietf.org
> Cc: [EMAIL PROTECTED]; Even, Roni; [EMAIL PROTECTED]
> Subje
[EMAIL PROTECTED] wrote:
Paul Hoffman wrote:
2) For IKEv1/IKEv2, the document should explicitly specify how
ECC points are converted to octet strings (for KE payloads
and resulting shared secret value). Currently, there are at
least three incompatible options (RFC 4753, RFC 2409, and
draft-ietf
> i am under impression that "may include " clause can
> lead to portability issues in applications - some application writers
> will include only and it will compile fine on some
> platforms, and not on some other platforms.
Header pollution definitely makes it easier to
The IAOC and the Internet Society are very pleased to announce the
addition of a new Host to the long list of companies and organizations
that have supported the IETF for more than 20 years.
Google will be tbe the Host for IETF 73 in Minneapolis and has stepped
up to be the Welcome Reception S
On Oct 16, 2007, at 5:00 AM, Frank Ellermann wrote:
Douglas Otis wrote:
Do you expect everyone to use inbound servers to send?
No. Of course I'd expect that mail to to the IP of an
MTA talking to an MX I care about works. BTW, it would be nice if
only the MXs of the envelope sender a
