[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


To: "Klaus Malorny" <Klaus.Malorny@knipp.de>
Cc: <ietf-provreg@cafax.se>
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
Date: Tue, 11 Jul 2006 07:19:00 -0400
Content-class: urn:content-classes:message
Sender: owner-ietf-provreg@cafax.se
Thread-Index: AcakY51WGrqUmWubToysJ755x8al+wAeBk4g
Thread-Topic: [ietf-provreg] extensding EPP <update> command for contact
Subject: RE: [ietf-provreg] extensding EPP <update> command for contact

> -----Original Message-----
> From: Klaus Malorny [mailto:Klaus.Malorny@knipp.de] 
> Sent: Monday, July 10, 2006 4:58 PM
> To: janusz
> Cc: Hollenbeck, Scott; ietf-provreg@cafax.se
> Subject: Re: [ietf-provreg] extensding EPP <update> command 
> for contact
> 
> janusz wrote:
> > Scott,
> > [...]
> > The same section in domain object mapping document contains 
> a provision 
> > for EPP domain <update> commands without any element to modify.
> > [...]
>  >
> > Janusz Sienkiewicz
> > 
> 
> While it is possible in the domain mapping (RFC 3731) to 
> legally create an 
> update command that does nothing, there is still a sentence 
> that requires 
> unnecessary XML (page 27, third paragraph from bottom):
> 
>     At least one <domain:add>, <domain:rem>, or <domain:chg> 
> element MUST
>     be provided.
> 
> So, RFC 3731 should be included in your considerations. When 
> we discovered this 
> problem last year we decided to simply ignore this MUST in our server 
> implementation and to do not reject the command if such a 
> condition occurs. I 
> don't see a reason for the prohibition of an "empty" update anyway.

Also fixed in 3731bis.

-Scott-


Home | Date list | Subject list