On 4/19/17 1:52 AM, Stewart Bryant wrote:
>
>
> On 19/04/2017 02:06, Randy Bush wrote:
5. Security Considerations
Operators should note the recommendations in Section 11 of BGP
Operations and Security [RFC7454].
SB> You do not address the question of whether
On Wed, Apr 19, 2017 at 03:54:06PM +0100, Stewart Bryant wrote:
> Thanks
>
> I think I have done the required Genart level of due diligence on
> Security.
Much appreciated, stay tuned for an updated version which incorporates
your feedback.
Kind regards,
Job
___
Thanks
I think I have done the required Genart level of due diligence on Security.
Stewart
On 19/04/2017 15:18, Job Snijders wrote:
On Wed, Apr 19, 2017 at 09:46:53AM +0100, Stewart Bryant wrote:
Operations and Security [RFC7454].
SB> You do not address the question of whether there are
On Wed, Apr 19, 2017 at 09:46:53AM +0100, Stewart Bryant wrote:
> > > Operations and Security [RFC7454].
> > >
> > > SB> You do not address the question of whether there are new
> > > SB> considerations, or considerations that are of increased importance?
> >
> > It is my understanding that R
> I was wondering if there was more scope to make mischief at a distance
> in a less less obvious way than before.
there isn't
but where were you when the blackhole community was passed?
> So you rely on the nodes that receive these community strings to
> interpret them in a common way.
no. as
Stewart Bryant wrote:
> Guessing is horrible, but if that is what you do, that is what you do,
> and if the risks are the accepted norm in the BGP
> community I am fine.
there's a general understanding out there that if you're directly
connect to $asn, you can somewhat believe $asn:* or $asn:*:*
c
>> you're supposed to guess
>>
>> the normal hack here is
>>
>>this document introduces no new security issues beyond those discussed
>>in 1997
>
> Guessing is horrible, but if that is what you do, that is what you do,
> and if the risks are the accepted norm in the BGP community I am fi
On 19/04/2017 02:06, Randy Bush wrote:
5. Security Considerations
Operators should note the recommendations in Section 11 of BGP
Operations and Security [RFC7454].
SB> You do not address the question of whether there are new
SB> considerations, or considerations that are of increased
On 19/04/2017 00:58, Job Snijders wrote:
5. Security Considerations
Operators should note the recommendations in Section 11 of BGP
Operations and Security [RFC7454].
SB> You do not address the question of whether there are new
SB> considerations, or considerations tha
>> 5. Security Considerations
>>
>>Operators should note the recommendations in Section 11 of BGP
>>Operations and Security [RFC7454].
>>
>> SB> You do not address the question of whether there are new
>> SB> considerations, or considerations that are of increased importance?
>
> It is
Hi Bryant,
Thank you for taking the time to go through the document.
On Tue, Apr 18, 2017 at 06:41:15AM -0700, Stewart Bryant wrote:
> Please treat these comments just like any other last call comments.
>
> SB> Even if you just copy the Introduction, the Abstract should
> SB> really be expanded
Tue, Apr 18, 2017 at 06:41:15AM -0700, Stewart Bryant:
> 5. Security Considerations
>
>Operators should note the recommendations in Section 11 of BGP
>Operations and Security [RFC7454].
>
> SB> You do not address the question of whether there are new
> considerations, or considerations
>
Reviewer: Stewart Bryant
Review result: Almost Ready
I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please treat these comments just
like any other last call comments.
For more i
13 matches
Mail list logo
