--On Tuesday, August 21, 2012 15:10 -0700 Bob Hinden
bob.hin...@gmail.com wrote:
In particular: should bullet 15,2 (and its supporting text
elsewhere) be removed?
15,2 should probably say People employed in the IETF
Secretariat…..
I would leave it in. My thinking is that the IESG,
Reply to your request dated 29/08/2012
Draft Reviewed By: Abdussalam Baryun (AB)Dated:22/08/2012
Reviewer Comment AB2: Related to OLSRv2 Packets.
-The reviewer is not sure how/when the OLSRv2 generates packets
[RFC5444] or how it puts information
Stephen,
To add to what Adrian said, the 1:1 mapping is only for node
identifiers, interface identifiers have no such restriction. I think
it's reasonable to add some informative text to the draft on this point
as it may help avoid such confusion in the future.
Lou
On 8/22/2012 1:01 PM,
On 8/17/2012 12:05 PM, Robert Raszuk wrote:
For example once I know the criteria I could check around in Poland to
see if there is any place which would satisfy the future IETF venue.
http://www.ietf.org/meeting/hosting-an-ietf.html
d/
--
Dave Crocker
Brandenburg InternetWorking
For example once I know the criteria I could check around in Poland to
see if there is any place which would satisfy the future IETF venue.
http://www.ietf.org/meeting/hosting-an-ietf.html
That's about how to be a meeting host, and it's mostly about terminal
rooms and social events.
Is
On Wed, 2012-08-22 at 20:11 +, John Levine wrote:
http://www.ietf.org/meeting/hosting-an-ietf.html
Is there a list anywhere of minimum requirements without which it's
not even worth looking at a venue? I'd expect that if a place doesn't
have (as some examples) a meeting room big
Reply to your request dated 29/07/2012
Draft Reviewed By: Abdussalam Baryun (AB) Dated:
22/08/2012
Reviewer Comment AB1: Terminology and Definition Related
In [1] the olsrv2-interface runs the NHDP, and some terms in [1] are
defined as
Reply to your request dated 29/07/2012
Draft Reviewed By: Abdussalam Baryun (AB)Dated:22/08/2012
Reviewer Comment AB3: Related to OLSRv2 Metric
++
OLSRv2-draft Note that the generation of (incoming) link metric
values is to be undertaken by a process
Reply to your request dated 29/07/2012
Draft Reviewed By: Abdussalam Baryun (AB) Dated: 22/08/2012
Reviewer Comment AB4: Related to OLSRv2 Messages.
Section 13.2. Messages with different originating routers MAY be
combined for transmission within the
Reply to your request dated 29/07/2012
Draft Reviewed By: Abdussalam Baryun (AB) Dated: 22/08/2012
Reviewer Comment AB5: Related to OLSRv2 update to IP Routing Table.
+
Section 4.6 It is intended that the Routing Set can be used for IP
Reply to your request dated 29/07/2012
Draft Reviewed By: Abdussalam Baryun (AB) Dated: 22/08/2012
Reviewer Comment AB6: Related to OLSRv2 Interfaces.
-Is NHDP a must for OLSRv2 routing?
Comment The relationship between RFC6130 and the [OLSRv2] was not
The IESG has received a request from the Public-Key Infrastructure
(X.509) WG (pkix) to consider the following document:
- 'Updates to the Internet X.509 Public Key Infrastructure Certificate
and Certificate Revocation List (CRL) Profile'
draft-ietf-pkix-rfc5280-clarifications-08.txt as
The IESG has received a request from the IS-IS for IP Internets WG (isis)
to consider the following document:
- 'IS-IS Multi-Instance'
draft-ietf-isis-mi-06.txt as Proposed Standard
The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send
The IESG has approved the following document:
- 'Datagram Congestion Control Protocol (DCCP) Encapsulation for NAT
Traversal (DCCP-UDP)'
(draft-ietf-dccp-udpencap-11.txt) as Proposed Standard
This document is the product of the Datagram Congestion Control Protocol
Working Group.
The IESG
The IESG has approved the following document:
- 'Distribution of diverse BGP paths.'
(draft-ietf-grow-diverse-bgp-path-dist-08.txt) as Informational RFC
This document is the product of the Global Routing Operations Working
Group.
The IESG contact persons are Ronald Bonica and Benoit Claise.
A
15 matches
Mail list logo
