IETF Logo Mail Archive

[Netconf] Re:  WGLC for draft-ietf-netconf-t ls-04.txt

badra@isima.fr Sat, 27 September 2008 15:54 UTC

Return-Path: <netconf-bounces@ietf.org>
X-Original-To: netconf-archive@ietf.org
Delivered-To: ietfarch-netconf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 961E13A6A03; Sat, 27 Sep 2008 08:54:52 -0700 (PDT)
X-Original-To: netconf@core3.amsl.com
Delivered-To: netconf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AEDDE3A69E3 for <netconf@core3.amsl.com>; Sat, 27 Sep 2008 08:54:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.545
X-Spam-Level:
X-Spam-Status: No, score=-0.545 tagged_above=-999 required=5 tests=[AWL=-0.607, BAYES_20=-0.74, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3, SARE_SUB_ENC_UTF8=0.152]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v7SEQK97pLDq for <netconf@core3.amsl.com>; Sat, 27 Sep 2008 08:54:51 -0700 (PDT)
Received: from sp.isima.fr (sp.isima.fr [193.55.95.1]) by core3.amsl.com (Postfix) with ESMTP id B89723A68F0 for <netconf@ietf.org>; Sat, 27 Sep 2008 08:54:50 -0700 (PDT)
Received: from www.isima.fr (www-data@www.isima.fr [193.55.95.79]) by sp.isima.fr (8.13.8/8.13.8) with SMTP id m8RGsRjm1040470; Sat, 27 Sep 2008 17:54:27 +0100
Received: from 88.164.98.77 (SquirrelMail authenticated user badra) by www.isima.fr with HTTP; Sat, 27 Sep 2008 17:53:29 +0200 (CEST)
Message-ID: <61122.88.164.98.77.1222530809.squirrel@www.isima.fr>
In-Reply-To: <20080927154119.GA803@elstar.local>
References: <20080927090622.GA431@elstar.local> <59304.88.164.98.77.1222523373.squirrel@www.isima.fr> <20080927154119.GA803@elstar.local>
Date: Sat, 27 Sep 2008 17:53:29 +0200
From: badra@isima.fr
To: j.schoenwaelder@jacobs-university.de
User-Agent: SquirrelMail/1.4.2
MIME-Version: 1.0
X-Priority: 3
Importance: Normal
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (sp.isima.fr [193.55.95.1]); Sat, 27 Sep 2008 17:54:27 +0100 (WEST)
Cc: � <netconf@ietf.org>
Subject: [Netconf] Re:  WGLC for draft-ietf-netconf-t ls-04.txt
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Network Configuration WG mailing list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/netconf>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: netconf-bounces@ietf.org
Errors-To: netconf-bounces@ietf.org

> On Sat, Sep 27, 2008 at 03:49:33PM +0200, badra@isima.fr wrote:
>> > On Sat, Sep 27, 2008 at 02:05:51PM +0800, fanhuaxiang 90002624 wrote:

> Can someone explain to me _why_ all this detail is needed? The SSH
> transport mapping does not spell how how the SSH teardown is done.
> So why do we need to be that specific with TLS?
>
> /js


Well, I think we can find the same text in all "Application over TLS"
documents, and there was no objection on integrating such text in those
documents, which can IMO improve the readability.

Please don't hesitate to propose your text (to the Connection Closure
Section) if you prefer to don't have this detail.

Best regards
Badra
_______________________________________________
Netconf mailing list
Netconf@ietf.org
https://www.ietf.org/mailman/listinfo/netconf

v2.23.0 | Report a Bug | By Email