Custom query (1019 matches)
Results (49 - 51 of 1019)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#919 | not broken | noc@ietf.org | ||
Description |
the meeting wiki front page (not the network page) says report trouble to noc@ietf.org. i am aware of at least one user, jen linova of google, who sent a report to that email address. it seems to have gone into a black hole. is noc@ietf.org equivalent to action@ietf.org, i.e. for reporting a problem with any part of the organizational infrastructure, or just the meeting? should it forward to tickets@meeting.ietf.org? to action@ietf.org? ... randy |
|||
#921 | not broken | Testing ticket forwarding | ||
Description |
Simply a message to test the email forwarding of noc@ietf.org to tickets@meeting.ietf.org *James Dishongh* Senior Network Engineer Verilan, Inc. 7327 SW Barnes Rd. #215 Portland, OR 97225 +1 360.907-9237 [mobile] jdishongh@verilan.com [email] jdishongh.verilan [skype] www.verilan.com [website] This e-mail contains proprietary information and may be confidential. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this message is strictly prohibited. If you received this message in error, please delete it immediately. |
|||
#988 | not broken | IPv6 connectivity | ||
Description |
I'm gathering from my trace routes that we're using some sort of tunnel for IPv6. While I understand that sometimes tunnels are unavoidable (shame on you L3!), is there any way that a secondary or replacement tunnel can be terminated a little closer to our actual geographic/IPv4 path (e.g. Miami), rather than in LA in order to avoid some of the tunnel-induced stretch? Those of us trying to reach things over IPv6 on the East coast of the US (or worse, Europe) could do without the extra transcontinental hop. Hurricane has tunnel termination endpoints in many locations that would be advantageous, and support BGP. https://tunnelbroker.net/ dhcp-b376:~ e158182$ traceroute6 2610:178:8::1 traceroute6 to 2610:178:8::1 (2610:178:8::1) from 2001:67c:370:176:1802:fd28:21ad:f998, 64 hops max, 12 byte packets 1 2001:67c:370:176::2 15.195 ms 8.408 ms 5.088 ms 2 2001:13b0:1:4::1 2.290 ms 2.021 ms 7.230 ms 3 xe-0-0-5.lax22.ip6.gtt.net 153.070 ms 171.330 ms 149.873 ms 4 xe-0-0-5.lax22.ip6.gtt.net 148.472 ms 147.259 ms 147.942 ms 5 et-7-3-0.was10.ip6.gtt.net 181.282 ms 182.144 ms 186.616 ms 6 as16668.ge-0-0-37-198.ar1.iad1.us.as4436.gtt.net 183.936 ms 190.716 ms 180.388 ms 7 2610:178:ffff:7::4 179.363 ms 179.903 ms 180.802 ms 8 2610:178:fff:fffc::2 190.304 ms 192.130 ms 201.137 ms dhcp-b376:~ e158182$ traceroute6 ripe.net traceroute6 to ripe.net (2001:67c:2e8:22::c100:68b) from 2001:67c:370:176:1802:fd28:21ad:f998, 64 hops max, 12 byte packets 1 2001:67c:370:176::2 1.203 ms 1.357 ms 1.331 ms 2 2001:13b0:1:4::1 2.128 ms 1.850 ms 1.987 ms 3 xe-0-0-5.lax22.ip6.gtt.net 148.327 ms 190.806 ms 148.772 ms 4 xe-0-0-5.lax22.ip6.gtt.net 147.872 ms 145.540 ms 146.473 ms 5 et-9-1-0.ams20.ip6.gtt.net 310.816 ms 247.944 ms 247.662 ms 6 surfnet-gw.ip6.gtt.net 263.186 ms 259.874 ms 276.546 ms 7 gw.ipv6.amsix.nikrtr.ripe.net 261.234 ms 260.290 ms 278.850 ms 8 gw.ipv6.amsix.nikrtr.ripe.net 267.455 ms !P 270.676 ms !P 345.798 ms !P dhcp-b376:~ e158182$ traceroute6 www.facebook.com traceroute6 to star-mini.c10r.facebook.com (2a03:2880:1010:3f20:face:b00c::25de) from 2001:67c:370:176:1802:fd28:21ad:f998, 64 hops max, 12 byte packets 1 2001:67c:370:176::2 3.706 ms 1.582 ms 1.662 ms 2 2001:13b0:1:4::1 3.134 ms 1.837 ms 2.439 ms 3 2001:450:2001:1000::670:1708:1142 144.942 ms 144.868 ms 145.338 ms 4 2001:1900:4:3::79 147.691 ms 145.984 ms 146.841 ms 5 vl-70.edge6.losangeles1.level3.net 149.108 ms vl-80.edge6.losangeles1.level3.net 145.773 ms vl-70.edge6.losangeles1.level3.net 146.851 ms 6 vl-4060.edge6.losangeles1.level3.net 270.016 ms 237.919 ms 221.735 ms 7 vl-4082.edge2.dallas1.level3.net 169.151 ms 168.206 ms vl-4083.edge2.dallas1.level3.net 168.563 ms 8 facebook-in.edge2.dallas1.level3.net 169.764 ms 167.867 ms 167.593 ms 9 be3.bb01.dfw1.tfbnw.net 189.040 ms be3.bb02.dfw1.tfbnw.net 189.759 ms be3.bb01.dfw1.tfbnw.net 202.147 ms 10 be19.bb02.ord1.tfbnw.net 189.504 ms be21.bb01.ord1.tfbnw.net 188.735 ms 189.485 ms 11 be7.bb02.atn1.tfbnw.net 197.267 ms ae7.bb03.atn1.tfbnw.net 189.977 ms be7.bb02.atn1.tfbnw.net 197.125 ms 12 ae2.dr06.atn1.tfbnw.net 197.923 ms ae1.dr05.atn1.tfbnw.net 188.921 ms ae2.dr06.atn1.tfbnw.net 188.747 ms 13 po21.fa01.atn2.tfbnw.net 189.066 ms po12.fa02.atn1.tfbnw.net 189.904 ms po509.csw01b.ash4.tfbnw.net 188.497 ms Thanks, Wes George Anything below this line has been added by my company¹s mail server, I have no control over it. ----------- ________________________________ This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout. |
Note: See TracQuery for help on using queries.