<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<font size="+1"><tt>Hi George<br>
<br>
</tt></font>
<div class="moz-cite-prefix">On 11/06/2014 04:55, George Michaelson
wrote:<br>
</div>
<blockquote
cite="mid:CAA=nHSLyDTpHAQ5Cg+axqZ7-om6WcFkWdAhdbNzkhGRWTVVr7w@mail.gmail.com"
type="cite">
<meta http-equiv="Context-Type" content="text/html; charset=UTF-8">
<div dir="ltr">I am trying to understand how this change could
{help,hinder} the APNIC problem of route objects which reference
differently maintained AS and Inetnum objects, and the added
complication of AS being vested from RIPE and Inetnum from
APNIC.
<div>
<br>
</div>
<div>I think stripping/changing the notify-on-ref mail might
hinder this. It would be materially useful to preserve it,
should exported IRR state be used at another site aggregating
data, to contact the prime information manager.</div>
</div>
</blockquote>
I think you are mixing up notifications with contacts here.
Notifications are usually a list of one or more people who want to
be notified when something changes. They may not be the same people
as the admin-c, tech-c, abuse-c contacts who you would talk to if
you have any issues/questions, who may also be different to the
maintainers of the data.<br>
<br>
<blockquote
cite="mid:CAA=nHSLyDTpHAQ5Cg+axqZ7-om6WcFkWdAhdbNzkhGRWTVVr7w@mail.gmail.com"
type="cite">
<div dir="ltr">
<div><br>
</div>
<div>I suspect RPSS/RPSAUTH issues are out of scope. Within one
IRR/RPSL data set, I think the notify-on-ref thing would help
the APNIC problem: it would make it easier for non-related
maintainer to understand changes were being made in routing by
address holders who want their AS to be in a route object, and
participate.</div>
</div>
</blockquote>
This sounds like you want this notification to be sent if an ASN is
associated with a ROUTE object. I presume you don't mean in the
"origin:" as this has already been authorised by the ASN holder, so
they already know of the association. Or do you want to cover the
option of more than the maintainer of the AUT-NUM object wanting to
know of the association?<br>
<br>
There are other attributes in a ROUTE object that can reference an
ASN, "aggr-mtd:" and "aggr-bndry:". So do you want this notification
to be triggered by a reference here?<br>
<br>
Regards<br>
Denis Walker<br>
Business Analyst<br>
RIPE NCC Database Team<br>
<br>
<blockquote
cite="mid:CAA=nHSLyDTpHAQ5Cg+axqZ7-om6WcFkWdAhdbNzkhGRWTVVr7w@mail.gmail.com"
type="cite">
<div dir="ltr">
<div><br>
</div>
<div>-George</div>
<div><br>
</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Wed, Jun 11, 2014 at 5:13 AM, Sander
Steffann <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:sander@steffann.nl" target="_blank">sander@steffann.nl</a>></span>
wrote:<br>
<blockquote class="gmail_quote">Hi Job,<br>
<div class=""><br>
> I think some notification feature would be nice to
have, but we need to<br>
> figure out what and when we expect notifications.<br>
><br>
</div>
<div class="">> I propose we dub the attribute for nice
alignment with existing<br>
> attributes:<br>
><br>
> notify-on-ref: <email-address>
optional, multi-valued<br>
><br>
</div>
<div class="">> Questions:<br>
><br>
> - do you want a notification each time an object
is updated and has<br>
> a reference to your object?<br>
<br>
</div>
Strong no<br>
<div class=""><br>
> - or do you only want notifications when a
reference inititally is<br>
> added to an object? (spares you a daily mailbomb
for daily updated<br>
> objects)<br>
<br>
Yes<br>
<br>
</div>
<div class="">> - do you want a notification when the
reference is removed from an<br>
> object?<br>
<br>
Yes<br>
<br>
</div>
<div class="">> - In what classes do you want to set a
notify-on-ref attribute? (I<br>
</div>
> think initially aut-num, as-set, rd-set)<br>
<br>
Ack<br>
<div class=""><br>
> - do we want the notify-on-ref email addresses to
be set to<br>
> <a moz-do-not-send="true"
href="mailto:unread@ripe.net">unread@ripe.net</a> upon
NRTM/ftp export?<br>
<br>
</div>
No strong opinion on this one. I would say yes, unless
someone comes up with a reason not to.<br>
<div class=""><br>
> Regarding authorisation, for me requiring
authorisation to reference a<br>
> given object is a bridge too far at this point in
time. Quite some<br>
> operators automatically generate an autnum,
route-sets & as-sets on a<br>
> daily basis to reject their policy, and I don't see
an easy way to make<br>
> this a painless adventure. Let's first do
notifications and based on<br>
> those experiences look further. ok?<br>
<br>
</div>
Yes, that sounds reasonable. Needing authorisation to be
allowed to put information in the policy sounds like a good
way to discourage people from updating/using them
altogether. Let's not make things more difficult unless we
really need to.<br>
<br>
Cheers!<br>
<span class="HOEnZb">Sander<br>
<br>
<br>
</span></blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</body>
</html>