Benjamin Kaduk has entered the following ballot position for
draft-ietf-lisp-rfc6833bis-29: No Objection
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
ooray!)
> On Thu, Jul 9, 2020 at 6:26 AM Benjamin Kaduk via Datatracker
> wrote:
> >
> > Benjamin Kaduk has entered the following ballot position for
> > draft-ietf-lisp-rfc6833bis-27: Discuss
> >
> > When responding, please keep the subject line intact and re
Benjamin Kaduk has entered the following ballot position for
draft-ietf-lisp-gpe-17: No Objection
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 https
Benjamin Kaduk has entered the following ballot position for
draft-ietf-lisp-rfc6833bis-27: 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
Benjamin Kaduk has entered the following ballot position for
draft-ietf-lisp-rfc6830bis-32: No Objection
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
On Mon, Dec 30, 2019 at 03:03:35PM -0800, Dino Farinacci wrote:
> > Thank you for all the updates in the -28; we're making great progress!
>
> Thanks Ben. Here are some brief answers.
Thanks Dino.
> > My ballot on the -26 included:
> >
> > % The usage of the Instance ID does not seem to be adeq
Benjamin Kaduk has entered the following ballot position for
draft-ietf-lisp-rfc6833bis-26: 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
Benjamin Kaduk has entered the following ballot position for
draft-ietf-lisp-rfc6830bis-28: 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
Benjamin Kaduk has entered the following ballot position for
draft-ietf-lisp-gpe-12: No Objection
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 https
reflects the
> approach above.
>
> It'd be great to hear your thoughts.
>
> We will discuss this approach with the WG in Singapore, and if there's
> support, we could go to LC right after the meeting.
>
> Thanks,
> Fabio
>
>
>
>
>
>
Benjamin Kaduk has entered the following ballot position for
draft-ietf-lisp-gpe-09: Abstain
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 https
Benjamin Kaduk has entered the following ballot position for
draft-ietf-lisp-gpe-08: 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 https
Since Ekr has cycled off the IESG, I'll try to take over any remaining
points here. It seems like there may just be the one left, hooray!
The authors very helpfully put together a spreadsheet with all the
comments, discussion about them, and pointers to what changed (if anything)
in the document a
Benjamin Kaduk has entered the following ballot position for
draft-ietf-lisp-rfc6833bis-25: 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
Benjamin Kaduk has entered the following ballot position for
draft-ietf-lisp-rfc6830bis-27: 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
On Sat, Mar 23, 2019 at 05:22:49PM -0500, Benjamin Kaduk wrote:
> On Sat, Mar 23, 2019 at 11:06:33AM -0700, Dino Farinacci wrote:
> > > I'm not sure I understand the need for "use a different key for
> > > consecutive
> > > messages", but proba
On Sat, Mar 23, 2019 at 11:06:33AM -0700, Dino Farinacci wrote:
> > I'm not sure I understand the need for "use a different key for consecutive
> > messages", but probably we should just talk about that on Tuesday.
>
> Well in your last reply you felt it was okay if we used the nonce in each
> Ma
On Wed, Mar 20, 2019 at 03:27:26PM -0700, Dino Farinacci wrote:
> Ben regarding using PSKs for Map-Registers. How about we do this:
>
> (1) The ETR and map-server can be provisioned with up to 256 keys.
> (2) Each Map-Register uses one of the 256 keys buy doing a random number
> modulo 256.
> (3)
On Wed, Mar 20, 2019 at 02:10:19PM -0700, Fabio Maino wrote:
> On 3/20/19 8:05 AM, Benjamin Kaduk wrote:
> > On Mon, Mar 18, 2019 at 03:01:07PM -0700, Fabio Maino wrote:
> >> Hi Ben,
> >> I'm starting this separated thread to discuss this point.
> > Thanks fo
On Mon, Mar 18, 2019 at 03:01:07PM -0700, Fabio Maino wrote:
> Hi Ben,
> I'm starting this separated thread to discuss this point.
Thanks for splitting it off.
>
> On 2/7/19 5:50 AM, Benjamin Kaduk wrote:
> > This document includes a mechansism to use HMAC keyed by
Hi folks,
Since this document is still sort-of in WGLC, I'm sending my notes on it.
They were originally written as notes to myself during my review of
6833bis, so my apologies for the parts that are inscrutable. I can try to
clarify as needed.
-Ben
Section 3
authoritative. In this way th
Splitting off a sub-thread for one fairly narrow point that AFAICT needs
further discussion to clarify the path forward:
On Thu, Feb 07, 2019 at 05:50:39AM -0800, Benjamin Kaduk wrote:
>
> --
>
Benjamin Kaduk has entered the following ballot position for
draft-ietf-lisp-rfc6830bis-26: 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
Benjamin Kaduk has entered the following ballot position for
draft-ietf-lisp-rfc6833bis-24: 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
On Tue, Feb 05, 2019 at 07:56:39PM -0800, Dino Farinacci wrote:
> > Nits/editorial comments: Section 2: Get rid of everything except the last
> > paragraph.
>
> Are you sure? I just followed what RFC 8174 suggested. Give me reason to not
> follow it?
Yes, he's sure.
You pasted the text that 81
On Thu, Sep 27, 2018 at 02:06:13PM -0700, Dino Farinacci wrote:
> Fixing the simple issues first. Clipping out the rest of the text.
>
> > Is there anything different between an "EID-to-RLOC Map-Request" and just a
> > "Map-Request"? (Same question for "Map-Reply", too.)
>
> No. But Map-Requests
ADs that are supporting making LISP-SEC a
normative reference and thus MTI; I don't know if that scale of change
meets your threshold for a "larger problem".
> Yours,
> Joel
>
> On 9/26/18 11:44 PM, Benjamin Kaduk wrote:
> > Benjamin Kaduk has entered the following
Benjamin Kaduk has entered the following ballot position for
draft-ietf-lisp-gpe-06: 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 https
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
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
On Wed, Sep 12, 2018 at 12:44:36PM +0200, Mirja Kuehlewind (IETF) wrote:
>
> > Am 11.09.2018 um 20:13 schrieb Dino Farinacci :
> >
> >>
> >> Further comments:
> >>
> >> 1) The example given in 5.5 should probably used IPv6 addresses and use
> >> the IP
> >> address space that is reserved for d
Kyle, Dino,
Thanks for the review and discussion -- I look forward to seeing where it
ends up. Just one note, inline...
On Sat, Aug 25, 2018 at 02:40:15PM -0700, Dino Farinacci wrote:
> > Reviewer: Kyle Rose
> > Review result: Has Issues
>
>
> > Another question it poses is: how does the Map-R
32 matches
Mail list logo
