Subject: Consideration of BGP Security Document for IDR draft
From: [email-masked]
To: [email-masked]
Cc: [email-masked], [email-masked]
Date: Thu, 28 Jan 1999 13:02:21 -0500 (EST)

Sandy Murphy has presented a security analysis for the BGP protocol
at a few of the past IDR meetings.  Sandy has written an Internet
Draft from that work.   I would like to have a list discussion about
forwarding her draft:

	draft-murphy-bgp-secr-02.txt 

toward an information RFC as a IDR working group draft.

The discussion will close in 2 weeks on 2/12/99.

Sue Hares

To: "jaihari loganathan" <[email-masked]>
cc: [email-masked], [email-masked]
Subject: Re: ignoring paths 
Date: Wed, 27 Jan 1999 20:13:56 -0800
From: Enke Chen <[email-masked]>
Sender: [email-masked]

> Date:    Wed, 27 Jan 1999 19:05:46 PST
> From:    "jaihari loganathan" <[email-masked]>
> To:      [email-masked]

> Hi,
>   Suppose we receive an update from a peer advertising certain set
>   of NLRI and we find the aspath looped or nexthop was invalid,
>   apart from ignoring such paths should we also (i guess so)   
> invalidate (any possible) current paths from the peer to the cited NLRI.
>   (similar to the instance where we find the new path to be unacceptable 
> for policy reasons )

Yes.   -- Enke

From: "jaihari loganathan" <[email-masked]>
To: [email-masked]
Subject: ignoring paths 
Date: Wed, 27 Jan 1999 19:05:46 PST
Sender: [email-masked]

Hi,
  Suppose we receive an update from a peer advertising certain set
  of NLRI and we find the aspath looped or nexthop was invalid,
  apart from ignoring such paths should we also (i guess so)   
invalidate (any possible) current paths from the peer to the cited NLRI.
  (similar to the instance where we find the new path to be unacceptable 
for policy reasons )
Thanks,
-Jaihari

______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com

Date: Fri, 22 Jan 1999 10:48:29 -0500 (EST)
From: Susan Hares <[email-masked]>
To: [email-masked]
Subject: FYI - IAB announcement
Sender: [email-masked]

>From [email-masked]  Thu Jan 21 10:15:37 1999
To: IETF-Announce: ;
Cc: RFC Editor <[email-masked]>
Cc: Internet Architecture Board <[email-masked]>
Cc: [email-masked]
From: The IESG <[email-masked]>
Subject: Document Action: A Framework for Inter-Domain Route
	 Aggregation to Informational
Date: Thu, 21 Jan 1999 10:14:30 -0500
Sender: [email-masked]

The IESG has approved the Internet-Draft 'A Framework for Inter-Domain
Route Aggregation' <draft-ietf-idr-aggregation-framework-04.txt> as a
Informational.  This document is the product of the Inter-Domain
Routing Working Group.  The IESG contact person is Rob Coltun.

Date: Fri, 22 Jan 1999 10:08:20 -0500 (EST)
From: Susan Hares <[email-masked]>
To: [email-masked]
Subject: BOUNCE [email-masked]:    Non-member submission from [The IESG <[email-masked]>]    (fwd)
Sender: [email-masked]

---------- Forwarded message ----------
Date: Thu, 21 Jan 1999 10:15:44 -0500 (EST)
From: [email-masked]
To: [email-masked]
Subject: BOUNCE [email-masked]:    Non-member submission from [The IESG <[email-masked]>]   

>From [email-masked]  Thu Jan 21 10:15:37 1999
To: IETF-Announce: ;
Cc: RFC Editor <[email-masked]>
Cc: Internet Architecture Board <[email-masked]>
Cc: [email-masked]
From: The IESG <[email-masked]>
Subject: Document Action: A Framework for Inter-Domain Route
	 Aggregation to Informational
Date: Thu, 21 Jan 1999 10:14:30 -0500
Sender: [email-masked]

The IESG has approved the Internet-Draft 'A Framework for Inter-Domain
Route Aggregation' <draft-ietf-idr-aggregation-framework-04.txt> as a
Informational.  This document is the product of the Inter-Domain
Routing Working Group.  The IESG contact person is Rob Coltun.