On 23 Aug 2013 04:22, l.w...@surrey.ac.uk wrote:
LC should not be treated as a right of passage, to test the patience of
folks who have developed a document.
rite?
Right - right or rite?
Lloyd Wood
http://sat-net.com/L.Wood/
On 08/22/2013 07:18 PM, John Levine wrote:
In article 5215cd8d.3080...@sidn.nl you write:
So what makes you think the above 4 points will not be a problem for the
next protocol that comes along and needs (apex) RR data? And the one
after that?
SPF is ten years old now. It would be helpful
On Aug 22, 2013, at 21:23, Barry Leiba barryle...@computer.org wrote:
Most Excellent(tm)
shepherd report:
https://datatracker.ietf.org/doc/draft-ietf-spfbis-4408bis/shepherdwriteup/
(This may not have helped much in this case, but:)
Why is it that IETF last-calls do not contain a direct
Announce Huawei Host Vancouver
The IAOC is pleased to announce that Huawei will be the Host for IETF 88 in
Vancouver.
Huawei has been a long time supporter of the IETF through its participation and
sponsorships
at IETF meetings, but this is their first time as the Host of an IETF meeting.
SPF is ten years old now. It would be helpful if you could give us a
list of other protocols that have had a similar issue with a TXT
record at the apex during the past decade.
I don't know of any (at least ones that are used in the global dns
namespace), and I would like to still not know of
The URL below is missing letter g in the word meeting.
http://www.ietf.org/meetin/88/hotel.html
-Original Message-
From: recentattendees-boun...@ietf.org
[mailto:recentattendees-boun...@ietf.org] On Behalf Of IETF Secretariat
Sent: Friday, August 23, 2013 10:26 AM
To:
Hi,
I've taken a look at the current version of the draft and I think it is
in good shape.
I have a couple of comments:
- I think it might be useful to include an additional NR
Code for obtaining Updated Access Network Identifier (ANI) parameters.
The LMA would send a UPN message to the MAG
The -07 version is also ready for publication as an Informational RFC
Thanks,
--David
-Original Message-
From: gen-art-boun...@ietf.org [mailto:gen-art-boun...@ietf.org] On Behalf Of
Black, David
Sent: Monday, July 29, 2013 7:20 AM
To: ldun...@huawei.com; Donald Eastlake;
Hi David,
Thank you for the review. Your time and comments are appreciated!
comments/questions inline.
Eric
On Aug 17, 2013, at 9:18 , Black, David david.bl...@emc.com wrote:
I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
Hi Carlos,
Thanks for your review comments. Please see inline.
On 8/22/13 6:28 PM, Carlos Jesús Bernardos Cano c...@it.uc3m.es wrote:
Hi,
I've taken a look at the current version of the draft and I think it is
in good shape.
I have a couple of comments:
- I think it might be useful to
Andras Salamon wrote:
On Thu, Aug 22, 2013 at 11:53:29PM -, John Levine wrote:
If you think it's important to move it to full standard, why don't you
do somthing about it? A quick look suggests that 3597 meets the
requirements in sec 2.2 of RFC 6410 I wouldn't think that it'd be hard
to
Begin forwarded message:
Resent-From: bmann...@vacation.karoshi.com
From: bmann...@vacation.karoshi.com
Subject: Re: [dnsext] SPF isn't going to change, was Deprecating SPF
Date: August 23, 2013 10:03:26 PDT
Resent-To: bmann...@isi.edu
To: John Levine jo...@taugh.com
Cc: dns...@ietf.org
and the hotel is fully booked….
/bill
On 23August2013Friday, at 6:36, IETF Secretariat wrote:
88th IETF Meeting
Vancouver, BC, Canada
November 3-8, 2013
Host: Huawei
Meeting venue: Hyatt Regency Vancouver:
http://vancouver.hyatt.com/en/hotel/home.html
Register online at:
Nobody has argued that SPF usage is zero, and the reasons for
deprecating SPF have been described repeatedly here and on the ietf
list, so this exercise seems fairly pointless.
the reasons for not deprecating SPF have been described here
and on the ietf list repeatedly ... yet
On Thu, Aug 22, 2013 at 11:12 PM, Dave Crocker d...@dcrocker.net wrote:
In pragmatic terms, the current operational model for a LC (and IESG)
review tends to enforce no rules or limits to what can be challenged or
suggested, while simultaneously expecting those who have been doing the
work to
In article b4828b8f-b900-4dc1-ad3e-7e3044fb8...@isi.edu you write:
and the hotel is fully booked�.
Not if you use the link on the meeting hotel page.
http://www.ietf.org/meeting/88/hotel.html
R's,
John
On 23 Aug 2013, at 18:49, manning bill bmann...@isi.edu wrote:
and the hotel is fully booked….
I guess it got fixed Bill, though I only booked for the meeting week itself.
tim
/bill
On 23August2013Friday, at 6:36, IETF Secretariat wrote:
88th IETF Meeting
Vancouver, BC, Canada
Hello,
This message has a Bcc to an IETF participant.
In my write-up for the Responsible Area Director I mentioned that:
There was an intermediate conclusion about the topic of whether the SPF
protocol should use the SPF RRTYPE or the TXT resource record. It was
followed by an
On 8/23/2013 11:06 AM, Scott Brim wrote:
We don't have to be like the ones we all know who sneer at anyone
presuming to get in the way of their code going into production.
Since this is such a fundamental point, I'm sending this reply to emphasize:
The concern I expressed had nothing at
On 23August2013Friday, at 11:04, John Levine wrote:
Nobody has argued that SPF usage is zero, and the reasons for
deprecating SPF have been described repeatedly here and on the ietf
list, so this exercise seems fairly pointless.
the reasons for not deprecating SPF have been described
The SPFbis document improperly conflates DNS terminology with identical terms
invented by this document. Examples are terms used to describe mechanisms
having the same identifier differentiated between mechanisms and DNS resource
records by using lower and upper case respectively. References
Dave Crocker wrote:
On 8/23/2013 11:06 AM, Scott Brim wrote:
We don't have to be like the ones we all know who sneer at anyone
presuming to get in the way of their code going into production.
Since this is such a fundamental point, I'm sending this reply to
emphasize:
The concern I
Hi Dave,
I read the messages on this thread. I suggested to the participant
to comment. I am okay with the comments which were made. I had an
off-list exchange before the message that generated the other
thread. The exchange was not antagonistic.
Some people read please read the
On Fri, Aug 23, 2013 at 3:46 PM, Dave Crocker d...@dcrocker.net wrote:
On 8/23/2013 11:06 AM, Scott Brim wrote:
We don't have to be like the ones we all know who sneer at anyone
presuming to get in the way of their code going into production.
Since this is such a fundamental point, I'm
88th IETF Meeting
Vancouver, BC, Canada
November 3-8, 2013
Host: Huawei
Meeting venue: Hyatt Regency Vancouver:
http://vancouver.hyatt.com/en/hotel/home.html
Register online at: http://www.ietf.org/meetings/88/
1. Registration
2. Visas Letters of Invitation
3. Accommodations
4. Companion
Announce Huawei Host Vancouver
The IAOC is pleased to announce that Huawei will be the Host for IETF 88 in
Vancouver.
Huawei has been a long time supporter of the IETF through its participation and
sponsorships
at IETF meetings, but this is their first time as the Host of an IETF meeting.
A new IETF non-working group email list has been created.
List address: pn...@ietf.org
Archive: http://www.ietf.org/mail-archive/web/pntaw/
To subscribe: https://www.ietf.org/mailman/listinfo/pntaw
Purpose: This mailing list will discuss how webrtc clients, proxies, NATs and
TURN servers
A new Request for Comments is now available in online RFC libraries.
RFC 7020
Title: The Internet Numbers Registry System
Author: R. Housley, J. Curran,
G. Huston, D. Conrad
Status: Informational
Stream: IETF
28 matches
Mail list logo
