Hi, all,
I've reviewed this document as part of the transport area directorate's
ongoing effort to review key IETF documents. These comments were written
primarily for the transport area directors, but are copied to the
document's authors for their information and to allow them to address
any
- Original Message -
From: Henrik Levkowetz hen...@levkowetz.com
To: Mathieu Goessens mathieu.goess...@irisa.fr
Cc: adr...@olddog.co.uk; 6low...@ietf.org; ietf@ietf.org; 'Paul Hoffman'
paul.hoff...@vpnc.org; rfc-edi...@rfc-editor.org
Sent: Sunday, March 27, 2011 12:34 PM
Subject: Re:
Hi Dave,
thank you for the detailed review of the draft.
For time reasons I only focus on a few minor items; a more detailed response
will follow later.
2. Software
The draft is predicated on a common point of confusion between software
architecture and network protocol architecture.
Hello,
I believe there is a problem with this draft that can void a claimed
security property: namely, resistance to dictionary attack. The issue is
not with the underlying key exchange itself, but with the way the key
exchange was added to IKEv2.
In this protocol, a random nonce is
Alexey Melnikov wrote:
Peter Saint-Andre wrote:
Agreed, thanks to Paul for the proposed text.
On 2/15/11 9:02 PM, Cullen Jennings wrote:
Paul's text is much better than mine. That was what I trying to get
at.
Agreed, I will add this as an RFC Editor's note.
On Feb 15, 2011, at 8:59
On 3/28/11 2:14 PM, Alexey Melnikov wrote:
Alexey Melnikov wrote:
Peter Saint-Andre wrote:
Agreed, thanks to Paul for the proposed text.
On 2/15/11 9:02 PM, Cullen Jennings wrote:
Paul's text is much better than mine. That was what I trying to get
at.
Agreed, I will add this as an RFC
As one of the authors/editors, I am fine with this change. Thanks!
On 2011-3-28, at 14:14, Alexey Melnikov wrote:
After discussing this new text with IESG and some participants of the TSVWG,
it became clear that while there is clear agreement for adding the first
sentence quoted above (There
Greetings,
Just to clarify, please note that the version available
in the RFC Editor repository
(http://www.rfc-editor.org/rfc/rfc4944.txt) is dated 24 Sept 2007, and
the RFC was announced on 25 Sept 2007. The document has not been
altered or updated since it was published.
Please let us know
As one of the authors, I'm fine with this change too.
Joe
On 3/28/2011 5:46 AM, Lars Eggert wrote:
As one of the authors/editors, I am fine with this change. Thanks!
On 2011-3-28, at 14:14, Alexey Melnikov wrote:
After discussing this new text with IESG and some participants of the TSVWG, it
Joe Touch skrev 2011-03-28 15:33:
As one of the authors, I'm fine with this change too.
Me too,
Magnus Westerlund
___
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf
+1
Michelle
On 3/28/11 5:46 AM, Lars Eggert lars.egg...@nokia.com wrote:
As one of the authors/editors, I am fine with this change. Thanks!
On 2011-3-28, at 14:14, Alexey Melnikov wrote:
After discussing this new text with IESG and some participants of the TSVWG,
it became clear that
Beginning of the Technical Plenary... this is my version of posting to
bad-attitude...
On 3/27/2011 4:59 PM, Peterson, Jon wrote:
Without speaking to your review of the draft as such, let me restate what has
already been said on the apps-discuss list:
Jon,
Forgive me, but a review of that
On 2011-03-28 11:39 t.petch said the following:
...
From: Henrik Levkowetzhen...@levkowetz.com
...
On 2011-03-27 03:00 Mathieu Goessens said the following:
...
The drafts are also wrong, both in txt, html and pdf:
http://tools.ietf.org/html/draft-ietf-6lowpan-format-13
For those at IETF 80 interested in HTTP and authentication, there will
be a side meeting on Wednesday night for more in-depth discussion than
will be possible during the SAAG session on Thursday. Logistics are
20:00 in Karlin II/III. Further details below...
Original Message
The IESG has approved the following document:
- 'RTP Payload Format for IP-MR Speech Codec'
(draft-ietf-avt-rtp-ipmr-15.txt) as a Proposed Standard
This document is the product of the Audio/Video Transport Payloads
Working Group.
The IESG contact persons are Gonzalo Camarillo and Robert
The IESG has approved the following document:
- 'An Incremental Carrier-Grade NAT (CGN) for IPv6 Transition'
(draft-ietf-v6ops-incremental-cgn-03.txt) as an Informational RFC
This document is the product of the IPv6 Operations Working Group.
The IESG contact persons are Ron Bonica and Dan
The IESG has approved the following document:
- 'Use of the Content-Disposition Header Field in the Hypertext Transfer
Protocol (HTTP)'
(draft-ietf-httpbis-content-disp-09.txt) as a Proposed Standard
This document is the product of the Hypertext Transfer Protocol Bis
Working Group.
The IESG
The IESG has approved the following document:
- 'Additional New ASN.1 Modules for the Cryptographic Message Syntax
(CMS) and the Public Key Infrastructure Using X.509 (PKIX)'
(draft-turner-additional-new-asn-08.txt) as a Proposed Standard
This document has been reviewed in the IETF but is
The IESG has received a request from the Multiple Interfaces WG (mif) to
consider the following document:
- 'Current Practices for Multiple Interface Hosts'
draft-ietf-mif-current-practices-09.txt as an Informational RFC
The IESG plans to make a decision in the next few weeks, and solicits
The IESG has approved the following document:
- 'Mobility Support in IPv6'
(draft-ietf-mext-rfc3775bis-13.txt) as a Proposed Standard
This document is the product of the Mobility EXTensions for IPv6 Working
Group.
The IESG contact persons are Ralph Droms and Jari Arkko.
A URL of this Internet
The IESG has approved the following document:
- 'Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Option for Dual-
Stack Lite'
(draft-ietf-softwire-ds-lite-tunnel-option-10.txt) as a Proposed
Standard
This document is the product of the Softwires Working Group.
The IESG contact persons
The IESG has approved the following document:
- 'MIKEY-IBAKE: Identity-Based Mode of Key Distribution in Multimedia
Internet KEYing (MIKEY)'
(draft-cakulev-mikey-ibake-06.txt) as an Informational RFC
This document has been reviewed in the IETF but is not the product of an
IETF Working Group.
Dear Colleagues,
Before I pass the credentials of this mail account I would like to
enthusiastically announce that Bernard Aboba is the new IAB chair.
I would like to thank the IAB for their trust.
--Olaf Kolkman
IAB member
---
The Internet Architecture
A new Request for Comments is now available in online RFC libraries.
BCP 42
RFC 6195
Title: Domain Name System (DNS) IANA
Considerations
Author: D. Eastlake 3rd
Status: Best Current Practice
Stream:
24 matches
Mail list logo
