IETF Logo Mail Archive

Re: adding IUTF8 to encoded terminal modes in SSH Protocol Assigned Numbers

Chris Lonvick <clonvick@cisco.com> Fri, 29 March 2013 19:56 UTC

Return-Path: <bounces-ietf-ssh-owner-secsh-tyoxbijeg7-archive=lists.ietf.org@NetBSD.org>
X-Original-To: ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com
Delivered-To: ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9FC4F21F8EAA for <ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com>; Fri, 29 Mar 2013 12:56:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level:
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 0xs5R3wUiDYo for <ietfarch-secsh-tyoxbijeg7-archive@ietfa.amsl.com>; Fri, 29 Mar 2013 12:56:44 -0700 (PDT)
Received: from mail.netbsd.org (mail.NetBSD.org [IPv6:2001:4f8:3:7::25]) by ietfa.amsl.com (Postfix) with ESMTP id CADBF21F8786 for <secsh-tyoxbijeg7-archive@lists.ietf.org>; Fri, 29 Mar 2013 12:56:43 -0700 (PDT)
Received: by mail.netbsd.org (Postfix, from userid 605) id 1741514A269; Fri, 29 Mar 2013 19:56:41 +0000 (UTC)
Delivered-To: ietf-ssh@netbsd.org
Received: from localhost (localhost [127.0.0.1]) by mail.netbsd.org (Postfix) with ESMTP id 1071914A261 for <ietf-ssh@netbsd.org>; Fri, 29 Mar 2013 19:56:39 +0000 (UTC)
X-Virus-Scanned: amavisd-new at NetBSD.org
Authentication-Results: mail.NetBSD.org (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.netbsd.org ([127.0.0.1]) by localhost (mail.NetBSD.org [127.0.0.1]) (amavisd-new, port 10025) with ESMTP id GibiJpNXYcJ0 for <ietf-ssh@netbsd.org>; Fri, 29 Mar 2013 19:56:38 +0000 (UTC)
Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by mail.netbsd.org (Postfix) with ESMTPS id 2F65214A25E for <ietf-ssh@netbsd.org>; Fri, 29 Mar 2013 19:56:37 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=900; q=dns/txt; s=iport; t=1364586998; x=1365796598; h=date:from:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=T37x10zMOY9KERqhjvrT/n02zHQoFkRUAAC2rbdkzDA=; b=XaDbwmFd8IqNGOHNTwyVG3LOw8ZcOHCaYE2Dm3iSKbuNL8ee4woZd/U2 VrqGLEElHao0LjsxbBCTmsspSzBPdTzuQzpwEBJ6njwuPw1lPwE+kVTBU NsSzaisc+IQrmDD/JIhy1RsMBQkadsJQtsw4tH3tsjNiHTSRNftkGAeEJ g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EADPhVVGrRDoG/2dsb2JhbABDwmOBChZ0gh8BAQEDATgCPxALRlcGiCEFwAyPJweDQAOIep58gys
X-IronPort-AV: E=Sophos;i="4.87,374,1363132800"; d="scan'208";a="77028821"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-4.cisco.com with ESMTP; 29 Mar 2013 18:47:34 +0000
Received: from sjc-xdm-112 (sjc-xdm-112.cisco.com [171.71.188.44]) by mtv-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r2TIlX3h000354 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 29 Mar 2013 18:47:33 GMT
Date: Fri, 29 Mar 2013 11:47:33 -0700
From: Chris Lonvick <clonvick@cisco.com>
To: David Madore <david+generic@madore.org>
cc: Mouse <mouse@Rodents-Montreal.ORG>, ietf-ssh@NetBSD.org
Subject: Re: adding IUTF8 to encoded terminal modes in SSH Protocol Assigned Numbers
In-Reply-To: <20130329173208.GA27197@achernar.madore.org>
Message-ID: <alpine.LRH.2.00.1303291126350.22406@sjc-xdm-112.cisco.com>
References: <20130329125734.GA24915@achernar.madore.org> <201303291331.JAA24710@Sparkle.Rodents-Montreal.ORG> <20130329173208.GA27197@achernar.madore.org>
User-Agent: Alpine 2.00 (LRH 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
Sender: ietf-ssh-owner@NetBSD.org
List-Id: ietf-ssh.NetBSD.org
Precedence: list

Hi David,

On Fri, 29 Mar 2013, David Madore wrote:
<eliding some discussion>

>> Given what it is, in this case, I think the right way is to spec the
>> bit even in the absence of any ssh implementations actually using it.
>> (Not that I have any particular authority to do so.)
>
> I'm willing to try this, but I somehow success that somebody is going
> to say "you can't just appear out of nowhere and publish an Internet
> draft that says 'now number 42 will mean this' to have it added to the
> list".

That is the right way to do this.  I'll send you separately an xml2rfc 
template that you can fill in, with instructions on how to submit it to 
the ID repository.

Once you have published this as an Internet Draft, bring the discussion 
back to this group.  Update the draft if needed and I'll tell you what to 
do to get it published as an RFC.

Best regards,
Chris

v2.23.0 | Report a Bug | By Email