IETF Logo Mail Archive

Re: [BEHAVE] Last call: draft-ietf-behave-nat64-discovery-heuristic-09

<teemu.savolainen@nokia.com> Thu, 28 June 2012 10:09 UTC

Return-Path: <teemu.savolainen@nokia.com>
X-Original-To: behave@ietfa.amsl.com
Delivered-To: behave@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A82C21F85A3 for <behave@ietfa.amsl.com>; Thu, 28 Jun 2012 03:09:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 vQkAjlwE5aRp for <behave@ietfa.amsl.com>; Thu, 28 Jun 2012 03:09:01 -0700 (PDT)
Received: from mgw-da02.nokia.com (smtp.nokia.com [147.243.128.26]) by ietfa.amsl.com (Postfix) with ESMTP id D920C21F863D for <behave@ietf.org>; Thu, 28 Jun 2012 00:44:46 -0700 (PDT)
Received: from vaebh105.NOE.Nokia.com (in-mx.nokia.com [10.160.244.31]) by mgw-da02.nokia.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id q5S7igPY021382; Thu, 28 Jun 2012 10:44:43 +0300
Received: from smtp.mgd.nokia.com ([65.54.30.21]) by vaebh105.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Thu, 28 Jun 2012 10:44:51 +0300
Received: from 008-AM1MPN1-053.mgdnok.nokia.com ([169.254.3.74]) by 008-AM1MMR1-012.mgdnok.nokia.com ([65.54.30.21]) with mapi id 14.02.0283.004; Thu, 28 Jun 2012 09:44:41 +0200
From: teemu.savolainen@nokia.com
To: petithug@acm.org
Thread-Topic: [BEHAVE] Last call: draft-ietf-behave-nat64-discovery-heuristic-09
Thread-Index: AQHNVGW0nV8ELkaGokCA2SiRbffcqZcOEWiAgABrVvCAAB1igIAAv/wg
Date: Thu, 28 Jun 2012 07:44:40 +0000
Message-ID: <916CE6CF87173740BC8A2CE443096962043C9DC1@008-AM1MPN1-053.mgdnok.nokia.com>
References: <9B57C850BB53634CACEC56EF4853FF653B62BDA4@TK5EX14MBXW601.wingroup.windeploy.ntdev.microsoft.com> <9B57C850BB53634CACEC56EF4853FF653B66483D@TK5EX14MBXW604.wingroup.windeploy.ntdev.microsoft.com> <4FE250F5.5010505@acm.org> <916CE6CF87173740BC8A2CE443096962043AF580@008-AM1MPN1-053.mgdnok.nokia.com> <4FEA3758.40203@acm.org> <916CE6CF87173740BC8A2CE443096962043BF32C@008-AM1MPN1-052.mgdnok.nokia.com> <4FEB1317.1080905@acm.org> <916CE6CF87173740BC8A2CE443096962043BF6A2@008-AM1MPN1-052.mgdnok.nokia.com> <4FEB85C7.20903@acm.org>
In-Reply-To: <4FEB85C7.20903@acm.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.163.23.252]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginalArrivalTime: 28 Jun 2012 07:44:51.0231 (UTC) FILETIME=[E664DAF0:01CD5501]
X-Nokia-AV: Clean
Cc: behave@ietf.org, dthaler@microsoft.com
Subject: Re: [BEHAVE] Last call: draft-ietf-behave-nat64-discovery-heuristic-09
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/behave>, <mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>, <mailto:behave-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jun 2012 10:09:04 -0000

Marc,

> My point was that an existing algorithm should be used, instead of designing a
> new one.

That's the implementation specific option. Your (application) implementation can use STUN, or some HTTP-based proprietary scheme (for example),  if it likes with your own connectivity check server. We do not want to create new protocol dependencies/requirements here - and requiring STUN or similar would be one.

If it is too difficult to agree on default connectivity check protocol, we can just drop the default connectivity check out from the specification and state that if implementation wants assurances other than just trying to establish connections, the implementation can use their own connectivity check systems.

Best regards,

        Teemu

v2.39.1 | Report a Bug | By Email | System Status