Suresh Krishnan has entered the following ballot position for
draft-ietf-lisp-rfc6830bis-20: Discuss
When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)
Please refer to htt
Benjamin Kaduk has entered the following ballot position for
draft-ietf-lisp-rfc6833bis-16: Discuss
When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)
Please refer to http
Is there text we can add about the scoping that will change your discuss
into a series of useful comments?
If so, Some indication of how you would like that phrased would help us
address these.
If not, we seem to have a larger problem.
Yours,
Joel
On 9/26/18 11:44 PM, Benjamin Kaduk wrote:
Be
Benjamin Kaduk has entered the following ballot position for
draft-ietf-lisp-rfc6830bis-20: Discuss
When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)
Please refer to http
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Locator/ID Separation Protocol WG of the IETF.
Title : Locator/ID Separation Protocol (LISP) Control-Plane
Authors : Vince Fuller
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Locator/ID Separation Protocol WG of the IETF.
Title : The Locator/ID Separation Protocol (LISP)
Authors : Dino Farinacci
V
Hi Mirja,
trying to follow up on this issue.
The ECN text for encapsulation is currently:
The 'Explicit Congestion Notification' (ECN) field (bits 6 and 7
of the IPv6 'Traffic Class' field) requires special treatment in
order to avoid discarding indications of congestion [RFC31
