Re: [GROW] Ben Campbell's Yes on draft-ietf-grow-bgp-gshut-12: (with COMMENT)

I read bogus as spoofed or forged. if (initial_ttl!=255) then (rfc5082_compliant==0) donald.sm...@centurylink.com From: Job Snijders [j...@ntt.net] Sent: Thursday, December 14, 2017 10:20 AM To: Smith, Donald Cc: bruno.decra...@orange.com; Ben Campbell

Re: [GROW] Ben Campbell's Yes on draft-ietf-grow-bgp-gshut-12: (with COMMENT)

if (initial_ttl!=255) then (rfc5082_compliant==0) donald.sm...@centurylink.com > > From: Job Snijders [j...@ntt.net] > Sent: Thursday, December 14, 2017 12:38 PM > To: bruno.decra...@orange.com > Cc: Smith, D

Re: [GROW] Ben Campbell's Yes on draft-ietf-grow-bgp-gshut-12: (with COMMENT)

I don't see anything around MD5/TCPAO authentication. >From https://tools.ietf.org/html/rfc6198 " Security considerations MUST be addressed by the proposed solutions. In particular, they SHOULD address the issues of bogus g-shut messages and how they would affect the network(s), as well as

Re: [GROW] I-D Action: draft-ietf-grow-bgp-reject-05.txt

I support this draft. This comment is probably out of scope for this RFC but may need to be addressed some where, some how? >From an operations POV how would you know if a peer is using the default >behavior or has overridden it. Or a customer as for a peer the default may be accept * ? if (i

Re: [GROW] WGLC draft-ietf-grow-bgp-reject - ends 3/19/2017 (mar 19)

Support, the basic concept that if I am not configured to speak to you, I don't listen, nor announce to you, is sound and should be the default behavior. if (initial_ttl!=255) then (rfc5082_compliant==0) donald.sm...@centurylink.com _

Re: [GROW] WGLC draft-ietf-grow-bgp-reject - ends 3/19/2017 (mar 19)

I too support. if (initial_ttl!=255) then (rfc5082_compliant==0) donald.sm...@centurylink.com From: GROW [grow-boun...@ietf.org] on behalf of Gert Doering [g...@space.net] Sent: Monday, March 06, 2017 12:21 PM To: Christopher

Re: [GROW] Stephen Farrell's Discuss on draft-ietf-grow-blackholing-02: (with DISCUSS and COMMENT)

M To: Smith, Donald Cc: Randy Bush; Christopher Morrow; GMO Crops; The IESG Subject: Re: [GROW] Stephen Farrell's Discuss on draft-ietf-grow-blackholing-02: (with DISCUSS and COMMENT) Hi, On Mon, Aug 08, 2016 at 04:39:56PM +0000, Smith, Donald wrote: > This discusses neighboring networ

Re: [GROW] Stephen Farrell's Discuss on draft-ietf-grow-blackholing-02: (with DISCUSS and COMMENT)

This discusses neighboring networks, and local scope, so one would assume in most cases these are directly connected peers (or not many hops away), I think the security section should recommend use of GTSM on such sessions. Then it can't easily be spoofed outside of the local network. if (i

Re: [GROW] Stephen Farrell's Discuss on draft-ietf-grow-blackholing-02: (with DISCUSS and COMMENT)

> On Wed, Aug 3, 2016 at 11:31 AM, Stephen Farrell > wrote: > > Stephen Farrell has entered the following ballot position for > draft-ietf-grow-blackholing-02: Discuss > > When responding, please keep the subject line intact and reply to all > email addresses included in the To and CC lines

Re: [GROW] WG Adoption: draft-ymbk-grow-blackholing (expires: 08/26/2015 - Aug 26)

Support but have some comments when they are ready for them :) Or did I miss that ? H8Hz donald.sm...@centurylink.com From: GROW [grow-boun...@ietf.org] on behalf of Mikhail A. Grishin [m.gris...@msk-ix.ru] Sent: Tuesday,

Re: [GROW] I-D Action: draft-ietf-grow-simple-leak-attack-bgpsec-no-help-03.txt

Prevent this: http://www.renesys.com/2013/11/mitm-internet-hijacking/ I suspect that is what Chris is talking about. I know it concerns me. (coffee != sleep) & (!coffee == sleep) donald.sm...@centurylink.com From: GROW

Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt

