Re: WG LC: draft-ietf-l3vpn-2547bis-mcast
Eric Rosen <erosen@cisco.com> Wed, 10 December 2008 17:30 UTC
Return-Path: <l3vpn-bounces@ietf.org>
X-Original-To: l3vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l3vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3F9393A6B94; Wed, 10 Dec 2008 09:30:16 -0800 (PST)
X-Original-To: l3vpn@core3.amsl.com
Delivered-To: l3vpn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 57A603A69E3 for <l3vpn@core3.amsl.com>; Wed, 10 Dec 2008 09:30:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.3
X-Spam-Level:
X-Spam-Status: No, score=-6.3 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rNySiTrEsJfE for <l3vpn@core3.amsl.com>; Wed, 10 Dec 2008 09:30:14 -0800 (PST)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 685D93A6B94 for <l3vpn@ietf.org>; Wed, 10 Dec 2008 09:30:14 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.33,748,1220227200"; d="scan'208";a="30594688"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-2.cisco.com with ESMTP; 10 Dec 2008 17:30:08 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id mBAHU8x1004283; Wed, 10 Dec 2008 12:30:08 -0500
Received: from erosen-linux.cisco.com (erosen-linux.cisco.com [161.44.70.34]) by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id mBAHU8DE027891; Wed, 10 Dec 2008 17:30:08 GMT
Received: from erosen-linux (localhost.localdomain [127.0.0.1]) by erosen-linux.cisco.com (8.13.1/8.13.1) with ESMTP id mBAHTp4P011376; Wed, 10 Dec 2008 12:29:51 -0500
To: Thomas Morin <thomas.morin@orange-ftgroup.com>
Subject: Re: WG LC: draft-ietf-l3vpn-2547bis-mcast
In-reply-to: Your message of Wed, 10 Dec 2008 15:13:23 +0100. <1228918403.6476.21.camel@l-at11168.FTRD>
Date: Wed, 10 Dec 2008 12:29:51 -0500
Message-ID: <11375.1228930191@erosen-linux>
From: Eric Rosen <erosen@cisco.com>
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1051; t=1228930208; x=1229794208; c=relaxed/simple; s=rtpdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=erosen@cisco.com; z=From:=20Eric=20Rosen=20<erosen@cisco.com> |Subject:=20Re=3A=20WG=20LC=3A=20draft-ietf-l3vpn-2547bis-m cast=20 |Sender:=20 |To:=20Thomas=20Morin=20<thomas.morin@orange-ftgroup.com>; bh=0ZBtGbY7mfCoOOkpU/oe8KdXbh5haHyi0g+otRzb3yk=; b=cylV1oNDAGk+jmwSCyKjy8NsEcupTzm4dACyQA1ghKUduAkNhnFrNMo22j kPDPYIjoV5swXYo9+GiyYNykv3Wb+f8d5zPoK5bOofDKMRbKAyw/2rt9yJ1E uGuVZMhZO9;
Authentication-Results: rtp-dkim-2; header.From=erosen@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim2001 verified; );
Cc: erosen@cisco.com, L3VPN <l3vpn@ietf.org>, Rahul Aggarwal <rahul@juniper.net>
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: erosen@cisco.com
List-Id: <l3vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/l3vpn>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=subscribe>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org
> Indeed there is no valid semantic for S-PMSI Join packets received from > a CE. But a wrong semantic can very easily be given to such packets by > a implementation not having been carefully written in this respect, Implementation errors which cause packets to be processed with incorrect semantics can cause a variety of problems. However, we cannot expect the security considerations section to list all the things that an implementation could possibly get wrong. However, if it makes you happy, I suppose we could replace: If one uses the UDP-based protocol for switching to S-PMSI (as specified in Section 7.2.1), then by default each PE router MUST install packet filters that would result in discarding all UDP packets with the destination port 3232 that the PE router receives from the CE routers connected to the PE router. with The S-PMSI Join messages defined in section 7.4.2 are valid only when received over a PMSI, and MUST NOT be processed in other contexts.
- WG LC: draft-ietf-l3vpn-2547bis-mcast Danny McPherson
- Re: WG LC: draft-ietf-l3vpn-2547bis-mcast Thomas Morin
- Re: WG LC: draft-ietf-l3vpn-2547bis-mcast Thomas Morin
- Identifying an ingress PE in ingress replication … Xu Xiaohu
- re: Identifying an ingress PE in ingress replicat… Xu Xiaohu
- Re: Identifying an ingress PE in ingress replicat… Eric Rosen
- Re: WG LC: draft-ietf-l3vpn-2547bis-mcast Eric Rosen
- Re: WG LC: draft-ietf-l3vpn-2547bis-mcast Eric Rosen
- re: Identifying an ingress PE in ingress replicat… Xu Xiaohu
- Re: WG LC: draft-ietf-l3vpn-2547bis-mcast Thomas Morin
- Re: WG LC: draft-ietf-l3vpn-2547bis-mcast Thomas Morin
- Re: WG LC: draft-ietf-l3vpn-2547bis-mcast Eric Rosen
- Re: WG LC: draft-ietf-l3vpn-2547bis-mcast Thomas Morin
- Re: WG LC: draft-ietf-l3vpn-2547bis-mcast Eric Rosen
- Re: WG LC: draft-ietf-l3vpn-2547bis-mcast Thomas Morin
- Re: WG LC: draft-ietf-l3vpn-2547bis-mcast Mark Fine
- Re: WG LC: draft-ietf-l3vpn-2547bis-mcast-bgp Mark Fine