On 02/24/2012 01:24 AM, Roy T. Fielding wrote:
On Feb 23, 2012, at 5:18 PM, Tim Bray wrote:
On Thu, Feb 23, 2012 at 5:13 PM, Roy T. Fieldingfield...@gbiv.com wrote:
How many times do we have to do this before we declare insanity?
I don't care how much risk it adds to the HTTP charter. They
On Feb 24, 2012, at 4:54 AM, Stephen Farrell wrote:
Proposals for new HTTP authentication schemes are in scope.
How would a plan like the following look to folks:
- httpbis is chartered to include auth mechanism work as
per the above (or whatever text goes into the charter)
- that'll
On Fri, Feb 24, 2012 at 01:54:32PM +1100, Mark Andrews wrote:
In message 4f46bfdf.3070...@dougbarton.us, Doug Barton writes:
2782 was published 12 years ago this month. I suppose it can be
considered mature enough to deploy at this point? :)
+1000
Over in spfbis, people are arguing
On 24 feb 2012, at 16:38, Andrew Sullivan wrote:
Over in spfbis, people are arguing that the SPF RRTYPE should be
deprecated and abandoned in SPF because nobody uses it because of
practical difficulties in getting new RRTYPEs deployed. What makes us
think that the arguments in favour of SRV
Colleagues,
The IESG has observed very rough consensus in favor of the allocation proposed
in draft-weil-shared-transition-space-request. Therefore, the IESG will approve
the draft. In order to acknowledge dissenting opinions and clarify the IETF
position regarding IPv6, the IESG will attach
Joe,
There were two things that I referenced in response to your initial
review that you hadn't seen. More details on those below:
On Feb 17, 2012, at 5:47 PM, Joe Touch wrote:
INTERLEAVING- sec 7.7 says that the server MUST interleave
replies;
Joe,
I've edited the the email trail to try to concentrate on
the remaining open issues. I've also removed the two
issues that were included in the email I sent you an hour
or so ago, since I expect that they will be covered in
continuations of that thread.
To summarize, there are 3 issues
On Thu, Feb 23, 2012 at 05:23:45PM -0800, Paul Hoffman wrote:
If only it were that simple. If the answer is design an HTTP auth mechanism
that is better than Digest, then this is a tractable goal. If it is get
IETF consensus on that auth mechanism, then it isn't. The latter has proven
to be
--On Friday, February 24, 2012 16:58 +0100 Patrik Fältström
p...@frobbit.se wrote:
On 24 feb 2012, at 16:38, Andrew Sullivan wrote:
Over in spfbis, people are arguing that the SPF RRTYPE should
be deprecated and abandoned in SPF because nobody uses it
because of practical difficulties in
On Friday, February 24, 2012 12:14:28 PM Andrew Sullivan wrote:
cc:s trimmed. I'm not on the w3c list anyway, and I don't think the
IESG cares about this detail.
On Fri, Feb 24, 2012 at 04:58:36PM +0100, Patrik Fältström wrote:
Because people disagree on whether it is actually hard to get
On Fri, Feb 24, 2012 at 12:47:10PM -0500, Scott Kitterman wrote:
It's occured to me that it might be useful to pre-allocate some new
types without a current use assigned (e.g. TXT1, TXT2, TXT3) so that
there's time for them to be integrated into tools before they are
needed.
How could you
On Friday, February 24, 2012 12:57:49 PM Andrew Sullivan wrote:
On Fri, Feb 24, 2012 at 12:47:10PM -0500, Scott Kitterman wrote:
It's occured to me that it might be useful to pre-allocate some new
types without a current use assigned (e.g. TXT1, TXT2, TXT3) so that
there's time for them to
At 13:06 -0500 2/24/12, Scott Kitterman wrote:
If there had been a TXT1 ... N in 2004, SPF (to put an example) could have
picked TXT1 (assuming it wasn't used by something else). Then later the label
could have been changed to SPF once usage was established and standardized.
Then a few years
+1
As an implementator of all these new mouse trap protocols with TXT
based solutions, some borrowing the same namespace, some using
different namespaces, it doesn't escape me to continue getting the
utopian idea (ignoring the technical issues) that it will be sweet
if they all can be
On Feb 24, 2012, at 5:02 PM, Paul Hoffman wrote:
On Feb 24, 2012, at 4:54 AM, Stephen Farrell wrote:
Proposals for new HTTP authentication schemes are in scope.
How would a plan like the following look to folks:
- httpbis is chartered to include auth mechanism work as
per the above
In message 20120224171427.gj48...@mail.yitter.info, Andrew Sullivan writes:
cc:s trimmed. I'm not on the w3c list anyway, and I don't think the
IESG cares about this detail.
On Fri, Feb 24, 2012 at 04:58:36PM +0100, Patrik Fältström wrote:
Because people disagree on whether it is
Hi, Kim,
On 2/23/2012 10:57 AM, Kim Kinnear wrote:
Joe,
There were two things that I referenced in response to your initial
review that you hadn't seen. More details on those below:
On Feb 17, 2012, at 5:47 PM, Joe Touch wrote:
INTERLEAVING-
Hi, Kim,
On 2/23/2012 2:00 PM, Kim Kinnear wrote:
Joe,
I've edited the the email trail to try to concentrate on
the remaining open issues. I've also removed the two
issues that were included in the email I sent you an hour
or so ago, since I expect that they will be covered in
continuations
Hi, Ralph,
On 2/18/2012 4:39 AM, Ralph Droms wrote:
Joe, Kim...
On Feb 17, 2012, at 5:47 PM 2/17/12, Joe Touch wrote:
Hi, Kim,
First, thank you for your detailed response to my quite lengthy review.
Some further clarifications and confirmations appear below.
Joe
On 2/17/2012 12:09 PM,
Hi, Ted,
On 2/18/2012 7:29 AM, Ted Lemon wrote:
On Feb 17, 2012, at 5:47 PM, Joe Touch wrote:
Thanks. In this case, it's important to suggest why others should not
add conventional DHCP query support to the TCP port.
The idea of doing DHCP stateful autoconfiguration over TCP is
nonsensical:
Hi Stephen,
On 24/02/2012, at 11:54 PM, Stephen Farrell wrote:
On 02/24/2012 01:24 AM, Roy T. Fielding wrote:
On Feb 23, 2012, at 5:18 PM, Tim Bray wrote:
On Thu, Feb 23, 2012 at 5:13 PM, Roy T. Fieldingfield...@gbiv.com wrote:
How many times do we have to do this before we declare
On 02/24/2012 07:38, Andrew Sullivan wrote:
On Fri, Feb 24, 2012 at 01:54:32PM +1100, Mark Andrews wrote:
In message 4f46bfdf.3070...@dougbarton.us, Doug Barton writes:
2782 was published 12 years ago this month. I suppose it can be
considered mature enough to deploy at this point? :)
On 2/24/2012 7:35 PM, Ted Lemon wrote:
On Feb 24, 2012, at 7:39 PM, Joe Touch to...@isi.edu
mailto:to...@isi.edu wrote:
OK, so although I disagree that this is the correct procedure, if it's
typical for DHCP then that's reasonable.
So just to be clear here, it seems that you are withdrawing
A reminder that you have until 1700 PST today, February 24th to vote for your
favorite t-shirt submission. You can view all 12 submissions and vote online at
http://www.ietf.org/meeting/83/t-shirt-design-contest-voting.html.
Please note that submission numbers appear above each entry. The
The IESG has approved the following document:
- 'Subcodes for BGP Finite State Machine Error'
(draft-ietf-idr-fsm-subcode-03.txt) as a Proposed Standard
This document is the product of the Inter-Domain Routing Working Group.
The IESG contact persons are Stewart Bryant and Adrian Farrel.
A URL
The IESG has received a request from the Pseudowire Emulation Edge to
Edge WG (pwe3) to consider the following document:
- 'Packet Pseudowire Encapsulation over an MPLS PSN'
draft-ietf-pwe3-packet-pw-03.txt as a Proposed Standard
The IESG plans to make a decision in the next few weeks, and
The IESG has adopted an update the WG Document Write-up Template. The write-up
is required by RFC 4858. The new template has been posted at:
http://www.ietf.org/iesg/template/doc-writeup.html
Please start using this new template immediately for publication requests. New
publications
Thanks for all of the testing. Several bugs were found and fixed. At this
time there are no show stopper bugs, so we will convert to the new Datatracker
database this weekend. Of course, to be prudent, we will run a complete backup
before we being the database conversion.
The database
The IESG has approved the following document:
- 'RTP Payload Format for Raptor FEC'
(draft-ietf-fecframe-rtp-raptor-07.txt) as a Proposed Standard
This document is the product of the FEC Framework Working Group.
The IESG contact persons are David Harrington and Wesley Eddy.
A URL of this
29 matches
Mail list logo
