2914:429 is a community to signal to NTT to not announce the route to peers
which would perhaps be why you don't see NTT doing that.
You can see the documented NTT communities here:
http://www.us.ntt.net/support/policy/routing.cfm
Jared Mauch
On Jan 7, 2015, at 5:35 AM, Song Li
If only we could create a committee to fix whois...
Quite astonishingly, the IETF WEIRDS working group finished
successfully, and its documents will be published as RFCs when they
get through the editing queue in a month or two. The protocol is
called RDAP, the queries are http, the results are
http://rdap.apnic.net/
redirects to a web page documenting service
http://rdap.apnic.net/ip shows a json error response
http://rdap.apnic.net/ip/203.119.0.0/24
shows the /24 record for 203.119.0.0/24
-G
On Thu, Jan 8, 2015 at 1:59 PM, shawn wilson ag4ve...@gmail.com wrote:
On Wed, Jan 7,
Thanks Frank... I do have a customer with 500 meg/sec service running 350
meg/sec average all day just 800 employees - no company driven focused
use of MS office 365.
Applications used and time of day, etc. So, I don't think one can compare
a college's overall app bandwidth usage to a
Looking for a HostGator contact, off-list
ARIN, APNIC, and RIPE have prototypes already that are a lot easier to
script than the text WHOIS.
Meaning the data structure is in place or they have a RDAP service up?
Both. ARIN's and RIPE's are based on early versions so the URLs and JSON
aren't quite what RDAP says they should be yet.
Thanks Jimmy - I agree - It's pretty much what we do today...it's just
this one customer wanted Office 365 specific details. I don't think anyone
knows. Including Microsoft, app creator.
Wonder when Cloud providers get a clue, step up and help recommend a
circuit size based on users and the
On Wed, Jan 7, 2015 at 10:22 PM, John Levine jo...@iecc.com wrote:
ARIN, APNIC, and RIPE have prototypes already that are a lot easier to
script than the text WHOIS.
Meaning the data structure is in place or they have a RDAP service up?
If so, is it publicly accessible?
On Wed, Jan 7, 2015 at 11:23 PM, John R. Levine jo...@iecc.com wrote:
Google is your friend.
Woops, you're right
On Tue, Jan 6, 2015 at 2:37 PM, Bob Evans b...@fiberinternetcenter.com wrote:
[snip]
Does anyone have any experience with Office 365 hosted that can tell me
the practical bandwidth allocation (NOT in KB per month, but in
Most likely in the real world where packets don't line up neatly... O365
Scripting languages have modules that can parse many registrar whois
formats. However, most are incomplete due to the plurality of output
formats as stated above. I, and i suspect many others, wouls *love* to see
a more concrete key value format drafted and enforced by ICANN.
-AK
On Jan 7, 2015
On 07/01/2015 20:07, Bill Woodcock wrote:
Correct. It gets you a blob of text. Sometimes, a blob is just a blob.
Other times, it contains what _appear_ to be key-value pairs, but are
instead loosely-formatted text. Other times, it contains
textually-represented key-value pairs that are
So, you’re not running into a poorly-documented mystery, you’ve run
afoul of one of the rotten armpits of the shub-Internet.
So there's no consensus between NICs for the information they should
have in whois and what search mechanisms they should provide? I guess
what you're saying is
On Wed, Jan 7, 2015 at 3:32 PM, anthony kasza anthony.ka...@gmail.com wrote:
Scripting languages have modules that can parse many registrar whois
formats. However, most are incomplete due to the plurality of output formats
as stated above. I, and i suspect many others, wouls *love* to see a
On Wed, Jan 7, 2015 at 3:07 PM, Bill Woodcock wo...@pch.net wrote:
So, you’re not running into a poorly-documented mystery, you’ve run afoul
of one of the rotten armpits of the shub-Internet.
So there's no consensus between NICs for the information they should
have in whois and what search
This is not the response I was looking for (and reading the RFC makes
me feel even worse).
Is there a better mechanism for querying NICs for host/owner information?
There will be, one day. And the start (although not the whole journey) will
be when this I-D follows the standard path all the
On 1/7/15 12:48 PM, Nick Hilliard wrote:
On 07/01/2015 20:07, Bill Woodcock wrote:
Correct. It gets you a blob of text. Sometimes, a blob is just a blob.
Other times, it contains what _appear_ to be key-value pairs, but are
instead loosely-formatted text. Other times, it contains
Thanks to those of you that answered...It is hypotheticalHowever, I
found another customer that uses Office 365 heavily ... said they
discovered 1 meg/sec per Microsoft Office 365 user works well in most
scenarios. This customer has 80 users and a 100 meg/sec connection with
us.
Thank You
On Wed, Jan 7, 2015 at 1:53 PM, Bill Woodcock wo...@pch.net wrote:
On Jan 7, 2015, at 10:38 AM, shawn wilson ag4ve...@gmail.com wrote:
Is there a list of NIC (and other popular whois server) features (what
can be searched on) and what data they provide (and what title they
give it)?
Heh,
So, you’re not running into a poorly-documented mystery, you’ve run afoul of
one of the rotten armpits of the shub-Internet.
So there's no consensus between NICs for the information they should
have in whois and what search mechanisms they should provide? I guess
what you're saying is that
On Wed, Jan 7, 2015 at 9:29 AM, Jared Mauch ja...@puck.nether.net wrote:
2914:429 is a community to signal to NTT to not announce the route to peers
which would perhaps be why you don't see NTT doing that.
it looks like this is the 'customer' of several networks (701, 2914)
and they just
Also note there is nothing stopping anyone from adding any community
they want.
The effect and how long the community stays attached to a route is
another matter.
On 1/7/2015 8:35 AM, Song Li wrote:
Hi everyone,
Today when I check one route in Routeviews I find something strange as
Hi,
Scripting languages have modules that can parse many registrar whois
formats. However, most are incomplete due to the plurality of output
formats as stated above. I, and i suspect many others, wouls *love* to see
a more concrete key value format drafted and enforced by ICANN.
ICANN can
Is there anyone from RADB or MerIt on this list that could contact me off
the list?
John
CRISP is dead. RDAP is real. If people need to script, then RDAP is
workable JSON and for once, has converged on sensible stuff in both names
and numbers.
the whois problem is a formalism owned by ICANN, but as DRC pointed out
the WHOIS solution is dispersed.
RPSL lies to one side btw. I wish
Thanks!
Because there is no standard syntax on the description of BGP community,
I think the problem is hard to understand.
在 2015/1/7 23:25, joel jaeggli 写道:
2914:429 is ntt's do not advertise to any peer community
bgp communities are transitive attributes, e.g. you can just pass them
to
[ Apologies if you saw this elsewhere already - jtk ]
Friends, colleagues, fellow operators,
The network security track, formerly known as the ISP security BoF,
will be on the agenda at NANOG 63 in San Antonio and I will be the track
facilitator.
We not only seek your participation, but we are
Is there a list of NIC (and other popular whois server) features (what
can be searched on) and what data they provide (and what title they
give it)?
A quick search yields:
http://www.ripe.net/ripe/docs/ripe-358
https://www.arin.net/resources/whoisrws/whois_diff.html
On Jan 7, 2015, at 10:38 AM, shawn wilson ag4ve...@gmail.com wrote:
Is there a list of NIC (and other popular whois server) features (what
can be searched on) and what data they provide (and what title they
give it)?
Heh, heh, heh. There are just about as many whois output formats as
Hi everyone,
Today when I check one route in Routeviews I find something strange as
follows:
route-viewssh ip bgp 176.108.0.0
BGP routing table entry for 176.108.0.0/19, version 23405621
Paths: (33 available, best #28, table default)
Not advertised to any peer
Refresh Epoch 1
202018
2914:429 is ntt's do not advertise to any peer community
bgp communities are transitive attributes, e.g. you can just pass them
to peers unmolested. so someone that's presumably not ntt ( e.g. the
neighbor is digital ocean) is sending that commmunity to route views as
part of their export.
31 matches
Mail list logo
