<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
--></style>
</head>
<body class='hmmessage'>
> Uh, yes. If dynamic update is configured to require that an<br>> RRSET (from the viewpoint of IDNA, a label) is already present,<br>> then one has a lookup situation. If it is configured for the<br>> "RRSET does not exist" or "Name not in use" cases, then one has<br>> a registration situation. That said, my personal recommendation<br>> would be to use the more conservative Registration rules any<br>> time one is going to start modifying DNS zones rather than<br>> simply looking something up. But the WG has not discussed this<br>> topic. If people are convinced that something must be said on<br>> the subject, we will need to have that discussion.<br><br>I do think that something needs to be said about this, since<br>the issue has come up in implementation. For example, based on<br>the distinction above, a client handling a dynamic update on<br>its own using TKEY would implement the lookup protocol,<br>whereas a DHCP server handling a dynamic update on behalf of<br>the client might implement the registration protocol.<br> </body>
</html>