> -Original Message-
> From: sidr-boun...@ietf.org [mailto:sidr-boun...@ietf.org] On Behalf Of
> Christopher Morrow
> Sent: Saturday, March 24, 2012 10:09 AM
> To: Matt Lepinski
> Cc: sidr@ietf.org
> Subject: Re: [sidr] wg adoption call for draft-ymbk-bgpsec-rtr-rekeying-00.txt
>
> oh, exce
https://datatracker.ietf.org/meeting/83/agenda/sidr-drafts.pdf
link on agenda page is broken
--
Jakob Heitz.
___
sidr mailing list
sidr@ietf.org
https://www.ietf.org/mailman/listinfo/sidr
Read and support…
Sorry, there are so many drafts, I can never keep clear which ones I have
already supported…
W
On Mar 24, 2012, at 11:18 AM, Christopher Morrow wrote:
>
> Hey folk,
> Is this draft stating something obvious and doesn't need to be
> documented? or are we in need of this doc to
The requested additional SIDR session has been secheduled
Stewart
Original Message
Subject:sidr - Requested sessions have been scheduled for IETF 83
Date: Sat, 24 Mar 2012 03:16:22 -0700
From: "IETF Secretariat"
To: mur...@tis.com
CC: sidr-...@tools.ietf.org
On Sat, Mar 24, 2012 at 10:05 AM, Christopher Morrow
wrote:
> On Sat, Mar 24, 2012 at 10:02 AM, Matt Lepinski wrote:
>> Chris,
>>
>> No, I believe Wes is talking about:
>> http://tools.ietf.org/html/draft-rogaglia-sidr-bgpsec-rollover-00
>
> oh :) burried further down the list :( Sorry, that seem
On Sat, Mar 24, 2012 at 10:02 AM, Matt Lepinski wrote:
> Chris,
>
> No, I believe Wes is talking about:
> http://tools.ietf.org/html/draft-rogaglia-sidr-bgpsec-rollover-00
oh :) burried further down the list :( Sorry, that seems to make a
clearer link to why combination would be good.
thanks!
-c
Chris,
No, I believe Wes is talking about:
http://tools.ietf.org/html/draft-rogaglia-sidr-bgpsec-rollover-00
- Matt Lepinski
On 3/24/2012 9:42 AM, Christopher Morrow wrote:
On Sat, Mar 24, 2012 at 9:33 AM, George, Wes wrote:
Yes, support. Anything that teaches router jockeys how to wrangle
On Sat, Mar 24, 2012 at 9:33 AM, George, Wes wrote:
> Yes, support. Anything that teaches router jockeys how to wrangle keys and
> not compromise the security of the system in the process is a good thing IMO.
>
> Though I'm wondering if perhaps this doc and bgpsec-rollover should be
> integrated
Yes, support. Anything that teaches router jockeys how to wrangle keys and not
compromise the security of the system in the process is a good thing IMO.
Though I'm wondering if perhaps this doc and bgpsec-rollover should be
integrated
Thanks,
Wes George
> -Original Message-
> From:
I have read now this document.
The issues discussed in this document are issues should be documented
somewhere.
(It is possible that this could be rolled into another document, since
its short, but this stuff definitely should be documented in some
product of the SIDR working group)
I really a
Have read and support adoption.
___
sidr mailing list
sidr@ietf.org
https://www.ietf.org/mailman/listinfo/sidr
Hey folk,
Is this draft stating something obvious and doesn't need to be
documented? or are we in need of this doc to keep us all on the same
page (us == ops + vendors) as to getting a cert created and installed
on our lovely devices?
If people could take a few minutes to read the 4 pages (minus
12 matches
Mail list logo
