Dear all,
The reseller drafts were suggested to have more reviews in last IETF meeting.
All of the issues raised on the mailing list have been solved and updated in
the latest version. Any more review or comments on these two drafts are
appreciated.
Regarding the draft-ietf-regext-reseller,
Hi Linlin,
I must admit I haven’t compared the proposed reseller structure to that of a
registrar, but what happens when a reseller suddenly wants to become a
registrar (or a registrar that will become a reseller under a larger
registrar)? Use cases that I think happen regularly.
Is it just a m
Hi Antoin,
Thanks for your suggestion and I have some clarifications of your suggestion.
Actually in the reseller draft, we've thought the issue about registrar and
reseller objects. The reseller has pretty much the same attributes that would
be captured for a registrar if a registrar could be pr
Hi,
As a co-author of these drafts and the one that pushed for the independent
reseller object of “C”, I believe that “C” is the best choice with some
explanation included below.
The driving reason for the creation of the reseller draft(s) is to enable the
display of reseller information in RD
Hi James,
Thanks for your explanation.
You just remind me of the first version of draft-ietf-regext-reseller-ext,
we've put both ID and name in the extension. Then we found that there is no
mechnism to keep the correctness of ID and name updates. So only the ID was
kept in the latest version wh