might preference would be just to pick one, and
provide a stick for hitting those who do it the other way.
I think that IESG is already using that stick :)
AB
On 1/9/13, Dean Willis dean.wil...@softarmor.com wrote:
On Jan 8, 2013, at 12:57 PM, Abdussalam Baryun abdussalambar...@gmail.com
Awesome news: JSON Patch has enough IESG votes to become a standards
track document, even though JSON Pointer still has a discuss. This way
of doing things is very efficient--lots of documents can be approved
this way.
- Rob
On Tue, Jan 8, 2013 at 1:41 PM, Barry Leiba barryle...@computer.org
John Day wrote:
For any formal proofing system worth its dime, this can be 100% ruled out,
since the proofing system will emit a 100% bugfree implementation of the
spec in the programming language of your choice as a result/byproduct of the
formal proofing process.
C'mon. You don't really
John Day wrote:
It would be interesting to see you apply that.
This is what I have been talking about. The human mind's ability to
believe that the whole world sees everything the same way they do.
It really is quite amazing.
These so-called gaps often arise because they were unstated
Maybe the survey to be done is a review of all the RFC, STD and see
which ones
- had a great abstract and introduction,
- had the better writing styles
- had the least endorsement resistance
- progress faster than most,
- had the most implementators,
- with least support/questions need to be
On 1 January 2013 21:50, =JeffH jeff.hod...@kingsmountain.com wrote:
Hi,
Here are some last call comments on draft-laurie-pki-sunlight-05.
Overall the spec is in basically overall reasonable shape but I do have some
substantive comments that if I'm not totally misunderstanding things (which
On 1/7/2013 6:01 PM, John Day wrote:
All standards groups that I am aware of have had the same view. This is
not uncommon.
Although, I would point out that the TCP specification nor do most
protocols specifications of this type follow this rule. State
transitions are not visible on the wire.
Orlando IETF Codesprint
When: Saturday, 9 March 2013, starting at 9:30 AM
Where: IETF Hotel
What: A bunch of hackers get together to work on code for the
IETF. All code will become part of the open source IETF tools.
Who: Hopefully you can help
Many of the results of previous
The IESG has received a request from the IP Flow Information Export WG
(ipfix) to consider the following document:
- 'Information Model for IP Flow Information eXport (IPFIX)'
draft-ietf-ipfix-information-model-rfc5102bis-09.txt as Proposed
Standard
The IESG plans to make a decision in the
This is an announcement of an IETF-wide Call for Comment on 'Issues in
Identifier Comparison for Security Purposes'.
The document is being considered for publication as an Informational RFC within
the IAB stream, and is available for inspection here:
The IESG has approved the following document:
- 'Format for the Session Initiation Protocol (SIP) Common Log Format
(CLF)'
(draft-ietf-sipclf-format-11.txt) as Proposed Standard
This document is the product of the SIP Common Log Format Working Group.
The IESG contact persons are Robert
The IESG has approved the following document:
- 'The Common Log Format (CLF) for the Session Initiation Protocol (SIP):
Framework and Information Model'
(draft-ietf-sipclf-problem-statement-13.txt) as Proposed Standard
This document is the product of the SIP Common Log Format Working Group.
12 matches
Mail list logo