"Pampers use multiple layers of protection to prevent leakage. Rommel used defense in depth to defend European fortresses." (A.White) donald.sm...@centurylink.com >-Original Message- >From: Tony Li [mailto:tony...@tony.li] >Sent: Thursday, January 03, 2013 4:15 PM

Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt

"Pampers use multiple layers of protection to prevent leakage. Rommel used defense in depth to defend European fortresses." (A.White) donald.sm...@centurylink.com >-Original Message- >From: grow-boun...@ietf.org [mailto:grow-boun...@ietf.org] On Behalf Of >Tony Li >Sent: Thursday, Jan

Re: [GROW] [Idr] I-D Action: draft-ietf-grow-ops-reqs-for-bgp-error-handling-06.txt

"Pampers use multiple layers of protection to prevent leakage. Rommel used defense in depth to defend European fortresses." (A.White) donald.sm...@centurylink.com >-Original Message- >From: idr-boun...@ietf.org [mailto:idr-boun...@ietf.org] On Behalf Of >Jeff Wheeler >Sent: Monday, De

Re: [GROW] RouteLeaks - problem or not?

"Pampers use multiple layers of protection to prevent leakage. Rommel used defense in depth to defend European fortresses." (A.White) donald.sm...@centurylink.com >-Original Message- >From: grow-boun...@ietf.org [mailto:grow-boun...@ietf.org] On Behalf Of >Christopher Morrow >Sent: Tu

Re: [GROW] I-D Action: draft-ietf-grow-bgp-gshut-04.txt

Where are the "Changes to BGP Finite State Machine" listed? BGP is supposed to be a Finite State Machine. Most early BGP rfcs called out the changes specifically. At least up to rfc4724 (Graceful Restart). This one CLEARLY changes the finite state machine but doesn't clearly state what those cha

Re: [GROW] Updates to draft-ietf-grow-private-ip-sp-cores

You don't need to include the Ethernet reference that is just a sig of mine. It wasn't intended as an actual comment on this rfc. It is based on the fact that in the early days of Ethernet some routers ignored the back off portion of the Ethernet standard. It is a reminder that standards are only

Re: [GROW] WGLC: draft-ietf-grow-private-ip-sp-cores

6:27 AM > To: tkirk...@anthony-kirkham.com > Cc: Smith, Donald; grow@ietf.org; grow-cha...@tools.ietf.org > Subject: Re: [GROW] WGLC: draft-ietf-grow-private-ip-sp-cores > > Using squat/stolen space will mean ICMP messages from the SP core > wouldn't be able to reach the legitim

Re: [GROW] WGLC: draft-ietf-grow-private-ip-sp-cores

space. (coffee != sleep) & (!coffee == sleep) donald.sm...@qwest.com<mailto:donald.sm...@qwest.com> From: Anthony Kirkham [tkirk...@anthony-kirkham.com] Sent: Wednesday, June 13, 2012 4:58 AM To: Smith, Donald Cc: 't.petch'; 'Chris

Re: [GROW] WGLC: draft-ietf-grow-private-ip-sp-cores

There is a mention of "squat" space that doesn't make any recommendations as to use or not. I can understand not expressing an opinion on the rfc1918/private space shouldn't this state that squating is bad? "This effect in itself is often not a problem. However, if anti- spoofing controls ar

Re: [GROW] Call for WG Adoption - draft-shakir-idr-ops-reqs-for-bgp-error-handling

+1 support (coffee != sleep) & (!coffee == sleep) donald.sm...@qwest.com From: grow-boun...@ietf.org [grow-boun...@ietf.org] On Behalf Of Russell Heilling [russ...@heilling.net] Sent: Friday, April 01, 2011 3:32 AM To: Christopher Morrow Cc: draft-shakir-i

Re: [GROW] [Idr] Fwd: New Version Notification for draft-shakir-idr-ops-reqs-for-bgp-error-handling-01

+1 reasonable bgp error handling (rather then dropping sessions and flushing routes) is a good idea. Ignorance is Bliss. "Bliss (Basic Language for Implementation of System Software) was a systems programming language originally for the PDP-10 and DECsystem-20 written at CMU." K-Oberman donald

[GROW] draft-ietf-grow-unique-origin-as-00

I support this draft as it would enhance the ability to control and monitor anycasted service announcements. http://tools.ietf.org/html/draft-ietf-grow-unique-origin-as (coffee != sleep) & (!coffee == sleep) donald.sm...@qwest.com This communication is the property of Qwest and may contain c