Re: [provreg] EPP Domain Contacts
Alexander Mayrhofer <alexander.mayrhofer@nic.at> Wed, 04 December 2013 07:55 UTC
Return-Path: <alexander.mayrhofer@nic.at>
X-Original-To: provreg@ietfa.amsl.com
Delivered-To: provreg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com
(Postfix) with ESMTP id 7B8301AE070 for <provreg@ietfa.amsl.com>;
Tue, 3 Dec 2013 23:55:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.731
X-Spam-Level:
X-Spam-Status: No,
score=-5.731 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,
HELO_EQ_AT=0.424, HOST_EQ_AT=0.745, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5,
RP_MATCHES_RCVD=-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 oFfPPL2NesVs for
<provreg@ietfa.amsl.com>; Tue, 3 Dec 2013 23:55:16 -0800 (PST)
Received: from mail.sbg.nic.at (mail.sbg.nic.at [83.136.33.227]) by
ietfa.amsl.com (Postfix) with ESMTP id 867071AE03C for <provreg@ietf.org>;
Tue, 3 Dec 2013 23:55:14 -0800 (PST)
Received: from nics-exch2.sbg.nic.at ([10.17.175.6]) by mail.sbg.nic.at over
TLS secured channel (TLSv1:AES128-SHA:128) with XWall v3.49 ;
Wed, 4 Dec 2013 08:55:11 +0100
Received: from NICS-EXCH2.sbg.nic.at ([fe80::a5b2:6e42:e54d:9d57]) by
NICS-EXCH2.sbg.nic.at ([fe80::a5b2:6e42:e54d:9d57%12]) with mapi id
14.03.0158.001; Wed, 4 Dec 2013 08:55:08 +0100
From: Alexander Mayrhofer <alexander.mayrhofer@nic.at>
To: Mike O'Connell <mcanix@gmail.com>, "provreg@ietf.org" <provreg@ietf.org>
Thread-Topic: [provreg] EPP Domain Contacts
Thread-Index: AQHO8K+SVURXwgYRaU+hIJnaX0G7o5pDqqdg
Date: Wed, 4 Dec 2013 07:55:06 +0000
Message-ID: <19F54F2956911544A32543B8A9BDE0750A3C7274@NICS-EXCH2.sbg.nic.at>
References: <07F9FB60-1BAE-4AB9-A6DC-5BA2F3283096@gmail.com>
In-Reply-To: <07F9FB60-1BAE-4AB9-A6DC-5BA2F3283096@gmail.com>
Accept-Language: en-US, de-DE
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.10.0.163]
Content-Type: multipart/alternative;
boundary="_000_19F54F2956911544A32543B8A9BDE0750A3C7274NICSEXCH2sbgnic_"
MIME-Version: 1.0
X-XWALL-BCKS: auto
Subject: Re: [provreg] EPP Domain Contacts
X-BeenThere: provreg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: EPP discussion list <provreg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/provreg>,
<mailto:provreg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/provreg/>
List-Post: <mailto:provreg@ietf.org>
List-Help: <mailto:provreg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/provreg>,
<mailto:provreg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Dec 2013 07:55:18 -0000
In the gTLD configuration of our Registry, we do require the contact type to be either "tech" or "admin". We don't allow for "billing" type contacts, since any billing goes via the registrar. Alex Von: provreg [mailto:provreg-bounces@ietf.org] Im Auftrag von Mike O'Connell Gesendet: Mittwoch, 04. Dezember 2013 06:13 An: provreg@ietf.org Betreff: [provreg] EPP Domain Contacts All, I came across an issue the other day around Domain Contacts, specifically, the domain contact element contains an optional attribute 'type' which can be one of [tech, billing, admin]. The problem here is that the attribute is optional with no assumed default. 1. Does anybody use the domain contact element without the 'type' attribute? 2. Does anybody use a default value for the 'type' attribute when it is not provided? Apologies if this is a old/duplicate topic. Regards, Mike -- If you don't know where you are going, any road will get you there.
- [provreg] EPP Domain Contacts Mike O'Connell
- Re: [provreg] EPP Domain Contacts Corey Goldfeder
- Re: [provreg] EPP Domain Contacts Mike O'Connell
- Re: [provreg] EPP Domain Contacts Alexander Mayrhofer
- Re: [provreg] EPP Domain Contacts Patrik Fältström