Re: [PWE3] draft-ietf-pwe3-iccp interaction with draft-pw-redundancy-bit
Lizhong Jin <lizho.jin@gmail.com> Fri, 16 March 2012 15:05 UTC
Return-Path: <lizho.jin@gmail.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5CCBC21F879E; Fri, 16 Mar 2012 08:05:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.35
X-Spam-Level:
X-Spam-Status: No, score=-3.35 tagged_above=-999 required=5 tests=[AWL=0.248, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EyLvASEF5emj; Fri, 16 Mar 2012 08:05:13 -0700 (PDT)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 30F5621F8623; Fri, 16 Mar 2012 08:05:13 -0700 (PDT)
Received: by yenm5 with SMTP id m5so4872915yen.31 for <multiple recipients>; Fri, 16 Mar 2012 08:05:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=dSdRdW94PGpQ5ZHjbPfbz3mYLMPSYdk+JtYQTXLdL0I=; b=rjdIAG4TfJv1uDxCo97maHvDnkq1Q39pfk4GnjEvmoTnOcgRlOuyBKjcJA+cFubvoQ Fnpi12fYOoV+cIgi2GRyJ3y6pBMbbTDDi/fy5E+mjenlPFg77k/x7uNcBUJNlwiA8P// x/1ijIbJJYlLUGoZNxCzzad8KmE9oYPIiGwGb9ufx3T+4XurzVmZh1WeZZwO2eEhbauR 3x6UnD6eOsudCVESdtSA/WAlnFUXcPFVKdyOsvS0NZ5EH5Er3LGgif50nwd5/N8R9GD8 zHsQMJ2dOMH8F+sK239PxI79sBaRblwxLQlnp1YzpNAH0X2XHDvcQVbfXohtwOpRLnsP Yn6A==
MIME-Version: 1.0
Received: by 10.182.147.35 with SMTP id th3mr3435563obb.29.1331910312723; Fri, 16 Mar 2012 08:05:12 -0700 (PDT)
Received: by 10.60.39.129 with HTTP; Fri, 16 Mar 2012 08:05:12 -0700 (PDT)
Date: Fri, 16 Mar 2012 23:05:12 +0800
Message-ID: <CAH==cJy7zKacaxY34Am-APDsbf13OD3GOtBuUF3vZAEHb3Or7Q@mail.gmail.com>
From: Lizhong Jin <lizho.jin@gmail.com>
To: ssalam@cisco.com
Content-Type: multipart/alternative; boundary="f46d0444005410068e04bb5d89ee"
Cc: l2vpn@ietf.org, pwe3@ietf.org
Subject: Re: [PWE3] draft-ietf-pwe3-iccp interaction with draft-pw-redundancy-bit
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Mar 2012 15:05:14 -0000
Sorry, send again with correct mail subject. Lizhong 2012/3/16 Lizhong Jin <lizho.jin@gmail.com> > >> The ICCP draft does assume the use of the pw-redundancy-bit draft. Section >> 9.1.3 describes two modes of operation (depending on configuration): >> >> - When an external AC redundancy mechanism is in use, and is being >> synchronized among the PEs via ICCP. In this mode, PW state is not >> synchronized via ICCP and the Independent Mode of operation is used for PW >> state signaling. This guarantees that the AC and PW states are always in >> sync for a given PE (to avoid deadlock). >> >> - When an external AC redundancy mechanism is not in use, then PW state is >> synchronized via ICCP. In this mode, either the Independent mode or the >> Master/Slave mode could be used for PW state signaling. >> > [Lizhong] and if independent mode is applied, the the operator MUST be > care to configure same high/low PW priority at two end-points of > active/standby PW, otherwise, will result two standby PW. More details > are in draft-liu-l2vpn-vpls-inter-domain-redundancy-02 section 5. > > Regards > Lizhong > > > > We will add clarifications to that effect in a future revision. > > Regards, > Samer > > > On 12-03-15 4:38 AM, "Daniel Cohn" <DanielC@orckit.com> wrote: > > > Hi draft-ietf-pwe3-iccp authors and list at large, > > > > Is there a reason why the ICCP draft does not explicit reference the pw > > redundancy draft? It does mention active/standby signaling for the PWs, > so > > implicitly it seems to assume that the other endpoint is implementing > > draft-pw-redundancy-bit, but in that case some details are missing such > as > > which pw redundancy mode should be used (e.g. master/slave), how PW > precedence > > should be configured, etc. > > > > Is this something you plan to add in future revisions? > > > > Thanks, > > > > Daniel > > > > > > > > _______________________________________________ > > pwe3 mailing list > > pwe3@ietf.org > > https://www.ietf.org/mailman/listinfo/pwe3 > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://www.ietf.org/mail-archive/web/pwe3/attachments/20120315/91462e58/attachment.htm > > > > ------------------------------ >
- [PWE3] draft-ietf-pwe3-iccp interaction with draf… Daniel Cohn
- Re: [PWE3] draft-ietf-pwe3-iccp interaction with … Samer Salam
- Re: [PWE3] draft-ietf-pwe3-iccp interaction with … Thomas Nadeau
- Re: [PWE3] draft-ietf-pwe3-iccp interaction with … Lizhong Jin
- Re: [PWE3] draft-ietf-pwe3-iccp interaction with … Luca Martini