IETF Logo Mail Archive

[kitten] Fwd: New Version Notification for draft-vanrein-dnstxt-krb1-05.txt

Rick van Rein <rick@openfortress.nl> Tue, 15 September 2015 14:39 UTC

Return-Path: <rick@openfortress.nl>
X-Original-To: kitten@ietfa.amsl.com
Delivered-To: kitten@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 99F961B32CA for <kitten@ietfa.amsl.com>; Tue, 15 Sep 2015 07:39:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 58guOfdBbLUg for <kitten@ietfa.amsl.com>; Tue, 15 Sep 2015 07:39:39 -0700 (PDT)
Received: from lb3-smtp-cloud3.xs4all.net (lb3-smtp-cloud3.xs4all.net [194.109.24.30]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CA7901B2CC5 for <kitten@ietf.org>; Tue, 15 Sep 2015 07:39:38 -0700 (PDT)
Received: from airhead.local ([83.161.146.46]) by smtp-cloud3.xs4all.net with ESMTP id HSfb1r00B10HQrX01SfcXx; Tue, 15 Sep 2015 16:39:36 +0200
Message-ID: <55F82DA5.10504@openfortress.nl>
Date: Tue, 15 Sep 2015 16:39:33 +0200
From: Rick van Rein <rick@openfortress.nl>
User-Agent: Postbox 3.0.11 (Macintosh/20140602)
MIME-Version: 1.0
To: "kitten@ietf.org" <kitten@ietf.org>
References: <20150915143628.21162.89108.idtracker@ietfa.amsl.com>
In-Reply-To: <20150915143628.21162.89108.idtracker@ietfa.amsl.com>
X-Enigmail-Version: 1.2.3
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/kitten/jBfAYzxM5YIJBdQvwutMMjmkSso>
Subject: [kitten] Fwd: New Version Notification for draft-vanrein-dnstxt-krb1-05.txt
X-BeenThere: kitten@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Common Authentication Technologies - Next Generation <kitten.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/kitten>, <mailto:kitten-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/kitten/>
List-Post: <mailto:kitten@ietf.org>
List-Help: <mailto:kitten-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/kitten>, <mailto:kitten-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Sep 2015 14:39:42 -0000

Friends,

I have posted a new version of the KREALM record definition,
incorporating the feedback on uses that were not Kerberos-specific.  It
is now very simple and straightforward.

If you guys are happy with this, I will jump back to DNSEXT and propose
it there, and push it forward to get an RRTYPE assigned.

I'm not sure how to proceed re. Kitten with this -- would you guys like
me to continue this document as an Individual Submission, or is it
better as a Kitten WG document?

Cheers,
 -Rick
> *From:* internet-drafts@ietf.org
> *Date:* 15 September 2015 16:36
> *To:* "Rick van Rein" <rick@openfortress.nl>, "Rick van Rein"
> <rick@openfortress.nl>
> *Subject:* New Version Notification for draft-vanrein-dnstxt-krb1-05.txt
> A new version of I-D, draft-vanrein-dnstxt-krb1-05.txt
> has been successfully submitted by Rick van Rein and posted to the
> IETF repository.
>
> Name:		draft-vanrein-dnstxt-krb1
> Revision:	05
> Title:		Declaring Kerberos Realm Names in DNS (KREALM)
> Document date:	2015-09-15
> Group:		Individual Submission
> Pages:		10
> URL:            https://www.ietf.org/internet-drafts/draft-vanrein-dnstxt-krb1-05.txt
> Status:         https://datatracker.ietf.org/doc/draft-vanrein-dnstxt-krb1/
> Htmlized:       https://tools.ietf.org/html/draft-vanrein-dnstxt-krb1-05
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-vanrein-dnstxt-krb1-05
>
> Abstract:
>    This specification defines a method to determine Kerberos realm names
>    for services that are known by their DNS name.  Currently, such
>    information can only be found in static mappings or through educated
>    guesswork.  DNS can make this process more flexible, provided that
>    DNSSEC is used to ensure authenticity of resource records.
>
>                                                                                   
>
>
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> The IETF Secretariat
>

v2.23.0 | Report a Bug | By Email