Re: [v6ops] [BEHAVE] protocols without need for ALG ?

Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 31 July 2015 16:52 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BFCE31A9148; Fri, 31 Jul 2015 09:52:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1
X-Spam-Level:
X-Spam-Status: No, score=-1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, J_BACKHAIR_37=1, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L2o8mUJOo7y3; Fri, 31 Jul 2015 09:52:09 -0700 (PDT)
Received: from mail-wi0-x22f.google.com (mail-wi0-x22f.google.com [IPv6:2a00:1450:400c:c05::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4C9C11A90C8; Fri, 31 Jul 2015 09:52:09 -0700 (PDT)
Received: by wicmv11 with SMTP id mv11so65162648wic.0; Fri, 31 Jul 2015 09:52:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=EaDaZgnl3owJfA8PKTFrawQv3rIC38OPVPQWHnb+oi0=; b=Bt+h3YAWIldiKHD00A5jF4/N1s02P99uBMN3rcp9ljFtRNo7JYxg3O/1koLkygmoBE 88l/rZj8h8vUDpmti4meO38KqaeuF4oYu/4FV7aaI8ZMVv85SO5ZyW9kU9liWWkf1XZG jp6rUMGkh+OsljrHde8JX+qL85b3vkY4IBJpZ1Z8ZWJe8tXNrkz9uCSoRnppmbu8My9W 2RK/s6Z9mV050tB8VJlrdjZrbjJQ4HMdYbQY7ykdutyli57n8XCsUOFExOhHcoFqORvA B1Dnio47FVXsTQlUtUgzadUV75a5hC3g+QMyZVEhz4C7N9KtA85MEr+NuD6EMrfbHzBe wmuA==
X-Received: by 10.194.123.4 with SMTP id lw4mr7494370wjb.94.1438361528128; Fri, 31 Jul 2015 09:52:08 -0700 (PDT)
Received: from [192.168.0.4] (cpc11-brig18-2-0-cust561.3-3.cable.virginm.net. [81.100.118.50]) by smtp.gmail.com with ESMTPSA id fs8sm8045444wjb.7.2015.07.31.09.52.07 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 31 Jul 2015 09:52:07 -0700 (PDT)
Message-ID: <55BBA7C1.3000502@gmail.com>
Date: Sat, 01 Aug 2015 04:52:17 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: Ca By <cb.list6@gmail.com>, Toerless Eckert <eckert@cisco.com>
References: <20150730205806.GI1667@cisco.com> <CAD6AjGSKc0jGSkgSKdMsY1gZwYYguJQ06f4nZsWEqBdR9J3e6w@mail.gmail.com>
In-Reply-To: <CAD6AjGSKc0jGSkgSKdMsY1gZwYYguJQ06f4nZsWEqBdR9J3e6w@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/AXyQD2-OgB7e22YJGTUHJimSRDM>
Cc: "v6ops@ietf.org" <v6ops@ietf.org>, "behave@ietf.org" <behave@ietf.org>
Subject: Re: [v6ops] [BEHAVE] protocols without need for ALG ?
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 Jul 2015 16:52:10 -0000

On 01/08/2015 01:37, Ca By wrote:
> On Thursday, July 30, 2015, Toerless Eckert <eckert@cisco.com> wrote:
> 
>> For autonomic networking (ANIMA WG), we are planning to rely only on IPv6
>> for initial
>> autonomic connectivity, and the question of connecting this (at least
>> initially)
>> to IPv4 only NOC equipment came up. Alas, IPv6 support in transport seems
>> to be still
>> weak on a range of commonly used NOC tools.
>>
>>
> Ehhh. For something as forward looking as anima , it is unfortunate that
> you believe you will need to bring this technical debt with you.

Yes, but we assume that during the phasing-in of autonomic operations,
we will be forced to interface to legacy NOCs. Personally I think I
disagree with NAT46 and NAT64 as the way to handle this, but Toerless
is asking the right questions in order to have this debate over on the
Anima list.

    Brian

> 
> My suggeation is that you require ipv6 for this case. If you do not shed
> this requirement now, you will carry it with you forever.
> 
> The iphone can require ipv6 apps, so can anima.
> 
> CB
> 
> 
>> If i understand the NAT RFCs and behave output correctly, we primaerily
>> want ALGs to go the way of the dodo, so i was wondering if there might be
>> any crucial protocols between typical NOC equipment and network devices
>> that
>> would require ALGs. And better of course:knowing which protocols would be
>> fine
>> without ALG.
>>
>> Are there any lists about this (eg: what requires ALG ?)
>>
>> Wrt to what seems to be important between NOC and network devices:
>>
>>    FTP     - NOK (requires ALG) - IMHO not a problem
>>    traceroute - ??  (initiated from v4 NOC) ??
>>    telnet  - OK
>>    ping    - OK ?
>>    SSH/SCP - OK
>>    syslog  - OK
>>    TFTP    - OK ?
>>    radius  - OK ? (i ran some tests, seemed to be fine)
>>    diameter/tacacs+ - OK ?
>>    NTP     - OK ???
>>
>>    For the following, that have extensible data-models (MIBs/OIDs, XML
>> schema etc.),
>>    i can see that some NOC tools relying on them might not support
>> data-models
>>    with IPv6, but that would be "fine" (aka: can't manage everything from
>> such tools,
>>    but transport stack works):
>>
>>    netconf - OK ?
>>    SNMP    - OK ?
>>
>> Whats the next most important NOC<->network management protocols... ?
>>
>> Thanks!
>>     Toerless
>>
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org <javascript:;>
>> https://www.ietf.org/mailman/listinfo/v6ops
>>
> 
> 
> 
> _______________________________________________
> Behave mailing list
> Behave@ietf.org
> https://www.ietf.org/mailman/listinfo/behave
>