Re: [pcp] WGLC: draft-ietf-pcp-base-12.txt
Francis Dupont <Francis.Dupont@fdupont.fr> Tue, 07 June 2011 19:27 UTC
Return-Path: <Francis.Dupont@fdupont.fr>
X-Original-To: pcp@ietfa.amsl.com
Delivered-To: pcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B0C811E8214 for <pcp@ietfa.amsl.com>; Tue, 7 Jun 2011 12:27:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YvpF0+9AUWQE for <pcp@ietfa.amsl.com>; Tue, 7 Jun 2011 12:27:25 -0700 (PDT)
Received: from givry.fdupont.fr (givry.fdupont.fr [IPv6:2001:41d0:1:6d55:211:5bff:fe98:d51e]) by ietfa.amsl.com (Postfix) with ESMTP id 8871211E8225 for <pcp@ietf.org>; Tue, 7 Jun 2011 12:27:24 -0700 (PDT)
Received: from givry.fdupont.fr (localhost [127.0.0.1]) by givry.fdupont.fr (8.14.3/8.14.3) with ESMTP id p57JPowg060680; Tue, 7 Jun 2011 21:25:50 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201106071925.p57JPowg060680@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Dan Wing <dwing@cisco.com>
In-reply-to: Your message of Sat, 04 Jun 2011 17:49:25 PDT. <04d801cc231a$6b2747c0$4175d740$@com>
Date: Tue, 07 Jun 2011 21:25:50 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: pcp@ietf.org
Subject: Re: [pcp] WGLC: draft-ietf-pcp-base-12.txt
X-BeenThere: pcp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PCP wg discussion list <pcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pcp>, <mailto:pcp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pcp>
List-Post: <mailto:pcp@ietf.org>
List-Help: <mailto:pcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pcp>, <mailto:pcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jun 2011 19:27:25 -0000
In your previous mail you wrote: If the NAT is EIM, it will reuse the same mapping it already has. Because that is the definition of being a EIM NAT. => this is a misconception: it can use it as to convert an implicit dynamic EIM/EIF mapping into an explicit dynamic mapping is more than easy but this doesn't mean it is the only way or there cannot be some constraint forbidding this. In particular when the explicit dynamic mappings use a different external port set (*). Regards Francis.Dupont@fdupont.fr PS (*): resource management is a good reason to split the external port space. Or the legal logging: explicit dynamic mappings have far longer lifetimes so the usual trick to log only the allocation of implicit mapping port sets is not adapted...
- Re: [pcp] WGLC: draft-ietf-pcp-base-12.txt Dan Wing
- Re: [pcp] WGLC: draft-ietf-pcp-base-12.txt Paul Selkirk
- [pcp] WGLC: draft-ietf-pcp-base-12.txt Dave Thaler
- Re: [pcp] WGLC: draft-ietf-pcp-base-12.txt Alain Durand
- Re: [pcp] WGLC: draft-ietf-pcp-base-12.txt Dave Thaler
- Re: [pcp] WGLC: draft-ietf-pcp-base-12.txt Tina Tsou
- Re: [pcp] WGLC: draft-ietf-pcp-base-12.txt Dan Wing
- Re: [pcp] WGLC: draft-ietf-pcp-base-12.txt Stuart Cheshire
- Re: [pcp] WGLC: draft-ietf-pcp-base-12.txt Tina Tsou
- [pcp] PCP Issue #24, PCP mappings same public IP … Dan Wing
- Re: [pcp] WGLC: draft-ietf-pcp-base-12.txt Francis Dupont
- Re: [pcp] PCP Issue #24, PCP mappings same public… Tina Tsou