Re: [pcp] #62: Client-driven or server-driven auth retransmissions
Simon Perreault <simon.perreault@viagenie.ca> Wed, 24 October 2012 14:29 UTC
Return-Path: <simon.perreault@viagenie.ca>
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 0855521F869A for <pcp@ietfa.amsl.com>; Wed, 24 Oct 2012 07:29:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.584
X-Spam-Level:
X-Spam-Status: No, score=-2.584 tagged_above=-999 required=5 tests=[AWL=0.016, BAYES_00=-2.599, NO_RELAYS=-0.001]
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 TtHPzlssrqbN for <pcp@ietfa.amsl.com>; Wed, 24 Oct 2012 07:29:54 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id 6414E21F85BF for <pcp@ietf.org>; Wed, 24 Oct 2012 07:29:54 -0700 (PDT)
Received: from porto.nomis80.org (unknown [IPv6:2620:0:230:c000:8891:30fb:d283:e7a7]) by jazz.viagenie.ca (Postfix) with ESMTPSA id C9BCF41A08 for <pcp@ietf.org>; Wed, 24 Oct 2012 10:29:52 -0400 (EDT)
Message-ID: <5087FB60.6060101@viagenie.ca>
Date: Wed, 24 Oct 2012 10:29:52 -0400
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121016 Thunderbird/16.0.1
MIME-Version: 1.0
To: pcp@ietf.org
References: <059.9cf5d7c12f5da883f5db53fb2786e69b@tools.ietf.org> <tslwqyggjxb.fsf@mit.edu>
In-Reply-To: <tslwqyggjxb.fsf@mit.edu>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
Subject: Re: [pcp] #62: Client-driven or server-driven auth retransmissions
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: Wed, 24 Oct 2012 14:29:55 -0000
Le 2012-10-24 07:59, Sam Hartman a écrit : > We could really use input from PCP implementations about whether having > the authentication retransmit timer on the client is easier than the > server. I can't say I understand all the technical details, but here's my view: Without auth, only PCP clients do retransmissions. Servers only reply to packets, so that's less state and load on PCP servers. It would be nice if we could keep it the way it is. My 2¢CAD... Simon -- DTN made easy, lean, and smart --> http://postellation.viagenie.ca NAT64/DNS64 open-source --> http://ecdysis.viagenie.ca STUN/TURN server --> http://numb.viagenie.ca
- [pcp] #62: Client-driven or server-driven auth re… pcp issue tracker
- Re: [pcp] #62: Client-driven or server-driven aut… Sam Hartman
- Re: [pcp] #62: Client-driven or server-driven aut… Yoshihiro Ohba
- Re: [pcp] #62: Client-driven or server-driven aut… Sam Hartman
- Re: [pcp] #62: Client-driven or server-driven aut… Simon Perreault
- Re: [pcp] #62: Client-driven or server-driven aut… Rafa Marin Lopez
- Re: [pcp] #62: Client-driven or server-driven aut… Alper Yegin
- Re: [pcp] #62: Client-driven or server-driven aut… Alper Yegin
- Re: [pcp] #62 (authentication): Client-driven or … pcp issue tracker