Hi Ed,
On 4/8/2021 3:36 PM, Edward Shryane via db-wg wrote:
Hi Jori,
On 8 Apr 2021, at 14:42, Tyrasuki wrote:
Hi Ed,
This seems like a good implementation to me.
However, I don't think it's a good idea to limit the values on the "remarks"
attribute in this way, as this could cause
Hi Jori,
> On 8 Apr 2021, at 14:42, Tyrasuki wrote:
>
> Hi Ed,
>
> This seems like a good implementation to me.
>
> However, I don't think it's a good idea to limit the values on the "remarks"
> attribute in this way, as this could cause unwanted side effects with for ex.
> messages left on
Colleagues
For the benefit of those who don't often check the mail archives of
the RIPE Database Task Force there have been 4 meetings in February
and March and the TF has just published the minutes of their most
recent meeting on their mail archive which can be found here:
Hi Denis,
On Thu, Apr 08, 2021 at 12:55:32AM +0200, denis walker via db-wg wrote:
> I don't see the issue of what, if anything, should be validated as a
> show stopper for introducing the "geofeed:" attribute. This is my idea
> of utilising the RIRs to improve the value of services with increased
On Thu, Apr 08, 2021 at 02:27:13PM +0200, Edward Shryane via db-wg wrote:
> > On 8 Apr 2021, at 13:54, Randy Bush via db-wg wrote:
> >
> >> Could we consider creating an NWI with a reduced scope?
> >
> > as an exercise, how minimal can we get?
>
> Given the draft RFC:
>
Hi Ed,
This seems like a good implementation to me.
However, I don't think it's a good idea to limit the values on the "remarks"
attribute in this way, as this could cause unwanted side effects with for ex.
messages left on objects for other network operators.
Also:
> "Do not support
Hi Randy,
> On 8 Apr 2021, at 13:54, Randy Bush via db-wg wrote:
>
>> Could we consider creating an NWI with a reduced scope?
>
> as an exercise, how minimal can we get?
>
> randy
>
Given the draft RFC:
https://datatracker.ietf.org/doc/draft-ietf-opsawg-finding-geofeeds/?include_text=1
I
> Could we consider creating an NWI with a reduced scope?
as an exercise, how minimal can we get?
randy
Dear Working Group,
RIPE Database release 1.100 has been deployed to the Release Candidate
environment. We plan to deploy to production on Thursday 22nd April.
This release includes the following main changes:
* Separate email address and leading/trailing space during Punycode conversion
