Section 2.2
b. Interface_list and router-id: For a functioning routing-instance,
can't think of a routing-instance without either of those defined. So,
either the optionality aspect needs to be changed to "required" or specify
how a routing-instance would work with either missing.
NB> A rout
Thanks Ravi for the detailed review.
Please see comments inline below. I will submit the updated draft once all
comments have been satisfactorily resolved.
From: Ravi Singh [mailto:ra...@juniper.net]
Sent: 2016年5月18日 0:55
To: rtg-...@ietf.org
Cc: 'Jonathan Hardwick'; 'Jon Hudson'; Susan Hares;
Thanks Ravi for the detailed review.
Please see comments inline below. I will submit the updated draft once all
comments have been satisfactorily resolved.
From: Ravi Singh [mailto:ra...@juniper.net]
Sent: 2016年5月18日 0:55
To: rtg-...@ietf.org
Cc: 'Jonathan Hardwick'; 'Jon Hudson'; Susan Hares;
WG there is an typo in section 7
Ephemeral-REQ-11: The data nodes MAY store I2RS client identity and
not the effective priority at the time the data node is stored. Per
SEC-REQ-07 in section 3.1 of
[I-D.ietf-i2rs-protocol-security-requirements], an identifier must
have just one pr
I2RS WG:
An I2RS interim is schedule for 10:00am – 11:30am on Wednesday June 22, 2016.
The ephemeral state document has 15 requirements for Ephemeral state, and 2
requirements for pub/sub support of ephemeral state.
I2RS interim
Wednesday, June 22, 2016
10:00 am | Eastern
This begins a 2 WG LC last call on the text of
draft-ietf-i2rs-ephemeral-state-10.txt. There are 15 requirement for I2RS
ephemeral state, and 2 requirements for ephemeral state utilized by pub/sub
documents.
Sue Hares and Russ White
-Original Message-
From: i2rs [mailto:i2rs-boun...
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Interface to the Routing System of the IETF.
Title : I2RS Ephemeral State Requirements
Authors : Jeff Haas
Susan Hares
